Where a promise comes apart
Most advice about coordination is advice about communication in general, which is why so little of it survives contact with a Tuesday. Drawn as a loop, the problem gets smaller and much more useful: a commitment has four moments, and there are only four places it can come apart.
What follows is one failure per quarter. They are ordinary — every one of them is something reasonable people do on a good day — and they compound, which is the part worth knowing. A vague request guarantees a contested acceptance a fortnight later, and by then it looks like a delivery problem.
The request that never said what it wanted
The first quarter is preparation and the asking, and its failure is the commonest of all: a request that leaves out what would count as done.
"Can you look into the pricing thing." "We should probably tidy up onboarding." "Have a think about the Henderson account." These are not requests. They are moods with a verb in them. Nobody has said who is being asked, what will have been true when it is finished, or by when — and those three are not decoration. They are the request. Without them Tomas has been handed a guess to make, and the guess is what gets delivered.
The reason this survives is that asking properly feels like distrust. Naming the date sounds like doubting somebody's diligence; saying what would count sounds like explaining their job to them. So the conditions stay in Priya's head, where they are perfectly clear, and the ten minutes it would have taken to say them out loud get spent three weeks later arguing about whether bay 3 is ready.
The question that fixes it is unglamorous and takes a sentence. What would have to be true for me to say yes, that was it? Answer it before, not after. If it cannot be answered, that is the finding — you have discovered you do not yet know what you want, which is worth knowing while it is still cheap.
The agreement nobody actually made
The second quarter runs from the asking to the answer, and it is where the most expensive misunderstandings are manufactured, because both parties leave it believing something different.
"Sure, I'll take a look." "Yes, should be fine." A nod in a meeting. Silence. Priya walks away holding a promise. Tomas walks away having expressed willingness. Nothing was agreed, and neither of them knows that yet.
Silence is the worst of these and the hardest to see, because it never announces itself. There is no act for it in this notation on purpose: having been asked and said nothing is not an answer, and the person waiting is right to be waiting. It is also the one failure that is entirely avoidable, because there are three honest answers and all of them are better than none.
A promise is one. A decline is another, and it is a service rather than a failure — no, ask Aran, he has the rig this week closes the conversation cleanly and leaves Priya a fortnight to go elsewhere. A counter-offer is the third and the most under-used: not that, but this; not then, but then. And when none of those is yet truthful there is a fourth move, which Flores names and most people have never been given: commit to commit. I cannot answer today. I will answer by Thursday. That is a promise about the answer, with its own date, and it is what silence is standing in for.
Underneath all of it is the harder question. Was the person free to say no? An agreement extracted from somebody who could not have declined is not a commitment; it is compliance, and compliance has none of the reliability of a promise. If declining is career-limiting where you work, you do not have commitments — you have assignments in the language of commitments, and they will be late for reasons nobody will say aloud.
The silence in the middle
The third quarter is performance, and it is the only stretch of the loop with nothing said in it. That is proper — the work is being done, and a promise is partly a licence to be left alone. The failure is what happens when the work stops going to plan.
Something arrives that was not in the picture. A dependency slips, the scope turns out to be larger, somebody is ill. And the honest move at that moment — going back and reopening the conversation — feels like an admission, so it does not get made. The date is quietly hoped at instead. Priya, who could have moved her crew to another bay, gets the news on the morning they were due to start, when it is worth nothing to her.
The value of a promise is not that it is always kept. It is that you can rely on what you were told, which means a promise that is going to break is information the other person needs before the date rather than after. Revoking is costly and sometimes right, and it is far better said than quietly not done.
Trust is lost here more often than anywhere else in the loop, and not because things went wrong. Things go wrong constantly. It is lost because somebody found out late that things had gone wrong, and now has to wonder what else they are not being told.
The closure that never happens
The fourth quarter runs from the report to the customer's verdict, and it fails at both ends.
At the performer's end: declaring it complete against their own standard rather than the one that was agreed. The work is done in the sense that they have stopped. Whether it answers the question that was asked is a different matter, and it is not theirs to settle.
At the customer's end, and this is the more common: never saying. The work arrives, it seems broadly fine, everybody moves on. Nobody says yes, that was it — and nobody says no, it was not. The loop is left open, and Tomas never learns which of the things he did was the thing that mattered.
The two are different moments held by two different people, and the structure depends on that. A task board lets whoever did the work drag the card to Done, judge and jury. This notation has no such move. Flores puts it plainly: "The customer has the final say on whether the conversation has ended."
The cost is quiet and cumulative: nothing is learnt. The same near-miss arrives next quarter attached to a different piece of work, standards drift towards whatever was tolerated last time, and everybody is busy without anybody getting better. A declaration of satisfaction is not a formality. It is the only feedback in the whole system that is about the thing that was actually wanted — and a declaration of dissatisfaction is worth more, because it is the one that changes something.
Reading your own
Take a commitment that hurts and walk its four quarters. Was what would count as done ever said out loud, and by whom? Did anybody actually answer, and could they have answered no? When it started slipping, who said so, and how soon? And has anybody, ever, said whether it was what was wanted?
Two of those with no answer is not a delivery problem. It is a loop with a hole in it, and the hole has an address.
All four are drawn, side by side, in one whole loop and four ways of coming apart — one sheet, six ordinary bits of work, and the first one whole to measure the rest against. The editor's own Check reads a drawing back to you and names the ones it can see.
Run it before anybody lives in it is what these look like in motion. The vocabulary has the terms with their exact meanings, including the acts this page says are missing.