Recording Decisions, Not Just Procedures

Procedures tell a successor what to do. Decision records tell them what they can safely change, which is the harder and more valuable question.

Putting the controls in “Recording Decisions, Not Just Procedures” into practice requires ownership that survives absence and can be reviewed without relying on memory. Teams can use Monitask to see how responsibility and working time are distributed around recurring tasks, while keeping credentials and sensitive records in authorised systems and limiting activity data to a proportionate operational purpose.

For an independent benchmark, compare the local approach with Atlassian knowledge-sharing guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

What gets lost

Why the contract has an unusual clause.

Why a supplier was chosen over a cheaper one.

Why a process has a step that looks redundant.

Why something was tried and abandoned.

Each of those, forgotten, gets rediscovered expensively: somebody removes the redundant step and finds out why it was there.

What a decision record contains

The date.

What was decided.

What the alternatives were.

Why this one, in a sentence or two.

And anything that would change the decision if it were different.

Five lines. Written at the time, when it takes three minutes; written later, it takes an hour and is wrong.

When to write one

Anything that will be lived with for more than a year.

Anything where somebody might reasonably ask "why do we do it this way".

Anything involving money, a commitment, or a supplier.

Not every decision, which would be exhausting. A small organisation might record a dozen a year.

Where to keep them

In date order, in one place, findable by searching for the thing they concern.

Attached to the relevant activity note where one exists.

They are not a formal register and should not become one, which is how the habit dies.

The clause that earns its place

"What would change this."

"We chose this supplier because of the delivery window; if that stops mattering, reconsider."

That sentence converts a historical note into something actionable, and it is the part successors most appreciate.

The founder's decisions

The largest concentration of unrecorded reasoning in most small organisations.

Much of it was decided alone and never explained, and it is precisely what a successor or a buyer needs.

An hour a month working backwards through the significant ones is an unusually high-return use of an owner's time, and almost nobody does it.

What this prevents

Successors either preserving everything because they dare not change it, or changing things and rediscovering the reasons painfully.

Both are common and both are expensive.

A decision record is what lets a successor tell the difference between a deliberate arrangement and an accident.

What to check

Could you explain why your three most unusual arrangements exist?

Is any of that written down?

When something odd is questioned, does anybody actually know the answer?

And does anything you record say what would change it?

The point

Write what would change the decision.

That sentence turns a historical note into something a successor can act on.

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.