Talk it through with Aurelius
When the client relationship lives in one person's head
One person holds the whole client relationship — the history, the context, the trust, all of it in their head. When they're on vacation, things stall; if they left, you'd be in real trouble. You know it's a risk, and you keep not addressing it because they're handling it fine — until the day they're not there.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
A key-person-risk problem, worked together. Mostly the craft of making tacit knowledge explicit and spreading it (knowledge); a little on valuing the person while de-risking (guidance).
How the two dials adapt to you →What’s really going on
A relationship (or any critical knowledge) living in one person's head isn't a sign of a great employee — it's a single point of failure you've been calling dedication. The person isn't hoarding maliciously; the team just never built a way to share what's in their head. We de-risk it without diminishing them: making the tacit explicit, spreading the relationship, and turning a key-person liability into team-owned continuity.
🔒 What you’ll build togetherUnlock by starting
KnowledgeWhen a key person is a single point of failure
KnowledgeMaking the tacit explicit
KnowledgeSpreading a relationship without breaking it
A moveName what would break if your key person left tomorrow — and who else knows it.
A movePick one relationship or knowledge area to start spreading beyond one head this month.
PractiseDe-risk the key person · a Pod of 5 · 45 min
What changes unlock by starting
- Critical knowledge stops living in one head.
- The relationship survives a vacation or a departure.
- The key person is valued without being a liability.
- A single point of failure becomes team-owned continuity.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.