The long version,
for anyone who wants it.
The homepage makes the argument. This is the detail behind it — every seat I've sat in, why it isn't a blame exercise, how a finding turns into something you can act on, and the two disruptions most likely to catch a network unready. None of it is required reading. It's here because a practice built on saying the quiet part out loud shouldn't hide its method either.
← Back to the homepageEvery seat, in order
Thirty years. Every department in the book. Delivered solo.
Mercedes-Benz · MINI
& Commercial Vehicles
Thirty years. Every department in the book. Divisional accountability for
enquiry management and KPI achievement. Then five marques, five different agency
models — each designed in isolation, all landing on one network, one set of
systems, one set of people. Over 40 sites. End to end, and through the
regression.
No team. Just me.
Verify all of it on LinkedIn →
What that seat actually held
The whole programme function
Change management. Process mapping. Training manuals. SharePoint build and delivery infrastructure. The single conduit between group and OEM — in both directions.
Five systems, learned from nothing
Each brand's architecture, structure and capability. Often taught to the network at go-live, because in several cases the system did not exist to be learned before it.
The agreement, read from the retail side
Reviewed the compliance provisions in each agency agreement and surfaced the operational gaps before they reached the network — the areas the process map and the what-ifs had not reached.
Every site, after go-live
Readiness, stakeholder alignment, DMS programme updates, and the resolution of the issues nobody had modelled. Because they only exist once it is live.
How I work
I'll say the quiet part out loud.
Everything I have written on this page is a thing everybody already knew and nobody said. The readiness gate that got signed because the date couldn't move. The used car seam nobody was looking at. The customer score still pointed at the site after the model changed. The manager who left, and the cost that never got counted.
None of it is a secret. It is simply unsayable — because saying it is career-limiting for the person who knows, and unwelcome for the person who decided.
I have no career left to limit inside your business. That is precisely what you are buying.
Why it lands
Every plan I have watched fail, failed in the room — not in the model. The design was fine. The people had quietly decided in advance that it wasn't for them, and nobody had earned the right to be told.
I don't run culture workshops. I read the room as carefully as the P&L, I ask the question everyone is avoiding, and I tell you what I heard — including the parts you would rather I didn't.
That is the method. It's also the reason the rest of it works — because a rollout, a target or a transition only lands in a business where someone was willing to hear the truth before it was too late to act on it.
What this is — and what it isn't
This is not a blame exercise.
Someone unheard will tell you everything you need to know within five minutes of talking.
Why it isn’t a blame exercise
That is the whole method, and it is why this works. Not an interrogation, not a witch-hunt, not a search for someone to hang it on. I am looking for the why, and whether there's a pattern — because one person struggling is a person, but the same thing happening across four sites is a process. And a process that leaks was built to leak. That isn't anybody's fault. It's a design nobody's gone back to look at.
Nobody planned to run reactive. The day decides.
Every business says it works proactively. Almost none does, and not through negligence. Budget has to be hit, manufacturer targets have to be hit, compliance has to hold, and the calendar is full before the day starts. So the doing slides down the list, and what's pressing takes the slot.
Then the day arrives. The target moves. The gap is suddenly too big to close in the month and it still has to be closed. A resignation nobody saw coming. A week of sickness in a department already spread thin. Annual leave that was agreed months ago and lands in the worst possible week. Four cars sold off the showroom floor — site and group — so replacements have to be called from port, PDI'd, cleaned, photographed, advertised, and the space filled before an event. And the damage on a service customer's car that was definitely not there at check-in.
None of that is on a plan. All of it has to be dealt with today, by the same people who were going to do the proactive work.
And you can't be in every building at once.
A director with a double-digit number of sites has every one of those pressures running in every one of those buildings, simultaneously. You physically cannot be there. That's arithmetic, not a shortcoming. So you trust the reports — and the reports are good now. Power BI gives you dashboards that are genuinely excellent. Everyone looks at the data. Everyone knows what it says and what it means they need to do.
And then service is a long way off target with nowhere near enough booking capacity left to recover it before month end, sales isn't dropping either, and you're staring at a loss on a site.
By that point the embarrassment is already in the building. The failure lies flat on the Head of Business, and it reflects straight up the chain to the director with a store way off budget. The questions get asked. Everyone in the room knows the job. They knew it before the questions started. It still isn't happening.
The why, not the who
I don't come back with a name to punish. I come back with the reason it keeps happening. Fix the mechanism and the symptom goes with it — blame a person and it moves to the next one in the chair.
The pattern, not the incident
One bad call is a bad day. The same gap in five buildings is a system telling you something. I'm reading for the pattern — that's what turns a complaint into a fix you can actually make.
How watertight is the process — really?
Not "who failed the process." Whether the process was ever tight enough to be followed under pressure on the last day of the month. Most aren't. That's the finding, and it's a fixable one.
The genuine feeling is the data
The person who feels unheard isn't a disloyalty risk — they're your best sensor. They'll tell me, fast and straight, exactly where it breaks. What they say is evidence, and it stays unattributable.
What's already working comes first
Before a single problem is named, I write down what's good — and I protect it. A review that breaks the thing that wasn't broken has failed. You'll see your strengths in writing, named, so nobody "fixes" them by accident. This is a strengths-first read: find what holds, keep it, then deal with what doesn't.
Nobody gets hung for a fault the system built. You get the why, the pattern, and a finding aimed at the mechanism — owned and dated, so it's fixed once, not blamed round in a circle.
Why this exists
This isn't about pulling a business apart. It's about making it work better with what it already has.
Nobody in this market can just sign off more headcount to fix a problem. What you can do is look honestly at how you work, where the effort leaks, and how the same people — supported properly — become more effective. The goal is a business that runs better commercially and operationally, not a report that lists everyone's failings. The finding is only worth having if it makes Monday better.
What “more effective” actually means
Work smarter, not bigger
Before you add cost, you look at effort. Most sites are carrying waste they've stopped noticing. Take that out and the same team has more room — no new headcount required.
The induction is the investment
You spend thousands recruiting someone, then their first weeks decide whether they succeed and stay. Get the induction wrong and you've burned it. A good landing protects the money you already spent — and there are playbooks and tools built precisely for that, already written, priced and in use.
They can also be rebuilt as your own — your branding, your process, your standards, your language — so what a new starter is handed on day one is the way your business does it, not a generic manual. Scoped on the frameworks that already exist rather than written from scratch, which is what keeps it affordable.
And built around the systems you already run, not alongside them. The reason most of this fails isn't the content — it's that it becomes another form to fill in, competing with the DMS at the exact moment somebody is busy. Anything that asks a manager to record the same thing twice will be abandoned within a month, and they'll be right to abandon it. If it doesn't point at where the work already happens, it doesn't land.
Embed the values, build the culture
Culture isn't a poster; it's what you tolerate and what you reward. Get that consistent and retention follows. The wider work kept surfacing the same thing: a real failure to attract and keep senior management. That's fixable — but only once it's named.
Ten minutes a day, given back to everyone.
You've had the call. I haven't had that report yet. Your forecast has moved back — why? And you know before you answer that there's no good version of it. The team has given everything. You've been through the basics with them, more than once. Everyone knows exactly where they're supposed to be. You shield them, you take the kick, and then the week starts again and nothing has actually changed.
Going through the basics again won't fix it, because the basics were never the problem. Time was. Nobody has an hour to think — but almost everybody could have ten minutes back, and ten minutes is enough to move one thing from reactive to done.
So the question I'd rather ask is a smaller one: what does each person do every single day that a machine could do in a fraction of the time, to the same standard or better? The report that gets rebuilt by hand every Monday. The same five customer replies typed from scratch. The month-end commentary. The handover notes. The follow-up list that gets rewritten instead of reused. None of that is the job. All of it eats the job.
This changes nothing structural. No new system, no headcount, no restructure — the same people, the same targets, the same day. What changes is what you let take the slot, and how much of the routine you stop doing by hand.
Do our standards apply to everyone — or only to the people who aren't hitting budget?
One size fits all, in theory. But do we treat every team the same, with the same tone and the same acceptance? Or do we quietly turn a blind eye to some — because the behaviour is outweighed by the numbers? The manager who delivers and is allowed to behave in ways others would be pulled up for is the most expensive thing in your business, because everyone below them learns exactly what really gets rewarded. This is a governance question, not a witch-hunt — consistency of standards, applied evenly, is what culture actually is. I'll ask it. Most won't.
The gap
Readiness isn't a state you reach. It's a thing you declare so the date can hold.
Every plan I have ever received was written as though the unknowns could be eliminated before go-live. They cannot. So you go anyway — knowing you have done everything you can, not knowing what tomorrow looks like — and you learn in contact. Everyone downstream of that assumption is quietly absorbing the difference. It never appears in the report.
What the plan assumes
- Readiness is verified before launch, and the gate means something.
- The model is the only model. It lands in a clean building.
- Process change is adopted once communicated and trained.
- The system supports the process, because the process was specified to it.
- Post-launch is a support phase.
What the morning after looks like
- Readiness was signed off because the date could not move. Everyone knew.
- Five marques, five agency models, one network, one DMS — and one person trying to remember which logic pays today.
- Adoption dies at the first month-end when the old way is faster and the target is real.
- The system holds one logic. You are running five. The gap is being closed manually, by people, at night.
- Post-launch is where the actual design happens — and nobody budgeted for it.
What happens after the finding
A finding is only the start. The point is a business that runs better.
I'm not here to hand you a document and leave. The honest view is only worth having if something changes because of it — so every engagement is built to move from here's what's true to here's what's better, with the same people you already employ. This is help, not a threat. Nobody's job is the target; the way the work works is.
The honest view
What's genuinely happening, heard from every level — and what's already working, protected first.
The why and the pattern
Not who to blame — where it leaks and why, and whether it's a one-off or a system you can actually fix.
Land it with what you have
Working smarter, values embedded, the right induction and playbooks — no new headcount to sign off. The frameworks are published and priced rather than written from scratch each time.
The 90-day return
I come back. What stuck, what reverted, what needs another go. Fixed once, not filed and forgotten.
The honest view is exactly the thing that thins the further up the tree it travels.
By the time it reaches the top, every layer has rounded it up a little — not out of dishonesty, but because each person has a stake in how it reads. So the people with the most authority to fix things are working from the most polished version of events. The whole value of an outside read is that it arrives at the top undiluted — the same account the floor would give you, delivered straight to the chair that can actually act on it. That's not there to frighten anyone. It's there so the decision gets made on what's real.
Method
A finding nobody adopts is a cost, not a deliverable.
Change delivery
Every engagement carries a change plan — stakeholder and impact mapping, a readiness gate that means something, and the objection handling for the three people who will quietly kill it. Kotter and the Change Curve, applied to a business that still has to sell cars while it changes.
What the numbers don't show
The reason your best manager is leaving. The reason the workshop and the showroom don't speak. The reason the last consultant's report is in a drawer. I read the room as carefully as the P&L, because in this industry the room is where the plan either lands or quietly stalls.
And it doesn't come back on you either. The finding is about the mechanism, not the person who commissioned it. It tells you where and why — what you do next is yours to decide, privately. Nobody in the building sees a verdict on the person who brought me in.
The second great disruption
After AI, EV is the change most likely to catch your network unready.
The government sets the manufacturer a BEV target. The manufacturer turns it into a retailer target. And then it lands on a network that was never asked whether it was ready — the workshop, the service drive, the sales floor. Nobody has time to stop and audit whether the infrastructure, the skills and the protocols are actually in place. That's exactly the gap I look at.
The four EV readiness questions
The workshop — is it actually safe and ready?
- How many qualified high-voltage technicians per site — and what happens on their day off?
- Correct PPE, signage and a genuine quarantine area — or a painted bay and good intentions?
- A real protocol for an electrical incident that the team has actually rehearsed
- Clarity on what can be done on site vs what must go to a battery centre — and who decides
The service drive — does the adviser know enough?
- Confidence on EV-specific servicing schedules — they are not the ICE schedule with fewer lines
- What the warranty covers, what the retailer can process, and what must be referred
- The battery warranty conversation — the one customers actually worry about
- Enough understanding to hold the customer's confidence, not hand it to a Google search
Sales — qualified, or just order-taking?
- What the team genuinely knows vs what they perform when a manager is listening
- The tools they use to qualify — charging, usage, home vs public, total cost of ownership
- What they qualify and what they refer — and whether referral is a system or a shrug
- Readiness for the new Chinese brands — price-led, arriving fast, sometimes ahead of a trained workshop
Retention & the customer parc
- What EV adoption does to servicing frequency and aftersales revenue over the ownership cycle
- The shift in warranty claim patterns and where the cost lands
- How change cycles and residuals reshape the customer relationship — and what offsets earlier weak EV values
- Whether your people stay through a transition they weren't trained for
The industry is openly split on this, and any honest read has to hold both sides. Retail leaders like Vertu's Robert Forrester have called the pace of the mandate "delusional" and pressed for an urgent review — arguing the targets outrun real consumer demand and force margin-destroying discounting. Others warn that watering the targets down damages the investment certainty the industry was built on. Commentators such as Auto Trader's Ian Plummer track the demand-and-affordability picture closely. My job isn't to take a side on the policy. It's to tell you whether your network is ready for the version of reality that actually arrives.
And the ground keeps moving. New price-led Chinese EV brands are entering the UK at speed — some through established groups, some as pop-ups ahead of a properly trained workshop. Fuel-price stability after the Iran and Strait-of-Hormuz tensions has quietly changed the EV-versus-ICE calculation again. None of this waits for you to be ready. The only question that matters is whether, right now, your sites actually are — and almost nobody has had the time to find out.
Free guide
Company car, cash, or sacrifice?
The same transition lands on your own people as a benefits question, and most of them are deciding it on a monthly figure and a fortnight's notice. An EV company car is taxed at 4% this year; a petrol equivalent can be 37%. That gap decides more than any conversation about charging ever will — and almost nobody in the building has been shown the arithmetic.
Written for drivers, not for fleet. The tax, the funding routes, PCP against contract hire, the insurance class most allowance drivers don't have, and what happens to a finance payment if somebody goes on long-term sick. Verified 2026/27 HMRC rates.
Read the guide →No sign-up. Free to send to your team.
Terms of engagement
Read these before you enquire. They are not negotiable.
- What I am told, I keep. I will tell you what I heard. I will never tell you who said it — not to a manager, not to a director, not under pressure, not ever. That promise is the entire mechanism by which this works, and people who have known me for thirty years know I mean it.
- I will not validate a plan I think is wrong. If you want a consultant who confirms the decision you've already made, there are excellent ones and I'll recommend three.
- I speak to your network directly, or not at all. A finding filtered through the people it implicates is not a finding.
- Every finding gets an owner and a date. If it cannot be written that way, it is not a finding — it is an observation, and observations are what fill drawers.
- I come back. Ninety days, to see what actually landed — including what I got wrong because somebody managed what I was allowed to see.
- Nothing is named without permission. Former employers, current clients, and the people who talk to me in confidence stay protected. Always.
- The report says what happened. Including the parts that are already working — those get protected in writing, because the second-worst outcome of a review is breaking the thing that wasn't broken.