The Wrong Queue — script v2

Stage 1 of 3, revised. Pure narrative. No visual direction. Judged as writing only.

Changes from v1, per 02-critique.md: stakes added (a named person, a real patient, the annual number); the concept named once it has been felt; retitled to match the spine; the funnel example cut; four signposts removed; new ending on the guess rather than the tease.

~1,150 words.

A clinic opens at eight. By noon, sixty people are waiting.

Everyone who works there can tell you exactly where the problem is. They are all pointing at the same desk.

They are all wrong.

Maria runs the front desk. She works through lunch most days. The phone starts before the lights are on and there is a queue at her window from opening until close. When patients write in to complain, and they do, they complain about her desk.

She is, visibly and unarguably, the hardest-working person in the building.

She is also irrelevant to how many people this clinic helps.

It treats twenty patients a day. It has treated twenty patients a day for four years.

Everyone who comes through passes five stations, in order, and every one has a limit. Check-in can process sixty people a day. Triage, forty-five. The doctor, twenty. Pharmacy, fifty. Follow-up booking, forty.

Four of the five can handle more than twice what the doctor can.

So the clinic treats twenty people a day. Not eighty-five, which is what its five stations could manage between them. Twenty.

The other forty go home.

One of them is a man in his sixties who has now come twice about a cough he has had since March. He waited three hours on Tuesday and left at four to collect his grandson. He will try again next week.

Multiply him. Forty people a day, five days a week — something like ten thousand people a year who came to a clinic where everybody was working flat out, and did not get seen.

The clinic has just been given enough money to hire one more person.

Put them on the front desk, where the queue is: still twenty. Put them on triage: still twenty. Pharmacy: twenty. Follow-up: twenty.

There is exactly one place that changes the number, and it is not where the queue is.

Hire at the front desk and check-in gets faster, so patients reach the waiting room sooner. You will have spent the entire budget to make people frustrated sitting down instead of standing up.

Maria was never the problem. She was busy absorbing the anger that something else was generating.

Busy is not the same as stuck.

The station that sets the number — the one every other station is waiting on, whether it knows it or not — is worth having a word for. Call it the constraint. Every system has one. Almost no system knows where it is.

Every single person in an organisation is working flat out, all day. Is that organisation running at its best?

Almost everyone says yes. It doesn't even feel like an opinion.

But look at what full effort at the front desk actually produces. Sixty people checked in, against twenty the doctor can see. The other forty do not vanish. They sit in the waiting room — and a waiting room is not output. It is forty afternoons, spent.

A station that isn't the constraint, running at maximum, manufactures work the constraint cannot absorb. In a factory that work is inventory, stacked and going stale. On a software team it is a queue of finished tickets nobody can review. Here it is people.

So a well-run system needs most of its parts to have slack — deliberately running below their maximum — so the one part that governs everything can run flat out.

Everybody working hard is not evidence that things are going well. It is evidence that nobody has found the constraint.

Picture an organisation doing everything right by conventional lights: a dozen energetic improvement teams, each working hard on something everybody agrees needs fixing. At most one of them is working on the constraint. The other eleven are producing effort.

We know it is the doctor. So hire another doctor.

Not yet. Watch her day first.

About two hours of it goes on things that do not need a medical degree — re-taking a history the triage nurse already took, hunting for notes, printing forms. Move those two hours off her desk and the clinic goes from twenty patients a day to twenty-eight.

Eight more people a day. Two thousand a year. The man with the cough is one of them. The cost of this is nothing.

That is the step almost everyone skips: get everything you can out of the constraint before you spend a penny on it.

The next step is harder, because it looks like failure. Everyone else now runs at whatever pace keeps the doctor working. Reception deliberately slows down. Every local number you have will show those people getting worse while the clinic gets better. If you cannot tolerate that on a dashboard, none of this is available to you.

Only then do you spend money — and you spend it on the doctor, not on the loudest queue.

A team where every calendar is full and nothing ships, because everything is queued behind the one person who reviews.

Or: a parent getting older. A dozen worries, all of them real — the stairs, the medication, the driving, the money. You are exhausted and you are working on all of them.

The thing actually holding everything up is one phone call to one agency that nobody has made. It is not the biggest problem on the list. It is the stuck one.

The question is never how hard are we pushing? It is: are we pushing on the thing that's stuck?

Fix the doctor and the clinic does not become fixed.

Get her to fifty a day and the pharmacy, at fifty, becomes the constraint. Fix that and it moves to follow-up booking. Push far enough and every station inside the building outruns the number of people it serves — at which point the constraint has moved outside the walls, to the hospital that won't take referrals any faster.

It is still a constraint. It just now needs an entirely different set of skills to attack.

Which is why this work never finishes, and why the most expensive sentence anyone in that clinic can say is we solved that one.

All of this was easy. Five boxes, five numbers, find the smallest.

Real organisations are not like that. The constraint is usually not a person or a machine. It is a rule.

Every prescription needs the doctor's countersignature. No appointment longer than ten minutes. Referrals are reviewed on Thursdays. Nothing goes ahead without sign-off.

Every one was introduced for a good reason, usually to solve a problem nobody now remembers. John Gardner described an established organisation as a coral reef of procedures laid down to achieve some long-forgotten objective.

Breaking one is nearly free — a rule costs nothing to change, next to hiring a doctor — and it usually improves things more than any purchase would.

And they are invisible, because everybody experiences them as normal. A bottleneck machine announces itself: there is a pile of work in front of it. A bottleneck rule has no pile. It hides inside that's just how it's done, and it is defended, sincerely, by good people whose own numbers depend on it.

So: find the constraint. Put nearly everything into it. Ignore, for now, almost everything else.

But if the constraint is usually a rule — invisible, normal-seeming, defended in good faith, connected to the symptoms you can see by long chains of cause and effect that cross every boundary on the org chart — then how would you ever find one?

Ask five colleagues what the most limiting thing about your organisation is. You will get five confident, different answers.

On what basis do you decide who is right? Seniority? Confidence? Volume?

Most organisations settle it with some blend of authority, anecdote and whoever tells the best story — which is to say they don't settle it.

They guess.

Then they spend a year, a budget and a great deal of everyone's goodwill finding out whether the guess was right. And somewhere in the building, someone is working through lunch on something that was never going to matter.