Chapter 17 – Practical Templates

17.1 Template Overview

In ODUI, structure doesn’t limit creativity — it enables it. Templates are the bridge between concept and execution, ensuring that every team, regardless of size or maturity, can apply ODUI’s logic in a consistent, repeatable way. They transform the framework’s philosophy into daily practice and prevent teams from reinventing the wheel each time they plan, prioritise, or reflect.

The ODUI Template Toolkit provides a set of simple, standardised documents that shape how teams think, communicate, and decide. Each template is designed to remove ambiguity and accelerate clarity — from the first intake of a request to the final retrospective of an outcome.

Why Templates Matter in ODUI

Consistency Across Teams – Everyone speaks the same operational language. Whether you’re an Intake Lead, Flow Lead, or executive, you use the same inputs and outputs.
Speed of Decision-Making – A shared structure cuts time spent on clarification. Teams can move faster with confidence.
Transparency and Accountability – When every idea, project, and outcome follows the same template, visibility becomes natural.
Scalability – ODUI templates make it possible for growing organisations to scale governance without adding bureaucracy.
Continuous Learning – Retrospective and KPI templates ensure insights don’t vanish after delivery — they become part of organisational memory.

A framework is only as strong as its habits. Templates make those habits visible and repeatable.

The ODUI Template Toolkit

Category	Template Name	Core Users	Typical Use
Prioritisation	ODUI Intake Sheet / Scoring Form	Intake Lead / Flow Lead	Initial classification and triage of new requests
Planning	Bucket Capacity Planner	Flow Lead / Team Leads	Weekly allocation of effort and time across B1–B4
Execution	Outcome Canvas	Intake Lead / Team	Defines desired results, success metrics, and acceptance criteria
Measurement	KPI Tree Template	Exec / Intake Lead	Links strategic goals to measurable product and operational outcomes
Visibility	Dashboard Blueprint	All	Visual reference for designing and maintaining ODUI dashboards
Review & Learning	Retrospective Sheet	Team	Captures insights, learnings, and improvements after each cycle

Each of these templates corresponds to a pillar of ODUI: clarity, rhythm, and learning. Used together, they form a closed-loop system where work enters through structured prioritisation, flows through measured execution, and exits through reflection and improvement.

How to Use the Templates Effectively

Keep it lightweight: Each template should take minutes, not hours, to fill.
Integrate into existing tools: Adapt templates into your workflow (e.g., Confluence, Notion, Google Sheets, or Miro). The goal is accessibility, not ceremony.
Review regularly: Templates are living assets. Update them to reflect lessons learned and evolving needs.
Connect them together: The output of one template becomes the input for another (e.g., Intake Sheet → Outcome Canvas → KPI Tracker → Dashboard → Retrospective).

When used rhythmically, these templates create an organisational heartbeat — a steady pulse of prioritisation, execution, measurement, and reflection.

Templates turn intent into rhythm. Used consistently, they anchor ODUI in the daily behaviour of every team.

17.2 ODUI Intake Form / Scoring Sheet

The ODUI Intake Form is where structure begins. It transforms the chaos of incoming ideas, demands, and issues into actionable clarity. This is the first operational touchpoint of ODUI — where the Intake Lead and Flow Lead convert noise into organised flow.

The Intake Form ensures every new request is treated objectively, within ten minutes or less, and not based on emotion or seniority. It gives every stakeholder a fair, transparent process to have their request acknowledged and assessed.

Purpose of the Intake Form

Prevent chaos: Capture new requests before they clutter Slack, emails, or meetings.
Create a single entry point: Every initiative starts here — nothing enters the ODUI system without it.
Enable fast triage: The goal is to classify quickly, not to analyse deeply.
Support transparency: Stakeholders can track where their request sits and why.
Facilitate decision-making: The structured scoring guides the Intake Lead and Flow Lead to the right bucket (B1–B4).

An idea is valuable only when it’s captured and classified. Without intake discipline, prioritisation becomes personal, not objective.

Core Fields and Their Purpose

