Skip to content

Chapter 22 — Becoming an ODUI Organisation - The First 90 Days

The first 90 days decide whether ODUI becomes “how we work here” or another failed initiative. This chapter is your practical guide to that transition.

You will see three things at once:

  • emotional reactions (fear, doubt, resistance)

  • structural friction (capacity, hidden work, B3 pressure)

  • signs of progress (calmer weeks, visible B2, moving KPIs)

The goal is not perfection. The goal is to cross the first 90 days with momentum, discipline, and belief.

22.1 The Emotional Journey of Change

Introducing ODUI is not just a process change. It is an emotional change.

ODUI makes work visible, exposes hidden problems, and forces decisions to be explicit. Even if the model is simple, the shift can feel uncomfortable.

People don’t resist ODUI. They resist what ODUI reveals.

Understanding these reactions helps leaders introduce ODUI with empathy and helps teams recognise that their discomfort is normal and temporary.

1. Leaders Fear Losing Informal Control

ODUI moves leaders from:

  • pushing work through informal influence

  • bypassing structure with “quick favours”

  • relying on heroics and escalation

…to a model where:

  • priorities and capacity are transparent

  • teams can challenge misaligned requests

  • decisions are traceable and shared

How it feels:

  • “Will I still be able to move things quickly?”

  • “Will teams say no to me?”

  • “Am I losing influence?”

In reality, leaders lose informal control but gain strategic control. That feels like loss before it feels like strength.

2. Teams Fear Real Accountability

Most teams are used to reactive work:

  • priorities change weekly

  • outcomes are vague

  • success is justified after the fact

ODUI flips this:

  • outcomes and KPIs are explicit

  • bucket mix is visible

  • excuses shrink

How it feels:

  • “We can’t hide anymore.”

  • “We’ll be judged on impact, not effort.”

  • “What if our work doesn’t move the KPI?”

The fear is natural. ODUI replaces ambiguity with ownership.

3. Stakeholders Fear Losing Influence

Before ODUI, many stakeholders win through persistence:

  • direct messages and side channels

  • escalation and politics

  • “urgent” pressure and noise

ODUI introduces structured B3 capacity and shared rules.

How it feels:

  • “Will I still be heard?”

  • “Will my requests be ignored?”

  • “Will teams say no more often?”

Stakeholders lose informal power but gain fair, visible, explainable influence.

4. Engineers Fear Unrealistic Bucket Mixes

Engineers see the cost of years of decisions:

  • technical debt and fragile systems

  • recurring incidents

  • missing automation

A sudden push to “more B2” can feel disconnected from reality.

How it feels:

  • “If we force B2, B1 will explode.”

  • “We’ll fail and get blamed.”

ODUI does not magically fix technical issues. It reveals them so they can finally be addressed deliberately.

5. Intake Leads and Flow Leads Fear Conflict and Exposure

Intake Leads (Outcome Owners) sit between leadership, stakeholders, and engineering. Flow Leads (Delivery Owners) often carry hidden operational load.

ODUI requires them to:

  • negotiate, not just organise

  • surface hidden work

  • say “no” or “not now”

How it feels:

  • “Stakeholders will get angry.”

  • “If we show the real workload, it will look like we’re failing.”

In reality, visibility unlocks support — but it feels risky at first.

6. Everyone Fears Transparency

ODUI exposes:

  • true capacity

  • interruptions and delays

  • ownership gaps

  • duplicated work

  • political pressure

How it feels:

  • “People will see the mess.”

For individuals this can feel personal. For the organisation, it is simply the truth. And only visible truth can be improved.

7. These Reactions Are Normal — and Temporary

Within a few weeks of consistent ODUI practice:

  • transparency reduces anxiety

  • teams feel more in control

  • stakeholders understand the rhythm

  • the organisation calms down

Discomfort turns into relief. The key is to expect these emotions and move through them, not around them.

What leaders must do in this phase:

  • normalise emotions (“this is expected”)

  • remove blame for early mistakes

  • protect teams from political shortcuts

  • keep the focus on learning, not perfection

What teams must remember:

  • discomfort is temporary

  • mistakes are training data

  • conflict is alignment work

  • rhythm creates safety

22.2 The Common Early Mistakes

The first 90 days reveal habits that conflict with ODUI. These mistakes are predictable, normal, and fixable.

Chapter 19 covered ODUI pitfalls in general. Here we focus on early mistakes in the first 90 days, when emotions are high and the system is still fragile.

