Chapter 6 – From Intake to Bucket in 10 Minutes

6.1 What “10 Minutes” Really Means

In ODUI, the “10 minutes” principle is both a rule and a mindset. It symbolises speed through clarity, not speed through chaos. The goal of these 10 minutes is not to plan or estimate — it is simply to classify. The team decides where a piece of work belongs, not how it will be done.

Request vs Work (important) A request can be captured by anyone. A work item is a request that the intake team has classified into B1–B4, with a short reason recorded.

A 10-minute intake session is intentionally brief. The request may be captured earlier (async) in a form or board — the intake session is where classification happens.

Intake is led by the Intake Lead (Outcome Owner) and supported by the Flow Lead (Delivery Owner), and it expands to include the minimum necessary subject-matter experts (engineers, architects, designers, compliance, etc.) for correct bucketing. For cross-team or cross-department work, intake includes the relevant Intake Leads (Outcome Owners) and the coordinating Flow Lead (Delivery Owner) as needed. The purpose is to gain just enough clarity to assign the correct bucket — not to design, estimate, or scope.

During these 10 minutes, three key things happen:

The intended outcome is identified — what the requester hopes to achieve.
The urgency is understood — why it matters now.
The request is placed into the correct ODUI bucket — B1, B2, B3, or B4.

That’s it. The result is a clear and visible record of where the item belongs, and why. The Intake Lead adds a short note or comment that summarises the reasoning. This ensures that the decision can be reviewed, challenged, or adjusted later — but never lost or forgotten.

The 10-minute process is deliberately light. In this time frame, the team does not:

Write detailed user stories or technical specifications.
Estimate the level of effort required.
Assign resources, deadlines, or owners.
Debate the solution or potential approach.

Why? Because detail at this stage is premature. The purpose of intake is to sort, not to solve. The ODUI system recognises that early over-analysis is one of the biggest causes of wasted time. Instead, it promotes progressive clarity — information deepens only when the work moves forward in importance.

If clarity cannot be achieved within 10 minutes — if the requester cannot clearly express the "what" and "why now" — the item is calmly parked in B4 (Keeps Ideas Breathing). This rule is non-negotiable. It keeps the system clean, protects the team’s time, and encourages better preparation from stakeholders. When ideas mature, they can be re-evaluated quickly and fairly.

The outcome of this 10-minute rhythm is simple but powerful: every new request finds a home. Nothing floats in limbo, and no one wonders what happened to their idea. Each item is either active (B1–B3) or resting (B4) until ready.

This rhythm builds organisational calm. Stakeholders see a process that respects both their input and the team’s focus. Over time, the 10-minute discipline becomes second nature — the gateway to ODUI’s promise of clarity, consistency, and control.

10 minutes of clarity now saves hours of confusion later. It’s not just a process — it’s a philosophy of respect for time and attention.

6.2 The Two-Stage Intake Model

In many organisations, the intake process is either too slow or too shallow. Some teams rush to act on every new request without proper evaluation; others spend weeks debating before taking a single step. ODUI solves this by introducing a Two-Stage Intake Model — a clear distinction between sorting and shaping. This model allows teams to stay both responsive and strategic without burning out.

Stage	Name	Objective	Time	Output
Stage 1	Rapid Intake	Confirm the bucket (B1–B4) and record the reason.	≤ 10 minutes	Confirmed bucket assignment + short reason.
Stage 2	Definition & Alignment	For accepted B1/B2 items: define the problem, metrics, acceptance criteria, and ownership.	Variable (hours–days)	Ready-for-planning brief.

Stage 1 – Rapid Intake: The Sorting Stage

Stage 1 assumes the request is already captured in a shared intake system (anyone can do this). Rapid Intake is where the accountable intake team (Intake Lead + Flow Lead and the minimum needed specialists) answers one simple question: Where does this belong right now?

