Collection
Systems and strategic leverage: feedback, flow, modularity, robust options, and information value
Develop systems-level judgment by tracing feedback and delays, measuring flow and queues, localizing change through modularity, designing robust strategies under deep uncertainty, and choosing higher-leverage interventions and information.
50 elements · Explore in any order.
6 checklists · 10 heuristics · 6 principles · 23 protocols · 5 questions
50 elements
Define the system boundary before optimizing
Optimization starts by deciding what is inside the model.
Read the idea PrincipleSeparate stock from flow
Stocks remember history; flows change stocks.
Read the idea ProtocolMap the reinforcing loop behind growth
Reinforcing feedback can make change compound.
Read the idea ProtocolMap the balancing loop behind a limit
Limits often emerge from balancing feedback.
Read the idea ChecklistPut delays on the map
Delays can make sensible control actions oscillate.
Read the idea QuestionAsk how the system will respond to the intervention
Interventions change incentives and behavior as well as the target variable.
Read the idea ProtocolTrace side effects through another loop
Side effects often travel through a different feedback path.
Read the idea ChecklistLook for policy resistance before scaling
Scale changes the environment that produced the pilot result.
Read the idea ProtocolUse a behavior-over-time view before root-cause stories
Patterns over time constrain causal stories.
Read the idea ProtocolTurn the causal map into a testable model question
A map earns value by making discriminating predictions or measurements possible.
Read the idea ChecklistMeasure arrival rate, work in progress, and cycle time together
Flow variables constrain one another.
Read the idea HeuristicTreat growing WIP as a delay signal
Accumulating work usually means elapsed time will not stay neutral.
Read the idea ProtocolLimit parallel starts when completion is the goal
Reducing starts can expose capacity and shorten queues.
Read the idea QuestionFind the bottleneck from waiting, not busyness
A constraint is revealed by system effect, not self-reported effort.
Read the idea ProtocolProtect bottleneck capacity from avoidable work
Constraint time should be reserved for work only the constraint can do.
Read the idea HeuristicMove quality checks upstream of the bottleneck
Do not spend the constraint on defects that cheaper checks can catch.
Read the idea ChecklistSeparate touch time from queue time
Elapsed time contains different levers.
Read the idea ProtocolReduce batch size when feedback delay dominates
Smaller batches can trade setup overhead for earlier information.
Read the idea HeuristicBuffer variability where it is cheaper to absorb
Variability plus high utilization can create disproportionate waiting.
Read the idea ProtocolRecheck the bottleneck after improvement
Removing one constraint usually reveals another.
Read the idea PrincipleDecompose around likely change, not the org chart
Useful boundaries localize likely change.
Read the idea ProtocolHide volatile decisions behind stable interfaces
Information hiding protects the rest of the system from volatility.
Read the idea HeuristicMinimize the number of teams that must change together
Cross-boundary coordination is a cost of architecture.
Read the idea PrincipleMake dependencies directional where possible
Mutual dependency amplifies coordination.
Read the idea