What the current operating model really costs — told the only way it can honestly be told: as the loop everyone in this room has personally ridden. One simple question, six weeks, every emotion on the map. Buckle in. It ends well.
Every transformation deck has a cost slide. This is ours, drawn honestly: the elevation profile of one ordinary question moving through the current operating model. Nobody in this room needs the legend explained.
Monday, 9:04 a.m. In a meeting, someone asks a genuinely simple question: how many members in the new program have actually used it? Heads nod. Great question. Easy question, surely — the data obviously exists. Someone will “pull that together.”
The request is filed with real optimism, because optimism is the one resource this operating model has never managed to deplete. Everyone agrees it would be great to have by Friday.
Ticket #847 joins the queue, where it makes many friends — some of them filed in a previous fiscal year. The estimated turnaround is “it depends,” which remains the only estimate this model has ever delivered on time.
On day four, the requester checks in, politely. The ticket, they are told, is in the pipeline. Friday arrives and leaves quietly, taking no questions.
Week two. Someone remembers a spreadsheet. There is always a spreadsheet. This one was built by someone who left two years ago, is named FINAL_v7_ACTUAL_USE_THIS_ONE.xlsx, and is quietly load-bearing for three departments.
And it has the number! Well. It has a number. It disagrees with the number in an email from March by exactly 4,116 — and nobody can say why, because the person who could say why is no longer reachable at this address. Confidence, briefly airborne, begins its descent.
Week three. Three decks. Three totals. One hour, spent deciding which reality we live in. The meeting about the number becomes a meeting about the meeting, and — in the model's most reliable ritual — schedules a follow-up. The follow-up will also disagree.
And here is the turn the ride hides in plain sight: quietly, off to the side, the decision the question was serving gets made anyway. It had to be. Deadlines don't wait for data here; they learned to stop waiting years ago.
Careful. Accurate. Footnoted. Formatted like it has somewhere nice to be. It is genuinely good work, produced by people who stayed late to finish it — and it answers the question perfectly, three weeks after the question stopped mattering.
It is received with gratitude, admired briefly, and filed in the folder where beautiful answers go to be safe. This is where the ride would end — if the only casualty were time.
Because here is what else was true during those six weeks. Somewhere in our data, a member's pattern sat waiting — the kind of rising signal a modern model routes to a care team while there is still time to act. It was visible to anyone with the right view. Nobody had the right view.
We laugh at the ride because we recognize it — laughing is how good people stay sane inside a loop they didn't choose. Members don't get that option. They live with the consequences of late answers without ever knowing there was a queue.
Ticket #847 cost us six weeks. What the queue costs members can't be filed — and it is why parts one and two exist.
As throughout this series: illustrative composites, not specific members, colleagues, or events.
Every ride prints a receipt at the exit gate. Ours, itemized honestly:
Now multiply — by every ticket, every month, every department. And note the line the receipt can never itemize, because it never becomes a ticket at all: the questions people stopped asking, because they knew better than to file them.
Here is the quiet good news this appendix exists to deliver: nothing on that map is fate. Every hill and drop is a design choice — a queue somebody built, a spreadsheet somebody had to build, a meeting somebody had to hold. Designs can be redesigned.
That is not optimism. It is part two, with dates on it. The plan is written, the proofs are ninety days apart, the people who kept this ride running are the same people who can help dismantle it — and the first station is already marked on the map.
We know every turn of this ride by heart.
That is exactly why we're sure of the way off.