Leadership Team Scorecard: Build One in a Spreadsheet

Start with the question the team keeps asking in meetings: are we about to miss something? A scorecard answers that with leading indicators, the numbers that move a week or two before the outcome you care about does. Revenue closed last month is a result. Qualified pipeline added this week is a signal.

Use these tests to decide whether a candidate measure earns a row:

• It changes at least weekly, so a weekly review can see movement.
• One named person can explain why it moved, and that person sits in the meeting.
• A red value would change what someone does that week.
• It comes from a system, not from memory, so two people pulling it get the same answer.
• It isn't a duplicate of another row measured a slightly different way.

Aim for three or four rows per function head: sales, delivery, customer, cash and people. If a function needs more than four, that function should have its own scorecard, with only its top two or three rolling up to leadership.

Build the sheet with these columns, left to right:

1. Measure: a plain name with the unit, such as "Qualified opportunities created (count)".
2. Owner: one person, not a department.
3. Target: the number that means on track.
4. Red line: the value that triggers discussion. This is usually different from the target.
5. This week and last week: two columns, so direction is visible without a chart.
6. Status: red or green only. Yellow invites debate about shades, and the meeting has five minutes.
7. Note: one line from the owner, filled in before the meeting for anything red.

Add a trailing thirteen-week sparkline or a simple up, flat, down arrow if you like, but treat it as optional. The seven columns above are enough to run the meeting.

Set the target from what the plan needs, then set the red line from what you can tolerate for one week. For example, say your delivery team's goal is to onboard a new customer in 21 days. You might make 21 the target and 28 the red line, because a single 25-day onboarding is worth a note but not an agenda item, while 28 signals a real queue.

If you don't have history for a measure, run it for four weeks without a red line. Write down the values, then set the line just outside the normal range. A red line set from a guess will either fire every week or never, and both teach the team to ignore the sheet.

For sales rows, a benchmark can help you sanity-check, not set, the target. The Ebsta x Pavilion 2025 GTM Benchmarks Report puts the average B2B new-logo win rate at 19 percent¹. Your own trailing twelve months is a better target, because your deal size and sales cycle aren't the average.

Read the scorecard top to bottom, and only say something about a red row. Green rows get no airtime. The owner of each red row states the number and the one-line cause from the note column. Then the group makes one decision: drop it onto the issues list for this meeting, or leave it for the owner to fix this week.

Two rules keep this honest. First, nobody explains a green. Second, the same row can't be red for three consecutive weeks without moving onto the issues list, since a repeat red means the owner's fix isn't working. Capture the decisions in your leadership meeting notes, and keep the scorecard itself separate so it stays one page.

Review the scorecard itself once a quarter. Remove any row that stayed green for the whole quarter and no longer predicts anything, and remove any row nobody could explain. Add a row when the same surprise showed up twice in meetings without a number warning you first.

Common mistakes to look for:

• Mixing weekly and monthly numbers on the same page, which leaves half the rows unchanged and untrusted.
• Giving one row to two owners, which means nobody answers for it.
• Tracking a metric because it's easy to pull, not because it predicts anything.
• Editing the target after a red week instead of fixing the cause.

If you later want the numbers pulled automatically, a BI tool like Metabase can read from your databases and refresh the sheet. If you want a red row to become a tracked project, Asana can link the goal to the work. Start in a spreadsheet, though. Once the team trusts the page, connecting it to tools is easy. See also the operations KPI dashboard for the deeper operational view.