The management problem
Activity is visible. Outcomes are what matter.
Many management systems are effective at describing work: plans, milestones, status, throughput, and utilization. Those signals can be useful, but completed work is not the same as value created.
ODM begins with a different management question: What meaningful outcome are we trying to create, and what are we learning about the path to it?
Historical context
From execution to delivery to learning.
Optimize execution
When requirements were knowable and change was expensive, planning and predictable execution created advantage.
Optimize delivery
As software accelerated change, shorter feedback cycles and more frequent delivery created advantage.
Optimize learning
As experimentation and creation accelerate, organizations increasingly need to discover what works through evidence.
ODM does not erase execution or delivery. ODM places both inside a learning system oriented toward measurable outcomes.
The operating model
Five components. One continuous loop.
Outcomes
Define what success looks like.
Bets
Make beliefs about the path explicit and testable.
Evidence
Use reality to validate or invalidate those beliefs.
Learning Loops
Improve understanding through experiment, evidence, decision, and adaptation.
Decisions
Convert learning into action.
The architecture
Philosophy becomes operating behavior.
What changes
A different basis for management.
Work completed
Value created
Defend the original path
Test and adapt the path
Describe status
Act on evidence