Chapter 16 – Progress Dashboards & Reviews

16.1 The Purpose of Dashboards in ODUI

Dashboards within the ODUI framework exist to bring clarity, focus, and alignment to teams and leaders. They are not management tools for surveillance—they are communication tools for shared understanding. When designed and used correctly, dashboards provide a living snapshot of how the organisation is performing, learning, and adapting.

At their core, ODUI dashboards serve as alignment engines. They ensure that everyone—from executives to frontline teams—can see how their work contributes to larger goals without wading through spreadsheets or reports. The goal is to translate data into insight and activity into meaning.

Why Dashboards Exist

Dashboards exist to answer three core questions:

What outcomes are moving? Dashboards show which goals are improving, stagnating, or regressing. This shifts focus from output to impact, allowing teams to celebrate genuine progress rather than busyness.
Which buckets need attention? Each ODUI bucket represents a unique type of work—B1 (urgent), B2 (strategic), B3 (stakeholder), and B4 (innovative). Dashboards reveal whether an organisation is balanced or drifting into unhealthy patterns, such as spending too much time firefighting or too little time innovating.
Where are we learning the most? ODUI dashboards highlight areas of experimentation, prevention, and insight. This reflects not only delivery but also discovery—where lessons are being generated that can strengthen future cycles.

When these three questions are answered clearly, dashboards become the heartbeat of organisational rhythm: fast enough to detect early signs of imbalance, but calm enough to sustain steady progress.

Dashboards Are Alignment Tools, Not Surveillance Systems

The ODUI philosophy rejects the idea of dashboards as productivity monitors. Dashboards should never exist to track individuals or create pressure through constant measurement. Their purpose is to illuminate the system, not the person.

They align teams by showing how efforts connect to outcomes.
They enable leaders to see system health without diving into micro-tasks.
They promote transparency by replacing hidden status updates with shared truth.

When used correctly, dashboards create psychological safety—a shared understanding that visibility is not about blame but about learning. This encourages open conversation about risks, progress, and improvements.

Healthy dashboards remove fear from visibility.

The Emotional Design of Dashboards

A well-structured ODUI dashboard should evoke calm confidence, not anxiety. The design itself matters—colours, layout, and tone all shape how teams perceive performance. Too much red and flashing alerts can create panic; too little context creates apathy.

Calm visuals (clear icons, neutral tones) help teams think clearly under pressure.
Simple charts over complex reports make trends obvious at a glance.
Consistent symbols across dashboards build intuitive literacy.

Clarity reduces emotional noise. A good dashboard lowers stress by showing control and progress.

From Information to Insight

Many organisations confuse data quantity with insight quality. Dashboards often drown in numbers, creating more confusion than clarity. ODUI flips that logic: less data, more meaning.

A useful dashboard doesn’t display everything—it displays what matters right now. This focus allows teams to:

Identify which buckets (B1–B4) are absorbing too much capacity.
See which KPIs from the KPI Tree are actually shifting.
Learn which experiments or prevention actions are yielding results.

Simplicity builds trust; complexity destroys engagement.

The Two-Minute Rule

In ODUI, every dashboard must pass the Two-Minute Rule: anyone—executive, Intake Lead, or engineer—should be able to understand the current state of the system in under two minutes.

If it requires explanation, it’s not a dashboard—it’s a report. Reports document history; dashboards enable action.

Dashboards are living conversations. Reports are records of the past.

The Essence of ODUI Dashboards

Dashboards transform the invisible (progress, learning, rhythm) into something visible and shareable. They help organisations:

Maintain strategic focus amid operational noise.
Detect imbalances before they become crises.
Foster transparency and accountability through shared truth.

Ultimately, ODUI dashboards are mirrors of the system’s health, not magnifying glasses for individual performance. They tell the collective story of progress and resilience.

When dashboards tell stories, teams make better decisions.

16.2 Layers of Dashboards

A single dashboard cannot serve every purpose or audience. ODUI therefore structures dashboards into layers, each designed to deliver the right information to the right people at the right frequency. This layering creates a clear flow of visibility — from operational reality to strategic insight — without overwhelming anyone with unnecessary detail.

The Principle of Layered Visibility

Dashboards act as different windows into the same system. Each layer provides context appropriate to its audience, while still connecting upward and downward through shared data. This ensures consistency of truth but flexibility of detail.

The golden rule: everyone looks at the same story, just from a different altitude.