At this stage, we are not designing or estimating. The goal is to decide whether the request is urgent and important (B1), important but not urgent (B2), supportive or maintenance (B3), or still an idea (B4). The Intake Lead, sometimes with a Flow Lead, looks at the request’s outcome and urgency, applies ODUI’s logic, and confirms the bucket. Each decision includes a short note explaining the reasoning — enough for transparency, not analysis.

This fast step prevents teams from being buried under unstructured requests. It turns intake from a chaotic inbox into a manageable decision queue. Every request gets a home, even if that home is temporary.

Stage 2 – Definition & Alignment: The Shaping Stage

Once a request is accepted as important enough to act on (typically B1 or B2), it moves into Definition & Alignment. This stage transforms a classified item into a ready-for-planning brief. Here, the Intake Lead defines the problem statement, clarifies outcomes and KPIs, and aligns with stakeholders or other teams on what success looks like.

Definition work can take hours or days depending on complexity. The purpose is to make sure that by the time something enters execution, everyone knows what is being done and why. The energy spent here prevents confusion and rework later.

This stage also introduces alignment with Flow Leads, who ensure that capacity and sequencing fit the broader plan. The outcome is a well-shaped, evidence-backed initiative ready for prioritisation and delivery.

Why Separation Matters

Separating sorting from shaping creates both speed and sanity. It allows Intake Leads to handle new inputs rapidly without derailing their focus on ongoing projects. Stakeholders appreciate fast, fair, and transparent responses — even if the answer is "not now." The team avoids the trap of endless clarification meetings or analysis paralysis.

This structure also teaches discipline: only validated, prioritised items receive deep definition time. Everything else waits its turn. As a result, ODUI intake remains light, responsive, and sustainable.

Speed and structure can coexist. ODUI achieves both by separating sorting from shaping. Each stage protects the other — one gives pace, the other gives depth.

6.3 The ODUI Rapid Intake Flow (10 Minutes)

The ODUI Rapid Intake Flow turns what could be an overwhelming influx of requests into a quick, structured conversation. It ensures that every idea, complaint, or opportunity gets fair consideration — without interrupting the flow of work. The process takes no more than ten minutes, yet it establishes clarity, transparency, and accountability from the start.

This is not about bureaucracy; it’s about discipline. The Rapid Intake Flow prevents teams from spending hours debating priorities or chasing vague requests. Each step has a purpose and a time limit, keeping conversations concise and decisions visible.

Step	Action	Purpose	Typical Time	Owner
1. Capture	Record the request in a shared intake board or form.	Get the signal into the system — no hidden work.	1 min	Requester (anyone)
2. Clarify	Ask two short questions: "What outcome do you expect?" and "Why now?"	Filter noise and uncover intent.	2–3 min	Intake Lead (Outcome Owner)
3. Score	Quick scoring: Importance (High/Med/Low) + Urgency (Critical/Rising/Stable).	Establish a shared view of impact and timing.	3 min	Intake Lead + Flow Lead
4. Classify	Apply the bucket logic: Importance + Urgency → B1–B4.	Make the triage decision.	2 min	Intake Lead
5. Communicate	Log the bucket, add a one-line rationale, notify requester.	Keep everyone aligned and informed.	1–2 min	Intake Lead or Coordinator

Step-by-Step Breakdown

1. Capture – Every request starts by being written down in a visible system (e.g., intake form, Trello board, Jira intake list). This ensures transparency. No side conversations or hallway requests. If it’s not logged, it doesn’t exist. The act of capture alone builds trust — everyone knows their input is seen.

2. Clarify – The Intake Lead asks two powerful questions: "What outcome do you expect?" and "Why now?" These questions expose weak reasoning instantly. If the requester struggles to answer, the request may belong in B4 (Keeps Ideas Breathing) until more clarity emerges. This step takes only a few minutes but filters 80% of noise from meaningful opportunities.

