LightWidget - Responsive Widget for Instagram

01
This week's key person test came down to a single finding: the organisation had built a system that could run without the leader, and had not yet built one that could run without its most experienced developer.

The absence test and the key person test look like versions of the same challenge. The risk they expose is different. The absence test is about where the leader's knowledge lives. The key person test is about where everyone else's knowledge lives, and whether the organisation has ever asked that question before a resignation forced it to.

The answer almost always reveals the same gap: technical knowledge is partially documented, relational knowledge is largely personal, and contextual knowledge (the reasoning behind decisions already made) is almost entirely undocumented because the person who holds it has never been unavailable long enough to make the gap visible.

The design work is the same regardless of which test reveals it. Knowledge that lives in the system is an asset. Knowledge that lives only in a person is a risk wearing the appearance of value.

What knowledge in your team is an asset, and what is still a risk?
12
The resignation arrived on a Monday morning. By Tuesday afternoon, the MD had found three gaps that eighteen months of system building had not addressed.

The delivery was completed and the client relationship stabilised, but the contextual knowledge (the reasoning behind three years of architectural decisions) was only partially recovered.

Eight months later, a second developer left; the departure protocol ran within 24 hours, the knowledge registry identified two gaps both addressed within the notice period, and the delivery schedule moved three days while the client expressed no concern.

The MD described the second departure as almost routine.

The difference between the two departures was not the people, the complexity of the knowledge, or the notice period. The difference was whether the system had been designed to absorb the loss before it arrived.

Where in your organisation is the knowledge that has not yet been designed for?
11
There is a specific category of continuity goal that organisations complete without actually completing: documentation that exists but has never been validated by someone other than the person who wrote it.

The test is concrete: if the documentation is intended to allow another person to perform a function, can that person perform it? Not with the author's help, not with an explanation of the parts that "need to be updated," but independently, using only what has been written.

Most organisations that ask this question honestly find that the documentation closes fewer gaps than it appears to. The knowledge that is hardest to capture (the why behind the what, the contextual judgements, the informal relationship history) tends to resist documentation precisely because it was never made explicit in the first place.

Setting a continuity goal with a genuine validation method is the shift that changes the outcome. Not "document the process" but "complete a process document that allows a new team member to perform the function without additional guidance."

How many of your organisation's continuity goals have a validation method attached to them?
11
Most leaders know exactly who their highest-risk team members are. The knowledge transfer conversation still does not happen, and the reason is specific.

Initiating a conversation about what would happen if someone left sends a signal that is almost impossible to calibrate. To a high performer who is deeply invested in the organisation, it reads as a precursor to being managed out, or as a failure to appreciate what they contribute. The result is that the conversation does not happen until the resignation has already landed.
The Diagnostic #2 examines the fear that sustains this pattern and the reframe that resolves it. The shift from "what would happen if you left?" to "how would you set a successor up for genuine success?" extracts identical information with a fundamentally different relational experience.

This is a systems design question as much as a communication one. The organisation that has built deliberate knowledge transfer into its development processes does not need to rely on a single conversation.

What knowledge in your team is most overdue for a transfer conversation?
11
Last week's absence test confirmed whether the system can run without the leader. This week's test is harder, because it does not announce itself.

The key person test is what happens when the person who holds the critical knowledge, manages the anchor client, or understands why three years of architectural decisions were made the way they were, hands in a resignation on a Monday morning with two weeks' notice.

The test reveals three categories of organisational dependency that tend to survive even deliberate system building: technical knowledge (how things work), relational knowledge (what clients and stakeholders expect), and contextual knowledge (why decisions were made). The first category is the most commonly documented; the third is almost never captured until the moment it is needed.

This week examines what the key person test reveals, and what it takes to build an organisation that can absorb the loss before the test runs itself.

What person in your organisation would create the most disruption if they resigned tomorrow?
01
There is a version of leadership where stepping away feels like a risk to be managed, and a version where stepping away is the most valuable diagnostic available.

The difference is not in the leader's comfort with risk. The difference is in how the system has been designed. A well-designed system produces specific, actionable findings when the leader withdraws. A poorly designed system produces anxiety.

This week launched a new 13-week series exploring what happens when leadership systems meet real-world pressure. The first test was the simplest: what happens when the leader steps away? The findings, from three patterns of absence to a case study where the gap revealed itself on a Tuesday, are specific enough to act on immediately.

Next week, a harder test: what happens when a key team member leaves, and the system must absorb the loss without reverting to dependency.