1. Team Dashboard: The Engine Room of Flow

Primary Audience: Developers, QA, Designers, Analysts Focus: Execution flow, blockers, and quality trends (B1–B2) Cadence: Daily or Weekly

Team dashboards are the operational heartbeat of ODUI. They display what’s actively in motion and where friction appears. These dashboards don’t measure productivity — they measure flow and focus.

Core Components:

Work-in-progress (WIP) view: Tracks how much the team has in play, preventing overload.
Cycle time trend: Shows how long work items take from start to completion.
Blocker board: Lists issues that stop progress and who owns resolution.
Quality metrics: Error rate, test coverage, or deployment success rate.

Team dashboards should be fast and interactive. They guide the team’s daily conversation: Where are we stuck? What needs help? What’s ready to move? The goal is clarity, not control.

A healthy team dashboard creates calm focus, not pressure.

2. Product Dashboard: The Bridge Between Output and Outcome

Primary Audience: Intake Leads (Outcome Owners), Flow Leads (Delivery Owners) Focus: Outcome movement, KPI progress, learnings, and cross-bucket visibility Cadence: Weekly or Biweekly

The product dashboard connects daily delivery with product and business impact. It’s the Intake Lead and Flow Lead’s main alignment tool — showing whether effort (from team dashboards) is translating into progress on KPIs and outcomes.

Core Components:

Bucket health: Distribution of work across B1–B4 to ensure balance.
Top 3 outcomes: Highlighting the measurable results currently being driven.
KPI Tree snapshot: Progress of product-level KPIs linked to strategic goals.
Learning log: A record of insights, experiments, and retrospectives.

This layer turns delivery metrics into meaning. It tells the story of “What value are we creating and what’s changing because of it?” It is not a report to executives — it is a reflection tool for Intake Leads and Flow Leads to stay adaptive and aligned.

The product dashboard is where impact becomes visible.

3. Executive Dashboard: The Strategic Lens

Primary Audience: Executives and Senior Leadership Focus: Strategic balance, outcome sustainability, and organisational health Cadence: Monthly or Quarterly

The executive dashboard sits at the top of the visibility chain. It doesn’t show tasks, tickets, or features — it shows patterns and performance health. Executives use it to make directional adjustments, not tactical interventions.

Core Components:

Bucket distribution: % of effort in B1–B4 to assess balance and stability.
Strategic KPI trends: Progress on top company outcomes (from the KPI Tree).
Urgency and risk map: Frequency of escalations or systemic bottlenecks.
Team and stakeholder sentiment: Confidence and alignment signals.

Executives review this layer to ensure strategy, delivery, and learning stay connected. It replaces status meetings with insight reviews.

Executives don’t need more detail — they need clearer perspective.

Design Rules for All Layers

Readability in under two minutes. Dashboards should tell a story instantly; if they need narration, they fail their purpose.
Shared visual language. Colours, labels, and categories must be consistent across layers to build intuitive literacy.
Progressive detail. Each layer adds depth but never contradiction — data rolls upward seamlessly.
Accessible to all. Transparency is a cultural norm in ODUI — every layer is visible across the organisation.

The Value of Layered Dashboards

This layered structure provides transparency without chaos:

Teams manage execution with autonomy.
Intake Leads and Flow Leads steer products with context.
Executives oversee direction with confidence.

Together, these dashboards create a unified language of progress. Everyone sees the same truth — just from the right height.

Layered dashboards make the invisible system visible, without drowning it in detail.

16.3 Core Dashboard Components

Every ODUI dashboard, regardless of its audience, follows the same underlying logic: it must make the system visible in a calm, simple, and actionable way. The structure is consistent across all layers so that anyone—from an engineer to an executive—can instantly understand where the organisation stands.

The goal is simple: make sense at a glance. A dashboard should guide decision-making, not require interpretation. Each component plays a specific role in reflecting the organisation’s rhythm of urgency, focus, and learning.

1. Bucket Overview – The Balance Lens

The Bucket Overview is the first and most critical view. Represented as a pie or stacked bar chart, it shows how organisational capacity is distributed across ODUI’s four buckets:

B1 – Urgent: Survival work and incident response.
B2 – Strategic: Growth-driving initiatives.
B3 – External: Stakeholder and relationship work.
B4 – Innovative: Experiments and long-term ideas.

This visual provides an instant sense of balance. If B1 dominates, the system is reactive; if B2 fades, strategic motion stalls; if B4 disappears, innovation suffocates. Executives and Intake Leads can spot drift early and act before imbalance becomes crisis.

