He’d been saying he needed to step back for three years.
Not vaguely. He’d said it in specific terms – particular meetings he shouldn’t be in, particular decisions that shouldn’t reach him, particular areas of the business he wanted to hand over.
He meant it.
And yet – nothing changed.
Not because he wasn’t trying. Because every time he tried to step back, something would happen that required him. A client issue. A pricing call. A team situation that needed navigating.
And he’d step back in.
And the pattern would reset.
THE DELIBERATE REDUCTION
When we started working together, we approached it differently.
Not “I’m stepping back” – which is a statement of intent that gets overridden by the first urgent thing.
But a deliberate, system-by-system reduction.
We started with the Decision System.
Mapped the recurring decision types that were coming back to him.
Defined which ones had clear owners already – and just needed the permission to be explicit.
Identified the two or three categories that would make the biggest difference if they stopped coming back.
Within six weeks, those categories had mostly stopped.
Not because the team had changed.
Because clarity had changed.
They’d always been capable of making those calls.
They just hadn’t been told they were supposed to.
WHAT HELD
Here’s what surprised him.
Things held better than he expected.
Not everything.
But the areas where we’d been most deliberate – clearest about ownership, clearest about standards – held well.
Decisions got made.
Problems got resolved.
Standards were maintained.
Not perfectly. But consistently enough that the owner wasn’t required.
The business had learned to operate without him as the default mechanism.
Not because it got better people.
Because it got better structure.
WHAT NEEDED WORK FIRST
Here’s the honest part.
Some areas didn’t hold.
One manager wasn’t ready for the accountability that came with real ownership.
One process wasn’t documented well enough to run without the owner’s tacit knowledge.
One client relationship was so owner-dependent it needed a deliberate handover plan.
Those things needed work first.
Which is why diagnosis matters before reduction.
You can’t step back from something that genuinely isn’t ready.
But you can step back from more than you think.
And identifying the difference is the starting point.
WHAT CHANGED PERSONALLY
Here’s what he noticed, six months in.
Two things.
First: headspace. “I’m thinking differently,” he said. “I’m not constantly in reactive mode. I’m thinking about where the business is going – not just what’s in front of me.”
Second: something quieter. He’d taken a proper week off. His first in four years.
Mid-week. No messages.
“I kept checking my phone for problems,” he said. “There weren’t any.”
WHAT WOULD YOU NEED TO TRUST?
That’s the question I ask every owner who wants to start this process.
Not “how do you step back” – which is a process question with a clear answer.
But: what would you need to trust?
Which system? Which decision type? Which area of the business?
What would need to be true – for you to trust that it works without you?
Because the answer to that question tells you exactly where to start.
What would you need to trust before stepping back from one decision you currently make every week?
