What it costs and what it buys

A team that starts naming commitments notices the change within about a fortnight, and not usually as an improvement. The first thing it buys is discomfort, because the things it makes visible were being avoided on purpose. What comes after that is worth the fortnight.

Things stop dying quietly

"I'll look into it" is the most expensive sentence in professional life. It is not a promise and not a refusal; it is a way of ending a conversation without answering it. The person who asked hears agreement, the person who said it has undertaken nothing, and the gap between those two readings is discovered a fortnight later at the worst possible moment.

There is no act for it in this notation, which forces the question. Are you promising, with a date? Are you declining, so I can go elsewhere? Are you making a counter-offer — not that, but this, and not then but then? All three are fine answers. Two of them are honest refusals, and a team that cannot say them out loud is a team whose plans are made of guesswork.

Ownership stops being a policy question

Ask a room who owns a piece of work and you get a team name. Teams do not promise; people do. When a commitment carries a customer and a performer by name, "who owns this" has already been answered by the act of drawing it, and the awkward cases — the ones where nobody can be named — are exactly the work that has been drifting.

The same goes the other way. A named performer can decline, and a person who cannot decline cannot really promise either; what they can do is comply, and compliance has none of the reliability of a promise. That is the uncomfortable corollary and it is not optional. If declining is career-limiting in your organisation, you do not have commitments. You have assignments wearing the language of commitments, and they will keep being late for reasons nobody will say aloud.

Rework has an address

Most rework traces back to a conversation nobody had at the start, about what would count as done. Not a specification — a sentence. Agreeing that sentence before the work costs ten minutes and feels like pedantry; discovering afterwards that the two of you meant different things costs a week and feels like somebody's fault.

The place this shows up hardest is the moment of acceptance. If nobody ever declares satisfaction, nothing is ever learnt: the same near-miss arrives again next quarter attached to a different piece of work, and the team's standards drift towards whatever was tolerated last time. The customer's "yes, that was it" is not a formality. It is the only feedback in the system that is about the thing that was actually wanted.

Delay becomes traceable

A promise is usually made of other promises. Once those are drawn as connected loops, a date has a derivation instead of an origin story: you can follow a slipped week to the person waiting on the person waiting on an answer nobody has given. That is a different conversation from asking a team why it is behind, and it has a different outcome, because it ends with something somebody can actually do.

Now the bill

It makes accountability visible, and some of that visibility will be unwelcome. Drawn honestly, a network shows work nobody asked for, approvals no person stands behind, and promises made by people who were not free to decline. Those are findings about the organisation, not about the notation, and somebody will prefer they had stayed unavailable.

It can also be used badly, in a specific way worth naming — and it is not the way usually offered. The usual worry is surveillance: write the promises down and somebody has a record to hold people to. That worry has lost its force, for reasons set out in what it does to software, and the short version is that the record exists whether or not anybody draws anything.

What actually goes wrong is imposition. Handed down — draw your work this way, use these words, here is the template, it is due Friday — the vocabulary becomes something people comply with, and compliance is the one thing this notation is least able to describe. It works when somebody picks it up because they have a coordination problem they cannot see, and it is close to worthless as a standard that has been rolled out. The tradition has been criticised for exactly this since the 1990s, and the criticism lands every time.

The last cost is the plainest: it takes talking. This notation makes it obvious when a conversation is missing, and cannot have it for you. Nothing on this site improves any coordination at all until two people say something to each other they were previously leaving implied.

A reasonable way to start

Take one thing that is currently late, or one handover everybody complains about, and draw it as it actually happened rather than as the process says. Four questions do it: who asked whom, what would have counted as done, what was actually said back, and who ever declared themselves satisfied. If two of those have no answer, you have found the problem, and it was never the one on the status report.

The vocabulary has the terms with their exact meanings, which is worth a minute before drawing your first one.