Field	Description	Example
Request Title	A concise summary of the request.	“Add export feature for client reports.”
Problem Statement	Describe the issue or opportunity in one sentence.	“Partners spend 3 hours weekly doing manual exports.”
Desired Outcome (KPI Link)	Link to measurable business outcome or KPI Tree node.	“Reduce partner admin time by 50%.”
Impact Score (1–5)	Rate potential business or customer value.	4 = High impact.
Urgency Score (1–5)	Rate time sensitivity.	2 = Not urgent.
Effort Estimate (S/M/L)	Rough workload estimate.	M = Medium (2–3 days).
Recommended Bucket (B1–B4)	Initial placement suggestion.	B2 – Makes You Great.
Owner / Reviewer	Person responsible for classification and validation.	Assigned Intake Lead or Flow Lead.
Status	Tracking progress: New / Accepted / Deferred / Rejected.	Accepted.

Scoring Logic

The Impact and Urgency scores form a simple matrix that drives the first classification decision:

Urgency →	1–2 (Low)	3 (Medium)	4–5 (High)
Impact 1–2 (Low)	B4	B3	B3
Impact 3–4 (Medium)	B4	B2	B2
Impact 5 (High)	B2	B2	B1

This keeps the triage consistent and prevents subjective prioritisation. The Intake Lead and Flow Lead validate classification before it enters planning.

The rule of ODUI Intake: classify fast, refine later. Triage is not prioritisation — it’s order before depth.

Usage Workflow

Submission: Any team member or stakeholder submits a request using the Intake Form (digital or spreadsheet version).
Review: The assigned Intake Lead reviews the request for clarity and links it to an existing KPI or outcome if applicable.
Validation: The Flow Lead checks resource feasibility and confirms the recommended bucket.
Decision: Together, Intake Lead and Flow Lead classify the request and update its status (Accepted, Deferred, Rejected).
Visibility: Accepted requests appear on the ODUI board for tracking and communication.

This process creates fairness and accountability — everyone can see why a decision was made and how it connects to organisational outcomes.

Practical Tips for Efficient Intake

Limit discussion time: Ten minutes per request is enough for classification.
Keep it public: Maintain the intake list in a visible workspace (e.g., Notion, Airtable, or Confluence).
Add comments, not debates: Stakeholders may add context but decisions remain with Intake Lead / Flow Lead.
Automate inputs: Use a simple online form or Jira intake portal to collect requests consistently.

Triage, don’t debate. Intake is about clarity, not consensus. Once the request enters ODUI, it will naturally find its place in the rhythm of reviews and prioritisation.

17.3 Outcome Canvas

The Outcome Canvas is one of ODUI’s most powerful tools — it bridges the gap between doing and achieving. It ensures that every initiative, no matter how small, directly links to a measurable outcome that supports the broader organisational goals.

Unlike traditional requirement documents or task lists, the Outcome Canvas focuses on intent and impact rather than activity. It makes sure every team member understands why something is worth doing, what success looks like, and how it connects to strategic priorities.

Purpose of the Outcome Canvas

Anchor decisions in value: Prevents teams from drifting into feature-driven thinking.
Clarify shared understanding: Everyone sees the same definition of success.
Enable focused execution: Keeps delivery aligned to measurable results.
Support learning: Captures assumptions and outcomes for future improvement.

An outcome is a change in behaviour or performance — not just a task completed.

Structure of the Outcome Canvas

Section	Description	Example
Outcome Goal	The quantifiable change you want to achieve. It should be time-bound and directly measurable.	“Reduce player churn by 10% within two quarters.”
Why It Matters	The strategic context. Links the initiative to the KPI Tree or organisational goals.	“Supports Strategic KPI: Customer Retention.”
Success Indicators	The measurable signs that tell you whether you achieved your goal. These should be leading and lagging indicators.	“Increase NPS +5 points; improve average session duration by 7%.”
Assumptions	The beliefs driving your approach. Each assumption should be testable.	“Faster onboarding will increase first-week retention.”
Key Actions / Experiments	The work or experiments that will deliver the intended outcome.	“Redesign onboarding flow; add interactive tutorial video.”
Risks / Mitigation	The main blockers or unknowns that could derail success — and how you’ll address them.	“Backend latency could slow onboarding → implement performance monitoring.”
Owner / Team	The person or group accountable for the outcome.	“Outcome: Intake Lead; Execution: Design + Dev teams.”

How to Use the Outcome Canvas

