A KPI Dashboard for Growing Companies: Choose 5 to 8 Numbers, Name Owners, Set a Rhythm

Why most dashboards fail

A growing company usually reaches a point where the founder can no longer feel how the business is doing just by walking around. Numbers become necessary. The common response is to build a large dashboard with every metric the software can produce. Within a month, nobody opens it. There are too many figures, nobody is sure which ones matter, and nobody is responsible for any of them.

A useful dashboard does the opposite. It is small, it is reviewed on a fixed rhythm, and every number has one named person who can explain it. Its purpose is not to impress anyone. Its purpose is to make the next decision easier: where to look, who to ask and what to change.

This article walks through a simple method. You do not need special software to follow it, and you do not need a data team. You need an afternoon with your leadership group and a willingness to leave most metrics off the page.

Start from questions, not from metrics

Before choosing any KPI, write down the five or six questions you would want answered every week if you could ask the business anything. Typical examples: Are we winning enough new work? Are we delivering it on time and to the standard we promised? Is cash coming in as fast as it goes out? Is the team stable and busy in the right way? Are customers staying and returning?

Each question then points to one or two candidate measures. This order matters. A metric chosen because it is easy to measure usually tells you little. A metric chosen because it answers a question you care about usually earns its place.

• Growth: new enquiries, proposals sent, new customers won.
• Delivery: jobs completed on time, rework or complaints, average time to complete a standard job.
• Cash: money collected, overdue invoices, cash balance against the coming month of commitments.
• People: team capacity used, open roles, resignations.
• Customers: repeat business, response time, satisfaction feedback.

Pick five to eight, and drop the rest

The limit is a discipline, not a rule of nature. Fewer than five and you will miss an important part of the business. More than eight and the page stops being read as a whole. A leadership team can hold roughly this many numbers in its head, and that is exactly the point: a dashboard should shape conversation, not replace it.

Mix leading and lagging measures. Lagging measures, such as revenue collected, tell you what already happened. Leading measures, such as proposals sent this week, hint at what is coming. A dashboard made only of lagging figures reports bad news too late to act on. Aim for at least two leading indicators.

Define each KPI and give it one owner

Two people can read the same label and mean different things. "On-time delivery" might mean delivered by the promised date, or by the original date, or within the week. Write a one-line definition for each KPI that states what is counted, from which source and over what period. If a number cannot be defined in one line, it is probably too vague to manage.

Then assign each KPI to one owner. The owner is not necessarily the person who does all the work behind the number. The owner is the person who answers the question "why is this number what it is?" in the review meeting and proposes what to do about it. Shared ownership usually means no ownership. If two people care about a figure, pick the one whose decisions affect it most.

Finally, agree on a target or a healthy range for each KPI, or at least a direction of travel. Set these with the owner, using your own recent history rather than figures borrowed from other companies. A range such as "between X and Y" is often more honest than a single target. If you have no history yet, spend the first month simply recording the numbers and set targets afterwards.

Set a review rhythm

A dashboard that is not reviewed on a schedule is decoration. Most growing companies do well with two layers. A short weekly check, fifteen to thirty minutes, looks at the fast-moving numbers such as enquiries, jobs in progress and cash collected. A longer monthly review, around an hour, looks at the full set, compares it with targets and decides what to change.

Keep the meeting format the same every time. Each owner reports their number, says in one sentence why it moved, and flags any decision they need. Where a number is outside its range, the meeting ends with an action, an owner and a date, written down. Where everything is within range, finish early. A good review meeting should feel routine, not dramatic.

Add a quarterly step. Once every three months, ask whether the dashboard still reflects the business. Strategy changes, new services launch, and a KPI that mattered last year may now be noise. This is the right moment to apply the one-in, one-out rule and retire what no longer earns its place.

Keep the tool simple

A shared spreadsheet is enough for most companies at this stage. Use one row per KPI, with columns for the definition, owner, target or range, and one column per week or month for the actual value. Add a status column using three simple states: within range, watch, and off track. Add a short comment cell for the owner. That is the whole dashboard.

Charts can come later, if at all. A small trend line next to each number helps the eye, but avoid the temptation to build visuals before the numbers are trusted. If the figures are wrong or late, polishing the display only hides the problem. Move to a dedicated reporting tool only when the manual update becomes a real burden, and connect it to the same definitions you already wrote.

Your first 30 days

In week one, hold a short session with your leadership group to agree on the questions and shortlist candidate KPIs. In week two, finalize five to eight, write definitions, and assign owners. In week three, build the spreadsheet, load the last few weeks of history where it exists, and hold the first weekly check. In week four, hold the first monthly review, note what felt unclear and fix the definitions.

Expect the first version to be imperfect. Some numbers will be hard to collect and a few will turn out not to matter. That is normal, and it is the reason to start small. If you want help designing the operating rhythm around the dashboard, Founders Hub provides operations systems support, but the method above is complete enough to begin without us.