THE ONE WHOSE FIXES RUN WITHOUT THEM

What changes when the system can see itself

A manager spends two hours every morning checking. Did the opener follow the checklist? Did the closer lock the walk-in? Did the new hire finish the training module? Did the order go out? Each question takes three minutes. Fifteen questions eats the morning.

The manager is not managing. The manager is being the eyeballs of a system that has none.

Every one of those questions exists because the result of the action is invisible. If the result were visible, the question would not need to be asked. And the manager would have two hours back. Not for more work. For the kind of thinking that actually moves the operation forward.

Every recurring task you check on manually is an open loop. The system produced an action but no visible signal of whether it happened. Your follow-up is the signal. You are the sensor.

  list every recurring task or standard in your area.
  for each one, answer: how do I know it happened without asking?

  task: __________
  how I know without asking: __________
  (if blank, this is an open loop)

  task: __________
  how I know without asking: __________

  task: __________
  how I know without asking: __________

  task: __________
  how I know without asking: __________

  task: __________
  how I know without asking: __________

  count your open loops: __________
  count your closed loops: __________

  ratio tells you: more open than closed → your day is maintenance.
  more closed than open → your day is leadership.

The open loops are where your time goes. Not all of them. Not equally. But the ones you check most often drain the most capacity.

02 — The three things that make a loop close

A closed loop has three properties. If any one is missing, the loop is open.

First: the done state is binary. Not “kitchen is clean” but “all 12 items on the closing checklist photographed by 10:15 PM.” If the completion state is subjective, nobody can verify it, including the person doing it.

Second: the result is visible without checking. The signal exists in the environment. A shared photo album. A board with marks. A timestamp in a system everyone sees. Not a report someone has to pull up. Ambient visibility.

Third: non-completion is as visible as completion. This is where most systems fail. Finished tasks show up. Unfinished tasks are simply absent. Absence is invisible. A properly closed loop shows a red mark where a green mark was expected. The empty space screams.

  pick your most time-consuming open loop from the previous exercise.

  the task: __________

  step 1 — define binary done state:
  what specifically must be true for this to count as done?
  __________

  step 2 — design ambient visibility:
  where will the signal appear without anyone having to check?
  __________

  step 3 — design the non-completion signal:
  what happens visibly if it does NOT get done?
  __________

03 — What happens when you close one loop this week

One closed loop returns one unit of maintenance time. That time is reinvested. The math compounds.

Close the loop you designed in the previous section. Not next month. This week. Accept that it will be imperfect. The first version is never elegant. It does not need to be. It needs to make the result visible.

  the loop I am closing this week: __________
  the done state: __________
  the visibility mechanism: __________
  the non-completion signal: __________

  time I currently spend maintaining this loop per week: __________
  time I will spend after closing it: __________
  time returned: __________

  what will I do with that returned time?
  __________

One hundred minutes returned from one loop. Invest those minutes in closing the next loop. Two loops closed returns more time. The time reinvests. Within a month, the compounding is visible in your calendar.

04 — Reading the data your closed loops are generating

A closed loop does more than confirm execution. It generates data. Patterns in that data are free intelligence that did not exist when the loop was open.

A loop that fails on the same days reveals a scheduling constraint. A loop that fails with the same person reveals a skill or commitment constraint. A loop that fails under the same conditions reveals a design constraint.

  pick a closed loop that has been running for at least two weeks.

  the loop: __________

  failures this period: __________

  pattern check:
  same person?      YES / NO → if YES: skill or commitment constraint
  same day/time?    YES / NO → if YES: scheduling or resource constraint
  same conditions?  YES / NO → if YES: process or design constraint

  the pattern points to: __________
  the intervention that matches: __________

Before the loop was closed, both failures would have been invisible. The pattern would have been invisible. The constraint would have been invisible. You would have continued maintaining and wondering why prep keeps slipping on random days. The days were not random. You just could not see the pattern.

05 — Seeing the handoff where your chain breaks

Individual loops can all be closed and the overall process can still fail. The failure lives in the handoffs between stages, not within them.

When prep finishes and nobody signals the line cook to start setup, thirty minutes evaporate in the gap. Both loops are closed. The chain is open.

  pick a process with multiple stages.

  stage 1: __________  → handoff → stage 2: __________
  stage 2: __________  → handoff → stage 3: __________

  for each handoff:
  does completion of the previous stage automatically trigger
  the next stage?  YES / NO

  if NO: what signal is missing?
  __________

  how would you make it visible?
  __________

The fix cost nothing. A card on the wall. The thirty minutes it recovers every day is worth more than most technology purchases.

06 — The difference between tracking and visibility

A report that shows completion rates is tracking. A board on the wall that shows today’s results in real time is visibility. Both contain the same information. One requires intention to access. The other is encountered by existing in the space.

  pick a metric or result you currently track.

  the metric: __________
  where it lives: __________
  who sees it without effort: __________
  who has to actively look for it: __________

  if most people have to actively look → this is tracking, not visibility.

  how could you move this into the environment?
  __________

The board is not surveillance. It is the system’s eyes made visible to the people inside the system. When the team can see their own performance, they self-correct. When they cannot see it, they need you to tell them. One produces autonomy. The other produces dependence.

07 — What your maintenance burden is actually telling you

The amount of time you spend maintaining is a direct measurement of how many open loops your system has. It is not a reflection of your team’s quality. It is a reflection of the system’s architecture.

  estimate your weekly time spent on:

  checking whether things happened: __________  hrs
  following up on things that did not: __________  hrs
  reminding people of things they should know: __________  hrs
  verifying quality of completed work: __________  hrs

  total maintenance hours: __________

  this number IS your open loop count, measured in time.

  if you closed your biggest open loop, how much would this drop?
  __________

Twelve hours is not the cost of management. It is the cost of open loops. Close the loops and the hours return. Not to “more management.” To the work that actually changes outcomes.

08 — Building the loop that makes other people build loops

The highest-leverage loop you can close is not an operational one. It is the one that installs loop-building in the people you lead.

When someone tells you they spend all their time checking on things, that is a diagnosis. They have open loops. Instead of telling them how to close a loop, ask the question that makes them generate the answer.

  the next time a direct report complains about being
  overwhelmed by follow-ups:

  the question to ask:
  "What is the one thing you check on most?
   What would it take to know without checking?"

  their answer: __________
  (do not give them your answer. wait for theirs.)

  if they design a loop: let them build it.
  if their design is missing a property (binary done state,
  ambient visibility, non-completion signal):
  ask the question that exposes the gap.
  do not fill it for them.

Building their loops for them is faster. It is also dependency-creating. If you design their systems, they will always need you to design the next one. If they design their own, they own the pattern. The one-month delay is worth the permanent capability.

The shift

There are two kinds of systems. One requires a human to be its eyes, checking and verifying and following up until the human burns out. The other can see itself. It generates its own signals. It corrects its own deviations. It frees the human for the work that humans are actually for.

The entire mechanism fits in one question: “How would I know this happened without asking?”

Every answer to that question is a loop you can close. Every closed loop is time returned. And time, reinvested in closing the next loop, compounds.

The mechanism this training stands next to lives in The Machinery of the Closed Loop.