Before You Try & Fix the Number, Diagnose What's Failed in Your Machine.
- Nathan Everett
- 5 days ago
- 5 min read
The Numbers on the Screen are Symptoms, Not Causes.
Every sales manager that I have met recently, has dashboard of some description, some have more than one. Pipeline coverage, win rate, average deal size, activity counts, deal velocity, stage conversion, quota attainment. The screens glow with certainty. The numbers look official, yet, quarter after quarter, the same gaps keep opening up in the same places.
That is because a dashboard shows you symptoms. It does not show you causes.
The symptom trap
When pipeline coverage drops to 2x against a target of 3x, the dashboard tells you the number. It does not tell you why. A sales manager will usually respond by asking the team to prospect harder. A week later the number ticks up, everyone exhales, and the real problem, whatever it was, stays exactly where it was.
Consider the common readings and what actually sits behind these numbers:
Low pipeline coverage. The surface reading is that sales reps are not prospecting enough. The cause is often that territory design has concentrated accounts in the wrong places, or that the ideal client profile was never written down, so sales reps chase anything with a pulse and discard most of it.
Poor forecast accuracy. The surface reading is that sales reps are sandbagging. The cause is usually that stage definitions in the CRM have no entry and exit criteria, so a stage 3 deal for one sales rep is a stage 5 deal for another.
Long sales cycles. The surface reading is that buyers are slow. The cause is often that no qualification framework is in use, so reps carry unqualified deals through every stage, inflating cycle time on deals that were never going to close.
Declining win rate. The surface reading is that competition has become harder. The cause is frequently that the sales process has never been mapped to how the buyer actually buys, so reps lose control of the conversation at the point where value needs to be proven.
Activity without outcome. The surface reading is that reps are busy. The cause is that there is no scorecard linking daily behaviour to the outcomes the business actually needs, so effort is spent on the wrong accounts, the wrong contacts, and the wrong conversations.
Sales force effectiveness and efficiency problems. The surface reading is that the team needs more training, or more people, or better tools. The cause is usually structural. Roles have not been separated between hunting, farming, and account management, so every rep is asked to do everything and does none of it well. Ride-along coaching has been replaced by pipeline interrogation. Onboarding is a folder of PDFs. The result is a team that is working hard at the wrong things, and a cost-per-dollar-of-revenue that quietly climbs each year.
Sales and marketing misalignment. The surface reading is that marketing leads are poor, or that sales does not follow up. The cause is that the two functions are operating from different definitions. Marketing counts MQLs against a lead scoring model that sales had no part in creating. Sales reps disqualify those leads against their own standards that have never been discussed with the marketing team. There is no shared ideal client profile, no agreed service level on lead response, and no closed-loop reporting that shows which campaigns actually produced revenue. Both teams are working. Neither team is winning.
Chasing the number on the dashboard is like taking a Panadol for a broken leg. The pain dulls for a while, but your leg is still broken.
Why this happens
Most sales departments have grown the way a house grows when you keep adding rooms without a floor plan. A CRM was installed because someone said it was time. A commission plan was written on the back of last year’s commission plan. Territories were drawn around who was hired first. Reporting was bolted on when the board asked for visibility. Each piece made sense on the day it arrived. Together, they form a function that nobody designed.
When a function is not designed, the metrics it produces cannot diagnose where the problem lies. They can only describe it. That's why the dashboard keeps showing the same symptoms, month after month, while the causes sit untouched buried underneath.
What sales architecture actually does
Sales architecture treats the sales department the way an engineer treats a building. Before you measure the load on a beam, you need to know what the beam is made of, what it is connected to, and what it is meant to carry. Apply that thinking to sales and the picture changes.
A properly designed sales function is assessed across ten dimensions: Foundation, Productivity, Organisational Design, Talent, Execution, Technology, Performance Management, Intelligence, Operating Rhythm, and Revenue Retention. Within those ten dimensions sit twenty-two modules, each one a specific part of the machine that can be examined, scored, and rebuilt. Ideal client profile. Territory coverage. Stage definitions. Scorecards. Meeting rhythm. Pipeline governance. Compensation design. Onboarding. Each module is a cause.
The dashboard is the consequence.
When I assess a business against this framework, the average score sits around 40(ish) out of a total score of 110. That is not a reflection of the sales managers running those departments. It is a reflection of how the function was built, which is to say, not built at all, but accumulated.
Once the twenty-two modules are scored, the conversation stops being about whether pipeline coverage is 2.1x or 3.5x. It starts being about which three or four modules are dragging the rest of the system down, and in what order they should be addressed. Stabilise first. Activate next. Scale after that. Optimise once the foundations hold.
From symptom to cause
The shift is simple to describe and hard to execute. It is the difference between asking, ‘Why is the forecast wrong again?’ and asking, ‘What in the design of this sales function makes an accurate forecast impossible?’ The first question produces another meeting. The second question produces a roadmap.
Dashboards are useful and I am not suggesting that they start being switched off. They tell you, quickly and cheaply, that something is wrong. What they cannot do is tell you what to fix. For that, you need a view of the whole system, scored against a standard, with a sequence for putting it right.
𝙒𝙞𝙩𝙝𝙤𝙪𝙩 𝙨𝙖𝙡𝙚𝙨 𝙖𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚™, 𝙞𝙩’𝙨 𝙟𝙪𝙨𝙩 𝙖𝙣 𝙤𝙥𝙞𝙣𝙞𝙤𝙣.
A low maturity in your sales function does not announce itself. It shows up as inconsistent revenue, over-reliance on one or two people, and a pipeline you cannot trust. The Sales Scorecard diagnoses it in less than five minutes.
Take the Test Now: https://www.immersiveinsights.com.au/scorecard
Comments