This is a Request For Comments about how to structure doctrine in terms of microdoctrine (a pattern language for implementing and learning doctrine)
In business, the industrialized domain encourages coherence, coordination, efficiency, and stability. Yet, the discovery of new capabilities in the uncharted domain requires experimentation. Any structure, a company, or a team, needs to manage both of these polar opposites. Components are also evolving between these extremes. These transitional components have a different set of characteristics. They need a third mechanism of management.
Use Lean and similar methods to reduce waste, improve measurement, and learn.
As a component evolves and we understand it more, then the focus changes. Sometime during the stage of custom built we start to think about creating a product. The focus becomes reducing waste, improving measurements, learning, and creating the first product. We add artifacts to the method and the activity is more permanent. We are no longer exploring the uncharted space. We start concentrating on what we found. In this part of the map, consider lean approaches, using product, using rentals.
In the below example we would use off the shelf products or rentals for Print, Web Site, CRM, Platform, Compute, and Data Center. We would focus on lean methodologies.
STOP READING, TAKE ACTION
Reproduced and adapted from writings by Simon Wardley under Creative Commons Attribution-ShareAlike 4.0 International License.