Before starting an initiative:
Fill out the canvas collaboratively (Intake Lead, Flow Lead, and team).
Ensure it connects to a KPI Tree node and ODUI bucket (usually B2 or B4).
During the initiative:
Revisit assumptions mid-cycle — are they still valid?
Update success indicators if data shows new learning.
After completion:
Review achieved results against outcome goals.
Capture learnings and feed them into retrospectives or B4 idea updates.

The canvas becomes both a planning and reflection tool — your “before and after” of value creation.

Best Practices for Effective Outcome Canvases

Keep it visual: Use a one-page format with clear sections and space for notes.
Use real numbers: Replace vague terms like “improve” or “enhance” with measurable targets.
Link to dashboards: Connect the success indicators directly to KPI dashboards for visibility.
Collaborate, don’t delegate: The canvas should be built together, not sent as a form to fill.
Limit to one outcome per canvas: Simplicity increases focus.

Common Pitfalls to Avoid

Pitfall	Why It’s a Problem	Fix
Vague goals	Leads to unclear direction and wasted effort.	Quantify and time-box every goal.
Skipping assumptions	Removes learning opportunities.	Write down at least two testable beliefs.
Focusing on outputs	Creates busywork, not value.	Ask, “What behaviour will this change?”
Too many indicators	Confuses measurement focus.	Choose 2–3 clear metrics max.

When to Use the Outcome Canvas

B2 (Makes You Great): Every improvement or growth project should start here.
B4 (Keeps Ideas Breathing): For validating new experiments or innovation hypotheses.
Quarterly Planning: As part of outcome-setting sessions.
Executive Reviews: To summarise the value and learning behind key initiatives.

A great canvas replaces 20 slides. It aligns people around purpose, focus, and impact in a single glance.

17.4 Bucket Capacity Planner

The Bucket Capacity Planner is ODUI’s guardrail against chaos. It ensures that each team plans realistically and maintains a healthy balance between short-term firefighting and long-term value creation. Rather than tracking individual hours, it focuses on how collective time and attention are distributed across the four ODUI buckets — B1 through B4.

This planner turns invisible workload patterns into visible insights. It helps Flow Leads, Intake Leads, and executives align on where time is being spent, and whether that allocation supports the organisation’s priorities.

Purpose of the Capacity Planner

Prevent burnout: Avoid overloading teams with too many urgent or unplanned tasks.
Expose imbalance: Visualise when certain buckets (especially B1 or B3) start dominating the schedule.
Protect innovation: Guarantee consistent time allocation for learning, improvement, and experimentation (B4).
Enable strategic conversation: Help leadership discuss trade-offs with facts, not opinions.
Keep ODUI in rhythm: Align capacity planning with the ODUI review cadence (weekly or biweekly).

Balance protects focus. When you can see your time, you can control it.

Structure of the Planner

Column	Description	Example
Team / Member	The person or group whose capacity is being planned.	“Frontend Squad”
Available Hours	Total working hours for the period (usually a week or sprint).	160 hrs
% Allocation (B1–B4)	Planned percentage of effort for each bucket.	B1=10%, B2=65%, B3=15%, B4=10%
Planned Tasks / Epics	Key items associated with each bucket.	B1: Incident fixes, B2: Feature X, B3: Compliance doc, B4: Prototype Y
Notes on Load or Risks	Qualitative notes to flag dependencies or overcommitment.	“B1 may spike if API issues persist.”

The planner can be implemented in a simple spreadsheet or visualised using capacity management tools such as Notion, Airtable, or Jira dashboards.

How to Use the Planner Effectively

Start with team-level capacity: Begin by listing total hours or story points available for the period.
Apply ODUI ratios: Use recommended baselines to guide initial planning:
B1: 10–15% — Stability and emergencies.
B2: 60–70% — Core growth and product outcomes.
B3: 15–20% — Relationship and stakeholder management.
B4: 5–10% — Innovation and improvement.
Review allocation: Adjust based on actual demand and historical data.
Visualise results: Convert numbers into a simple pie chart or bar graph.
Share for visibility: Present in weekly syncs and monthly ODUI reviews.

This visual approach ensures that discussions about workload remain grounded in data, not perception.

Outputs and Insights

A completed Bucket Capacity Planner delivers three crucial insights:

