Why Outstanding Performance Is Not Enough to Earn Recognition

Every time I sit with a leadership team after a lower-than-expected assessment result, the same question arrives in almost identical words: “We genuinely do good work — why didn’t that come through?”

In most cases the answer is uncomfortable: the performance was real, but it reached the assessor in a form that made it impossible to credit.

This article is about that distance specifically: how it forms, where it hides, why better writing does not close it, and what it actually takes to close.

The gap is not in the work. It is in the reading of it.

An organisation that works hard knows its own value from the inside. It knows how long the project took, what complexity it absorbed, who stayed late to finish it, how many times the design was reworked before it settled. None of that internal knowledge travels automatically to someone reading the submission from the outside.

An assessor does not see effort. They see what was written. And if what was written is a list of activities, activities are what they will score — not impact.

This distance is what I call the Impact Gap: the space between what an organisation actually achieved and what it can demonstrate in a form that is understandable and assessable.

Because the gap is invisible from the inside, its most dangerous quality is that it is almost always misdiagnosed. The organisation assumes the problem lies with the assessor, or the criteria, or the luck of the cycle. It rarely considers the simpler possibility: that what it sent was not enough for someone who had not been on the journey with it.

Why internal knowledge does not travel on its own

There is a well-documented phenomenon in cognitive science called the curse of knowledge: once you know something well, it becomes extremely difficult to imagine how it looks to someone who does not.

A team that spent eighteen months on a digital transformation writes a sentence like “we launched the unified platform” while seeing everything behind it: the integration with eleven legacy systems, the internal resistance, the hard decision to shut down an entire workstream in month nine.

The assessor sees five words.

This is not a failure of intelligence or diligence. It is a structural problem in how knowledge transfers, and it is only solved by a deliberate decision: to write for the person who was not there, rather than the person who was.

Where the gap actually forms

In my experience the gap does not form at the moment of writing. It forms long before, at four points.

1. At measurement: we measured what was easy to count

Many organisations measure what can be easily counted — number of workshops, number of beneficiaries, number of visits — rather than what genuinely expresses change.

When submission time arrives, the organisation finds itself holding many numbers that say nothing important, and missing the single number that would have said everything.

The remedy does not begin in the submission. It begins in the design of the initiative itself: what question do we want to answer a year from now, and what data must we start collecting today to be able to answer it?

2. At documentation: it happened and was never recorded

This is the most painful category. The organisation genuinely did something excellent, but there is no written trace: no minutes recording the decision, no pre-intervention measurement, no documentation of the case that was resolved.

Two years later, when the submission needs evidence, the team faces two options: write a claim with no support, or delete the achievement. Both are losses.

The practical rule is blunt: if it was not documented when it happened, it will later be treated as though it did not happen.

3. At framing: we described what we did, not what changed

This gap looks linguistic on the surface and is methodological underneath. I will come back to it, because it costs more points than anything else.

4. At timing: we wrote in the final weeks

A submission that begins a month before the deadline is necessarily an act of retrieval, not construction. The team tries to remember, searches old email, and asks busy departments for numbers.

The predictable result: a submission that reflects what a team could gather in one month, not what an organisation achieved in three years.

Activity, output and impact

This distinction is the foundation, and most submissions stop at the first or second level.

Activity is what we did: “we delivered 12 training workshops”.

Output is what came out directly: “400 employees were trained and 360 passed the assessment”.

Impact is what changed in the world as a result: “average transaction completion time fell from 14 minutes to 9.6 minutes over six months, saving approximately 44,000 waiting hours annually across 60,000 customers”.

Notice what appeared in the third move: a baseline (14 minutes), a timeframe (six months), a population (60,000), and an understandable unit of value (waiting hours).

The first sentence describes the organisation. The third describes the difference the organisation made. Assessors award points for the third.

A practical exercise: the same achievement, three ways

Take one achievement in your organisation and write it three times:

• Version one: what did we do? (activity)
• Version two: what did we produce? (output)
• Version three: what is different for someone outside the organisation? (impact)

If you cannot write the third version, you are facing one of two possibilities: either the impact was never measured, or the achievement is smaller than you believed. Both are worth knowing before an assessor discovers them.

Four readers — four different ways of reading

The other reason the gap widens is that organisations write for one imagined audience, while their work is in fact read by four very different ones.

The assessor

Reads for evidence and consistency. They are not looking to be impressed; they are looking to award a score they can defend to colleagues. Every unsupported sentence makes that harder — so they mark down.

Leadership

Reads for the decision. What does this mean for next year’s budget? Do we scale or stop? Leadership does not need the full narrative, only the conclusion and the numbers holding it up.

