Rotating Ownership So No One Is A Single Point Of Failure

Every team has areas with exactly one owner. The person who handles the billing run. The one who knows the deployment. The one client contact nobody else has ever spoken to. It works fine until it does not.

Rotating ownership means each of those areas gets a second person who takes it over for a fixed period, on a schedule, whether or not anything is wrong. It costs a few hours a month once it is running. The first two cycles are genuinely worse than not doing it, and most teams quit there. Understanding what breaks early is the difference between a rotation that survives and one that gets abandoned by March.

What a rotation actually is

Pick the areas where one person is the only owner. For each one, name a second person. Then set a period, usually a month or a quarter, during which the second person does the work and the first person is available but does not do it.

Three rules make it work rather than becoming theatre:

• The second person does the real work. Watching does not transfer anything. They press the buttons and take the calls.
• The first person stays reachable but silent. Available to answer, not to take over. This is the hardest rule for the original owner.
• It is on a calendar. A rotation that happens when things are quiet never happens.

What breaks in cycle one

The first cycle is slow and slightly embarrassing. Expect these.

• Everything takes about three times as long. The new owner does not know the shortcuts. Plan for that rather than being surprised by it.
• A hidden dependency shows up. Access somebody never had. A password in one person's notes. A supplier who only recognises one name.
• Quality dips somewhere visible. A report is late. A client gets a slightly worse answer. This is real cost, not imaginary, and it is worth telling the client's expectations in advance if the area touches them.
• The original owner interferes. They will step in, usually with good intentions, and the transfer stops. Somebody senior has to notice and stop it.

Cycle one produces one very valuable thing: a list of everything that was undocumented. Write it down while it hurts, because it is the starting point for writing down a process only you know.

What breaks in cycle two

Cycle two is where teams quit, because the pain is less obvious.

The new owner now knows enough to be dangerous but not enough to be confident. They will make a decision the original owner would not have made. Sometimes theirs is better. Sometimes it is worse. Either way there is an awkward conversation about who was right.

That conversation is the point of the whole exercise. It is where the unwritten judgement finally becomes explicit and gets recorded. Skip it and you have moved the tasks without moving the reasoning.

Also expect a drop in enthusiasm around here. The novelty is gone and the payoff has not arrived. Say out loud that this is the expected shape.

Where it starts paying off

By the third cycle, three things change.

Handovers get faster, because the second person has done it before. Documentation exists, because the first cycle forced it. And the original owner gets time back, which is the benefit they never believe in at the start. Even the handover note gets shorter, because most of it has already been written.

The measurable signal is simple: how long does it take to hand this area to someone new. If that number is falling cycle over cycle, it is working.

Keeping track without a spreadsheet

A rotation dies when nobody can see whose turn it is.

Keep ownership on the same records as the work itself, so the current owner of an area is visible next to the tasks rather than in a separate document. SicherOne is built around project records and HR records sharing one set of data, so the rotation, the leave calendar and the workload view all read from the same place. That matters more than it sounds: a rotation that lands on somebody's annual leave is the fastest way to kill the habit.

Start with two areas, not all of them

Do not rotate everything at once. Pick the two areas where a single person leaving would hurt most, which you can work out by counting the cost of one person holding the knowledge, and run those for two quarters.

Two areas, two cycles, a few hours a month. If the handover time has dropped by the end, add two more. If it has not, work out which of the three rules you quietly broke, because it is almost always one of those.