Visual Balance: A pie or stacked bar chart instantly shows whether the team is maintaining a healthy spread across B1–B4.
Early Warning: When B1 starts exceeding 20%, it’s a signal that the team is spending too much time in firefighting mode — an alert to invest in prevention or automation.
Strategic Visibility: Leaders can see which teams are overcommitted, underutilised, or missing B4 exploration time.

The planner is not about control; it’s about conversation. It gives teams and leaders a common view of workload health.

Tips for Implementation

Review weekly or biweekly: Capacity changes often — stay adaptive.
Use colour coding: Assign each bucket a consistent colour (e.g., B1=red, B2=green, B3=blue, B4=purple) for instant recognition.
Keep flexibility: Allow buffer for unexpected B1 or B3 work.
Connect to dashboards: Feed planner data into ODUI dashboards for transparency.
Encourage honesty: The planner only works if teams report realistically — not optimistically.

When used consistently, the Bucket Capacity Planner becomes a strategic safety net. It turns time — the most limited resource — into an intentional, balanced investment across survival, growth, stability, and innovation.

17.5 KPI Tracking Sheet

The KPI Tracking Sheet is the heartbeat monitor of ODUI. It translates strategy into measurable motion, ensuring that outcomes remain visible, relevant, and actionable. This tool links the day-to-day execution of teams to the strategic intent of the organisation, providing a clear record of performance evolution.

Where the KPI Tree shows relationships and hierarchy, the KPI Tracking Sheet captures the rhythm — showing whether metrics are moving, stagnating, or drifting in the wrong direction.

Purpose of the KPI Tracking Sheet

Track outcome movement: Turn strategic goals into visible progress indicators.
Highlight patterns early: Identify trends before they become problems.
Connect buckets to performance: Link each KPI to the type of work driving it (B1–B4).
Simplify reporting: Provide a single source of truth for dashboards and leadership reviews.
Encourage accountability: Every KPI has a clear owner responsible for updates and insights.

A moving KPI is a learning KPI. Stagnant numbers often mean the goal has been forgotten or the data ignored.

Core Columns and Their Purpose

Column	Description	Example
KPI Name	The metric being tracked.	“Customer Retention Rate”
Owner	The person or role responsible for the KPI.	“Intake Lead – Retention”
Level (Tree Node)	Link to the KPI Tree layer (Strategic / Product / Operational / Activity).	“Product Level – Engagement”
Target Value	The desired outcome for the KPI.	“85% retention”
Current Value	The most recent measurement.	“78% retention”
Trend	Directional indicator (↑ improving / ↓ declining / → stable).	“↑ Improving”
Bucket Impact (B1–B4)	Which type of work most influences this KPI.	“B2 – Makes You Great”
Next Review Date	When the KPI will next be reviewed or refreshed.	“30 April”
Comments / Actions	Notes on insights, blockers, or next steps.	“Retention up 3% after new onboarding flow. Next test: referral feature.”

Usage Workflow

Update regularly: The KPI Tracking Sheet should be refreshed before each monthly and quarterly ODUI review.
Integrate with dashboards: Automate data pulls where possible to avoid manual updates.
Review trends, not just values: Look at the direction and speed of change, not just static numbers.
Flag learning opportunities: When a KPI improves or declines sharply, capture what caused it — this fuels the learning cycle.
Link to buckets: During review, correlate movement with the bucket driving that impact. Example: if uptime (B1 KPI) improves after automation, record that link explicitly.

Interpreting KPI Trends

Upward (↑) – Indicates success or improvement. Review what worked and reinforce those behaviours.
Downward (↓) – Signals a problem. Identify whether it’s due to execution gaps, external factors, or unrealistic targets.
Stable (→) – Suggests either maturity (plateaued success) or neglect (stalled progress). Decide if this KPI still matters.

The direction of the trend is often more valuable than the number itself — it shows whether learning is happening.

Practical Implementation Tips

Use colour coding: Green = on target, Yellow = at risk, Red = off target.
Add sparklines or mini-charts: Visual trends are faster to interpret than text.
Keep scope small: 3–5 KPIs per level; avoid overwhelming with data.
Automate wherever possible: Pull data from analytics tools, CRMs, or monitoring systems.
Use comments actively: Notes create organisational memory — why metrics moved, what was tried, what worked.

