Who Is Accountable When an Agent Is Wrong Introduction

What you will need to show when an agent gets it wrong

Three questions that define accountability, the four places the trail goes cold, three you can close yourself — and the paperwork that is not worth keeping.

Part of the leadership bundle · coming soon
You can read this introduction now. The 12 steps open when purchases do. Meanwhile, The Judgment Gap is free to read in full.
Part of the leadership bundle: $49.99
Every leadership volume, including new ones when they're released. One-time purchase, free updates. The Judgment Gap is free to read in full.
Decision Q&A

Four questions this volume answers

1Why does it matter to me?

Someone will ask you to explain what an agent did on your team's behalf, months after it happened. Accountability is a property of your records, not your intentions: who decided this, on what evidence, and what were they told at the time? None of the three can be answered from memory.

Shown in step 1 · 2 · 3
2What should I ask?

Ask your team to reconstruct one decision from last month and see where it stops. Then check four records against what you keep: the version of the thing that ran, the inputs it was given, who said yes and when, and what that person was shown. Most managers find the last one is kept for nothing.

Shown in step 6 · 7
3How will I know it's going wrong?

Configurations edited in place; approvals that are a name or a thumbs-up with nothing showing what the approver saw; agents still running whose owner has moved on; and “a human is in the loop” in a design document with no record of anyone looking at anything.

Shown in step 4 · 5 · 9 · 10
4What do I decide?

Close three breaks yourself this month: keep a dated copy of anything that runs, attach what an approver was shown to the approval, and put a current name against every agent. Then raise reproducible inputs as engineering work, using your reconstruction result. Don't install paperwork that answers none of the three questions, and rewrite or delete the “human in the loop” sentence.

Shown in step 8 · 10 · 11

Accountability is a property of your records, not your intentions.

At some point somebody is going to ask you to explain something an agent did on your team's behalf. You have reviewers. You have approvals. You believe there is a human in the loop. Believing that and being able to demonstrate it are different states, and the difference is discoverable in advance.

This volume is three questions, four break points, and the four records that close them. It assumes you have read nothing else in this series.

the decision the evidence the configuration the run the output the question starts at the output and travels backward somebody chose this recorded on this basis recorded which was set to this recorded and this ran recorded and produced this recorded who decided this? and it arrives this is the chain working. It is an ordinary thing and it ordinarily works, when the records are there.
The spine of the volume: a reconstruction starts at the output, which is the only thing you have, and works backward toward the decision, which is the thing you need.
What moves: a query enters at the output end of the chain and travels leftward along it, arriving at the decision.

The three questions

  1. Who decided this? A record naming a person and a moment.
  2. On what evidence? Whatever they were looking at when they decided — not what is available now, which is different.
  3. What were they told at the time? The one people leave out, and the one that decides whether the first two mean anything.

Three of the four break points cost almost nothing to close, and you can close them yourself without a mandate. The fourth is real engineering work and is not yours alone — and the volume says which is which rather than leaving you to promise all four.

One step is about what not to do. A great deal of what gets installed after an incident costs real time and produces nothing anybody can use. A volume about accountability that could not name that paperwork would be an argument for more process, and this one is not.

What you can do afterward

Try to reconstruct one decision your team made last month, and find out where you stop. Tell an approval from a name beside a decision. Stop writing a sentence about a human in the loop that survives no examination. And close three break points this month without asking anybody.

The three questions, the four records and the break points in order of cost are on one page you can print.