Situation · Succession

Someone else has to run this.

You want to stay involved, but the business needs to work without you in every decision. Someone will step into the seat. They can’t inherit chaos.

If this is you

The conditions we see most in Succession.

You don’t need all of them. One is usually enough.

01

Everything still comes back to you.

05

Your team waits for you, even when they shouldn’t have to.

06

You’ve been meaning to fix this for two years.

These aren’t problems you solve by working harder or thinking differently. They’re structural. The conversation starts here.

Inside the engagement

What Decision Architecture looks like when it’s applied to Succession.

Succession fails when the successor inherits an unstructured business. “Handover” usually means transferring relationships, passwords, and half-remembered decision patterns that only made sense in the founder’s head. The successor takes the seat and immediately becomes the new bottleneck, because the structure was never the problem the founder was solving; the founder was the structure.

Structural readiness is different work. Decision rights get written down as roles, not people. Delegation gets codified. The rules that used to live in the founder’s judgment get externalised into a framework the incoming decision-maker can read, question, and adjust. When that’s done, the successor inherits a business, not a personality.

The Architecture is where this happens. It’s not a rescue operation for the successor, it’s a re-architecture of the business they’re stepping into so the seat is worth taking. Structural work has to lead.

The founder’s role in this doesn’t vanish. Most succession clients want to stay involved, board seat, advisor, chair. The redesign makes that involvement additive rather than load-bearing. You get to weigh in without being the thing the business waits on.

Practice

Three tiers. One methodology.

Every situation runs through the same practice. The context changes; the methodology holds.

Beyond the ladder Systems Build — On inquiry

The Architecture becomes how the business actually runs. Guardrails deployed. Decision rules embedded. Resistance in the team worked through. Scope depends on the state of the business at the point of installation.

For Succession, Systems Build is where the inherited framework gets installed before the successor takes the seat. Larger engagements, succession windows, and specific operational builds. By inquiry.

Scope and price by inquiry

Start the inquiry →

Outcome

What you get, and what it does.

For Succession, the artefact is the Architecture: a full written redesign document, ninety days, covering decision rights, reporting lines, delegation frameworks, and operational guardrails. It is not a succession plan written for lawyers and not an org chart with new names in old boxes. It is the operating structure the successor will inherit on day one.

Act on it, and the handover stops depending on the successor having the founder’s instincts, because the instincts are written down. The business runs the same way after the seat changes as it did before. That is what makes successions survive, and what the Architecture is built to produce.

How we work

Fifty years of pattern recognition.
Applied to your situation.

Fifty years across seven industries and four continents teaches you how businesses actually break. Work spanning the US, UK, Australia, Singapore, China, and Bangladesh. Food service, financial services, real estate, workforce training, construction, mining services, recruitment. The patterns repeat. The work here is to read the pattern in front of us, and design the structure that holds it.

Every engagement leaves a permanent artefact. A bound booklet after the Diagnostic. A written brief after the Blueprint. A full architecture document after the Architecture engagement. A decision that is made once and stays made, on paper, signed at the top.