3. Score – In three minutes, the Intake Lead and Flow Lead jointly evaluate importance and urgency using ODUI’s scoring logic. No detailed metrics are needed — just a quick, honest assessment. High importance with critical urgency means immediate focus (B1). Medium importance and stable urgency might fall into B3 or B4. The goal is not numerical precision but shared understanding.

4. Classify – With scores in hand, the Intake Lead applies ODUI’s bucket logic: Importance + Urgency = Bucket. This determines whether it’s B1 (Keeps You Alive), B2 (Makes You Great), B3 (Keeps Others Quiet), or B4 (Keeps Ideas Breathing). The classification locks in the decision, keeping work visible and organised. Importantly, decisions are documented — not just spoken.

5. Communicate – The Intake Lead or Coordinator records the decision, adds a short rationale (one sentence is enough), and shares it with the requester. For example:

"Moved to B2 — High importance, Medium urgency, supports retention KPI."

This note closes the loop and reinforces trust. Even if the request isn’t accepted immediately, the requester knows it was reviewed objectively.

Why It Works

The 10-minute intake flow is deceptively simple — but it changes behaviour. It creates a rhythm where new work enters the system fairly, not frantically. Requesters feel respected because they get a quick, reasoned response. Intake Leads stay in control of their focus. Flow Leads maintain visibility of team capacity. And leadership gains a real-time snapshot of what’s coming next.

The process also builds transparency and accountability. Every classification includes a clear reason, making prioritisation defendable and reviewable. No one needs to guess why something was delayed or moved.

The Psychological Effect

When a team consistently applies this process, panic and persuasion lose power. People stop escalating through emotion and start communicating through evidence. The intake board becomes a living map of priorities — calm, fair, and visible to all.

Structure brings calm. When everyone knows the rules, urgency loses its power to disrupt. Ten minutes of structured clarity can save days of confusion, frustration, and noise.

6.4 The ODUI Outcome Brief (Minimum Input)

At the heart of ODUI’s 10-minute triage lies a simple principle: you can’t prioritise what you don’t understand. Yet, understanding doesn’t have to mean writing pages of documentation. The ODUI Outcome Brief captures just enough information to make a fast, fair, and consistent intake decision.

This brief acts as the entry ticket into the ODUI system. It tells the story of the request in plain language — what it is, why it matters, and why now. The goal is not to provide a full project specification, but to establish context and intent.

Field	Description	Example
Title	A short, clear name that anyone can recognise. Avoid jargon or technical shorthand.	"Add Bonus Expiry Warning."
Outcome (Why)	Describe the change or result this will create if successful. Focus on impact, not action.	"Reduce bonus loss complaints."
Urgency Trigger (Why Now)	Identify the event, data, or signal that makes this request timely.	"Customer tickets rising about bonus expiry."
Requester / Owner	Specify who raised the request and who owns its clarity going forward.	"CRM Team / Intake Lead John."

These four fields are the foundation of a healthy intake process. They give Intake Leads enough context to assess importance and urgency without deep investigation. If any of these are missing, incomplete, or unclear, the request should automatically move to B4 (Keeps Ideas Breathing) until clarity improves.

This rule is not meant to be bureaucratic — it’s protective. It shields teams from wasting hours chasing unclear requests or debating assumptions. It also signals to stakeholders that clarity is a shared responsibility. The requester must do a small amount of thinking before asking for action.

Why the Minimum Matters

Complexity is often the enemy of speed. The more fields you demand upfront, the fewer people will use the process — and chaos returns. ODUI’s minimalist intake brief ensures speed, inclusivity, and discipline all at once. One paragraph, or even a few bullet points, is usually enough.

Teams using this approach report fewer misunderstandings and faster decisions. Stakeholders learn to communicate outcomes instead of tasks ("improve retention" vs. "build a dashboard"). Over time, this clarity compounds — every request becomes sharper, every decision easier.

If you can’t explain it simply, it’s not ready yet. Clarity isn’t a luxury — it’s the cost of entry into an outcome-driven system.

6.5 From Classification to Definition

