A board pack can present a reassuring picture of customer performance.
Service levels are green. Customer satisfaction is stable. Complaints remain within tolerance. Account reviews have taken place. Renewals are broadly on target. The improvement programme is progressing.
Nothing on the page is necessarily wrong.
Now imagine placing that same page in front of a customer who has recently tried to resolve a recurring service problem, understand an incorrect invoice or get a clear decision from the organisation.
Would they recognise the business being described? What is their customer reality?
They may not dispute the figures. They may accept that calls were answered, tickets were closed and meetings took place. Their concern would be that the page bears little relationship to the effort, uncertainty and repetition they experienced.
The board pack may be accurate about what the organisation has measured and still incomplete about what the customer is living through.
A board pack is designed around management needs
Leadership reporting is naturally structured around how the organisation operates. Information is divided by function, product, channel, region, contract, programme, team or financial period. Each part of the business reports the measures for which it is responsible. That structure is necessary. Leaders need manageable information, clear accountability and a consistent way to monitor performance.
The customer does not experience the organisation in those divisions.
They may begin with sales, move through contracting and onboarding, interact with delivery or technical support, receive an invoice from finance and discuss the wider relationship with an account manager.
The customer experiences one business.
A problem can look relatively minor within each function while becoming significant across the whole relationship.
Sales may believe the handover was completed. Delivery may record that onboarding met its date. Support may show that all tickets were closed within the agreed service level. Finance may confirm that the invoice was corrected. The account team may report that regular meetings are taking place. Each statement can be true.
The customer may still remember having to repeat the same information to several people, chase progress, explain the commercial consequence and find somebody willing to take responsibility for the whole issue.
The board pack reports each part, but the customer experiences the connections between them.
The customer does not experience the KPI
Performance measures turn complex activity into manageable signals. That is their purpose.
Leaders cannot examine every interaction, case and customer journey in detail. They need indicators that help them see where confidence is justified and where attention is required. The danger comes when the indicator is treated as though it is the experience itself.
- A ticket can be closed while the customer’s underlying problem continues.
- A call can be answered quickly without the caller receiving a useful answer.
- A delivery can meet its contractual date after the customer has spent several weeks chasing uncertain information.
- An account review can take place without either side addressing the issues most likely to affect the relationship.
- A service credit can be applied without restoring confidence.
- A contract can be renewed because changing supplier would be difficult, not because the customer is satisfied.
In each example, the organisation may have completed the activity its measure was designed to record. However, the customer is judging something broader:
- Did dealing with the organisation feel easy?
- Did the business create confidence?
- Did the customer receive useful value?
- Did the interaction help them make progress?
These are familiar Customer Spectacles questions because they shift attention from what the organisation completed to what the customer experienced as a result.
A green measure may still be valid. The test is whether leadership understands the narrower question it has answered.
The organisation records events; the customer forms one conclusion
Board reporting often separates customer activity into individual events.
It counts complaints, tickets, meetings, deliveries, orders, projects and renewals. Each event has a date, owner, status and outcome.
Customers experience those events cumulatively.
One delayed response may be understandable. Repeated chasing across several teams becomes a judgement about whether the organisation is dependable.
One invoice error may be corrected. Recurring errors, slow responses and unclear ownership become evidence that the supplier is difficult to work with.
One missed commitment may be forgiven. A sequence of commitments that need to be renegotiated can change how much confidence the customer places in every future promise.
The organisation may store each event in a different system, function or reporting period.
The customer combines them into one conclusion.
This creates a particular risk for leadership teams. No individual incident appears sufficiently serious to change the reported status, but the accumulated experience is gradually changing the relationship.
The account remains green because no single measure crosses its threshold.
The customer becomes less confident because their experience does not reset at the end of the reporting month.
Customer silence is easily misread
Low complaint volumes are reassuring when they reflect a genuinely good experience. They are more dangerous when leadership assumes that silence must mean satisfaction. Customers do not raise every problem.
Some reduce their expectations and work around the supplier. Others decide that another escalation will consume more effort than the issue appears to justify. A customer may tolerate poor service because changing provider would create immediate disruption.
An internal sponsor may continue protecting the relationship while becoming increasingly frustrated. A customer may move new work elsewhere without creating a formal dispute. They may wait for a renewal, procurement exercise or leadership change before acting.
Some simply disengage. Meetings become shorter. Senior decision-makers stop attending. Requests for advice reduce. The customer shares less information about future plans. Conversations become transactional.
Nothing dramatic happens, except that the relationship becomes thinner.
This is why customer behaviour matters alongside stated satisfaction and formal complaints. Silence may reflect satisfaction. It may also reflect resignation, dependency or a declining belief that speaking up will change anything.
The board pack needs enough context to distinguish between them.
Board pack aggregation can remove the customer leadership most needs to see
Averages and portfolio measures are essential for oversight.
They can also hide important differences.
Overall retention may remain strong while strategic customers reduce their spending. Average satisfaction may look healthy while new customers struggle through onboarding. Revenue may grow while service recovery and customer exceptions erode margin.
Complaint volumes may be stable while the seriousness of the complaints increases. Delivery performance may be green overall while one customer segment experiences repeated failure. A high-value account may appear healthy within the portfolio even though its senior relationship is weakening.
The problem is not aggregation itself.
The problem is failing to ask what the aggregate has concealed.
A board cannot examine every customer individually. It should still understand whether the headline figure is being carried by strong performance in one part of the portfolio while a commercially important segment moves in the opposite direction.
The average tells leadership what happened across the population.
It does not always reveal where the next material risk or opportunity is forming.
Internal language in the board pack can sanitise customer reality
Professional reporting requires careful language.
Board packs should not become collections of emotional anecdotes or exaggerated claims. Leaders need proportionate, evidence-based descriptions.
However, internal language can sometimes create too much distance from what actually happened.
An “isolated service incident” may be the third failure experienced by the same customer in six weeks.
“Customer communication required” may mean that nobody told the customer what was happening until they escalated.
A “billing query resolved” may mean that the customer spent two months proving that the invoice was wrong.
“Account engagement reduced” may mean that the customer has stopped inviting the supplier into conversations about future plans.
“Renewal at risk” may mean that the customer no longer believes the organisation will improve.
The first versions are concise and may be technically defensible.
The second versions reveal the commercial meaning.
A useful board pack must retain discipline without removing consequence. If the language makes an uncomfortable experience sound administratively routine, leadership may underestimate what it needs to address.
The test is not whether the wording sounds more dramatic.
It is whether the wording allows the board to understand why the issue matters.
Applying the customer-recognition test to the board pack
The board pack test can be applied to any page making a claim about customer, service, delivery or commercial health.
It does not require a new reporting system.
It requires leaders to question what the existing page allows them to conclude.
1. What would the customer call this?
Would the customer use the same description?
They may agree that the issue was resolved but describe the journey as slow, repetitive or unnecessarily difficult. They may recognise the event while rejecting the organisation’s interpretation of it.
The difference in language can expose a difference in perceived consequence.
2. Which part of the customer’s experience is missing?
A report may record the final outcome while omitting the effort required to achieve it.
- How many times did the customer have to make contact?
- How many teams became involved?
- How long did they remain uncertain?
- Did they need to escalate?
- Did somebody take ownership of the whole situation?
The missing context may matter more than the closing status.
3. Is the green status describing activity or outcome?
Did the organisation complete its process, or did the customer achieve useful progress?
A completed meeting, answered call or closed ticket records activity. It does not automatically prove that the customer’s need was met.
Leaders should understand which of those two things the measure represents.
4. What would the customer add to the explanation?
This is not simply asking whether the customer agrees with the status. The more useful question is what they know or experienced that could materially change leadership’s interpretation.
They may:
- Explain that the issue is technically resolved but confidence has fallen.
- Show that an isolated failure is part of a repeated pattern.
- Reveal that the reported improvement has not reached the part of the service they depend upon most.
5. Whose experience is concealed by the average?
Which customer, segment, journey or type of problem sits furthest from the headline result?
The answer should be commercially relevant. Leadership does not need to investigate every statistical variation, but it should know when an important customer group is moving differently from the portfolio.
6. What happened across functional boundaries?
Many customer problems form in the hand-offs between teams.
Sales promises something delivery did not expect. Onboarding information does not reach support. Finance resolves the invoice without understanding the underlying service failure. The account manager knows about the commercial risk but cannot influence the operational response.
Each function may complete its own task.
The customer experiences the gaps between them.
7. What is the customer doing rather than saying?
Look beyond survey responses and complaints.
Is usage declining? Are orders becoming smaller? Are senior people attending fewer meetings? Has the customer stopped asking for advice? Are they moving work to another supplier? Are responses slower because the relationship matters less to them?
Behaviour can reveal changes the customer has not yet formally expressed.
8. What evidence would make us change the status?
Leaders should know what would cause a green page to become amber or red.
- Would repeated customer effort matter?
- Would declining engagement matter?
- Would a deteriorating strategic relationship outweigh strong portfolio averages?
- Would evidence of recurring cross-functional failure change the interpretation?
If no realistic evidence can change the status, the page is not supporting judgement. It is defending an existing conclusion.
Bringing customer reality into the board pack
Applying the test does not require a large new customer-research programme.
Many organisations already hold the relevant evidence. It is simply distributed across account management, service, complaints, billing, delivery, sales and customer-support systems.
The task is to connect enough of it to see the experience more completely.
That might involve:
- Including a short direct customer quotation where it materially changes the interpretation.
- Following one customer journey across functions rather than reporting only functional measures.
- Separating strategic customers or vulnerable segments from the portfolio average.
- Bringing account, service and commercial evidence together.
- Asking frontline employees what explanation the board pack currently misses.
- Reviewing a small number of recent cases through the customer’s eyes.
- Tracking customer behaviour alongside stated satisfaction.
- Inviting selected customers into appropriate review conversations.
The answer is not automatically more data.
A business can increase the volume of customer measures while preserving the same blind spots. If every function continues to report its own activity independently, the leadership team may receive more information without gaining a better view of the relationship.
The value comes from connecting what the organisation knows.
Customer evidence does not remove the need for judgement
The customer-recognition test must not become an argument that one unhappy customer should overrule portfolio evidence, strategic direction or commercial reality.
Customers can be mistaken. Their expectations may be unrealistic. Requests can conflict with the interests of other customers or with the sustainable operation of the business.
One quotation is not a trend. One difficult case does not invalidate strong performance elsewhere. A commercially sound decision can still disappoint an individual customer.
Leaders must continue to judge:
- Scale.
- Frequency.
- Materiality.
- Evidence quality.
- Commercial value.
- Strategic relevance.
- Appropriate trade-offs.
Customer Spectacles are not a way of surrendering leadership judgement to the loudest voice; they are a way of testing whether leadership is making that judgement with a sufficiently complete view. The customer reality may confirm the board pack. It may reveal an exception or it may expose a pattern the current measures cannot see.
The important thing is that leadership understands which of those it is looking at.
When customers would not recognise the page
If customers would not recognise the business described in the board pack, the answer is not necessarily the creation of another KPI.
The gap may exist because:
- The measure is answering the wrong question.
- Aggregation is hiding a material segment.
- Functional reporting is missing the end-to-end experience.
- Internal language has sanitised the consequence.
- Reporting is lagging behind current reality.
- The organisation is measuring process completion rather than customer progress.
- Customer evidence exists but is not reaching leadership.
Each cause requires a different response. A new measure may help in some cases. In others, leadership needs to connect evidence already held across the organisation, examine a small number of journeys or create a better route for customer and frontline reality to enter the room.
The objective is not to make the board pack longer. It is to make the leadership picture more useful.
Would customers recognise the business you are discussing?
A board pack cannot reproduce every customer experience, nor should it try.
Its purpose is to give leadership a sufficiently accurate picture to make sound decisions. That requires correct internal measures, but it also requires an understanding of whether those measures describe a business customers would recognise.
Before accepting the next green customer page, ask:
If we placed the board pack in front of the customers it describes, what would they say is missing?
The answer may not change the status, but it may change what leadership decides to do about it.
Oak CORE helps leaders connect internal reporting with customer reality as well as commercial and operational reality when the current picture feels incomplete.
If several parts of the organisation are reporting accurately but the leadership view still does not match what customers appear to be experiencing, arrange a CORE Fit Conversation.