Ask: “Is our attention where our strategy is?”

2. Outcome Progress View – The Impact Lens

This section visualises progress on key outcomes and KPIs. It’s the pulse of the dashboard, typically shown as a traffic-light system or trend indicator:

Green: On track or exceeding expectations.
Amber: At risk — requires monitoring or decision.
Red: Off track — needs intervention.

Each outcome should tie back to the KPI Tree. The goal is not to show every number, but to summarise whether our work is moving the right metrics. This keeps reviews focused on results, not activity.

Good dashboards show direction, not justification.

3. Urgency Map – The Stability Lens

The Urgency Map gives visibility into all active B1 incidents or crises. It lists each item with:

Its current status (open, resolved, or recurring)
Age (how long it’s been active)
Owner (who is driving resolution)

By mapping B1 issues over time, teams can spot recurring patterns — a sign that prevention work is missing. For example, repeated infrastructure failures point toward a B2 reliability initiative. The Urgency Map shifts conversations from firefighting to prevention.

Visibility ends panic. Silence feeds chaos.

4. KPI Tree Snapshot – The Strategy Lens

This view connects operational activity to strategic outcomes. It highlights the top 3–5 metrics from the company’s KPI Tree and shows whether they are trending up, flat, or down.

Rather than dumping data, this snapshot provides a compact overview of how delivery is influencing business performance. Intake Leads and executives can instantly see whether key goals (e.g., retention, stability, satisfaction) are improving.

Example visual:

Up arrows (📈) for improving metrics
Side arrows (➡️) for stable
Down arrows (📉) for decline

This section transforms dashboards from operational trackers into strategic compasses.

Dashboards are not about completion; they’re about contribution.

5. Team Load Balance – The Capacity Lens

A healthy organisation distributes effort evenly across teams and roles. The Team Load Balance visualises who is carrying what share of active work. Common formats include heatmaps or horizontal bar graphs.

This helps Flow Leads and Intake Leads detect early signs of burnout or underutilisation. If one squad or specialist repeatedly carries most of the load, capacity allocation and prioritisation may need adjustment.

Metrics to include:

% of work in progress per team
Average WIP per contributor
Variation in cycle times

Balanced teams sustain predictable flow.

6. Learning Highlights – The Growth Lens

Perhaps the most overlooked component, Learning Highlights capture insight velocity — what the organisation learned in this cycle. Instead of only showing what was done, this view summarises what changed in understanding or process.

Examples:

“Discovered automation reduces QA cycle by 30%.”
“Customer interviews invalidated Feature X — archived.”
“Recurring incidents traced to outdated dependency.”

Including learning signals creates a psychologically safe culture. It tells teams that reflection and discovery are valued outcomes, not secondary to output.

If learning isn’t visible, it’s not happening.

Optional Add-ons: Rhythm & Health Indicators

1. Next Review Timer: A small countdown clock showing when the next ODUI review or retrospective occurs. It reinforces rhythm and prevents last-minute preparation panic.

2. Health Score: An aggregated score blending multiple dimensions: outcome success rate, delivery predictability, and team morale. It offers a simple pulse of organisational well-being.

Dashboards should not only show performance — they should show health.

In Summary

Every dashboard component serves a purpose:

Bucket Overview: Balance.
Outcome Progress: Impact.
Urgency Map: Stability.
KPI Tree Snapshot: Strategy.
Team Load Balance: Capacity.
Learning Highlights: Growth.

Together, they create a full picture of organisational health — one that values progress, learning, and focus over speed or volume.

An ODUI dashboard is a mirror of balance — not busyness.

16.4 The ODUI Review Cadence

Dashboards gain meaning only when they drive reflection and action. In ODUI, reviews form the heartbeat of organisational rhythm, ensuring teams stay aligned, learn continuously, and adapt without chaos. The cadence is designed to balance short-term responsiveness with long-term learning — from daily flow checks to quarterly strategic resets.

The purpose of each review is not to report activity, but to interpret insight. Every review ends with the same question:

“What will we do differently next cycle?”

This single question transforms meetings from administrative updates into cycles of improvement.

The ODUI Review Ladder

Each layer of review aligns with a different level of system visibility. Together, they ensure information flows upward (insight) and direction flows downward (clarity). The cadence maintains both focus and stability.

