What gets decided
isn't what gets done.
I played professional tennis. Then I spent the last decade working out why organisations decide one thing and do another. Performance Architecture is the method I built to fix it.
Most organisations lose their best work in the gap between deciding and doing.
The strategy is usually sound. The people are usually good. But the thing agreed in the room isn't the thing that reaches the customer. It slows down, gets watered down, or stops.
Most people blame effort or talent. It's almost never that. It's the structure around them: how decisions get made, how work moves, who gets rewarded for what. Change the structure and the same people deliver.
The cost of that gap rarely gets counted, because it doesn't show up as a line on a report. It shows up as the launch that missed its window, the programme that stalled at 60%, the good people who stop putting themselves forward and start waiting to be told. Left alone it compounds. You spend more and move slower.
Performance Architecture
Most improvement work treats the symptom. A missed deadline gets a new process. A stalled programme gets more governance. The thing that actually caused the problem sits untouched, so it comes back.
Performance Architecture is a systems approach I've built since 2015, from doing the work rather than writing about it. It reads an organisation across the places performance is won or lost: how decisions get made, how work flows, where dependencies bite, whether the way people are measured points the same way as the strategy. It finds the seam where your results stop converting, and it names the move that closes it.
It doesn't come with a framework to install. I diagnose first and build what fits, rather than turning up with the answer already written.
The same method is starting to move across to individual performance, which is where it began for me in the first place, on a tennis court.
You don't have to take the method on faith.
Here's what happened when I used it.
The whole model, on 26 slides
The Performance Architecture Blueprint walks the method end to end: the performance matrix, the seven domains, the seams where results stop converting, what the gap costs, and the five questions to put to your own organisation.
It's the thinking, free. Applying it to your organisation is what I do for a living.
Where this comes from
I played tennis professionally before I did any of this. That's not a line on a bio, it shaped how I see everything. Elite sport teaches you early that performance isn't luck, and it isn't talent on its own. It's a system you build, measure and hold together under pressure.
When I moved into business I kept seeing the same thing at organisational scale: capable people, sound plans, and a structure around them that worked against both without anyone ever deciding it should. So I've spent the last ten years learning to find that structure and change it, across financial services, gaming, government and large-scale delivery. Performance Architecture is what came out of it.
What I'm working on in the open
I've written more than fifty pieces figuring this out in public: how organisations perform, why change stalls, and what actually moves it. If you want the thinking rather than the pitch, start there.
Work with me
For organisations
I work with COOs, CIOs and transformation leaders who know the strategy is right but can't get it to land. It usually starts with a diagnostic: find the real constraint before anyone commits to a big programme, then do the work to close it. Delivery runs through my firm, Baseline Partners - fixed fees, senior people only, measured against a baseline.
For individuals
This one's newer. If you're serious about your own performance and you think like a systems person, tell me what you're working on. I'm taking on a small number as I extend the method.