Rotating Tasks Nobody Wants to Rotate

Some tasks resist spreading for good reasons, which is exactly why they end up as single-person dependencies.

For a resilience routine built around “Rotating Tasks Nobody Wants to Rotate”, improvement depends on seeing whether backup work happens outside an emergency. Teams can use www.monitask.com to organise practice time and compare planned coverage with actual participation, but the record should prompt a handover conversation rather than become an automatic judgement about an employee.

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 categories

Tasks the expert does far faster. Rotating costs real time every month.

Tasks with consequences if done wrong. Payroll, regulatory filings, anything involving money.

Tasks nobody enjoys, where the current holder is the only volunteer.

And tasks requiring a relationship, where rotating damages something.

The honest arithmetic

Rotation costs: slower execution, more errors initially, and the expert's time supervising.

It buys: resilience, and a second person who understands the area.

For a monthly task, three or four rotations is enough to establish coverage, after which it can go back to the fast person.

That is a bounded cost, which is a different proposition from permanent rotation.

The pattern that works at small scale

Not a rota. A planned handover of a few instances, then return.

"You do the next two month-ends with me available, then I take it back" is achievable.

"We rotate month-end between four people forever" is not, in an organisation of twelve.

High-consequence tasks

These are the ones most worth covering and the ones people most resist rotating.

The answer is supervision rather than avoidance: the learner does it, the expert checks before it goes out.

Checking is much faster than doing, so the cost is lower than expected.

And the check gets removed after two or three clean runs.

Tasks nobody wants

Usually held by whoever is most conscientious, which is unfair as well as risky.

Rotating these is a fairness question before it is a resilience one, and framing it that way makes it easier to raise.

Consider also whether the task should exist, which is sometimes the better answer.

Timing it

Rotate when things are calm, which is never obviously the moment but is the only time it is possible.

Attaching it to a quiet period in your year works better than scheduling it abstractly.

And do one thing at a time. Attempting to spread five tasks at once produces five half-transfers.

Recording the fact

Update the map: this activity now has two names.

Which is the point of doing it and the thing that gets forgotten, so the next review shows no progress despite real work.

What to check

Which tasks has nobody else ever done, and why not?

Have you done the arithmetic on a bounded rotation rather than a permanent one?

Could a high-consequence task be done by somebody else with a check?

And does anything on your map have two names that did not last year?

The point

A bounded rotation — do the next two with me available, then I take it back — is achievable where permanent rotation is not..

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.