1. Misclassifying Work (Especially B1, B2, and B3)

When ODUI is new, teams often:

  • put too much into B1, confusing urgency with importance

  • inflate B2, because everything sounds “strategic”

  • avoid B3, to escape conflict with stakeholders

  • starve B4, because “we don’t have time for ideas”

Why it happens: old reactive habits, unclear outcomes, and fear of saying “this is not urgent”.

What fixes it:

  • short weekly bucket review sessions

  • joint Intake Lead + Flow Lead scoring

  • leadership reinforcing that B3 and B4 are valid homes

  • rewarding correct classification, not speed

2. Treating ODUI as a Process, Not a System

Some organisations reduce ODUI to:

  • “fill intake form, assign bucket, move on”

ODUI is not admin. It is a decision and alignment system.

It only works when:

  • outcomes are clear

  • buckets are applied consistently

  • capacity limits are respected

  • leaders participate, not just delegate

3. Trying to Perfect the Buckets Too Early

Teams obsess:

  • “Is this B1 or B3?”

  • “Is this 60% or 70% B2?”

This slows everything down.

ODUI is about useful clarity, not mathematical precision.

Good enough early questions:

  • “Is this mostly keeping us alive (B1), making us great (B2), keeping others quiet (B3), or keeping ideas breathing (B4)?”

4. Allowing B3 to Flood the System

In the first month, stakeholders test boundaries:

  • “Can you just add this quickly?”

  • “This is really important for my department.”

If teams say yes to everything, ODUI collapses back into firefighting.

What fixes it: clear B3 capacity, simple negotiation scripts, and visible leadership backing when teams say “not now”.

5. Leaders Forgetting That Capacity Is Limited

Before ODUI, lack of visibility allows leaders to assume infinite capacity.

During adoption, they may still:

  • request “one more thing”

  • expect old timelines

  • ignore B2 protection

What fixes it: weekly capacity snapshots and explicit trade-offs (“if we add this B3, this B2 slips”).

6. Overloading B2 (Trying to Change the Whole World at Once)

New excitement often leads to:

  • too many B2 initiatives

  • too many KPIs and experiments

Execution scatters.

What fixes it:

  • 2–3 active B2 initiatives per team

  • simple sequencing of improvements

  • cycle-by-cycle impact reviews

7. Ignoring B4 (“No Time for Ideas”)

Chaotic cultures neglect B4:

  • ideas stay in chat, never captured

  • people fear that suggesting ideas creates extra work

What fixes it:

  • small, explicit B4 capacity

  • simple B4 backlog

  • monthly B4 review to select a few ideas, park the rest

8. Letting Rhythm Slip

The weekly and monthly ODUI rhythm is the spine of alignment. Under pressure, teams skip reviews “just this week”.

Every skipped review quietly re-opens the door to chaos.

What fixes it:

  • leadership protecting review time

  • keeping rituals short but non-negotiable

  • automating simple dashboards

9. Expecting ODUI to Work Instantly

Common but unrealistic expectations:

  • perfect buckets in week 1

  • immediate KPI movement

  • silent, compliant stakeholders

ODUI is a 90-day adoption, not a 9-day fix.

10. Blaming the Framework Instead of the Habit

Under friction, teams say:

  • “ODUI isn’t working.”

  • “This slows us down.”

But the real issues are usually:

  • inconsistent rhythm

  • misaligned outcomes

  • overloaded teams

  • unbounded B3

  • weak leadership reinforcement

11. The Real Message

Early mistakes are not a bug; they are how the organisation learns.

The first 90 days are not about flawless execution. They are about building shared language, shared discipline, and shared expectations.

If you keep the rhythm and keep correcting, ODUI becomes easier every week.

22.3 The First 90 Days — A Practical Rollout Plan

Rolling out ODUI is a real organisational transition. The first 90 days determine whether ODUI becomes your operating system or a forgotten experiment.

Chapter 20 described pilots and rollout. This section gives you a practical timeline.

ODUI doesn’t need perfection — it needs momentum.

Phase 1 — Orientation & Stabilisation (Weeks 1–3)

Goal: introduce ODUI without overwhelming people and stabilise enough to prevent chaos.

Week 1 — Kickoff & Language Alignment

Objectives:

  • explain why ODUI exists

  • align on language (B1–B4, outcomes, capacity, rhythm)

  • reduce fear by emphasising learning over perfection

