Early in my career, I inherited a Weekly Business Review that had been running for months. On paper, it looked like a functioning operating cadence: a standing invite, a consistent time slot, and a polished deck.
In practice, it was a reading session. Each leader walked through their section of the deck, narrating numbers everyone had already seen. By the time the last person finished, the hour was gone, no real decisions had been made, and most action plans could be summarized as “we’ll improve next week”. Within a day or two, the same issues were now urgent escalations.
The deeper problem wasn’t just that we were reading slides, it was that every metric we reviewed was an output result: on-time delivery, cost per unit, customer defects. Nobody was diving into the controllable behaviors that drove those results. So even when the review went “well,” we still had no clear idea what anyone should do differently.
The Problem With Reviewing Only Outputs
Output metrics such as fill rate, cost per unit, on-time shipment, customer satisfaction, tell you whether you won or lost. They don’t tell you why, or what to do next.
When a WBR is built entirely around outputs, a familiar dynamic sets in: the Senior Leader and Site Leader can see a site is missing its delivery target, but nobody can point to a specific behavior that changed this week and would change the outcome next week.
Input metrics are different. They describe the controllable behaviors that drive outputs. A frontline supervisor can directly influence pick rate per hour, dock-to-ship cycle time, or pack audit pass rate. Nobody can directly manage “on-time shipment %” as a behavior. They can only manage the inputs that produce it.
Shifting from output-only to input-plus-output review is one of the highest-leverage changes an Leader can make. It changes the conversation from “we missed” to “here’s exactly what we’re doing about it.”
Output vs. Input Metrics: Examples
| Output Metric | Why It’s Not Enough Alone | Controllable Input Metrics to Review |
|---|---|---|
| On-Time Shipment % | Tells you whether you shipped on time, but not why or how to fix it. | Pick rate vs. plan, dock-to-ship cycle time, trailer load start compliance, labor hours plan vs actual |
| Cost Per Unit | A result of dozens of decisions. No one can directly manage it as a behavior. | Units per labor hour by function, idle time %, overtime hours vs. plan, indirect-to-direct labor ratio |
| Inventory Accuracy | A score, not a behavior. It doesn’t tell anyone what to do differently. | Cycle count completion rate, receiving confirmation compliance, misstow rate by zone, discrepancy age |
| Customer Defect Rate | Reflects what already went wrong. By the time it shows up, this week’s failures are already baked in. | Pack audit pass rate, label error rate, short-ship rate by SKU, quality check completion by shift |
The outputs belong in your WBR as context. The inputs are what Site Leaders should be held accountable to discuss, explain, and act on.
The Five Ways a WBR Breaks
Input-focused or not, WBRs fail in a small number of predictable ways.
1. It Becomes a Status Report Reading Session
Reading numbers is not reviewing them. A real review involves interpretation, root cause discussion, and a decision about what changes. The diagnostic is simple: if you could replace your WBR with an email and lose nothing, it’s a reading session.
The fix is the pre-read. Distribute the metrics deck 24 hours in advance so that meeting time is reserved entirely for discussion.
2. Vague Action Plans Without Owners or Dates
A site misses its target and the Site Leader commits to improving next week. Next week arrives, the target is still missed, and a new commitment is made. The problem is almost never intent, but rather specificity.
Three questions that break this cycle:
What specifically will be different? Not “we’ll focus more”, but what process, what behavior, what decision changes?
Who is doing it and when? A plan without an owner and a timeline is a conversation, not a commitment.
What’s your fallback if it’s not working? A credible plan has contingencies, not just optimism.
These questions force the Site Leader to think through the plan in detail, which often surfaces when the plan isn’t actually achievable as stated. Specificity also creates accountability. When the same site misses again, the question is simply, “What happened to the plan we agreed on last week?”
Most organizations only need to go through this a few times before the dynamic shifts. Once Site Leaders understand what level of detail is expected, they arrive prepared.
3. Side Discussions That Swallow the Agenda
Every WBR has someone who wants to use the forum as a time to get answers on something else: a policy question, an exception request, a niche issue at a specific site, a complaint about missing technology. These conversations aren’t always bad, they just don’t belong here.
A parking lot helps. Capture the topic visibly, assign a follow-up owner, and move on. “We’ll get to that, but not here.” Done consistently, people learn the WBR has a specific purpose, and other issues have their own forum.
4. The Meeting Has No Real Authority
First, a WBR is only as good as the person running it, so a strong, knowledgeable facilitator is important. The facilitator doesn’t need to be the most Senior Leader, but they do need the standing to keep the agenda moving, the judgment to know when an action plan is too vague or will not work, and the respect to push-back and drive accountability.
Second, the WBR needs at least one subject matter expert for each metric category. Their role is not to own the metric or action plan, but to validate root causes and ensure Site Leaders leave with a credible plan. If a proposed action won't move the metric - or has already failed before – the subject matter expert must be willing to say so and help drive a better solution. Without this capability, a WBR can appear rigorous while producing little impact.
5. The Meeting is Not Focused
Many WBRs fail because they try to review everything. Teams build dashboards full of output metrics, input metrics, site metrics, trend lines, and exceptions, then wonder why the meeting feels overwhelming and produces little action.
The goal of a WBR is not to discuss every metric. The goal is to identify the few input gaps preventing the business from achieving its desired outputs.
Start with the outputs that matter most. Then identify the critical inputs that drive those outputs and establish clear goals for each. Use conditional formatting or similar visual cues to quickly highlight gaps. The discussion should naturally gravitate toward the metrics that are off track, while metrics performing as expected receive little or no airtime.
When every metric receives equal attention, the conversation becomes noise. When the meeting is focused on the handful of gaps that actually require action, teams can quickly identify root causes, make decisions, and improve performance.
A Sample WBR Structure
The design principle: input metrics drive discussion, sites meeting metric threshold are not discussed, and no one leaves without a specific commitment.
Sixty minutes works for a single site or a small network. For larger operations networks, 90 minutes is usually the better investment. The alternative to a longer, focused WBR isn’t a shorter one. It’s the same ground that ends up getting covered piecemeal: a Slack thread here, a hallway conversation there, three follow-up calls to chase down what one structured WBR input review could have resolved in the room.
The main section of the agenda is an input-by-input walk through each metric category, where the only Site Leaders who speak in a given section are the ones missing that category’s goal. A site missing on every category will naturally come up in every section, but the agenda isn’t framed around a single site deep dive. Rather, it deep dives into each input across the network.
| Time | Agenda Item | Owner | Purpose |
|---|---|---|---|
| Pre-read | Input + Output Metrics Distributed. Sites missing a metric threshold are flagged; sites meeting threshold are not discussed unless trending toward missing it. | Senior Ops Leader | Everyone arrives informed; no time wasted orienting the room |
| 5 min | Wins & Priorities: What landed well? What must move this week? | Senior Ops Leader | Sets the tone; focuses energy before the review begins |
| 10 min | Prior Action Item Review: Did last week’s commitments land? A miss requires an explanation. | Notetaker | Closes the accountability loop; repeated misses are a leadership conversation, not a WBR topic |
| 35-65 min | Input Metric Review, by Category. Work through each input metric category in turn. Only Site Leaders whose sites are missing that category's metrics speak, with root cause and a specific action plan, named steps, owners, and dates. |
Site Leaders on the hook for each category | Where the meeting earns its time. Vague plans get challenged here before they leave the room. |
| 5 min | Horizon Check: Risks, volume shifts, or operational changes in the next 2-4 weeks. | Senior Ops Leader | Prevents surprises; lets Site Leaders plan ahead rather than react |
| 5 min | Actions & Wrap: Confirm every action with a named owner, specific step, and due date. | Notetaker | No one leaves with a vague commitment. Every action is concrete and visible. |
*For networks with a high site count, narrow each category’s discussion to the sites with the largest misses, or to regional rollups if Regional Directors are on the call instead of individual Site Leaders. However, even in regional rollups, the deep dive should still focus on specific site controllable actions and plans, not a generalization.
What Real Accountability Looks Like in the Room
Real accountability is the ability to challenge a plan without demoralizing the person presenting it. The goal is not to embarrass the Site Leader; it is to help them leave with a plan that will actually improve performance.
If a site is missing pick rate and the plan is “pick up the pace,” the response is not simply to accept or reject it. The right question is: “Walk me through what is causing the miss and what specifically will change.” That either creates a stronger plan or reveals that one does not exist yet.
When a plan is vague, ask for specificity. When it is specific but optimistic, ask for contingencies. When the same target is missed repeatedly, the conversation may need to move outside the WBR into a focused performance discussion.
Conclusion
The Weekly Business Review is one of the most powerful levers a Senior Operations Leader has, and one of the most underused.
When it’s working, it does something no dashboard can: it creates a weekly moment where the organization translates data into decisions, and decisions into commitments.
When it’s not working, it becomes a ritual: a recurring hour that produces the feeling of management without the substance of it.
