Learning Center / Operating an Outcome

Course 2 · Lesson 1 of 5

What has to stay true

A restaurant passes its food hygiene inspection on a Thursday. The inspector signs the form, says well done, and leaves. That is the whole of the good news. The outcome the restaurant actually carries is not the inspection; it is the kitchen being in a state to pass an inspection on any Thursday, including the one after a bank holiday weekend when two staff are away.

Reaching and holding are different jobs

Reaching an outcome has a shape. There is preparation, a moment of completion, and a relief. Holding an outcome has no shape at all. It is a set of conditions that need to be true continuously, and nothing announces the day one of them stops being true.

This is why so much operational trouble looks sudden and is not. The date was missed because a condition stopped holding six weeks earlier and nobody was watching that condition.

The staying-true conditions

Take any outcome and ask: what has to stay true for this to keep being true? The answers are the conditions, and they are usually dull.

For the restaurant, they look like this:

• The temperature log is filled in every day, including the days the manager is off.
• Supplier delivery notes are kept and filed by date.
• The allergen sheet is current and posted where staff can find it.
• Every member of staff has a dated record of training.
• The cleaning schedule is signed, not just performed.

None of these is the outcome. All of them hold it up.

Each condition needs three things

*A check.* Something that would reveal the condition failing. A temperature log reveals itself: either there is a reading for Tuesday or there is not. A cleaning schedule reveals itself the same way. A condition with no visible check is not a condition, it is a hope.

*A record.* Written evidence that the check happened. Records are what turn an argument about whether something was done into a question of whether a page exists. They are also what makes an outcome handoverable, because the next person can see the pattern.

*An owner.* A single name for the condition. Not the outcome's owner, necessarily. The restaurant owner is answerable for the hygiene outcome. The head chef is answerable for the temperature log.

Maintenance is where the hours live

Ask a landlord how long the certification of forty flats takes and the honest answer is not the inspections. It is the chasing, the filing, the diary, the duplicate certificates found two years later in three different folders. That maintenance is the reason the machinery around an outcome costs more than the outcome itself.

The useful question is not how do I do this faster? It is *which of these conditions needs a person at all?* A temperature log can be kept by whoever is standing there, and a record of it can be assembled by something that does not get tired. The judgement about what to do when a fridge reads warm stays with the chef.

Drift, and why it is normal

Conditions decay. A form gets filled in from memory rather than from the probe. A supplier's delivery note goes into a drawer. A new member of staff is trained but nobody writes the date down. This is not evidence of bad character. It is what happens to any condition that nobody checks.

Which is why the check on the check matters. Somebody, once a month, opens the log and looks. It takes ten minutes and it is the difference between holding an outcome and believing you hold one.