THE PERFORMANCE MANIFESTO
THE PERFORMANCE MANIFESTO
For leaders who refuse to manage fiction and choose to design for reality
1. Performance is what the architecture produces through competent people
Performance is not a trait certain individuals carry into the building. It emerges where two things meet: an architecture built for clarity and flow, and people with the competence to act well inside it.
Neither half works alone. A coherent system staffed by people who can’t do the work produces confident failure. Capable people inside an incoherent system spend their capability fighting friction instead of creating value. You cannot hire your way out of a broken architecture, and you cannot design your way out of missing competence.
This is why the high performer is a misleading idea. People rise to the level the architecture permits, and the architecture rises only to the level of competence the organisation is willing to develop. Praise and blame aimed at individuals miss the larger fact: most of what looks like performance, or its absence, was settled by the structure before the person arrived.
2. Static goals are a category error
A static goal assumes a world that holds still long enough to be planned against.
That world is gone, if it ever existed.
The issue isn’t goals, or ambition, or even metrics; an organisation needs all three.
The issue is fixity: a target set in one quarter’s reality and defended through the next four while conditions move underneath it. Annual objectives, OKRs, and KPIs aren’t the problem in themselves. They become the problem the moment they harden into fixed commitments inside a system that has already changed shape around them.
Used that way, they stop measuring performance and start manufacturing their appearance. The capable person, who can see the target has gone stale, is forced to choose between hitting the number and doing the right thing. The less capable person, who couldn’t have hit a moving target anyway, is handed a fixed one to stand behind. Rigidity punishes the judgement you most need and shelters the kind you don’t.
3. Performance theatre is the enemy of performance
Organisations rarely fail because people lie.
They fail because the architecture quietly rewards fiction over truth.
It works like this. Once goals are fixed and reporting is mandatory, honesty becomes expensive. People report progress against commitments that stopped mattering in March. Teams optimise for the metric instead of the outcome it was meant to track. Leaders, without ever asking for it, are fed the version of reality that’s safest to deliver upward.
The result is theatre, a well-rehearsed performance of alignment and control.
The dashboards glow green while the business quietly burns. Reviews celebrate milestones that turned out to be irrelevant. And the people who can actually tell the difference learn to stay quiet, because in a theatre, the reward goes to the most convincing performance, not the most accurate one.
Competence doesn’t survive that for long. It either leaves or learns to act.
4. Coherence beats cascading
Cascading goals belong to a picture of the organisation as a machine: strategy decomposed into parts, alignment stamped out through templates, clarity trickling tidily downward. Real organisations don’t work that way. They behave as networks: interdependent, shifting, full of feedback; the org chart never shows.
Coherence is what actually aligns a network, and it doesn’t come from decomposition. It comes from a shared sense of what matters, priorities that are visible to everyone at once, and the ability to coordinate in real time rather than through a chain of restated objectives.
Competent people don’t need the strategy cascaded to them in ever-smaller boxes. They need context, clear priorities, and the authority to act on their own judgement. Cascading manages people who can’t be trusted to think.
Coherence is what you build when you can.
5. Adaptive capacity is the competence that counts now
The strongest organisations are not the most disciplined. They are the most adaptive, quick to sense a change, quicker to adjust, and able to coordinate the turn without waiting for permission to ripple through the hierarchy.
This is the distinction that trips people up: adaptation is not the same as inconsistency. Changing course when the conditions change is not a failure of resolve. It’s competence expressed in motion, the intelligence to recognise that the plan has expired, and the judgement to do something useful about it.
Static goals reward the leader who holds the line while the ground shifts.
The work now rewards the one who saw the shift and moved.
6. Metrics are instruments, not verdicts
A metric shows you a pattern. It does not hand you the truth, and the distance between those two things is where organisations lose themselves.
When the metric becomes the goal, the optimisation starts: people improve the number rather than the thing the number was supposed to represent. Dashboards get managed instead of businesses. The measure, built to inform a decision, ends up replacing it.
A good metric provokes a question; it doesn’t settle one. It makes a leader look harder, not look away. The competent use numbers to sharpen their judgement, the incoherent system uses them to avoid having to judge at all. What everyone is actually after is impact, and impact is the thing the metric is always only pointing toward, never quite holding.
7. Accountability runs in one direction, and only one
Individual accountability is real.
But it comes last, not first, and the order is not negotiable.
A leader cannot hold a person accountable for an outcome that the architecture made unreachable. To do so is to charge the individual for a structural failure, not accountability, but its counterfeit.
The sequence has to hold: leaders are accountable for the conditions, teams for the coordination within them, individuals for the competence and judgement they bring. Each layer can only be held to account once the layer beneath it is sound.
Reverse it: start by holding individuals responsible for a system they didn’t design and can’t change, and you get the most common failure in corporate life: a structure protecting itself by blaming the people it set up to fail.
8. Psychological safety means candour, not comfort
Psychological safety is widely misread as the protection of feelings. It isn’t. It’s the protection of the truth, the condition under which someone can say the thing the organisation needs to hear and not be punished for it.
In a genuinely safe system, a person can say ‘this isn’t working,’ ‘the goal no longer makes sense,’ ‘we need to change direction,’ ‘the system is blocking us,’ ‘I need help,’ ‘or this is beyond what I can do,’ and have it treated as information rather than insubordination or weakness.
Comfort is optional, and sometimes counterproductive. Candour is the non-negotiable. An organisation only knows what its people are willing to tell it, and they will only tell it what the architecture makes safe to say.
9. People are partners, not compliance units
People don’t perform better when compressed into templates and tracked against fixed boxes. They perform better with clarity, autonomy, access to information, and the right to challenge the plan.
This follows directly from everything above: performance is produced by the architecture and enabled by competence, and neither responds well to control. You can compel attendance and compliance. You cannot compel judgement, initiative, or the willingness to say a hard thing; those are given, not extracted, and they’re given only where the conditions invite them.
Treat people as adults accountable for real work, and most will meet it. Treat them as units to be monitored, and they will give you exactly the monitored minimum. The architecture you build is also a statement about which of those two you expect.
10. A performance system has to be a living system
A performance system should resemble the environment it operates in: alive, responsive, capable of learning. Most are the opposite: fixed annual scaffolding bolted onto a business that reconfigures itself every quarter.
A living system adjusts as new information arrives. It re-prioritises when conditions move. It rewards the outcome over the ritual and the truth over the performance of progress. And it treats the development of competence not as an annual training line item but as continuous, deliberate work.
This is not a gentler version of traditional performance management. It’s a different premise altogether, one that stops treating performance as something you demand from individuals and starts treating it as something a well-built system produces through capable people.
11. Leadership is the design of conditions and the stewardship of competence
Leadership is not the enforcement of goals, rules, and policies. It is the design of the architecture in which good performance becomes the path of least resistance rather than a constant act of will.
That design work is concrete: clarity about what matters, coherence among competing priorities, information that flows instead of pooling at the top, decision rights placed where the knowledge actually is, friction managed deliberately, and conditions in which the truth can be spoken without cost. None of it is soft, and all of it is the leader’s job.
But conditions are only half of it. Leaders also build the competence the architecture depends on, through who they hire, what they develop, what they expect, and, crucially, what they tolerate. The standard a leader walks past is the standard they’ve set. Performance, in the end, is not what leaders demand. It’s what their architecture produces, and their competence enables.
12. The future belongs to the adaptive, the honest, the coherent, and the competent
Organisations that hold on to static goals will keep getting the same results: a strategy that lags reality, talent that quietly disengages, and innovation that suffocates under commitments no one believes in anymore. The planning cycle will keep producing confident plans for a world that has already moved on.
Organisations that build living systems and invest seriously in competence will move faster, learn faster, and steadily outpace competitors still staging the theatre of predictability. Not because they try harder, but because they’ve stopped asking people to compensate for a structure designed to hold them back.
The world is not waiting for your planning cycle. Your performance system shouldn’t be either. Competence without a coherent architecture is wasted; a coherent architecture without competence is hollow. Performance needs both, designed together and on purpose.
THE DECLARATION
We reject static goals, performance theatre, and the belief that discipline can manufacture a predictability the world no longer offers.
We hold that performance is not extracted from people but produced by the architecture they work inside, and that the architecture is the leader’s responsibility to design.
We choose reality over ritual, coherence over control, judgement over compliance, and the patient work of building conditions over the theatre of demanding results.
This is the manifesto.
This is the work.