Analytics · Management ritual
Twenty minutes.
Five decisions.
Dashboards do not improve operations by being available. They improve operations when the same people use them on a reliable cadence to make a small number of decisions and check whether last week's decisions worked.
The ritual
One screen, one owner, one decision at a time.
The review is not a performance. Nobody needs a polished deck describing numbers everyone can already see. Open the operating view, move from outcome to exception, assign the next action, and record the expected effect.
Twenty minutes creates useful pressure: discuss only what can change, park investigations that require more evidence, and prevent the meeting from becoming a tour of every metric.
The agenda
Five questions, four minutes each
1. Did demand surprise us?
Compare
Forecast versus actual
Look at cohort and time window, not only the weekly vehicle total.
Decide
Change one assumption
Update an event input, seasonal range, or lead-time rule for the next comparable shift.
2. Where did the service promise fail?
Read
P50 and P90 together
The center describes ordinary flow. The tail shows repeated unreliability.
Open
Named exceptions
Inspect the sessions around the failure instead of debating the percentage in the abstract.
3. Where did labor and work stop matching?
Link
Cars per labor hour
Segment by stand and demand window, then read beside wait, safety, and exceptions.
Decide
Move capacity with a hypothesis
Change a start time, role assignment, break plan, or supervisor window and state what should improve.
4. What did the system fail to capture?
Find
Missing outcomes
Refusals, abandonments, vehicle problems, manual handoffs, and incomplete sessions can make reports look cleaner than the week.
Repair
Simplify capture
Remove fields, add a one-tap exception, or infer context so the next event is easier to record.
5. Did last week's change work?
→A decision without an owner and review date is a conversation. Record both before moving on.
Keep the artifact smaller than the meeting
The review record needs enough structure to preserve accountability, not another reporting system.
Decision
What changes
One sentence describing the staffing, process, configuration, or investigation action.
Owner
Who moves it
One accountable person, even when several teammates help.
Expected
What should change
Name the metric or exception pattern and the direction expected.
Review
When we look again
Choose a window that can realistically contain enough comparable operating data.
The operating cadence
The dashboard is the agenda.
Begin with the live evidence, drill into only the exceptions that matter, and end with five or fewer owned decisions. Deeper investigations can continue outside the review without holding every manager in the room.
The takeaway: analytics becomes management when the same evidence produces a decision, an owner, and a return date every week.