Key actions:

  • run a 60–90 minute kickoff workshop

  • explain buckets with concrete examples

  • show the desired bucket mix as a direction, not a target

  • introduce intake, weekly rhythm, and monthly reviews

Week 2 — Build Intake and the B1 Playbook

Objectives:

  • create a simple intake for all new work

  • prevent B1 from derailing teams immediately

Key actions:

  • implement the ODUI intake template (in your existing tools)

  • define the B1 playbook (who responds, how, when)

  • run a joint Intake Lead + Flow Lead scoring session on recent work items

Week 3 — First Real Bucket Classification

Objectives:

  • classify all incoming work using B1–B4

  • expose hidden work and overload

Key actions:

  • classify all work for the week in real time

  • review tricky cases together

  • create the first simple “bucket distribution” chart

Expected reaction: anxiety (“we are overloaded”) followed by relief (“at least we can see it”).

Phase 2 — Capacity & Outcome Alignment (Weeks 4–6)

Now ODUI moves from classification into real strategic alignment.

Week 4 — Establish the First Capacity Baseline

Objectives:

  • understand your real B1/B2/B3/B4 capacity

  • compare reality with the desired mix

Key actions:

  • measure last 2–3 weeks of bucket distribution

  • identify bottlenecks (high B1, uncontrolled B3, no space for B2/B4)

  • share a simple capacity view with leaders and teams

Week 5 — Define Outcomes (If Missing)

Objectives:

  • connect ODUI to strategy

  • clarify what B2 should achieve

Key actions:

  • define 1–3 outcomes per team

  • attach KPIs and baselines

  • draft 3–6 month improvement targets

Objectives:

  • build the first meaningful B2 engine

Key actions:

  • select 2–3 B2 initiatives per team

  • connect each to a KPI and outcome

  • sequence B2 work across 6–8 week cycles

  • check that B2 fits alongside B1 and B3 capacity

Phase 3 — Rhythm & Accountability (Weeks 7–10)

Here ODUI becomes a habit.

Week 7 — First Clean Weekly Rhythm

Objectives:

  • run a full ODUI week as designed

Key actions:

  • Monday: intake + classification

  • Mid-week: quick B1/B3 health check

  • Friday: B2 progress and KPI review

  • send a short written summary to leadership

Week 8 — Strengthen B3 Negotiation

Objectives:

  • help teams push back professionally

Key actions:

  • train Intake Leads / Flow Leads on stakeholder negotiation

  • provide simple scripts for common B3 conversations

  • clarify B3 capacity limits and how trade-offs are made

Week 9 — Outcome Check & Refinement

Objectives:

  • check whether outcomes are still correct

  • refine KPIs and targets based on learning

Key actions:

  • review each outcome and KPI with current data

  • adjust outcomes if strategy has shifted

Week 10 — First Signs of Stability

Objectives:

  • achieve a relatively stable bucket mix for several weeks

Key actions:

  • re-measure capacity distribution

  • validate that B3 is under control

  • celebrate first visible wins (predictable B1, protected B2)

Phase 4 — Consolidation & Acceleration (Weeks 11–12)

Now ODUI becomes your default operating model.

Week 11 — Prepare the First Quarterly Adjustment Loop

Objectives:

  • close the loop between strategy, outcomes, and work

Key actions:

  • review KPI movement and stalled B2 initiatives

  • identify promising B4 ideas

  • prepare a short briefing for leadership

Week 12 — Run the First ODUI Quarterly Cycle

Objectives:

  • run a full strategy → outcomes → work → learning → adjustment loop

Key actions:

  • leaders review strategic signals

  • teams present outcome progress

  • reset B2 priorities and bucket mix for the next 6–8 weeks

By Day 90 — What Success Looks Like

You will see:

  • people speaking in buckets naturally

  • intake as the default entry point for work

  • B1 predictable and under control

  • B2 with visible, protected capacity

  • B3 boundaries respected

  • weekly and monthly rhythms consistent

  • KPIs either moving, or their stagnation openly discussed

At this point, ODUI is no longer a pilot. It is your operating system.

22.4 Leadership Behaviours That Make or Break ODUI

ODUI is simple. Leading an ODUI organisation is not.

Tools and templates help, but leadership behaviour decides everything. If leaders reinforce old habits, ODUI collapses. If leaders model new ones, ODUI sticks.

1. Model Calm, Not Urgency

