One Number, Please. Not Twelve Columns.

The Number That Should Have Been on Page One

The slide had everything.

Twelve columns, three shades of amber, and a footnote explaining that amber meant something different in the previous quarter.

It was a rather complete piece of work.

The client looked at it for a moment and asked whether the next phase of the project should go ahead.

The consultant started with the left-hand column. Then she explained the exception rule. By the time she reached the forecast assumptions, the client had stopped taking notes.

It was tragic, really.

Nobody had made a calculation error. Nobody had forgotten the data.

We had simply put the answer in a cupboard behind twelve other cupboards.

When the question is “Can we expand?”, a page needs to show the constraint first.

Pick the one number attached to that decision, put the comparison beside it, and say what happens next.

The Clutter

We tend to build metric-heavy reports for perfectly understandable reasons.

Someone wants revenue. Someone else wants utilisation. The operations team insists on capacity. Finance would like the forecast. The account manager adds three satisfaction scores because they look reassuring.

Eventually, everything makes it onto the page.

Nobody wants to remove a metric because someone, somewhere, might ask about it.

So we keep adding.

This is how reporting turns into a storage problem disguised as a design problem.

But the client is not paying us to display all available information simultaneously.

They want to know what matters now.

Imagine a client deciding whether to expand a delivery programme.

The report includes completed jobs, open tickets, total revenue, staff hours, customer feedback, regional performance, and several other perfectly respectable numbers.

Buried among them is the important figure.

On-time delivery: 81%.

The agreed target is 95%. Last month, delivery was at 89%.

There it is.

Performance is fourteen percentage points below target and has deteriorated by eight percentage points in a month.

Perhaps expanding immediately is not the best idea.

We do not need another eleven columns to understand why this deserves attention.

Of course, the other figures may help explain the problem. But they should not compete with the primary message for attention.

Here is the rule I use: the most important metric is not necessarily the biggest, most impressive, or most commercially flattering number.

It is the number most likely to change the next decision.

If the meeting is about increasing capacity, show the capacity constraint.

If it is about profitability, show the profit figure that matters.

If it is about customer retention, lead with the measure that tells us whether customers are staying.

Not all three at once, in equally large boxes.

That is not balance. That is indecision.

The Clarity

Start with the question the client is trying to answer.

Then build the page backwards from the decision.

For our delivery programme, the main section might look like this:

On-time delivery: 81%

Target: 95% | Last month: 89%

Recommendation: Resolve the delivery bottleneck before approving expansion.

Three lines.

Nobody has to decode a legend. Nobody needs to know which filter is active.

The important figure gets the largest type on the page. The comparison sits directly underneath. The recommendation follows.

Below that, I would show a small trend or a simple comparison against the target.

Not a speedometer. Not a gauge with a glowing needle and a dramatic gradient.

We are measuring deliveries, not landing an aircraft.

The visual should answer a basic question: how far are we from where we need to be?

That is enough.

The next section can explain what is driving the result. Perhaps delayed handovers account for most missed deadlines. Perhaps the team is still investigating.

If the cause is uncertain, say so.

A report that admits what we do not yet know is more useful than one that invents confidence because the template has a box labelled “Key Insight”.

Now look at the hierarchy we have created.

The first layer tells the client what matters. The second shows the comparison. The third provides the evidence.

The order is doing the work.

Illustrative before and after: the same delivery figures

BEFORE: TWELVE COLUMNS COMPETE FOR ATTENTION
+---+---+---+---+---+---+---+---+---+---+---+---+
|C01|C02|C03|C04|C05|C06|C07|C08|C09|C10|C11|C12|
+---+---+---+---+---+---+---+---+---+---+---+---+
|81%|95%|89%| --| --| --| --| --| --| --| --| --|
+---+---+---+---+---+---+---+---+---+---+---+---+
C01: on time   C02: target   C03: last month
C04-C12: secondary fields; values not supplied

+----------------------------------------------------+
| AFTER: THE DECISION LEADS                          |
|                                                    |
| 81% ON-TIME DELIVERY                               |
|                                                    |
| Target: 95%       Last month: 89%                  |
|                                                    |
| Fix the bottleneck before expansion.               |
|                                                    |
| [Full breakdown: C01-C12]                          |
+----------------------------------------------------+

The dashes mean unspecified, not zero. The article supplies only the three delivery figures, so the schematic does not invent the other nine values. The full-breakdown control represents access to the supporting detail; the before and after use identical results.

Keep the Evidence, Lose the Maze

There is a dangerous interpretation of this advice, so let us deal with it.

“One number that matters” does not mean “one number and nothing else”.

That would be dodgy reporting.

If the sample size is tiny, the client needs to know. If one region is performing terribly while the others are fine, that may change the recommendation.

Definitions, exceptions, and supporting metrics still matter.

They simply belong in the evidence layer, where they can be inspected without interrupting the main argument.

Think of the page as a short briefing rather than a miniature data warehouse.

A good briefing has a conclusion, a reason, and enough evidence to be trusted.

It does not begin with the entire filing cabinet.

There is also no permanent “one number” for every client. The figure that matters this month may become a secondary measure next month because the decision has changed.

That is fine.

A report should follow the client’s decisions, not the rigid structure of the software used to build it.

Before sending the next report, ask yourself which number you would mention first if the client rang you and had thirty seconds to talk.

Put that number on the page.

Give it a clear comparison. Explain the consequence. Keep the detailed analysis close enough to verify.

If the client responds, “Right, we need to fix that first,” the report has done its job.

No dramatic reveal. No complicated dashboard.

Just a decision.

Spot on.

FAQs

How do I choose the one number that matters in a client report?

Start with the decision the client needs to make. Select the metric most likely to change that decision, then give it a target or meaningful comparison.

Can one KPI accurately represent a complex project?

Not on its own. One KPI should lead each decision-focused page, supported by enough context and secondary metrics to explain what is happening.

What should I do with the other metrics?

Keep them in a clearly labelled supporting section or appendix. The client should be able to investigate the detail without being forced to navigate it first.