The 10-minute classification is the starting line, not the finish. Its purpose is to place each request into the right ODUI bucket — but the real value begins when a request moves into Stage 2: Definition & Alignment. This is where the quick classification evolves into a well-shaped initiative, ready for execution.

Classification gives direction; definition gives depth. Once an item is placed in B1 (Keeps You Alive) or B2 (Makes You Great), it earns the right to be explored further. The goal of this next step is to shape the work just enough for the team to plan and deliver confidently — not to create endless documentation.

In Stage 2, the Intake Lead leads the definition process, supported by the Flow Lead and relevant team members. The goal is to turn the initial idea into a clear, measurable, and aligned plan of action.

The Core Elements of Definition

To move from classification to clarity, ODUI recommends focusing on five key elements:

Problem Statement – What issue are we solving or opportunity are we seizing? Define it in one or two sentences, written in plain language that everyone understands.
Success Metrics – How will we know this work made a difference? Define clear outcomes or KPIs linked to business or product goals.
Acceptance Criteria – What must be true for this work to be considered done and successful? These criteria provide the bridge between intention and delivery.
Involved Teams & Contributors – Identify who needs to be involved to deliver the outcome. This builds ownership and alignment early.
KPI Ownership – Confirm who is accountable for moving the key metric. Every B1/B2 item must connect to a measurable result and a responsible owner.

Each of these elements deepens the understanding of why the work matters and what success looks like. The goal is not to create volume but to create focus.

Progressive Clarity in Action

ODUI’s approach to definition is called progressive clarity — details grow in proportion to importance. If something is low priority or uncertain, it stays light. Only when it’s approved as important or urgent do we add definition. This avoids the waste of writing long briefs for work that might never happen.

This principle also keeps the system dynamic. As context evolves, the definition can be refined. New data may sharpen the problem statement or update the success metric. Definition is not a one-time event — it’s an ongoing conversation between clarity and reality.

The Power of Timing

By separating classification from definition, ODUI ensures the right people spend the right amount of time on the right work. Teams don’t drown in detail too early, and leaders don’t get blocked waiting for perfection before taking action. Clarity grows at the same pace as confidence.

Define later, decide now. Classification comes first; deep work follows only for what matters. Fast clarity, followed by focused definition, creates a calm and powerful rhythm of execution.

6.6 The 10-Minute Discipline

The 10-minute rule is not just a technique — it’s a discipline that shapes culture. It creates rhythm, respect, and shared responsibility across the organisation. When practiced consistently, it becomes one of ODUI’s most powerful cultural tools: it turns chaos into calm and confusion into clarity.

At its core, the 10-minute rule says this: decide, don’t drift. Every new idea or request deserves attention — but only for a short, structured moment. In that moment, we decide where it belongs, document why, and move on. This small habit, repeated daily, prevents hours of rework, frustration, and emotional debate.

Why It Works

Focuses Intake Leads and Flow Leads on structured intake, not endless discussion. The 10-minute boundary forces discipline. Intake and Flow Leads stay responsive but avoid being consumed by undefined requests. It gives them a polite, objective reason to close circular conversations: "Let’s capture this, classify it, and move on."
Teaches stakeholders to come prepared. When requesters know the meeting is short, they arrive with clearer thinking. They learn to articulate purpose — what they want and why now. Over time, this raises the overall quality of requests and reduces back-and-forth clarification later.
Keeps the backlog clean and trustworthy. Unclear or emotional requests don’t linger. If something can’t be explained clearly, it goes to B4 (Ideas) until ready. This rule filters noise automatically and protects everyone’s time.
Encourages ownership. Each requester becomes responsible for bringing enough context to justify a classification. The Intake Lead facilitates, not fixes. The accountability shifts toward shared clarity instead of unilateral decision-making.
Builds respect for focus. The 10-minute rule sends a message that time and attention are valuable. It’s a boundary against the constant urgency that erodes productivity.

The 10-minute rule is not about speed — it’s about respect for focus.

The Cultural Ripple Effect

