Clubhouse Notes #02

What stops working if you stop?
‍

Most companies know what business they are in.

Far fewer know what would happen if they suddenly stopped delivering.

That distinction matters more than it used to.

Critical infrastructure was once relatively easy to recognize: energy, water, transport, telecommunications, hospitals.

Today, criticality is distributed through software, specialized suppliers, outsourcing and tightly connected supply chains.

A company may never have thought of itself as critical.

Its customers might.

So instead of asking: Are we part of a critical sector?

Ask: What stops working if we stop?

Look for dependency, not labels

Criticality is not necessarily a characteristic of the company itself.

It is a characteristic of the dependency around it.

A cloud provider may be critical to a transport company. A maintenance supplier may be critical to a hospital. A small specialist may be essential to a much larger organization.

So, begin with the system you are part of.

Take one important product, service or capability you provide.

Then ask four questions.

1. What stops if we stop?

Do not ask what becomes inconvenient.

Ask what genuinely ceases to function.

Which customers can no longer operate?

Which services cannot be delivered?

Which processes come to a halt?

The more concrete the answer, the clearer the dependency.

2. How quickly does it become serious?

Some disruptions can be absorbed for weeks.

Others become critical within hours.

How long can the customer operate without you?

When does disruption become operational failure?

The shorter the interval, the more critical your role may be.

3. Can someone else replace us in time?

A company may be replaceable in theory, but not in practice.

A new supplier may require integration, approval, specialist knowledge or physical changes.

Can somebody else do what we do?

Can they do it quickly enough?

That difference often reveals hidden criticality.

4. What must still work under pressure?

Most operating models are designed for normal conditions.

Critical systems must also work when conditions are not normal.

Imagine reduced staffing, a cyberattack, loss of a supplier or sudden demand.

What is the minimum service you still need to provide?

Which people, systems and suppliers does that depend on?

This is where resilience becomes a management question.

From continuity to responsibility

Once an organization discovers that others genuinely depend on it, something changes.

The issue is no longer only business continuity.

The organization acquires what we might call a duty to operate.

Not necessarily a legal duty.

But a managerial one.

That does not mean building redundancy everywhere. It means knowing where efficiency can no longer be the only consideration.

If your failure stops something important elsewhere, decisions about suppliers, staffing, cybersecurity and backup systems are no longer purely internal choices.

They become part of a wider system of resilience.
‍

Bring the dependency into the room

Discovering that others depend on you is only useful if that knowledge changes how the organization is managed.

Start with the decisions where criticality should make a difference.
‍

Leadership. Which decisions would you make differently if continuity were treated as part of your responsibility - not simply as an operational concern?
‍

Operations. Where are you dependent on a single person, supplier, system or piece of infrastructure that is difficult to replace?
‍

Communication. Do the people who depend on you understand what you can maintain under pressure - and where the limits are?
‍

Brand and positioning. Does the way you describe your role reflect the responsibility customers actually place on you, or only the product you sell?
‍

The point is not to turn criticality into a new corporate narrative.

It is to make sure that an important dependency, once discovered, becomes visible in the decisions that shape the organization.

In practice

To understand whether your organization has become critical:

• Identify what stops if you stop.
• Assess how quickly the consequences become serious.
• Test whether others can replace you in time.
• Define what must still work under pressure.

Critical infrastructure is increasingly difficult to recognize from the outside.

Sometimes the most important organization in the system is simply the one everyone discovers they cannot do without when it stops working.