Skip to content
The Method

THE SIX SYSTEMS

What actually gets built. Six systems that take what a founder carries - belief, judgment, standards, relationships, rhythm, story - and make the organization able to carry it instead.

Why six

Everything a founder carries falls into six loads.

When PLAYERTWO maps founder dependency, the same invisible load appears again and again: belief, judgment, standards, relationships, rhythm, and story. As long as those live only in the founder, the organization has a single point of failure, however large it grows.

Each of the Six Systems exists to take one or more of those loads off the founder and place it into infrastructure the organization operates daily. Together they are the tangible product of a Legacy Management engagement.

ObservedThe recurring six-load pattern is drawn from PLAYERTWO's diagnostic work with founder-led organizations. It is a field observation, not an independently measured taxonomy.

A system is not what you wrote down. It is what your organization does when you are not watching.

The systems

Six systems. One legacy.

Belief Map

What the business exists to protect, pursue, and refuse.

Carries: Belief

The documented purpose, principles, narrative, standards, and tenets that guide the organization. The identity everything else is measured against. Not aspirational values on a wall: the actual convictions that decide hard trade-offs, written precisely enough to be applied without the founder in the room.

Signals it is missing

  • Values exist but do not influence real decisions
  • Different leaders describe the company's purpose differently
  • Trade-offs escalate to the founder because nobody knows what wins

Founder Doctrine

The founder's judgment, captured so others can apply it.

Carries: Judgment

The decision logic, non-negotiables, and hard-won instincts that currently live in one person's head, translated into decision rules, worked examples, and boundaries the team can reference and repeat. The pattern behind the founder's 'no', made reproducible.

Signals it is missing

  • Only the founder can make certain calls
  • Decisions made in the founder's absence get reversed
  • New leaders take years to 'get it', if they ever do

Decision Rights

Clear ownership of who decides what, and why.

Carries: Judgment · Rhythm

Explicit authority: where decisions sit, what escalates, and what does not. Teams resolve trade-offs against the doctrine instead of routing everything through the founder, removing the bottleneck without losing the standard.

Signals it is missing

  • The founder is in every meeting that matters
  • Approval queues form behind one calendar
  • People escalate to be safe, not because they must

Behavioural Systems

Belief turned into actions people can repeat.

Carries: Standards · Rhythm

Hiring standards, onboarding, meeting structures, incentives, feedback loops, and communication protocols designed so the organization behaves like itself, consistently, without supervision. Standards stop being enforced by presence and start being carried by process.

Signals it is missing

  • Quality depends on who happens to be involved
  • Onboarding transfers tasks but not standards
  • Culture dilutes with every hire beyond the founder's reach

Identity & Expression

The internal truth made visible.

Carries: Story · Relationships

Brand, messaging, visual identity, content, and digital experiences aligned with the belief infrastructure so what customers, candidates, and partners see matches what the company actually is. The narrative becomes tellable, and trust becomes transferable, without the founder present.

Signals it is missing

  • The founder is the brand: sales and recruiting stall without them
  • External messaging drifts from internal reality
  • Key relationships are personal to the founder, not institutional

Continuity Infrastructure

Alignment made teachable, repeatable, and transferable.

Carries: All six carriers

The documentation, tools, training, and reinforcement systems that let the organization preserve its identity through growth, succession, and leadership change. This is the layer that makes the other five durable: the difference between a project and a legacy.

Signals it is missing

  • Knowledge transfer depends on shadowing one person
  • Succession planning exists on paper but not in practice
  • Past initiatives faded once attention moved on
Questions

Frequently asked.

Next step

Find out which systems your organization is missing.

A Legacy Consultation maps where your organization depends on you today, and which of the Six Systems would take that load.