The Arrows Nobody Checks — script v2

Stage 1 of 3, final. Pure narrative. No visual direction.

Changes from v1, per the independent critique:

  • The crux claim was false as written ("nobody has ever said I don't accept that arrow"). People contest flowcharts all the time. The true and stronger claim is that there is no criterion a challenge has to satisfy. Rewritten.
  • Opening reshaped — v1 reused Part 1's closing device almost verbatim. Now opens on one chain made visible, then widens.
  • The count-announcement ("there are eight of them") cut; the weakest test merged.
  • Ends on "a different kind of object entirely." Sequel-bait cut to one line.
  • "No expertise required" softened — asking the question needs none, answering it often does.
  • Narrator intrusions and mid-paragraph bolding thinned.

~1,150 words.


Dr Adeyemi can tell you exactly what is wrong with the clinic, and she can show her working.

Every prescription needs her countersignature. So the pharmacist interrupts her, on average, eleven times a morning. So consultations overrun. So she finishes late, writes her notes after seven, and the notes for the next patient aren't ready when they walk in — so that history gets taken twice, and that consultation overruns too.

That is not an opinion. It is a chain. It has parts, and each part could be wrong somewhere specific.

Four other people in that building are carrying chains just as detailed, and they arrive somewhere else entirely. The practice manager's ends at funding. A nurse's ends at the ten-minute appointment rule. Maria's ends at the referral backlog.

All of them are intelligent. All of them have been there years. All of them are certain.

And not one of those chains has ever been outside the head that made it.


This is the thing standing between the clinic and its constraint. Not that nobody knows — five people have a theory. It's that there is no way to choose between them.

You can't do it by arguing, because you have been in that meeting. The winner is whoever is most senior, most confident, or least tired at four o'clock.


Try it yourself, on something small.

Take something you believe about why something in your life isn't working. Why the team misses deadlines. Why the meetings are useless. Why you never get to the gym.

Write it down as a sentence: X causes Y.

Two things tend to happen. The belief that felt crisp in your head goes vague the moment it has to survive on paper. And once it's written, it starts sprouting doubts you'd never consciously entertained while it lived comfortably inside your skull.

Nothing has changed except that it is now outside you, where it can be looked at.


Most of our thinking about complicated situations happens invisibly, in intuition. Intuition is fast, rich, and often right. It is also unexaminable.

When your instinct says the real problem here is funding, there is no chain of inference to inspect, because there is no chain. There is a feeling with a conclusion attached.

So disagreements between intuitions can't be settled by evidence. Only by rank, charisma, or exhaustion.


Now — plenty of people already draw diagrams. Flowcharts. Mind maps. Boxes on a whiteboard with arrows between them.

And people do argue with them. That shouldn't come before this. That box is wrong. Anyone who has sat through a workshop has watched someone contest an arrow.

But watch what happens next. There is no way to settle it. Nothing says what would make an arrow correct, so the objection is just one more opinion, and it gets resolved the same way everything else in the room does — by whoever is most senior or most persistent.

The arrows are contestable. They are not checkable. There is no standard a challenge has to meet, and therefore none it can win by.

An arrow is only worth drawing if it can be shown to be wrong. And that requires rules.


So here are the rules. They are less a technique than a set of questions you are allowed to ask about any claim anybody makes.

Do I understand you? Not do I agree — do I know what you mean. This comes first, and deliberately, because a great many arguments that look like disagreement are two people using one word differently and getting steadily angrier about it.

Is that a claim at all? Is it a complete thought, one idea, that could be true or false? "Funding" is not a claim. "Our budget fell twelve per cent in real terms since 2019" is.

Is that cause enough on its own? This is the most common flaw in human reasoning, and Dettmer's example for it is perfect. If we have fuel and a heat source, then we have fire. True? No. You forgot oxygen. You forgot it because it is always there — so ordinary that it never occurred to you to say it.

Every argument has an oxygen: the condition so unremarkable that nobody names it, right up until the day it isn't there.

Could something else have done it? A fever can come from an infection or from an afternoon in the sun. Remove your stated cause — would the effect have happened anyway? If so, you haven't explained anything yet.

Have you got it backwards?

Many fishermen are on the riverbank. Their nets are full. Therefore the fishing is good.

That is precisely wrong, and almost everybody nods it through. Anglers on the bank did not cause good fishing. They are how you know the fishing is good. The cause is that the river was stocked on Tuesday.

Confusing the sign for the cause is how organisations end up managing their indicators instead of their problems. It is how you end up hiring a receptionist because the queue is at the desk.

If you're right, what else would be true? Suppose the pain in your abdomen is appendicitis. Then we should also expect a fever, and a raised white cell count. If those aren't there, it isn't appendicitis, however confident you were.

This is the one that turns an assertion into something that can be checked, because it makes a prediction that could fail.

And are you going in a circle? We're behind because we're slow. We're slow because we're behind.


Seven questions. Notice what almost none of them are about.

They are not about clinics. You do not need to know anything about running one to ask is that cause enough on its own? — and that is what makes the challenge survivable. You aren't disputing someone's fifteen years of experience, which you don't have. You are asking about the shape of an argument, which is on the page in front of both of you.

Answering is a different matter. Knowing that fire needs oxygen, or what else raises a white cell count, often takes exactly the expertise you lack. But the question can come from anyone, and a question nobody can dismiss is a great deal more than most meetings have.


And here something changes that has nothing to do with logic.

When reasoning is invisible, criticising someone's conclusion means criticising them — their judgement, their competence, their years. So they defend, and you push, and the meeting generates heat instead of light.

When the reasoning is out on the page, the page takes the criticism. Two people can stand side by side, looking at the same diagram, hunting for the flaw together. Dettmer's phrase for it: not you against me, but you and I against the problem.

I don't see how this cause is sufficient — what am I missing? is not an insult. It's a legal move.

It doesn't always work. Some people won't update however cleanly their chain breaks, and a diagram can be gamed as easily as a meeting can. But when a group has genuinely tried to break a piece of reasoning and failed, they tend to believe it — not because they were told, but because they attacked it and it held.


Back to the clinic, and the five certain people.

Nobody has to decide who is right. Each of them puts their chain on the wall, and then everybody gets the questions.

Some chains won't survive contact. Two will turn out to be describing the same cause from different ends. Dr Adeyemi's countersignature and Maria's referral backlog may well be the same animal seen from opposite sides of the building.

What's left is not five opinions.

It is one map that five people built and none of them could break — which is a different kind of object entirely.


Though it does raise the question of what, exactly, you should be mapping. Why are we stuck turns out not to be the first question. It isn't even the most important one.

Built with LogoFlowershow