If leaders:

  • bypass intake

  • demand same-day responses

  • treat their requests as special

…ODUI dies quickly. Teams learn: “We follow ODUI unless someone senior wants something.”

Great ODUI leaders:

  • route their own requests through intake

  • use the same scoring as everyone else

  • respect bucket decisions once made

  • ask, “Does this fit our capacity?” before pushing

2. Protect B2 — Even When It Hurts

If B2 dies, strategy dies.

Protecting B2 means:

  • saying no more often than yes

  • delaying stakeholder requests

  • absorbing external noise instead of passing it downstream

  • preventing roadmap thrashing

This is uncomfortable leadership work — and non-negotiable.

3. Enforce Intake

Most organisations live on:

  • Slack messages

  • hallway conversations

  • email escalations

ODUI replaces this with a single intake.

Great leaders say:

  • “Please submit this through intake.”

  • “If it’s not in intake, it won’t be prioritised.”

This gives teams cultural safety. The rules apply to everyone.

4. Reward the Right Signals

If you praise only:

  • speed

  • heroics

  • firefighting

…you will always get chaos.

In an ODUI organisation, leaders also praise:

  • rejecting misfit B3 work

  • preventing B1, not just fixing it

  • calm cycles, not frantic ones

  • clean execution, not rushed delivery

People follow what leaders celebrate.

5. Communicate Clearly During Shifts

Strategic shifts are normal. Poorly communicated shifts are destructive.

Leaders must:

  • explain why the shift is happening

  • show how it affects outcomes and buckets

  • avoid creating panic (“drop everything now”)

Clarity prevents ODUI from being blamed for strategy changes.

6. Show Up to Reviews

If leaders regularly skip:

  • weekly bucket reviews

  • monthly KPI sessions

  • quarterly adjustment loops

…teams stop taking ODUI seriously.

Presence signals commitment. It also:

  • legitimises trade-offs

  • provides psychological safety

  • gives leaders real visibility, not filtered reports

7. Ask Better Questions

Great ODUI leaders shift from giving answers to asking clarifying questions:

  • “Which bucket is this?”

  • “What outcome does it serve?”

  • “What KPI should move?”

  • “What are we saying no to if we do this?”

Questions reinforce ODUI thinking everywhere.

8. Tolerate Short-Term Discomfort

ODUI exposes overload, poor prioritisation, and unreasonable expectations. This is uncomfortable.

Weak leaders hide the discomfort. Strong leaders say:

  • “Yes, this is heavy. Now we know what we’re dealing with.”

You cannot fix what you refuse to see.

9. Make Capacity Decisions Explicit

Instead of implicit assumptions, leaders make public statements like:

  • “We are capping B3 at 15% this cycle.”

  • “We are temporarily reducing B2 because B1 is too high.”

  • “We will increase B4 space for innovation next quarter.”

Explicit decisions reduce politics and confusion.

10. Stay Consistent for at Least 12 Weeks

ODUI breaks when leaders:

  • get impatient

  • revert to side-door requests

  • relax bucket boundaries

  • allow “one-time exceptions” that become normal

Consistency is the hardest and most important behaviour.

If leaders stay disciplined for the first 90 days, ODUI sticks. If they don’t, it dissolves.

22.5 How Teams Must Learn

Teams do not learn ODUI from slides. They learn it by doing the work differently, week after week.

This section summarises the learning curve.

1. Confidence Comes From Repetition

Confidence grows every time teams:

  • classify work together

  • negotiate B3

  • review buckets at week’s end

  • adjust capacity based on reality

Leaders should repeat one message:

“You are not expected to be perfect. You are expected to be consistent.”

2. Fix Mis-Bucketed Work Without Blame

The first 4–6 weeks will include bucket mistakes. This is not failure; it is training data.

Teams should:

  • review a small sample of items weekly

  • ask “why did we classify it this way?”

  • refine their rules of thumb

By weeks 6–8, classification becomes much more stable.

3. Stop Uncontrolled B3 Inflow

Stakeholders will test the system. Teams must learn to negotiate, not surrender.

Key behaviours:

  • send all requests through intake

  • ask for outcomes, not tasks

  • score urgency and importance with stakeholders

  • explain B3 capacity limits

Useful phrases:

  • “We can do this, but here is what we’d have to drop.”

  • “This belongs in the next cycle’s negotiation.”

4. Manage Initial B1 Overload

Most teams start with too much B1. ODUI just makes it visible.

