''' Most weekly business reviews are a waste of time. They are performative theater. A manager drones through a slide deck of stale charts, everyone nods, and then goes back to doing exactly what they were doing before. Nothing changes.
The meeting is a reporting exercise, not a management tool. It focuses on lagging indicators presented on cluttered dashboards that tell you what already happened, usually too late to matter. The conversation is a mix of excuses and stories. Accountability is optional.
A weekly scoreboard review, run correctly, is the opposite. It is the most potent, high-leverage meeting an operator can run. It’s a 25-minute, highly structured session designed to do one thing: change behavior *this week*.
The Scoreboard Is Not a Dashboard
First, we must agree on terms. A dashboard is a rearview mirror, often a blurry one. It’s a collection of charts, usually tracking lagging outputs like monthly revenue or customer churn. By the time you see the number is off, the opportunity to influence it has passed. Dashboards encourage passivity.
A scoreboard is a forward-looking instrument. It tracks a small, curated set of predictive, input-based metrics that a team can directly influence *right now*.
This is a core Cendryva pillar: manage by statistics, not stale dashboards. The objective is to create a single, intelligible loop where data informs a hypothesis, which dictates an immediate action. Instead of presenting a dashboard of last month’s sales (a lagging output), a proper scoreboard tracks this week’s "prospect meetings booked" (a predictive input). One is history; the other is destiny, and it’s still in your hands.
The 25-Minute Agenda
The clock is non-negotiable. The pace forces focus and eliminates storytelling. One person, the meeting owner, drives the entire session by sharing the live scoreboard.
Minutes 0–5: The Numbers
Go down the list of 5–7 key metrics. No discussion. The owner of each metric simply states the number, the target, and the color (Red/Green).
"New Leads: 82. Target: 100. Red." "Demo Conversion Rate: 28%. Target: 25%. Green." "Customer Tickets Closed: 257. Target: 250. Green." "Time to Close: 4.2 hours. Target: 4 hours. Red."
That’s it. The goal is to establish a shared, objective reality in five minutes. No "whys" yet.
Minutes 5–20: The "Why" and "What"
Now, go back to the top of the list, but focus *only* on the Red metrics. The owner of the first Red number gets the floor. They have 1-2 minutes to answer two questions:
1. Why was it red? (This must be a data-informed hypothesis, not an excuse.) 2. What is the single action you will take this week to make it green?
"We missed the lead target because our cost-per-click on the main campaign spiked and we throttled the budget. This week, I am reallocating 20% of the budget from Campaign B to Campaign A and rewriting the ad copy to improve the quality score."
This is not a discussion. It is a declaration of accountability. The proposed action must be a specific, controllable input. "Work harder" or "do a better job" are not actions. "Increase daily outreach calls from 30 to 45" is an action. The group’s job is to ensure the proposed action is credible and sufficient.
Minutes 20–25: The Cascade
In the final five minutes, quickly review the list of committed actions. This is where dependencies are flagged.
"I can increase my outreach calls, but I need that new contact list from Marketing by Tuesday EOD."
This confirms the plan for the week. The meeting doesn’t end with ideas; it ends with a concrete list of owners and action items that become leading indicators for the *next* scoreboard review. The loop closes.
Rules of Engagement
This meeting fails if it devolves into a typical unstructured conversation. The rules are the structure.
- No New Topics. If a metric isn’t on the scoreboard, it doesn’t get discussed here. If an issue is important, get it on the scoreboard for next week. Protect the agenda.
- The Number’s Owner Speaks First. Do not let a senior leader jump in to diagnose the problem or assign a solution. The person accountable for the number must own the analysis and the resulting action. Otherwise, you’re building a culture of dependency.
- Hypotheses, Not Excuses. The "why" is not a time for stories about how complex things are. It’s for a testable theory. "We think the conversion rate dropped because of the website change" is a hypothesis you can analyze. "We had a lot of people on vacation" is a powerless excuse.
- The Data Is the Authority. The scoreboard itself is the source of truth. Grounding the conversation in the numbers depersonalizes failure and focuses everyone on the tangible problem to be solved.
What This Replaces
This 25-minute session replaces the meandering, hour-long weekly "all-hands" or "team sync" where everyone gives a subjective update on how "busy" they are. It replaces performative reporting with tactical execution.
This is not a strategy meeting. It is the engine of your operating cadence. It’s the weekly loop that ensures the strategy is translating into measurable action. It connects the C-suite to the front line through a shared and unbiased language: statistics.
Stop talking about the work and start talking about the numbers. '''