Pruning My Pothos
← StoryboardsStoryboard · 10 frames · Stage 05, Human judgment

Human-in-the-Loop Is a System Design Choice

An Approve button isn't oversight. Ten frames on what a person needs before their judgment actually controls anything.

Download PDFRead the article →

01 / 10

  1. A man in a deckchair, lassoed inside a rope loop that runs to a machine labelled automation, sips his tea under a sign reading human, required. Present, polite, powerless. Below, a screen asks: send refunds automatically to all customers? Approve is the only option. Being present isn't the same as being in control. Oversight needs a decision still open, an owner, enough context, real alternatives, and a path that works when they say no.

  2. Three different things: a person is present, perhaps only notified after the fact. Their approval is required, a real constraint but only on sequence. They can judge, and only this one is oversight. On an architecture diagram the three look the same.

  3. Approve. Or also approve. If a workflow asks a human to decide, at least one meaningful way to say no has to exist. Otherwise the person is only a signal.

  4. An envelope is stamped sent. Later, a person is asked to approve something that already happened. Approval is crossed out in favour of notification. If the outcome is decided before they look, the step is monitoring, audit, or the start of a correction, not approval.

  5. Pulled the brake. Kept the brake. A review step is weak when refusing has no implemented consequence. The no has to change what happens next.

  6. Whoever's free is crossed out: available isn't responsible. The reviewer should own the decision, have the standing so their yes settles it, and know the subject, or they are a delay rather than a control.

  7. Reviewed at the speed of a stamp. A person is present and the workflow requires their approval. That is not the same as the person being able to judge: they need the context, the time and real alternatives.

  8. Approve and it ships. Decline and then what? A toast saying Declined, followed by nothing, is crossed out. Real non-approval paths: revise with the reason, stop and release what was held, ask for evidence, escalate, or fall back to a manual route. If refusing does nothing, the reviewer has a delay, not a decision.

  9. Kept in the loop. By email. Afterwards. A decision reserved for a person needs it still open when they see it, an owner, enough context, real alternatives, and a path that works when they refuse.

  10. Five questions for any Approve button: what decision stops here, who owns it, what does the reviewer see, what else can they do, and what happens when they decline. If any answer is missing, the gate is doing less than it appears to.