Outputs and Insights

The KPI Tracking Sheet produces three layers of value:

Operational Awareness: Teams see how their work affects outcomes.
Strategic Alignment: Executives and Intake Leads can spot whether the company’s direction is producing measurable change.
Learning Velocity: By tracking both numbers and actions, teams learn faster from results.

In ODUI, data is not decoration — it’s direction. The KPI Tracking Sheet keeps that direction alive, visible, and honest.

17.6 Review and Retrospective Sheet

The Review and Retrospective Sheet is ODUI’s structured reflection tool — it transforms every cycle, release, or incident into a learning opportunity. Rather than focusing on blame or justification, it focuses on clarity, accountability, and improvement. Every review becomes a deliberate pause to extract insight from experience.

This sheet brings consistency to retrospectives across all ODUI buckets — from urgent incident reviews (B1) to strategic growth initiatives (B2), stakeholder projects (B3), and experimental innovations (B4). It ensures that lessons don’t stay in meeting notes but are captured, shared, and acted upon.

Purpose of the Review and Retrospective Sheet

Capture lessons systematically: Turn outcomes into actionable insights.
Reinforce accountability: Each improvement item gets a clear owner.
Prevent recurrence: Identify root causes and embed preventive actions.
Share learning organisation-wide: Feed key insights into dashboards or B4 idea cycles.
Build a culture of reflection: Encourage open, non-judgmental discussions.

The best teams document wisdom, not excuses.

Structure of the Sheet

Section	Purpose	Example
1. What happened?	Provide a short factual summary — what occurred, when, and how it unfolded.	“Service outage on 12/08 due to expired SSL certificate.”
2. What worked well?	Highlight successes or responses that should be repeated.	“Incident detected quickly via monitoring alert; rapid collaboration between Ops and QA.”
3. What did we learn?	Identify new insights, both technical and behavioural.	“We lacked a renewal reminder system; also learned our escalation protocol works efficiently.”
4. What will we change next time?	Translate learning into future action or process improvement.	“Add SSL auto-renewal check; create visual alert in dashboard.”
5. Who owns the improvement task?	Assign clear responsibility and due dates to drive accountability.	“Ops Manager – implement automation by 30/08.”

How to Use the Sheet Effectively

After each cycle or incident: Conduct a review within 48–72 hours of completion or resolution.
Collaborative discussion: Involve everyone who participated — Intake Leads, Flow Leads, engineers, designers, QA, or stakeholders.
Stay blameless: Focus on systems, not individuals. Frame every issue as an opportunity to improve structure or process.
Record insights clearly: Summaries should be concise and actionable. Avoid generic statements like “communicate better.”
Feed learnings forward: Enter key takeaways into the ODUI “Learning Highlights” dashboard or as B4 ideas for future improvement.

Levels of Retrospective Application

B1 (Keeps You Alive): Incident and post-mortem reviews — focus on resilience and prevention.
B2 (Makes You Great): Feature or outcome reviews — evaluate what drove results or missed targets.
B3 (Keeps Others Quiet): Stakeholder or compliance reviews — assess communication, delivery quality, and trust.
B4 (Keeps Ideas Breathing): Innovation retrospectives — analyse what experiments taught the team, regardless of success.

Connecting to ODUI Dashboards

Each retrospective output feeds into the ODUI ecosystem:

Learning Highlights: A dedicated dashboard section showing what was learned this cycle.
Bucket Adjustments: Insights that impact workload balance or process efficiency.
Future B4 Ideas: Innovative solutions or process improvements become new B4 entries.

This creates a continuous loop between reflection and evolution — closing the gap between insight and action.

Best Practices

Keep sessions short (30–45 minutes): Depth comes from focus, not duration.
Rotate facilitators: Prevent bias and encourage shared ownership.
Capture in real-time: Fill the sheet during the discussion, not afterward.
Summarise learnings publicly: Transparency reinforces trust and psychological safety.
Follow up: Review previous actions in the next retrospective to measure improvement.

Reflection without follow-up is entertainment. The Review and Retrospective Sheet ensures that learning becomes change.

17.7 Visual Dashboard Blueprint