Cadence	Scope	Key Participants	Focus	Duration
Daily Standup	Team	Dev, QA, Flow Lead	Immediate blockers (B1)	15 min
Weekly Sync	Product	Intake Lead, Flow Lead	B2/B3 progress, learnings, next focus	30–45 min
Monthly Review	Department / Domain	Intake Leads, Flow Leads, Executive Rep	Bucket balance, KPI shifts	60 min
Quarterly ODUI Review	Cross-Organisation	Executives, Intake Leads, Flow Leads	Outcome reflection, direction reset	90–120 min

1. Daily Standup – Maintaining Flow

Purpose: Keep work unblocked and priorities visible.

This is the team’s micro-rhythm. It ensures momentum by quickly surfacing obstacles or urgent issues. Discussions should stay tactical and focused:

What’s currently in motion?
What’s blocked and why?
What needs escalation to the Flow Lead?

Good practice:

Keep it to 15 minutes max.
Focus on problems, not updates.
Document blockers briefly in the dashboard.

Standups are for flow, not storytelling.

2. Weekly Sync – Translating Delivery into Outcomes

Purpose: Connect product progress to measurable impact.

The weekly or biweekly sync (depending on cycle length) bridges delivery with product performance. Intake Leads and Flow Leads review B2 and B3 progress, interpret insights from dashboards, and decide what needs course correction.

Key agenda points:

Review top outcomes from the product dashboard.
Discuss learnings and blockers across B2/B3.
Identify upcoming focus and capacity shifts.
Reconfirm ownership of next steps.

Tone: Calm, constructive, and data-driven — not reactive.

Weekly syncs sustain direction between strategy and execution.

3. Monthly Review – Calibrating Balance

Purpose: Maintain organisational equilibrium across buckets.

At the monthly level, reviews move from task focus to pattern analysis. Domain leads and executive representatives review bucket distribution, KPI trends, and team health. This is where potential drift (too much B1, not enough B2 or B4) becomes visible.

Discussion points:

Are our current efforts balanced across B1–B4?
Which KPIs are improving or stagnating?
What systemic risks or dependencies are emerging?
What learnings can be promoted across teams?

Outcome: Adjust priorities or resource allocations before imbalances harden into habits.

Monthly reviews turn reflection into proactive steering.

4. Quarterly ODUI Review – Resetting Direction

Purpose: Reflect, realign, and renew strategic focus.

The quarterly ODUI Review is the framework’s highest rhythm — a strategic checkpoint where executives, Intake Leads, and Flow Leads step back to assess how the entire system is performing.

Core elements:

Review top-level outcomes from the KPI Tree.
Reflect on cross-bucket health and team energy.
Discuss strategic adjustments or resource rebalancing.
Celebrate wins and formally capture learnings.

This meeting closes one ODUI cycle and sets the tone for the next. It prevents drift, reinforces clarity, and keeps long-term goals connected to operational reality.

Quarterly reviews are where insight becomes strategy.

Why Cadence Matters

Without a defined rhythm, dashboards devolve into static reports and teams lose the habit of reflection. Cadence builds predictability, accountability, and learning velocity.

Predictability: Everyone knows when reflection happens — no surprises.
Accountability: Decisions are revisited rhythmically, not reactively.
Learning velocity: Frequent, small reviews accelerate growth.

ODUI reviews are for decisions, not status. They transform data into direction and meetings into momentum.

16.5 Visual Design Principles

Good dashboards feel calm and intuitive—they guide, not overwhelm. ODUI dashboards follow a visual design philosophy based on clarity, consistency, and emotional neutrality.

Guidelines:

Consistent colour coding: B1 = red, B2 = green, B3 = blue, B4 = purple.
Show trends, not snapshots: Line charts over time are more valuable than single data points.
Use human language: Replace technical jargon with intuitive labels.
Add learning notes: Numbers alone don’t teach—context makes them actionable.
Keep it public: Dashboards should be open-access across the organisation to foster shared ownership.

A calm dashboard drives calm leadership.

16.6 Integrating Dashboards with ODUI Tools

Dashboards should sit at the centre of ODUI’s data ecosystem. They pull live data from multiple sources, keeping everyone aligned with one version of truth.

Data Sources:

Intake System: Feeds B1–B4 classification and prioritisation.
KPI Tree: Provides progress data for key outcomes.
Task Management Tools (e.g. Jira, ClickUp): Supply delivery flow and cycle-time metrics.
Team Surveys: Measure morale, burnout risk, and focus levels.