The market and partners

Read for trust and differentiation. What does this entity do well that others do not? Is it worth being associated with?

The employee who joins in five years

This is the reader almost every organisation forgets. Years from now, the submission or report will be the only institutional memory left. If it was written as a list of activities, the organisation will have permanently lost the reasoning behind its own decisions.

Good narrative serves all four with the same structure, because it is built on evidence — and evidence is the common denominator between them.

What the gap actually costs

The Impact Gap is sometimes treated as a matter of reputation or moral recognition. In practice its cost is operational and financial.

• Rework every cycle. An organisation without an evidence system rebuilds its submission from zero every two years, at a cost measured in hundreds of working hours.
• Weaker budget positions. A department that cannot evidence its impact enters budget discussions from a weaker position than one that can — even when its actual performance is better.
• Lost partnerships. A potential partner evaluates on what it can verify, not on what it is told.
• Erosion of institutional memory. When the person who knows the story leaves, the story leaves with them.
• Retention effects. Teams whose impact is never visible lose motivation gradually — the hardest thing to measure and the most expensive to lose.

A quick diagnostic: seven questions for your current submission

Take any submission or report your organisation has produced and answer honestly:

1. Does every headline number carry a baseline, or do the numbers stand alone?
2. Can every claim be traced to a data source that can be returned to?
3. Does the organisation describe how it decided, or only the outcome?
4. Is there at least one external comparison?
5. Is what did not work mentioned, along with the correction made?
6. If the organisation’s name were removed, would the text remain distinctive — or could it belong to anyone?
7. Do all departments describe the same achievement in the same way?

Every “no” is a lost scoring opportunity — and also a fixable one.

A detailed example: the same paragraph, before and after

Because talking about impact in the abstract stays abstract, here is a realistic paragraph in two versions. It is composed from multiple cases, not any single entity.

Version one — as it is usually written

“In line with the entity’s commitment to improving customer experience and in alignment with strategic directions, the customer services development initiative was launched, comprising a number of training workshops and the updating of internal systems. The initiative was very well received and contributed to raising satisfaction levels significantly.”

Read it as an assessor would:

• “In line with the entity’s commitment” — decorative language carrying no information.
• “a number of training workshops” — how many, and for whom?
• “updating of internal systems” — which systems, and what changed in them?
• “very well received” — on what evidence?
• “significantly” — from what, to what?

The entire paragraph contains not one verifiable number. An assessor could not award it a high score even if they wanted to, because they could not justify it.

Version two — the same facts, with an evidence structure

“Average completion time for licence renewal was 14 minutes in Q1 2024, against 8 minutes at a reference entity in the same sector. Process analysis showed that 61% of that time was consumed by a single manual verification step.

The step was redesigned through automated integration with the licensing register, supported by training for 400 of 430 employees in the relevant units (93% coverage).

The average fell to 9.6 minutes within six months (−31%), saving approximately 44,000 waiting hours annually across 60,000 customers. Satisfaction for this service rose from 78% to 91% over the same period, while the entity’s overall satisfaction index remained flat at 85% — indicating the improvement is attributable to the intervention rather than a general trend.

The first phase did not succeed in two peripheral units due to weak network connectivity; deployment there was deferred by three months pending infrastructure upgrades.”

Notice what entered the text:

• A baseline (14 minutes) and an external comparison (8 minutes at a reference entity).
• A diagnosis explaining the cause (61% in one step) — which is what proves method rather than improvisation.
• A coverage rate (93%) rather than an absolute count.
• Variable isolation: comparing the specific index against the general one to rule out an alternative explanation.
• An acknowledgement of what did not work, and how it was handled.

The facts did not change. The organisation did exactly the same things. What changed is that the work became assessable.

The evidence inventory: where to actually start

The most common question at this point is “where do we begin?” The answer is not “begin writing”. It is “begin with an inventory”.

An evidence inventory is a simple two-day exercise that saves weeks later. Gather a small team and complete four columns for each major achievement:

1. The claim: what are we saying? (one sentence)
2. The evidence: where is the data supporting it? (system, report, file)
3. The comparison: against what are we measuring it?
4. The owner: who can extract and verify this evidence?

Three kinds of rows will emerge.

Complete rows — ready to use, and usually fewer than expected.

Rows missing evidence — the achievement is real but unprovable. Here the decision is binary: extract the evidence if possible, or lower the claim to match what can be proven.

Rows with no owner — the most dangerous. An achievement whose data nobody owns means the organisation has lost control of its own memory. Fix these first.

How to write “what did not work” without damage