A well-designed ODUI dashboard is a decision surface — a single-screen view that helps teams and leaders understand where attention is needed. This blueprint provides a repeatable structure for building dashboards that are clear, calm, and aligned with ODUI’s principles of focus and rhythm.

Dashboards are not meant to impress; they are meant to orient. Their true value is in how quickly someone can answer: Where are we, and what should we do next?

Standard Sections

Each dashboard, regardless of audience (Team, Product, Executive), should contain the following visual anchors:

1. Bucket Distribution (B1–B4 Pie)

A simple pie or horizontal bar chart showing the percentage of effort invested in each bucket.
Helps reveal imbalance: too much B1 (firefighting), too much B3 (politics), or lack of B4 (innovation decay).
Should be colour-coded: B1 = red, B2 = green, B3 = blue, B4 = purple.

2. KPI Progress Bars

Short bars showing movement of top KPIs connected to strategic outcomes.
Use green/amber/red to show status at a glance.
These bars are not deep analytics — they are signals indicating where attention is required.

3. Urgency Tracker (B1 Open Count)

A simple count of active B1 incidents, plus their age.
Optionally include a trend line showing the last 4–8 weeks.
This widget is the organisation’s early-warning system.

4. Team Load Chart

Displays current workload distribution across individuals or squads.
Helps detect overload, uneven distribution, or hidden bottlenecks.
Encourages healthier planning and prevents burnout.

5. Learning Feed from Retrospectives

A short list of insights or actions generated from recent reviews.
Reinforces the idea that learning is a continuous asset, not an afterthought.
Allows leaders to see improvement momentum, not just delivery.

Guidelines for Effective Dashboard Design

Keep it to one screen height

No scrolling. No deep menus. A dashboard must give answers at a glance.
If you need multiple pages, you don’t have a dashboard — you have a report.

Use a consistent colour schema

B1 = red, B2 = green, B3 = blue, B4 = purple.
Apply the same colours across all teams and dashboards for familiarity and reduced cognitive load.

Avoid animation or visual noise

Movement distracts. Clutter hides insight.
Prioritise clarity, simplicity, and static visuals that communicate instantly.

Prioritise legibility over aesthetics

Labels must be readable without zooming.
Use plain language instead of technical jargon.
Every element must answer a question — if not, remove it.

Why the Blueprint Matters

This blueprint ensures that dashboards across the company feel familiar, comparable, and trustworthy. With a consistent layout:

Teams spend less time interpreting and more time improving.
Executives can understand multiple product lines without re-learning formats.
Intake Leads and Flow Leads can anchor discussions in the same visual language.

Dashboards are not decoration — they are discipline in colour.

17.8 The ODUI Language

Term	Meaning
Template toolkit	The small set of standard templates that make ODUI repeatable day to day.
ODUI Intake Form / Scoring Sheet	The front-door form used to capture, score, and bucket a new request quickly.
Impact score	A simple rating of potential business/customer value (e.g., 1–5).
Urgency score	A simple rating of time pressure (e.g., 1–5). Urgency is about consequence, not emotion.
Outcome Canvas	A one-page tool that defines what will change, why it matters, and how success will be measured.
Success indicators	The few metrics/signals that prove whether the outcome happened.
Assumptions	The beliefs behind your plan that should be tested (not just hoped).
Bucket Capacity Planner	A simple planner that shows how much effort you will invest in B1–B4 for the period.
Allocation ratios	The planned percentage split across buckets (e.g., B2 protected at 60–70%).
KPI Tracking Sheet	A single place to track KPI targets, current value, trend, and actions.
Trend (↑/↓/→)	A fast signal for whether a KPI is improving, declining, or stable.
Review and Retrospective Sheet	A structured way to capture what happened, what was learned, and what will change next time.
Learning Highlights	The small set of learnings/actions you make visible so lessons don’t disappear.
Dashboard blueprint	A repeatable layout for ODUI dashboards so they stay calm, consistent, and readable.
Decision surface	A dashboard view designed to support decisions fast, not to impress.

Core ODUI questions (Chapter 17)

Is this request clear enough to score and bucket?
What is the impact, and what is the urgency?
Which bucket does this belong to (B1–B4) — and why?
What outcome are we trying to create, and how will we measure it?
Where are we, and what should we do next?