Flying Blind: The Business With No Scorecard
The founder hears about problems from angry clients, weeks late. Fix it with a 5–9 number weekly scorecard, each owned, each with an off-track trigger.
This is a representative example illustrating the method below. It is a composite scenario, not a specific named client engagement.
The constraint
A growing services business was profitable on paper and increasingly anxious in practice. Every month, the founder was surprised by something — a client threatening to leave, a project quietly running over, a hiring gap that had been obvious to the delivery lead for weeks. The information existed somewhere. It just did not exist anywhere the founder could see in time to act.
The team was not hiding anything. They simply had no shared instrument.
What was actually happening
The business had reports. It had a monthly P&L. It had a project-management tool with dashboards. It had a CRM with pipeline views. What it did not have was a single small set of numbers that leadership looked at together, weekly, that would tell them whether the business was on track before a client had to tell them it was not.
Every dashboard the team had was a lagging indicator — reporting what already happened. The founder needed leading indicators — numbers that predicted what was about to happen.
The decision
Build one scorecard, small enough to be memorized. Five to nine numbers, each owned by one person, each with an explicit "off-track" threshold that would trigger discussion in the weekly operating meeting. Not a dashboard. A scorecard.
What got built
Seven numbers. Reviewed every Monday. Each owned by a single named person. Each with a defined green / yellow / red threshold. Reviewed in the first five minutes of the weekly operating meeting: on-track numbers get no discussion, off-track numbers get parked for the issues block. Total time to review: five minutes. Total time saved downstream: hard to measure and enormous.
How to pick numbers that predict, not report
Most scorecards fail because they measure what is easy to measure, which is almost always historical output. A useful scorecard is different. The construction method:
For each critical function of the business (sales, delivery, cash, people), ask: what is the earliest observable signal that this function is drifting off-standard? Not "did we hit the goal" — that is the report. What comes before that?
Some examples of how this reframes numbers:
- Sales. Report: closed revenue last month. Leading: qualified conversations this week. The first tells you what happened. The second tells you what is about to happen.
- Delivery. Report: client NPS quarterly. Leading: number of clients whose last scheduled touchpoint slipped. The second predicts churn weeks before the first measures it.
- Cash. Report: bank balance today. Leading: invoiced but uncollected past thirty days. The second tells you where next month's cash pressure will come from.
- People. Report: turnover last year. Leading: weekly one-on-ones held versus scheduled. The second is a leading indicator of engagement and retention.
Rules of construction that keep the scorecard useful:
- Five to nine numbers. Fewer than five and you are missing something material. More than nine and no one holds them in memory.
- Each number owned by one named person. Not a team. "Ops" cannot own a number. A person can.
- Each with a specific off-track threshold, decided in advance. "Feels low" is not a threshold. A number is.
- Reviewed weekly, in the same meeting, in the same order, always. The ritual is the whole point.
- Off-track numbers are discussed. On-track numbers are not. Do not celebrate green. Attention on green is time not spent on red.
The seven numbers in this case
Specific to this business — yours will differ. Included so the shape is concrete:
- Qualified sales conversations this week. Owner: sales lead. Off-track: below eight.
- New signed contracts, trailing four weeks. Owner: sales lead. Off-track: below two.
- Active clients with a slipped touchpoint. Owner: delivery lead. Off-track: any.
- Aged receivables over thirty days. Owner: finance. Off-track: above a defined dollar value.
- Thirteen-week rolling cash view. Owner: finance. Off-track: any week below the reserve floor.
- Utilization across billable roles. Owner: delivery lead. Off-track: below seventy or above ninety.
- One-on-ones held versus scheduled, previous week. Owner: each function lead reports for their team. Off-track: below ninety percent.
What changed
Within six weeks, the founder had stopped being surprised by things that other people had known for weeks. Aged receivables — historically ignored until they became a crisis — moved before they had to be discussed. Delivery slippage was caught early enough to reassign, before it turned into a churn conversation. The scorecard was memorized by the leadership team within a month; it stopped being a document and started being how they thought about the business.
Is this you?
Symptoms: you learn about client problems from clients, not your team. You review numbers monthly, not weekly. When asked "how is the business doing this week," you answer with a feeling. Any two are true, and the constraint is visibility, not effort.
Related reading
A scorecard without a weekly meeting is a spreadsheet. If your operating rhythm is broken, fix it in parallel — see Meetings Without an Operating Rhythm. And if the numbers you can actually collect are unreliable because they live in three different tools and three different definitions, that is a documented-process problem: Tribal Knowledge Is Not a System.