> ## Content Index > Fetch the complete content index at: https://www.darlison.com/llms.txt > Use this file to discover other available public pages before exploring further. # Scoreboard Day And The Weekly Leadership Review - URL: https://www.darlison.com/scoreboard-day/ - Published: 2025-12-15T15:21:06.000Z - Updated: 2026-08-24T11:39:07.000Z - Description: How to actually use dashboards to ignite continuous improvement: a simple weekly rhythm where Scoreboard Day exposes the numbers, Fritz-style situation reports explain every red, and a focused leadership status review turns gaps into structural fixes. - Author: Byron Darlison - Tags: Scoreboard Day, Scoreboard, execution, Accountability, Critical Number, business operating system, strategy, Operating Rhythm, Leadership Meetings, Robert Fritz, Managerial Moment of Truth Most leadership teams I meet are drowning in data and still missing their numbers. Every quarter brings more dashboards, more KPIs, and more meetings. The issues look familiar, the language sounds sophisticated, but the same problems keep coming back unchanged. The pattern is usually the same. Targets are missed, so the response is to add metrics and drag more people into longer meetings. Those meetings turn into unfocused post-mortems where everyone has a story, nobody has clean ownership, and the “fix” is some version of work harder, be more accountable, push the team. Very little changes in the actual structure of how the business runs, so results do not change either. This article is for founders and leadership teams who are tired of that cycle and want something simpler: a way to see reality clearly, assign ownership cleanly, and make structural corrections without consuming the whole leadership team in every problem. Two things happen every week: Scoreboard Day and a Leadership Status Review. A red number on the Scoreboard produces a written Situation Report, which is what travels from the first to the second. A Small-Group Decide Meeting is optional, and happens only when a situation is too complicated to settle in the leadership meeting itself. Together they create a loop where every red number is treated as a structural test, not an occasion for drama. The key to this process is a simple pattern from Robert Fritz’s book The Managerial Moment of Truth: situation, cause, correction, and follow-up. That structure turns missed results into concrete structural learning instead of blame. What I have done is embed it into a straightforward weekly cadence that any team can run with whatever tools they already have and a bit of discipline. The rest of this article works through it in order: what has to be in place before any of this makes sense, what a Scoreboard holds and where its targets come from, each of Fritz’s four parts and what a good one looks like, and the leadership meeting that turns them into decisions. ### ***Where Scoreboard Day fits in the system*** In earlier articles I described two tools that must be in place before Scoreboard Day makes sense: the [Key Function Flow Map](https://www.darlison.com/how-your-company-makes-money/) and the [Functional Accountability Chart](https://www.darlison.com/how-your-company-makes-money/). The Key Function Flow Map describes how value and cash move through your business, end-to-end. It forces you to make the customer journey explicit and to name the Functions along the way. The Functional Accountability Chart takes those Functions and assigns 1 owner to each, with 1 Critical Number per Function and clear green, yellow, and red thresholds. In that article I laid out four blunt tests for it. It must define success for the Function. It must be under the owner's control, assuming the inputs they were promised arrive. It must be close enough to the work that they have a decent sense most days whether they are on track. And it must not be easy to game in a way that hurts the rest of the business. Once that groundwork is laid, a Scoreboard almost builds itself. It is simply a single view of those Functions and their Critical Numbers, with thresholds and history. The head of the company (usually the CEO) owns the Scoreboard as a whole and is accountable for the overall outcome and the cross-Function trade-offs it reveals. The CEO also carries their own Critical Number on it, alongside everyone else's. What that number should be depends on what you want out of the company, and it is worth being honest about that before you choose. If you are building something to hold, a business you intend to run for a long time or pass on, cash reserve is one number that could represent that: how many months of cash expense sit in the bank. If you are building to sell, the Rule of 40 might serve you better, because growth plus margin is what a buyer prices. Those are examples, not a prescription, and there are others. The test is whether the number reflects the trade-off you are actually making between growth and profit, because that trade-off belongs to the CEO and nobody else. ### ***Scoreboard vs Scoreboard Day*** A Scoreboard is a simple, shared place where you capture: - each Function - the name of its Critical Number - the target for that week, posted beside the result rather than left implied - the green, yellow, and red thresholds - the result for each week, kept as a running history ![A Scoreboard: the head of the company above the Functions, each with the week's target above the week's posted result, newest week at the left](https://storage.ghost.io/c/42/33/4233497c-fcb6-4830-b40a-012948df926f/content/images/2026/08/scoreboard-artifact.png) A Google Sheet is all you need, and I would start there before anything more sophisticated. Everyone sees the same numbers the moment they are posted, and it takes almost no effort to maintain. Keep the most recent week in the far left column and let earlier weeks move right, so the current status and a short trend for each Function are obvious the moment you open it. The template below is built that way. Without a target beside it, a red number is only an opinion. The target is not a judgment call made at the start of the week. It comes from the 36 month forecast, and specifically from the Approved column: the plan the leadership team locked at the start of the year. Take the Function's number for that month and share it across the month's weeks. Do not take it from the Rolling column. Rolling moves every month, so a forecast that is drifting downwards would quietly lower the target and hide the miss you are trying to see. Share it by working days rather than by weeks, so a short week over a holiday is not asked to do a full week's work. Then check whether the Critical Number is something the Function produces or something it holds. Leads, closes and tickets are produced, so they divide across the month. A backlog, a headcount or a cash reserve is held, so it does not divide: the weekly target is the standard itself. Divide one of those by four and you will mark a Function green for holding a quarter of what you asked for. Two different things are at work. The forecast sets the number. The Functional Accountability Chart sets the bands around it: how far below target is yellow, and how far is red. Both are agreed before the week starts, so when a number lands nobody is arguing about how serious it is. The severity was settled in advance, and the conversation goes straight to the situation. If you do not have a forecast to take those numbers from, you can learn how to build one in [Cash! Who Owns the Forecast?](https://www.darlison.com/who-owns-the-forecast/). It covers how the forecast is built, and who owns each number in it. The template below is a worked example from a fictional company: a summary page carrying every Function's Critical Number, and a tab for each Function holding the rest of the numbers it watches. Only the Critical Number on the summary page triggers a Situation Report when it goes red. The others are there to help the owner work out why. Its targets come from the Approved column of the 36 month forecast that ships with it, and it colors itself: type a result under a target and the cell turns green, yellow or red on its own. Weekly Scoreboard Template The Google Sheet from this article, and the Excel version. A tab per function, and cells that colour themselves. [⇩ Template](https://www.darlison.com/scoreboard-tools/) ### ***Scoreboard Day is not a meeting. It is a rule.*** Once per week, on the same day, all Critical Numbers must be updated by 10:00 a.m. by the owner of the Function or their delegate. That is it. No debate. No discussion. The rule does the work. Pick your own day. What matters is that it never moves, so nobody has to be reminded and nobody has to ask. By 10:00 a.m. on Scoreboard Day, anyone in the company can look at the Scoreboard and see: - which Functions are green, yellow, or red this week - how each Critical Number has been trending over the past few weeks Scoreboard Day’s job is to make reality visible. It does not try to solve anything. It simply reveals where the structure of the business is and is not producing the results you want. Every Critical Number that is red on Scoreboard Day then does one more important thing: it triggers a written Situation Report which is where Robert Fritz’s work comes in. In The Managerial Moment of Truth, Fritz describes the moment of truth as the point where you stop rationalizing and confront the gap between what you wanted and what actually happened. The value is not in blaming people for the miss. The value is in using that gap to understand and change the underlying structure that produced it. I use his structure directly. For every Critical Number that goes red on Scoreboard Day, the owner writes exactly 1 Situation Report with 4 sections: - Situation - Cause - Correction - Follow-up The credit for that pattern belongs to Fritz. What follows is my interpretation of how each part should work inside this operating rhythm. ### ***Situation*** The Situation section describes, in plain factual terms, what happened versus the target. You are answering: what is the gap? “Target was 10 onboarded customers this week. We completed 3.” “The Critical Number is average days to collect invoices. Green is ≤35 days. This week we were at 49 days.” No stories. No excuses. No interpretations. Someone outside your Function should be able to read the Situation and picture what happened without needing a call. ### ***Cause*** The Cause section explains why that result was likely, given the way you have set things up. Fritz is explicit that “they need to try harder” is almost never the real cause. Structure is. You are looking for structural causes: capacity, policies, incentives, handoffs, priorities, missing ownership, broken processes. “The sales team closed 14 deals with start dates in the same week. Onboarding has capacity for 5 per week. There is no mechanism for onboarding to veto dates in the proposal stage. Overcommitment is built into the structure.” “We changed payment terms to net 45 for enterprise customers but left the Critical Number definition at 35 days. The number is now misaligned with our policy. It will trend red by design.” “No 1 person owns collections. It is a side task split across 3 roles. When things get busy, it loses every priority battle.” If your Cause section routinely comes down to motivation or attitude, you are not using this framework properly. ### ***Correction*** The Correction section describes the structural change or set of actions you will put in place so that the same situation is less likely to happen again. The test is simple. If you ran the same week again with this correction already in place, would you expect a different result? “Freeze new onboarding start dates for 2 weeks while we clear the backlog. Cap future start dates at 5 per week. Require onboarding sign-off on all proposed start dates before a deal is closed.” “Redefine the Critical Number to match net 45 terms and add a leading indicator for invoices past 30 days. Set green at ≥90% of invoices collected within terms.” “Move all collections work to 1 named owner in Finance. Block time daily for collections and remove ad hoc collections work from Sales.” Correction is not “I will work harder” or “I will talk to the team.” It is a structural change. ### ***Follow-up*** The Follow-up section defines how and when you will test whether the Correction worked. There is a date, a metric, and a check-in. “In 6 weeks we expect to be processing ≥5 onboardings per week with a backlog of ≤2\. We will review this number in the leadership meeting that week.” “In 4 weeks we will review the percentage of invoices collected within terms. If we are still below 90%, we will revisit either payment terms or how we chase late invoices.” The Follow-up date is not a formality. It is the point at which you compare the story you told in the Situation Report with the actual behavior of the number over time and decide whether you learned something or just wrote something that sounded good. ### ***One red, one report, one follow-up date*** I enforce a simple rule: every Critical Number that goes red produces exactly 1 Situation Report and 1 Follow-up date. A number that stays red in the meantime does not earn another report. It already has one, with a date on it, and the correction has been given until that date to work. Writing it up again every week is how this turns into paperwork. When the Follow-up date arrives, there are only 2 outcomes. The Critical Number is back in range. The situation is closed. You do not edit the old report or push the follow-up out. You move on. The Critical Number is still red. The correction did not work, and that is a new situation. It earns a new Situation Report, with a new Cause, a new Correction, and a new Follow-up date. You can reference the previous attempt, but you do not reuse it. This avoids zombie issues and bureaucratic novels. It forces you to admit when a Correction did not work and to treat that as fresh information. ### ***Timing*** In my company, Scoreboard Day was Thursday. Owners updated their Critical Numbers by 10:00 a.m. on Thursday. Any red number triggered a Situation Report. Those written reports were due to the leadership team by end of day on Friday. You can pick different days to fit your calendar. The important part is the rhythm: Scoreboard Day exposes the reds. The following day forces owners to confront them in writing. The next leadership meeting reviews the situations and routes the work. ### ***The Leadership Status Review*** The weekly leadership team meeting that follows this work is a Leadership Status Review, not a live problem-solving session. At a minimum the inputs for this meeting are: - the updated Scoreboard - the Situation Reports for every red Critical Number - any Follow-up dates that fall in the current week The purpose of the meeting is to align on reality, confirm the Corrections that have cross-team or resource implications, and delegate anything that needs deeper work to the smallest group that can resolve it. I find it useful to think in 3 categories as we move through the situations. First, there are Corrections that live entirely within a single Function and require no extra resources or cross-team changes. In those cases, the leadership team reads the Situation Report, asks clarifying questions if needed, confirms that the owner owns the Correction, and moves on. There is no redesign of their Function in the room. Second, there are Corrections that affect multiple Functions, priorities, or budgets. These need leadership confirmation because they change commitments across the company. The leadership team’s job is to test whether the proposed structural Correction is the right move and, if it is, to confirm the resource and priority changes that go with it. If it is not, the owner is sent back to rethink. Third, and this should be the exception rather than the habit, there are situations where the Cause or Correction is still fuzzy or the implications are complex. The leadership team does not debug those live. It names a small group, the owner plus whoever else is essential, gives that group an owner and a “decide by” date, and expects a short written update when they are done. If every red is ending up here, the reports are arriving half-finished and that is the thing to fix. That group meets on its own time, not the leadership team's. It has whatever format suits the problem. What is fixed is the output: by the decide-by date, a short written update saying what was decided, which goes back to the leadership team the same way a Situation Report does. Nobody reconvenes to hear it. Throughout, the meeting stays a status and routing forum. It aligns everyone on reality and ensures that every red either has an accepted structural Correction in motion or a named group working it. It does not try to pull the entire leadership team into every operational rabbit hole. ### ***Why the Follow-up date matters*** If you do not enforce the Follow-up date, the whole system collapses into theater. Without Follow-up, Corrections become aspirations. People optimize for writing a smart-sounding Situation Report rather than for making a structural change that will move the number by a given date. With Follow-up, every Correction becomes a test. When the date hits, you look at the history on the Scoreboard and ask a simple question: did this structure change the behavior of the number in the way we expected? If yes, you have learned something that is now part of how you run the business. If no, you have also learned something: your understanding of the structure was incomplete or wrong. That realization is the starting point for the next Situation Report. I also treat missed Follow-up dates as a problem in their own right. If an owner routinely ignores their Follow-up commitments, that is a structural signal about priorities, capacity, or culture. ### ***A note on leadership accountability*** It is important not to weaponize this system downwards. A Function owner is accountable for their Critical Number; the head of the company is accountable for the pattern across all of them. If one Function is occasionally red, that is local execution and local structure. If many Functions are red quarter after quarter, that is a signal that the way the company is set up is wrong. Only the CEO can change that. In other words, a chronically red Scoreboard is feedback about leadership, not a reason to demand that everyone else “try harder”. ### ***What this rhythm solves*** Done properly, this rhythm addresses the pattern I described at the start. Missed results no longer lead automatically to longer meetings, more dashboards, and vague calls to try harder. Every red Critical Number produces 1 written Situation Report with a structural Cause, a specific Correction, and a real Follow-up date. The Scoreboard and its weekly history keep everyone honest about what is actually happening. The Leadership Status Review aligns the team on reality, confirms cross-team Corrections that matter, and keeps most of the detailed problem-solving in small groups close to the work. Over time, fewer issues recur. You can see the story in the Scoreboard: a number drifts red, gets a structural Correction, and then settles back into green. You get back leadership time and attention. Ownership stops being a slogan and starts being visible behavior. Weekly Scoreboard Template The Google Sheet from this article, and the Excel version. A tab per function, and cells that colour themselves. [⇩ Template](https://www.darlison.com/scoreboard-tools/) None of this is complicated. It does require discipline, and a commitment to take reality seriously. Put it in place and you will still miss numbers from time to time. The difference is that each miss will leave the business structurally stronger rather than just more tired. --- *Related articles:* - [*How Your Company Makes Money*](https://www.darlison.com/how-your-company-makes-money/) covers the KFFM and the FAC, where Functions, owners and Critical Numbers come from - [*Cash! Who Owns the Forecast?*](https://www.darlison.com/who-owns-the-forecast/) covers the forecast the weekly targets are taken from - [*The Eight Meetings That Run Your Company*](https://www.darlison.com/the-eight-meetings-that-run-your-company/) covers where the Leadership Status Review sits in the wider meeting cadence - [*Situations That Won't Go Away*](https://www.darlison.com/situations-that-wont-go-away/) is where I first wrote about Fritz's approach to a situation that will not resolve itself