Teams must:

  • log every B1 item

  • look for patterns weekly

  • link recurring issues to small B2 prevention work

Leadership must:

  • temporarily reduce B2 expectations

  • protect teams from extra B3 while B1 stabilises

Within 4–6 weeks, B1 becomes predictable. Within 8–10, it drops.

5. The Team Learning Stages

Teams usually move through five stages:

  1. Confusion — “What bucket is this?”

  2. Exposure — hidden work and B3 pressure appear.

  3. Alignment — classification becomes consistent; B2/B3/B4 get real space.

  4. Stability — B1 predictable, B3 controlled, B2 flowing.

  5. Mastery — ODUI is the default mental model.

6. What Teams Must Keep in Mind

  • the system will feel wrong before it feels right

  • mistakes are normal

  • capacity resets are expected

  • every week can be slightly better than the last

ODUI is not about perfection. It is about clarity, protection, and predictable progress.

22.6 The First Moment of Success

Every ODUI journey has a moment when it finally “clicks”.

Before this moment:

  • teams feel unsure

  • leaders feel impatient

  • stakeholders feel threatened

  • ODUI feels like extra work

After this moment:

  • confidence rises

  • resistance drops

  • conversations shift from fear to curiosity

The first real win turns belief from theory into experience.

Common Breakthrough Moments

  • The first calm week — no panic, stable priorities, no chaos.

  • The first clean B2 cycle — strategic work moves forward without being constantly interrupted.

  • The first time a stakeholder waits — a previously “urgent” request goes through intake and negotiation, and the stakeholder accepts it.

  • The first predictable B1 pattern — incidents stop feeling random and start looking manageable.

  • The first KPI movement — even a small shift proves ODUI is not cosmetic.

How to Accelerate the Breakthrough

Leaders can speed this moment up by:

  • protecting B2 from day one

  • setting clear B3 capacity limits early

  • enforcing intake consistently

  • running the weekly rhythm even when busy

  • celebrating visible wins loudly (“This is the calmest week we’ve had in months.”)

Protecting the Breakthrough

The first success is fragile.

Teams can slide back into:

  • saying yes too easily

  • skipping reviews

  • allowing side-door requests

  • overloading B2 again

Leaders must protect the breakthrough with boundaries, consistency, and the right rewards.

The breakthrough reminds everyone of something important:

Work can feel calm. Progress can be predictable. Strategy can actually move.

22.7 How to Know ODUI Is Becoming “Real”

There is no official announcement when ODUI takes root. You simply notice that behaviour has changed.

1. People Naturally Speak in Buckets

You hear:

  • “This is clearly B3 — let’s negotiate it.”

  • “This idea stays in B4 until we define the outcome.”

  • “Our B2 capacity for this cycle is already committed.”

The vocabulary shift is the first cultural signal.

2. Meetings Shrink in Size and Frequency

Meetings become shorter because:

  • priorities are clear before the meeting

  • work is already visible in the system

  • fewer decisions require debate

Status updates take minutes instead of hours.

3. Requests Flow Through Intake

Stakeholders:

  • submit requests via intake

  • define outcomes upfront

  • wait for negotiation

  • accept capacity limits

Side-door interruptions fade.

4. Escalations Drop

Escalations become rare and meaningful. When they occur, they are about real business risk, not internal misalignment.

5. Teams Push Back Calmly

Teams say:

  • “Our B3 capacity is full.”

  • “Here’s what we would have to drop.”

  • “This belongs in the next cycle.”

Pushback is factual, not emotional.

6. Work Feels Lighter

People report:

  • fewer surprises

  • more deep work

  • more control over their time

You hear sentences like:

  • “I can finally breathe again.”

  • “We’re actually making progress.”

7. KPIs Start Moving and Stress Drops

Protected B2 work starts to move outcomes. Stress falls across planning and delivery cycles.

When you see these signals together, ODUI has stopped being “new”. It has become normal.

People say:

“This is just how we work now.”

22.8 Why ODUI Works Even When You Doubt It

Every meaningful change passes through doubt. ODUI is no exception.

Teams ask:

  • “Is this really going to work for us?”

  • “Our culture is different — will this fit?”

  • “Can we really keep this discipline?”

These questions are not a sign of failure. They are a sign that you have left the comfort of the old system.

1. Hesitation Is Normal

