A weekly scorecard has one job: to show your leadership team a problem before it shows up in the financials. That means fewer numbers than you think, and a meeting where green numbers get acknowledged and left alone. If a number can't change a decision, it doesn't belong on the scorecard, no matter how good it makes the team look.
Plenty of leaders will push back on that. They like their dashboards. I'd rather have 8 numbers that drive decisions than 40 that drive commentary.
The problem: a scorecard that reports and never warns
Most scorecards I see at growing companies started small and grew every quarter. Someone added a metric after a bad month. The board asked about something, so it went on. Marketing wanted its numbers represented. Two years later there are 30 lines, half of them lagging, a few that nobody remembers adding.
Then every week, each owner walks through their numbers one by one. Most of them are fine. The one that isn't gets the same airtime as the ones that are. Twenty minutes go by, and the team leaves without a single decision.
That's a reporting archive. It tells you what already happened. It doesn't warn you about anything.
Why more numbers feel safer and aren't
The common belief is that more metrics means more control. If you track everything, nothing slips through.
In practice it works the other way. When everything is on the scorecard, the important signal is buried in noise. People stop reading closely. Owners get good at explaining small movements instead of acting on big ones. If everything is important, nothing is important.
The other problem is that most long scorecards are heavy on financial results. Revenue, margin, cash. Those matter, but they're lagging. By the time they move, the problem is already weeks or months old.
The chain that makes a scorecard useful
The numbers worth tracking connect in a chain:
Activity predicts operations. Operations shape customer outcomes. Customer outcomes produce financial results.
A healthy scorecard has a few numbers at each link. For a services business that might look like: sales calls booked (activity), jobs completed on schedule (operations), repeat or complaint rate (customer), and gross margin (financial).
The upstream numbers are the ones that give you time to act. Say on-schedule jobs slip for three straight weeks. Customers feel it next, then they stop calling back, and only then does revenue dip. Problems almost always show up upstream first. If you wait for revenue to tell you, you're reacting to a problem that's already old.
Keep the total to 5 to 12 numbers. Each one gets one owner and a weekly target.
Run the review by exception
Here's the operating rule:
Green numbers are acknowledged and left alone. Red numbers are clarified, owned, and either fixed immediately or put on the issues list.
In the meeting, each owner reads their numbers as on or off target. No commentary on the greens. For each red, the owner gives one sentence: what changed. If it's a quick fix, they commit to it. If it isn't, it goes on the issues list to be solved properly.
A red number is ready to become an issue when you can state four things:
- The facts. What changed, with the number.
- The impact. Why it matters to the business.
- The constraint. What you think is actually causing it.
- The decision needed. What the team has to decide.
The exact words for an owner: "Jobs on schedule were 82% against a 90% target. It's the second week in a row. I think it's contractor capacity in two markets. I need us to decide whether we add capacity or slow new sales there."
That's a conversation the team can finish.
What to do this week
- Print your current scorecard.
- Next to each number, write the last decision it changed. Be honest.
- Cut every number with a blank next to it.
- Check what's left against the chain: activity, operations, customer, financial. Fill any empty link.
- Stop at 12.
The low-hanging fruit is almost always the first cut. Most teams can drop a third of their numbers in 20 minutes.
Weekly Scorecard
The Weekly Scorecard is a free tool that walks you through picking your numbers across the chain, entering them weekly, and flagging exceptions. Red numbers flow into an issues queue with the four elements above, and it produces a short, decision-focused brief for your leadership meeting. Build it with your team so each owner picks and agrees to their own numbers.
Open the Weekly Scorecard →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →