This is a Request For Comments about how to structure doctrine in terms of microdoctrine (a pattern language for implementing and learning doctrine)
There is little point of doctrine in the organization if no one is willing to challenge it.
Consider these first:
Spend Control Introduction
Spend Control does not control the budgets. The purpose of Spend Control is to challenge what we’re doing. Spend Control goes beyond asking about users, needs, and measurement.
Spend Control does not control the budgets. Few months after Spend Control Introduction, the first thing Spend Control starts to ask for is a map. The point of the map is to challenge beyond users and needs. Spend Control now challenges using maps and doctrine.
Remove Bias And Duplication
Map and challenge flows of capital. The capital itself can be physical, financial, social, risk, information, etc.
Spend Control builds the view of the landscape you are competing in. All the maps are connected and are part of the wider landscape. You are starting to see the landscape and your part of it.
STOP READING, TAKE ACTION
Spend Control Intelligence
Reproduced and adapted from writings by Simon Wardley under Creative Commons Attribution-ShareAlike 4.0 International License.