When the 10-minute discipline becomes habit, the benefits multiply far beyond intake meetings. It begins to reshape how people think, communicate, and plan. Teams start to default to simplicity — short summaries instead of essays, clear outcomes instead of open-ended debates.

This simplicity spreads upward and outward. Executives see patterns faster because information flows cleanly. Stakeholders gain confidence that their input won’t be ignored, even if it’s not acted on immediately. Teams feel lighter, because the mental clutter of "maybe" work disappears.

As this culture matures, conversations across the organisation change tone. Instead of emotional appeals ("This is urgent!"), people speak in evidence and structure ("This is B2, stable and moving to rising urgency next quarter"). ODUI becomes not just a framework but a shared language.

The Habit of Clarity

Building this habit takes commitment. At first, some may resist — they’ll want longer discussions or more context. But over time, the results speak for themselves:

Meetings shorten, yet decisions improve.
The backlog reflects reality, not wish lists.
Prioritisation becomes faster and less political.
Everyone knows where things stand — and why.

To reinforce the habit:

Schedule short, recurring intake reviews — e.g., twice a week, 30 minutes total.
Keep a visible intake board so everyone can see outcomes.
Track how many requests move directly to B4 — this metric shows clarity improving over time.

Protecting the 10-Minute Rule

The real challenge isn’t starting the habit — it’s protecting it. Under pressure, teams often revert to long, emotional conversations. Leaders play a critical role here. They must model brevity, ask outcome-based questions, and enforce boundaries with kindness but firmness.

If a discussion exceeds 10 minutes, pause it and assign it a bucket. The classification decision can always be refined later. The discipline lies in making some decision quickly — to keep the system moving and confidence high.

When the System Clicks

A mature ODUI organisation feels different. New requests arrive and are calmly processed. Intake Leads are not gatekeepers — they’re guides. Stakeholders trust the rhythm because they see fairness and consistency. Every item finds a home; nothing falls through the cracks.

The 10-minute discipline, repeated daily, creates a sense of order and reliability. People spend less time managing work and more time doing meaningful work.

Simplicity is strength. The 10-minute rule proves that great organisations don’t move fast by rushing — they move fast by staying clear.

6.7 The ODUI Language

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

New ODUI terms (Chapter 6)

Term	Meaning
10-minute principle	A time boundary for intake decisions: classify quickly, don’t plan or estimate.
Request vs work item	A request is input; a work item is a request that has been classified into B1–B4 with a reason.
Two-Stage Intake Model	Stage 1 sorts (Rapid Intake). Stage 2 shapes (Definition & Alignment).
Rapid Intake	A short session to confirm the bucket and record a one-line rationale.
Definition & Alignment	The shaping stage for accepted B1/B2 work: clarify problem, success metrics, and ownership so it’s ready to plan.
Ready-for-planning brief	A short, clear description of the problem, success metrics, acceptance criteria, ownership, and key risks — enough to plan delivery.
ODUI Rapid Intake Flow	Capture → Clarify → Score → Classify → Communicate. The 10-minute conversation structure.
One-line rationale	A single sentence that explains the bucket decision so it stays transparent and reviewable.
Urgency trigger	The event, data, or signal that makes “why now” true.
ODUI Outcome Brief	The minimum input for intake: title, outcome, urgency trigger, requester, and the intake owner.
Progressive clarity	Adding detail only as work proves important enough to deserve it.
Decide, don’t drift	A cultural rule: make a visible classification decision quickly instead of letting requests sit in limbo.
Non-negotiable B4 parking rule	If a request can’t be explained clearly in intake, it goes to B4 until clarity improves.

Core ODUI questions (Chapter 6)

Clarity: What outcome do you expect?
Urgency: Why now? What is the urgency trigger?
Scoring: Is importance High/Med/Low? Is urgency Critical/Rising/Stable?
Classification: Which bucket does this belong in right now?
Transparency: What’s the one-line rationale we will record?