Integration Logic:

Avoid duplication — every data point should have a single source.
Automate updates — dashboards should pull information, not rely on manual entry.
Focus on interpretation, not maintenance.

If your dashboard needs a weekly update meeting, it’s not automated enough.

16.7 From Reporting to Reflection

In ODUI, dashboards are not built for justification — they exist to enable collective learning. Traditional reporting focuses on proving that work was done; ODUI replaces that mindset with reflection on what changed and why it matters. Dashboards become tools for insight, alignment, and improvement, not weapons for control.

The Purpose of Reflection Over Reporting

Reporting answers, “What did we do?” Reflection answers, “What did we learn?”

This distinction defines maturity in an ODUI organisation. Reflection turns data into dialogue, allowing teams and leaders to adapt with clarity instead of reacting with blame.

Traditional reporting fails because it:

Focuses on activity, not outcome.
Encourages defensiveness rather than curiosity.
Rewards busyness instead of progress.

ODUI reflection succeeds because it:

Centres on learning and improvement.
Normalises honest conversation about failure.
Encourages ownership of change, not protection of ego.

Reflection is performance without fear.

The Mindset Shift

Moving from reporting to reflection requires a cultural and behavioural pivot:

From	To
“What’s done?”	“What’s changing and why?”
Status	Story
Numbers	Insights
Accountability through blame	Accountability through ownership
Fear of exposure	Freedom to explore

This mindset shift transforms dashboards into spaces for shared intelligence. Teams stop defending performance and start interpreting it.

In ODUI, dashboards talk with people, not at them.

Creating a Culture of Reflection

Reflection thrives in a psychologically safe environment — one where transparency is rewarded, not punished. Leaders and managers must model this by speaking openly about uncertainty, trade-offs, and learnings from failure.

How to foster reflective habits:

Ask “why?” before “who?” When something goes wrong, focus on cause and system, not blame.
Include learnings in every review. Each dashboard section should highlight at least one insight gained.
Use open-ended prompts. Replace “Are we on track?” with “What surprised us this cycle?”
Celebrate discovery, not perfection. Learning faster than competitors is the ultimate advantage.

Reflection isn’t just about metrics — it’s about mindset. It signals that the organisation values learning velocity over rigid performance.

A good dashboard tells the truth, even when it’s uncomfortable.

Reflection in Practice

During ODUI reviews, dashboards become conversation catalysts. Instead of reading updates, teams explore patterns:

Why did certain KPIs improve while others stalled?
What recurring blockers suggest systemic issues?
Which experiments produced new knowledge?

These reflections transform meetings into learning forums — places where insight compounds over time. When teams know reflection is safe, honesty increases, decisions improve, and trust grows.

Transparency without judgment creates the fastest path to growth.

The Outcome of Reflection Culture

When reporting evolves into reflection:

Teams operate with curiosity over compliance.
Leaders act with coaching over control.
Dashboards become living instruments of awareness.

Ultimately, this shift changes how success feels inside the organisation. The atmosphere moves from anxiety to progress, from noise to clarity.

ODUI reflection isn’t about proving worth — it’s about improving wisdom.

16.8 Sample Dashboard Layouts

Dashboards are the visual heartbeat of ODUI — they synchronise attention, insight, and rhythm across every layer of the organisation. Each dashboard layout is tailored to its audience but built on the same principle: make the system visible, not overwhelming.

ODUI defines three primary dashboard types — Team, Product, and Executive — each serving a different level of reflection and decision-making.

1. Team Dashboard – The Pulse of Daily Flow

Purpose: Enable teams to see what’s in motion, what’s blocked, and how efficiently they are working. Audience: Developers, QA, Designers, and Flow Leads.

Key Widgets:

Work-in-Progress (WIP) Board: Displays current items per bucket (mainly B1 and B2). Helps maintain healthy flow and avoid overload.
Cycle-Time Trend: Tracks how long tasks take to move from start to finish — revealing efficiency and friction points.
Top Blockers List: Visual list of obstacles affecting progress, tagged by owner and blocker type.
Focus Load Chart: Shows workload distribution across individuals or squads.

Ideal Use: Daily standups and retrospectives. The Team Dashboard turns raw work data into shared situational awareness — everyone knows what’s moving, what’s stuck, and where help is needed.

If a standup takes more than 15 minutes, the dashboard isn’t clear enough.

2. Product Dashboard – The Bridge Between Delivery and Impact

