What to Spread First

The map produces more items than anybody will address. Ordering them properly is the difference between real improvement and a year of scattered effort.

The principles in “What to Spread First” become easier to maintain when ownership and time spent are visible. Teams evaluating productivity tracking platform can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The two questions

What happens if this is unavailable for two weeks?

How much effort would a second person cost?

Score each roughly — high, medium, low — and the ordering falls out.

The order

High consequence, low effort: do these immediately. Access, credentials, supplier contacts, a second signatory. Most organisations have several and they are frequently the whole of the practical risk.

High consequence, high effort: schedule these. Client relationships, qualifications, genuine expertise. They need a year and a decision.

Low consequence, low effort: do them when convenient. Writing a note while the knowledge is fresh.

Low consequence, high effort: do not do these. Saying so explicitly prevents them from sitting on a list generating guilt.

Why consequence beats frequency

People instinctively start with what happens most often, because it is most visible.

A daily task with a two-day workaround matters less than an annual task with no workaround and a legal deadline.

Ask what breaks and how badly, not how often it comes round.

The two-week test

Use a fixed period rather than imagining indefinite absence.

Two weeks is long enough to be realistic and short enough to reason about.

Some things survive two weeks untouched, which is the finding that removes them from the list.

Doing the cheap ones first

Not because they matter most but because they build the habit.

An organisation that has fixed its access problem in an afternoon has evidence that this is tractable, which makes the expensive items easier to commit to.

Starting with the hardest item is how these efforts stall in month one.

How many at once

One expensive item at a time.

The cheap ones can be batched.

Three expensive transfers running simultaneously produces three incomplete ones, and incomplete transfer is close to no transfer.

Revisiting the order

After each item, and whenever the organisation changes.

New activities arrive with one person attached, so the list regenerates.

The question is whether you are closing faster than new ones open, which the measurement note covers.

What to check

Have you scored your list by consequence and effort?

Are the high-consequence, low-effort items done?

Is anything on the list that should be struck off as not worth doing?

And are you working on one expensive item or several?

The point

Order by consequence and effort, not by frequency.

A daily task with a two-day workaround matters less than an annual one with a legal deadline.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.