ODUI Framework Manifesto

ODUI (Outcome-Driven Urgent/Important prioritisation framework) is a decision operating system for modern work.

ODUI exists to answer one question, calmly and consistently:
What matters now, what matters next, and what can safely wait?
Outcome-driven Urgent vs Important Buckets B1–B4 Visible trade-offs Protected focus

What is the ODUI Framework?

The ODUI Framework is an outcome-driven urgent/important system for modern work. It helps teams decide what matters now, what matters next, and what can safely wait.

ODUI gives teams a shared language for urgency, importance, and outcomes. It makes it clear what deserves attention now, what builds value next, what keeps relationships stable, and what should stay as an idea until it is ready.

ODUI does this by:

  • using Urgent vs Important as the first filter,
  • prioritising by outcomes (measurable change, not activity),
  • keeping work in four clear buckets: B1, B2, B3, B4,
  • making trade-offs visible so focus is protected.

The ODUI principles

Outcomes over outputs Work matters when it changes something real.
Urgency is consequence, not emotion We use Critical / Rising / Stable — not panic and pressure.
Buckets create clarity We classify before we debate. The bucket decides the behaviour.
Trade-offs are part of truth If we add something, something else moves or stops.
B2 is protected Important work must not be repeatedly eaten by loud work.
Visibility is for alignment, not surveillance Dashboards are mirrors for learning, not weapons for control.
Rhythm beats heroics ODUI works because it repeats: intake, review, rebalance.
Progressive clarity We don’t over-plan unclear work. Detail grows when value is proven.

Delivery discipline by bucket

Once the bucket decision is made, the bucket decides the behaviour.

B1 Keeps You Alive (urgent + important)
Run: Detect → Assess → Act → Communicate → Learn
  • Communication must be factual: impact → action → ETA, using one source of truth.
  • Afterwards, convert lessons into B2 prevention work (B1 → B2 conversion).
Explore the B1 Playbook
B2 Makes You Great (important, not urgent)
  • Prioritise B2 by which one moves outcomes the most.
  • Protect B2 time so it isn’t constantly stolen by B1/B3 (trade-offs must be visible).
Explore the B2 Playbook
B3 Keeps Others Quiet (urgent, not important)
  • Handle B3 as a limited contract lane: predictable, visible, proportionate.
  • Use the structured expectation conversation:
acknowledge → clarify → trade-off → commit/reframe → close visibly
  • Convert repeating B3 themes into B2 improvements (automation, templates, education).
Explore the B3 Playbook
B4 Keeps Ideas Breathing (not urgent, not important yet)
  • Use an idea lifecycle and review ritual.
  • Every review ends with one decision: promote to B2 / keep in B4 / archive, with a short visible note.
Explore the B4 Playbook

What “ODUI-compliant” means

You may call your work “ODUI-compliant” only if all of these are true:

  • Every request has a bucket decision (B1–B4), made fast and recorded.
  • You use the same two filters: Urgency + Importance (official meanings).
  • Urgency is labelled Critical / Rising / Stable using consequences.
  • Important work is expressed as an outcome (what will change and how we’ll notice).
  • You run regular intake and bucket reviews (a visible operating rhythm).
  • You protect capacity by bucket, especially B2, and you keep B3 bounded.
  • You keep a living B4: ideas are reviewed and get a decision (promote / keep / archive).
  • When priorities change, you show the trade-off (what moved out).
  • Dashboards follow the ODUI intent: clarity and learning, not tracking individuals.

Minimum viable compliance (if you start small): Daily quick intake + weekly bucket review + visible trade-offs.

What is not ODUI

ODUI is not any of the following:

  • One-time adoption. ODUI is not a workshop badge; it’s a repeating practice.
  • “Everything is B1.” Permanent emergency mode with no prevention.
  • Bucket labels without behaviour. Calling things B2 while never protecting time for B2.
  • Urgency by volume or hierarchy. “Because I said so” is not urgency.
  • Busywork worship. Measuring outputs while ignoring outcomes.
  • Hidden trade-offs. Adding work without removing or moving something else.
  • Dashboard surveillance. Using visibility to punish people instead of improving the system.
  • B4 as a dumping ground. Ideas captured forever with no review or decisions.
  • Hero culture. Relying on burnout and last-minute saves instead of rhythm and learning.