Diagram of a Classically Broken Change Engine

Using broken Functional Model to illustrate weak conception, date-driven creation, and deferred, serialized characterization

The reason why this picture might seem familiar is that the Pressures which form this mess are endemic to traditionally managed companies:
The importance of rushing to coding (aka. Development) is elevated over: discovery of product/market fit; and, discovery of quality and user experience (aka. Research)
Implementation management is incorrectly being applied to creative activities as if pressurizing commitments by setting dates and rushing to market will result somehow in speeding superior product/market fit or discovery of epic user experience
Discovery activities are not being facilitated by the platform or culture; but in R&D, R is actually more important than D:
Epic ≈ Learning
Vs.
Deferred
Discovery
. Diagram of a Classically Broken Change Engine. ©2018 iiSM.ORG, All Rights Reserved.

Click slide to see in context of slide deck

Click to enter the site

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.