Discomfort usually means:

  • hidden work is finally visible

  • poor prioritisation is being confronted

  • vague requests are no longer accepted

  • unrealistic expectations are surfacing

This is what progress looks like from the inside.

2. ODUI Works Even When Adoption Is Imperfect

ODUI does not require:

  • perfect classification

  • perfect leadership behaviour

  • perfect stakeholder cooperation

Even imperfect ODUI brings:

  • clearer priorities

  • more visible capacity

  • fewer interruptions

  • more protected B2

  • calmer decisions

The only real requirement is consistency.

3. Trials Reveal the Truth

In the first 30–60 days, ODUI reveals:

  • the true volume of B1

  • the real level of B3 pressure

  • the amount of hidden work

  • how overloaded teams really are

This can feel confronting. But you cannot fix what you cannot see.

4. The Only Way ODUI Truly Fails

ODUI does not fail because:

  • you mis-bucket some work

  • you skip a review

  • a stakeholder pushes too hard one week

ODUI fails when:

  • exceptions become the norm

  • rhythm is abandoned

  • intake is bypassed without consequence

  • teams hide work instead of surfacing it

As long as people keep showing up and using the language of urgency, importance, and capacity, the system bends but does not break.

5. Results Arrive Quietly, Then All at Once

You may not notice the slow improvements:

  • slightly fewer interruptions each week

  • slightly shorter meetings

  • slightly calmer cycles

Then, all at once:

  • B2 progress becomes visible

  • KPIs start to move

  • stakeholders follow intake without argument

  • stress drops noticeably

That is the moment ODUI shifts from “something we’re trying” to:

“This is simply how we work now.”

6. The Deep Reason ODUI Works

ODUI aligns with how humans naturally think:

  • urgency vs importance

  • outcomes vs tasks

  • capacity vs demand

  • rhythm vs chaos

It does not fight human nature. It organises it.

When doubt appears, ODUI acts as a quiet stabiliser:

  • buckets catch the chaos

  • rhythm keeps teams aligned

  • KPIs anchor decisions

  • intake slows down noise

7. Final Reassurance

If your adoption feels messy, you are doing the real work.

Stay with it:

  • keep the rhythm

  • protect B2

  • enforce intake

  • treat mistakes as learning

ODUI will repay you with calm, clarity, and progress — not because your organisation became perfect, but because you gave real teams a system that works in the real world.

22.9 The ODUI Language

Here are the new ODUI terms introduced or used heavily in this chapter.

New ODUI terms (Chapter 22)

Term Meaning
90-day adoption The realistic time window to embed ODUI habits. ODUI becomes normal through repetition, not a quick launch.
Momentum Keeping ODUI moving week to week (intake, reviews, corrections), even when things are messy.
Visibility shock The initial discomfort when hidden work, overload, and B3 pressure become visible.
Learning over perfection The adoption mindset: early mistakes are training data, not failure.
Bucket misclassification Early-stage errors where work is placed in the wrong bucket (often B1/B2/B3 confusion).
Bucket distribution chart A simple view showing how work/time is split across B1–B4 for a week or cycle.
Capacity snapshot A quick weekly view of what the team can realistically do (so trade-offs stay visible).
Capacity baseline The first reliable understanding of your real bucket mix, based on measured weeks (not hopes).
B1 playbook The agreed method for handling B1 so incidents don’t become chaos (roles, updates, rules).
B2 protection Actively defending improvement work from being consumed by B1/B3 (guardrails and trade-offs).
B3 negotiation scripts Short, repeatable phrases that help teams push back calmly and professionally.
Side-door request Any request that tries to bypass intake (DMs, escalations, hallway asks).
Quarterly adjustment loop A regular cycle that closes the loop: outcomes + KPIs → learning → adjusted priorities and capacity.
Breakthrough moment The first visible win that converts belief into experience (calm week, clean B2 cycle, KPI movement).
Exceptions become the norm The failure pattern where “one-time” bypasses and shortcuts quietly replace the ODUI system.

Core ODUI questions (Chapter 22)

  • Is this mostly B1 (alive), B2 (great), B3 (quiet), or B4 (breathing)?
  • Does this fit our capacity — or what must move if we add it?
  • If we add this B3, what B2 will slip?
  • Are we protecting B2 this week, or letting it get eaten by noise?
  • Is this request coming through intake — or through a side door?
  • Which bucket is this?
  • What outcome does it serve?
  • What KPI should move?
  • What are we saying no to if we do this?