What organisations fear most is admitting failure. The paradox is that concealing it is what causes the damage.

A professional assessor knows any initiative of real scale met obstacles. So when they read a submission that is flawless from the first line to the last, they conclude one of two things: either the initiative was small, or the submission is not candid. Both lower the score.

Writing failure well follows three rules:

• State what happened precisely — without apology and without drama.
• Explain how it was detected — which is, in fact, evidence of a mature monitoring system.
• Connect it to the adjustment made and its result.

For example: “The quarterly review showed adoption in peripheral units had reached only 34% against a 70% target. Analysis attributed this to connectivity rather than user resistance, so priorities were resequenced to upgrade infrastructure first; adoption reached 81% the following quarter.”

That paragraph does not weaken a submission. It strengthens it, because it demonstrates measurement, analysis and the capacity to correct course — precisely what a learning-and-improvement criterion is looking for.

From the two-month scramble to a twelve-month cycle

The difference between organisations that improve each cycle and those that plateau is not talent. It is timing.

Here is an annual cycle worth adopting.

Q1 — Foundation. Identify which initiatives will be told, assign an owner to each, and begin baseline measurement where none exists.

Q2 — Running documentation. No submission writing yet; only continuous evidence collection. Decision minutes, system extracts, beneficiary feedback.

Q3 — First draft and critical review. The draft is written and then — most importantly — reviewed by someone who was not involved in the initiative. The person who was not there is the best person to find the gap.

Q4 — Verification and preparation. Reconcile every number with its source, assemble the supporting evidence file, and rehearse the likely questions.

A side benefit of this cycle is that it improves the performance itself, not only its presentation. When teams know their impact will be measured and told, they begin designing work to be measurable from the start.

Who owns the evidence? A governance question, not a writing one

In many organisations institutional narrative is an additional task handed to whoever has time or writes well. That is the root cause of quality swinging between cycles.

Organisations whose results stabilised distributed the roles clearly across three levels.

The initiative owner. Accountable for the accuracy of facts and figures in their area. They do not necessarily write, but they sign off on accuracy. Without this role, review becomes collective guesswork.

The narrative owner. One person accountable for consistency across all initiatives: the same structure, the same terminology, the same standard of evidence. This is the role that prevents competing versions from appearing.

The independent reviewer. Someone outside the team who reads with an assessor’s mindset and asks the hard questions before anyone else does. Their essential qualification is that they were not involved.

Where these roles are absent, the organisation restarts every cycle and depends on the memory of individuals who may leave.

Multi-year initiatives: a particular problem

Initiatives running three or four years face a challenge short projects do not: the story changes over time, and the team forgets why a decision was taken in year one.

The common mistake is narrating the initiative as a straight line from planning to success. In reality any long initiative passed through a rethink — and hiding that makes the narrative flat and unconvincing.

The better approach narrates it as stages of maturity rather than a sequence of events:

• Stage one: what assumption did we start with?
• What we learned: which part of the assumption held, and which failed?
• Stage two: how did we redesign on that basis?
• Where we are now: and which indicator evidences it?

This structure turns time from a liability into evidence: an organisation that learned across four years is stronger than one claiming it got everything right on the first attempt.

Terminology discipline: a small detail with large consequences

One of the quietest things that weakens submissions is using different terms for the same thing.

“Customer” in one section, “beneficiary” in another, “client” in a third. Or an indicator called “completion time” in one place and “transaction duration” in another, with slightly different figures.

Internal readers do not notice, because they know these are the same thing. An assessor notices immediately and assumes one of two things: either they are genuinely different indicators, or the data is not disciplined. Both are damaging.

The fix is cheap: a one-page glossary agreed before writing, defining for each indicator its official name, precise definition, unit and source. Twenty lines can prevent a significant scoring deduction.

What if you discover the gap three weeks before the deadline?

This is a realistic scenario and deserves a realistic answer rather than an ideal one.

In that position, do not try to close every gap. Triage.

First: protect the submission’s credibility. Scan for any claim you cannot evidence within three weeks, and lower it to match the available proof. A weaker honest sentence beats a strong one that collapses at the first question.

Second: concentrate on two or three initiatives. Three told in depth with full evidence beats ten mentioned superficially. Assessors reward depth, not volume.

Third: extract what is automatically available. Service systems, HR systems and contact centres record more than people assume. One week with a technical team can produce the missing baselines.

Fourth: document the gaps for next cycle. Every gap you find now and cannot close is a line item in next year’s plan. Organisations that do this improve cycle after cycle; those that do not repeat the same crisis.

The first ninety days: a practical start

