Which performance difference is operational, and which is explained by the market or capacity?
Normalise what must be fair, preserve the local context that explains demand, and investigate transitions before ranking totals.
Illustrative diagnostic only. Replace the sample values with a consistently defined cohort before using the view for a commercial decision.
01
Totals confuse opportunity with execution
A large location can produce more revenue while converting poorly. A smaller location can show a high conversion rate because capacity constraints filter demand before it enters the report. Ranking either number alone invites the wrong management response.
Start with the customer journey and compare the same transition using the same definitions. Then show the context capable of explaining the difference: lead mix, catchment, available hours, service range, maturity and staffing.
02
Standardise definitions before targets
Every location must agree what counts as a qualified enquiry, response, appointment, sale, successful delivery and retained customer. Local labels can remain in operational tools, but the reporting translation must be explicit.
Test the definition with real edge cases. Transfers, duplicate enquiries, shared customers, temporary closures and central sales teams can distort a comparison unless ownership rules are decided in advance.
- One event definition and time basis
- One rule for transfers and duplicates
- Capacity and opening-time context
- Comparable cohorts or maturity bands
- Visible completeness for every location
03
Compare transitions and constraints
Use a compact scorecard across response, qualified conversion, delivery and retention. Highlight where a location materially differs from the network range, then open the underlying cases. The purpose is to form a question, not declare a verdict.
If demand is strong and response is slow, capacity or ownership may be the constraint. If response is strong but qualified conversion is weak, investigate offer, source mix and local sales practice. Different constraints require different support.
04
Find practices that survive transfer
A high-performing location may rely on one exceptional person, a favourable market or a repeatable practice. Observe the work before copying the number. Document the trigger, action, role and evidence that make the practice function.
Pilot the practice in one comparable location and watch for unintended effects. A faster response standard that damages service delivery is not a transferable win; it is a shifted bottleneck.
05
Use comparison for support, not theatre
Share the scorecard with enough context for local teams to recognise their reality. Invite explanation before prescribing action, and distinguish controllable operating standards from central constraints such as pricing, media allocation or system limitations.
The review should end with one hypothesis per outlier, a named owner and a period for learning. Public rankings without diagnostic support encourage teams to game inputs or reject the reporting entirely.
Field checklist
Run the diagnostic
- Agree network definitions and test edge cases.
- Add capacity, service mix and maturity context.
- Compare transition rates before total outcomes.
- Inspect underlying cases and observe the local practice.
- Pilot transferable changes before network-wide rollout.