What would your absence reveal that your presence is currently hiding?
01
The system held for three days. On Tuesday, a client scope change exposed the gap that two years of building had not yet addressed.
The finding was not that the system failed. The finding was that the system handled clear-cut decisions and obvious escalations well, and struggled with the contextual grey area: decisions where the technical criteria were met but the relational and commercial context was missing.

The fix was three contextual questions added to a single process. Within three months, the same division lead handled a similar situation independently.

This is what systems testing looks like in practice: specific findings, specific fixes, measurable improvement. The value is not in whether the test passes or fails; it is in the precision of what the test reveals.

Where in your business is the grey-area decision that your team would hesitate on without you?
01
Most leaders have taken holidays. Very few have conducted a genuine absence test.

The difference is in the design. A holiday preparation smooths things over: pending questions pre-answered, a colleague briefed to "keep an eye on things," email checked once a day. The system is never fully tested because the leader never fully withdraws.

An absence test requires three conditions: genuine withdrawal (no checking in), normal operating conditions (not a deliberately quiet week), and someone documenting what actually happens while the leader is gone.

Without all three, the exercise confirms what you already believe rather than revealing what you need to know.

The leaders who have run this test consistently describe the preparation as the most valuable part. Identifying which decisions need criteria documented, which team members need briefed, and which processes have never been written down surfaces the gaps before the absence even begins.

What's one process in your team that has never been documented because the person who runs it has never been away?
01
The fear that prevents most leaders from testing their own systems is not about risk. Preparation handles risk.
The deeper fear is about identity.

Careers are built on direct contribution, on being the person who solves the problem, makes the call, holds things together. Testing the system means confronting the possibility that the organisation can function without that direct involvement, and that your value needs to be measured on a different scoreboard.

The Diagnostic is a new recurring series examining the fears leaders avoid naming and providing systematic frameworks for addressing them. This first edition introduces the decision inventory: mapping every decision you make in a typical week and categorising each as "requires my judgement" or "requires my criteria."

The ratio almost always surprises the leader who runs it.

What do you think your ratio would look like?
11
Every organisation has a version of the same hidden question: what would actually happen if the senior leader disappeared for a week?

Not a holiday where they check email on the quiet. A genuine withdrawal, where the business has to operate on whatever has been built before that moment.

The answer tends to fall into one of three patterns. The bottleneck, where decisions accumulate because the team is waiting for permission. The drift, where operations continue but standards shift without the leader's quality judgement. The surprise, where the system works and the leader must reckon with what that means for their role.

Each pattern tells a different story about the state of the organisation, and each points toward a different kind of work.

This week begins a new 13-week series exploring what happens when leadership systems meet real-world conditions. The first test is the simplest and the most revealing.

What do you think would happen in your organisation after five days without its most senior leader?
01
Most strategic reviews are exercises in retrospective justification. Targets get reframed, shortfalls get contextualised, and the narrative emerges that reasonable progress was made in challenging conditions.

The leaders who actually improve from one cycle to the next do something different. They separate what was achieved from what was intended. They identify where the gap came from: wrong objective, insufficient execution, or changed environment. Each requires a different response.

The hardest question in any review is not "why didn't this work?" It's "if we weren't already doing this, would we start it today?" The answer to that question, applied honestly across every ongoing initiative, produces more strategic clarity than any retrospective can.

What's one initiative you'd stop if you were being fully honest about the results?
12
The fear of measuring your own leadership impact is one of the least discussed barriers to growth.

It's not about discovering you're ineffective. Most leaders have enough evidence that they're performing. The deeper fear is discovering that the work you find most satisfying is producing the lowest returns, and that the work you spend the least time on is where your real impact sits.

The Impact Audit framework breaks impact into three categories: direct contribution, capacity creation, and system design. Each operates on a different time horizon. Each tells a different story about where your effort is producing returns.

The leaders who run this audit honestly and act on what it reveals tend to produce disproportionate results in the following year.

What would your time-versus-impact distribution look like if you tracked it honestly for a fortnight?
00
Always wonderful to recieve 5-star feedback!
01
Legacy is a word that gets saved for retirement speeches and succession plans. In practice, the leaders who leave the most durable mark are the ones who started building it years before anyone expected them to.

The test is simple. If your team can explain why the organisation operates the way it does, including the standards, the decision logic, the values in action, without referencing you personally, the culture is designed rather than dependent.

If they can't, what you've built is impressive. It's also fragile.

This week we're exploring what it means to build something that outlasts your direct involvement, and why the leaders who do it best are the ones who started early.

What's one element of your team's culture that would hold its shape without you?
00
Always wonderful to recieve 5-star feedback!