Intent stays legible
Strategy flows through Themes, Initiatives, and an Outcome Portfolio so every team knows the change it owns.
Overview
Outcome Driven Operating Model (ODOM)
ODOM is an AI-native, evidence-driven operating model designed to preserve learning, attribution, and decision quality as AI accelerates delivery. It replaces time-based control with outcome-based control, giving teams and leaders a simple loop for turning intent into meaningful change and understanding how the world responds. The loop keeps one Outcome in focus at a time, with progress measured by the rate at which Signals converge and uncertainty decreases.
Evidence packages decisions
Signals, Evidence Packages, and Assessment produce traceable decisions with Completed, Retired, or Adjusted end states. Teams own truth. Leaders own direction. The operating model protects the boundary.
AI accelerates the loop
AI accelerates clarity when the system is clear. AI accelerates confusion when the system is unclear. Responsible human judgment remains essential for appropriateness.
Context
Why organizations should move to ODOM
AI collapsed the cost of output but not the cost of knowing whether the output mattered. As AI accelerates delivery, attribution—the ability to connect actions to observed outcomes with enough confidence to support learning—becomes the scarce resource, not execution capacity. Forecast-heavy frameworks still assume scarcity of data and long feedback loops. ODOM assumes the opposite: signals are abundant, uncertainty deserves respect, and evidence should determine pace.
- Leaders need a portfolio view of Outcomes, not a backlog of features.
- Teams need Discovery to sharpen intent before committing to Build.
- Customers expect safe, reversible change that proves value with Signals.
- This is an operating model problem, not a team problem.
The shift
We define Outcomes, Build Solutions, and pause for Assessment when Signals are ready. Velocity theater is replaced by rate-based thinking where progress is the reduction of uncertainty.
Evidence > opinion.
Signal convergence > forecasts.
Learning > ceremony.
Mindset
Principles that steer behavior
Outcomes > outputs
Judge work by behavioral change, not ticket volume. Funding, flow, and storytelling all start with Outcomes.
Evidence over opinion
Signals reveal whether reality is converging or drifting. Assessment interprets what Signals mean.
Rate over forecasts
Progress is the reduction of uncertainty, not the completion of tasks. One Outcome in focus, the ODOM loop, and Pulse for daily alignment.
Pull, don’t push
Teams pull the next Outcome from the pipeline when Ready and capacity exists. Work is never forced into queues.
Transparency without theater
Assessments, Evidence Packages, and Outcome Shows replace status reports and green slides.
AI as an accelerator
AI accelerates clarity when the system is clear. AI accelerates confusion when the system is unclear. Humans remain responsible.
Structure
The canonical ODOM stack
Strategy, Themes & Initiatives
Strategy defines where the organization intends to go. Themes describe major areas of focus. Initiatives refine Themes into concrete directions.
Outcome Pipeline
A living list of Outcomes moving from idea to learning: Draft, In Discovery, Ready, In Progress, Under Evaluation, Completed/Retired/Adjusted.
Discovery
The period where an Outcome becomes Ready. Discovery runs alongside Build of the current Outcome, sharpening behavioral intent, refining Hypothesis, shaping the Evidence Package, and identifying the dominant condition. By the time an Outcome reaches Kickoff, it is fully formed.
The ODOM Loop
Four stages adapted from Deming’s PDCA: Kickoff (commit to Outcome), Build (create the Solution), Assessment (interpret Signals and decide end state), Reflection (improve how the team works). Assessment separates truth from direction—teams state what evidence supports; leaders decide what to do next.
Evidence Package
Signals that reveal behavior change, qualitative traces, guardrails for fairness and risk, and expected patterns. Must include disconfirming signals and explicit stop criteria—otherwise outcome control becomes narrative control. Defined during Discovery.
Outcome End States
Completed (Signals show meaningful change), Retired (pursuing further is not valuable), or Adjusted (directionally correct but needs reframing).
Teams build one Outcome at a time. When Build completes, the Outcome enters Assessment, where it sits Under Evaluation while Signals mature. Multiple Outcomes may be Under Evaluation while the next Ready Outcome is in Build. The team interprets Signals and decides the end state when evidence is sufficient. Outcome Shows narrate progress on their own cadence.
Cadence
How Outcome cycles move
1. Kickoff
The team commits to an Outcome that Discovery has shaped to be Ready. Confirm the Hypothesis and Evidence Package (including disconfirming signals and stop criteria). The Solution itself is figured out during Build.
2. Build
Create and deliver the Solution. Normal tasks implement the work. Pulse provides daily alignment. Signals are not interpreted yet.
3. Assessment
Interpret the Signals in the Evidence Package. Consider context, risk, quality, and fairness. Decide end state: Completed, Retired, or Adjusted. Assessment is triggered by evidence sufficiency, not the calendar.
4. Reflection
Examine how the work felt, what supported flow, what created friction, and what practices to adjust for the next cycle.
The four phases above are not separate meetings. They are stages an Outcome moves through inside the ODOM Loop. The only standing meetings are Discovery (upstream and continuous), Pulse, and the Outcome Show. A single Pulse may include a Kickoff for an Outcome that is ready, a sync on Build activity, an Assessment of an Outcome whose Signals have matured, and a brief Reflection on one that just concluded.
Cadenced events
Pulse (Daily Rhythm)
Short daily alignment meeting focused on flow, risks, and shared understanding. When Signals are ready, Assessment can occur in the same meeting.
Outcome Show
Cadenced event where teams present Outcomes, Signals, decisions, and learning to stakeholders and leaders.
Progress is measured by the rate at which Signals converge and uncertainty decreases, not by completed tasks. AI accelerates understanding, but Assessment and Reflection require responsible interpretation.
Signals
Evidence and signals built in
Signals
Describe the reasonable range of how the world may respond. Signals reveal whether reality is converging toward or drifting from intended behavioral change.
Guardrails
Constraints for fairness, quality, and risk. Expected positive patterns and potential negative patterns defined in the Evidence Package.
Evidence Packages
Signals, qualitative traces, guardrails, and context. Forms the knowledge environment AI depends on. When intent is clear, AI amplifies clarity.
Instrumentation and Signal collection are prepared during Discovery. Assessment interprets what Signals reveal. Evidence Packages must include disconfirming signals and stop criteria so that Assessment remains honest. AI extends awareness but does not decide Outcomes or end states.
Journey
Practical adoption path
-
Frame work as Outcomes
Keep existing ceremonies but express goals, reviews, and roadmaps in Outcome language with Hypotheses and Signals.
-
Introduce Discovery
Run Discovery before committing to Build. Shape Evidence Packages and identify the dominant condition that influences learning.
-
Run full ODOM loops
One Outcome in focus. Kickoff, Build, Assessment, Reflection. Decide end states: Completed, Retired, or Adjusted.
-
Pipeline & scaling
Strategy, staffing, and budgets revolve around the Outcome Pipeline and its Evidence. Alignment emerges from Outcomes and Signals, not ceremonies.
Deep dives
Bring ODOM to your org
Executive Briefing Deck
Narrative for sponsors on why strategy flows through Themes, the Outcome Pipeline, Discovery, and evidence-led decisions.
ODOM Team Playbook
Hands-on practices for the ODOM loop, Evidence Packages, Assessment, AI usage, and daily working agreements.