If you are reading this while responsible for an upcoming submission, here is a plan you can start immediately without large approvals or budget.

Week one — choose only three initiatives. Do not try to cover everything. Choose the ones with real data available, not the ones that sound most impressive. A glamorous initiative without evidence is a liability; a modest documented one is an asset.

Weeks two and three — run the evidence inventory. The four columns above. Involve people who know the systems, not only people who write well. The normal outcome is discovering that a third of what you intended to say cannot be proven — which is the best possible discovery at this stage.

Month two — close the closable data gaps. Some baselines can be reconstructed retrospectively from system logs. Some cannot. What cannot be reconstructed, start measuring today so it exists next cycle.

Month three — write one draft and have it reviewed from outside the team. Give it to an intelligent person who was not involved and ask for one thing: mark every sentence they do not understand or do not believe. Do not defend any mark — just record it. Those marks are an exact map of your gap.

After ninety days the submission will not be ready, but you will know precisely where you stand — which already puts you ahead of most organisations.

Phrases that weaken a submission unnoticed

Certain phrases recur in institutional documents and look neutral, but read as weakness signals. The most common, with alternatives:

“In alignment with strategic directions…” — opens thousands of paragraphs, carries no information, and consumes the first line, which is the most valuable line you have. Instead: open with the problem or the number.

“It was launched…” — the passive voice hides both the actor and the decision. Assessors want to know who decided and why. Instead: “The operations team decided to redesign the step after analysis showed…”

“Significantly” / “considerably” / “a marked improvement” — all linguistic substitutes for a missing number. If the number exists, use it; if it does not, the sentence is not ready.

“The first of its kind” — a uniqueness claim with no defined scope. First across what, verified against which scan? If you cannot define scope and source, delete the claim — one unverified claim undermines trust in the rest.

“The initiative contributed to…” — a weak verb implying an uncertain relationship. If the relationship is causal, prove it by isolating the variable; if it is only correlation, say so plainly. Candour here reads as maturity, not retreat.

The governing rule: any phrase that adds neither a fact, a number nor a reason is wasted space in a page-limited document.

Three objections I always hear

“We don’t have data”

You usually have more than you think, but it is spread across systems that do not talk to each other. Start with a simple inventory: which systems record something automatically? A usable baseline is often already there.

And if it genuinely does not exist, start measuring today. The worst decision is deferring measurement another year and meeting the same problem again.

“Our work is qualitative and cannot be measured”

Qualitative value is measured through disciplined qualitative methods: documented case studies, content analysis of beneficiary feedback, structured before-and-after interviews. Assessors do not necessarily ask for a number — they ask for methodical evidence. The difference is significant.

“There is nobody to compare ourselves with”

Comparison does not require a twin organisation. You can compare against yourself over time, a published sector standard, an approved target, or the situation before the intervention. The absence of comparison is a choice, not a fate.

What changes once the gap closes

Organisations that build this chain stop preparing for awards seasonally. They become permanently ready, because readiness has become part of how they operate — not a separate project starting two months before a deadline.

But the most important effect usually does not show in the assessment result. It shows internally: when a team starts asking “what is the evidence?” before anyone external asks, the organisation has changed its own internal standard — and that change outlives any project.

Early signals that the gap is closing

• Someone asks “what is the evidence?” in an ordinary meeting, unprompted.
• New initiatives are designed with a baseline from day one.
• Two people from different departments describe the same achievement in nearly the same way.
• The time needed to prepare any leadership report shrinks, because the material is ready and classified.
• A new employee can understand why a decision was taken three years ago from the documents alone.

The last signal matters most, because it means the organisation no longer depends on individual memory.

A note on the difference between sectors

The gap presents slightly differently in government and semi-government contexts than in the private sector.

In the private sector the ultimate indicator is usually financial and clear: revenue, market share, customer acquisition cost. The gap tends to sit in connecting the initiative to the financial measure.

In government the ultimate value is societal: time saved, easier services, greater safety, higher trust. These are real values but harder to measure, so teams drift toward describing activity instead.

The answer is not to import private-sector indicators, but to build a unit of value appropriate to the context: hours saved for customers, cases prevented, reduction in in-person visits. What matters is that the unit is specific and verifiable, not that it is financial.

The question I start with

When I begin with a new organisation, I don’t ask about achievements. I ask something different: if someone outside this organisation read your submission today, what would they understand — and what would they miss?

Answering that question exposes the gap in a single session. Closing it is the work worth spending time on.

Because recognition, in the end, is not given to the best performance. It is given to the best performance that managed to prove itself. The difference between the two is the whole matter.