Purpose: Connect product progress to measurable business outcomes. Audience: Intake Leads, Flow Leads, and cross-functional leads.

Key Widgets:

KPI Heatmap: Displays key product metrics (retention, NPS, revenue lift) colour-coded by trend direction.
Bucket Distribution Pie: Shows effort allocation across B1–B4, helping teams spot imbalance early.
Learning Log: Captures key insights from experiments or releases — lessons learned are as visible as results achieved.
Outcome Summary Cards: Each card summarises an active initiative with status, owner, and expected impact.
Review Countdown Timer: Indicates time left until the next review cycle.

Ideal Use: Weekly or biweekly reviews. The Product Dashboard promotes a rhythm of reflection — teams focus on movement and meaning, not just metrics. It serves as the connective tissue between the tactical and the strategic.

Good product dashboards tell the story of evolution, not activity.

3. Executive Dashboard – The System Health View

Purpose: Provide leadership with a strategic overview of organisational balance, direction, and resilience. Audience: Executives, Department Heads, and Strategic Planners.

Key Widgets:

Outcome Index: Aggregated score showing progress across top strategic KPIs from the KPI Tree.
B1–B4 Trend Graph: Visualises capacity balance and its shifts over time — early signal of organisational drift.
Trust Index: Reflects stakeholder and partner confidence, derived from satisfaction surveys and delivery reliability.
Urgency Heatmap: Highlights volume and age of B1 incidents to show operational stability.
Innovation Flow Tracker: Displays how many B4 ideas graduated into B2 initiatives, signalling long-term health.

Ideal Use: Monthly or quarterly leadership reviews. Executives don’t need to see every detail — they need patterns, direction, and emerging risks. The Executive Dashboard distils ODUI into a strategic compass, guiding investment and attention.

Executives should spend time reading trends, not tickets.

Shared Design Principles Across All Dashboards

Regardless of level, all ODUI dashboards share these universal traits:

Consistency: Same colour coding for buckets (B1–B4) across all dashboards.
Simplicity: Each view is readable in under two minutes.
Context: Every metric is paired with an interpretation or insight.
Transparency: Dashboards are accessible to all — no hidden versions.

When everyone reads from the same visual language, alignment becomes automatic. Dashboards stop being tools for reporting and become living maps that guide teams and leaders toward clarity.

Dashboards are not mirrors — they are maps. They don’t just show where you are; they show where to go next.

16.9 The ODUI Language

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

New ODUI terms (Chapter 16)

Term	Meaning
Dashboard (ODUI)	A shared, living view of system health and progress — designed for clarity and alignment, not surveillance.
Alignment engine	A dashboard’s job: make outcomes, bucket balance, and learning visible so teams and leaders stay aligned.
Two-Minute Rule	A good dashboard can be understood in under two minutes by anyone. If it needs narration, it’s a report.
Layered visibility	Different dashboard layers (team/product/executive) show the same story at different detail levels.
Team dashboard	The day-to-day view: WIP, blockers, cycle time, and quality signals that support flow.
Product dashboard	The outcome bridge: bucket health, top outcomes, KPI snapshot, and learning signals.
Executive dashboard	The strategic lens: patterns, bucket trends, top KPI movement, and organisation health.
Shared visual language	Consistent colours and labels across dashboards so people “read” ODUI the same way.
Progressive detail	Each layer adds depth without contradicting the story — data rolls up cleanly.
Bucket overview	A chart that shows how capacity is split across B1–B4 (balance at a glance).
Outcome progress view	A simple view (often RAG) showing if key outcomes/KPIs are on track, at risk, or off track.
Urgency map	A view of active B1 incidents: status, age, and ownership (stability at a glance).
KPI Tree snapshot	A compact view of the top metrics from the KPI Tree and their direction (up/flat/down).
Team load balance	A view that shows workload distribution to spot burnout risk and unfair load early.
Learning highlights	Short, visible learnings (experiments, insights, prevention) so “learning” is treated as progress.
Review ladder	The ODUI cadence stack: daily standup → weekly sync → monthly review → quarterly review.
Reflection (vs reporting)	Shifting from “what did we do?” to “what changed and what did we learn?”

Core ODUI questions (Chapter 16)

What outcomes are moving?
Which buckets need attention?
Where are we learning the most?
Is our attention where our strategy is?
What will we do differently next cycle?
What surprised us this cycle?
What recurring blockers suggest a system issue?