What Ready Didn't Include
The product team built something good. The launch succeeded by every metric that got measured. The cost of what didn't get measured was absorbed quietly by the people closest to it — and by the time the organization learned what it needed to know, two of its best people had already decided to leave.
She had been running the regional operations function for six years when the product team launched the new service line.
She found out the same way her team did — an all-hands announcement, slides prepared in advance, a Q&A that had the careful energy of a conversation where the important decisions have already been made. She sat in the back of the room and listened. She knew things the product team did not. She had been hearing them for months — from the field, from the clients who called when something wasn't working, from the coordinators who had learned to route around the processes that slowed them down. She knew which regions could absorb a new service line and which ones were already at the edge of what their infrastructure could hold.
She had not been asked.
Not because anyone decided to exclude her. Because the product team had its own rhythm, its own internal review process, its own definition of ready — and that definition did not include a conversation with regional operations before the deck was finalized. No one made that choice explicitly. The choice had been made, earlier, when the organization built a planning process that felt complete without it.
The service line launched on schedule.
The first ninety days looked like a success by the metrics that got reported upward. Enrollments were ahead of projection. The product team presented the numbers at the quarterly review with the particular satisfaction of people who had built something that worked.
What the quarterly review did not include was what the regional coordinators were managing by then. The service line had landed unevenly — well in three regions, poorly in two, and in one region catastrophically, in ways that were visible to anyone within fifty feet of the operation and invisible to anyone reading a dashboard from a distance. The coordinators were problem-solving in real time, absorbing the friction through longer hours and improvised workarounds that did not appear in any report. They were good at their jobs. They made it look like a smaller problem than it was.
She knew. She was managing them, listening to them, watching the gap between what the dashboards said and what the coordinators were actually living. She wrote it up. She sent it to her manager. Her manager said he would raise it when the time was right.
The time was not right for eleven weeks.
By the time the conversation happened, two of the best coordinators in the struggling regions had already decided to leave. They did not say, in their exit interviews, that they were leaving because they had spent three months fixing a problem that should never have been deployed into their region. They said they were looking for new opportunities. That is the language people use when the real language requires naming something the organization has not yet admitted is a problem.
The product team received the operational findings as feedback. They were gracious about it. They incorporated several of the recommendations into the next version of the service line. The process improvement was noted in the following quarter's planning retrospective as evidence that the organization learned from its launches.
What the retrospective did not note was the coordinator capacity lost in the interim. Or what it cost to recruit and train their replacements. Or the clients in the struggling regions who had a worse experience than they should have, during a window that could have been shorter, with a problem that did not need to be discovered in deployment.
The organization learned. It learned slowly, at a cost it never fully calculated, from information it already had.
Silosolation does not always announce itself as a turf problem or a communication breakdown. Sometimes it looks like a launch that succeeded by every metric that got measured, while the cost of what didn't get measured was absorbed quietly by the people closest to it.
The regional operations leader was not excluded. She was simply not included at the moment when inclusion would have changed something. That distinction matters, because the first version of the problem is about intent, and the second is about structure. Intent is easy to defend. Structure is what actually determines what information reaches a decision before the decision is made.
The coordinators were not undertrained or under-resourced. They were skilled people doing what skilled people do when the organization gives them a problem without giving them the authority to name it: they solved it quietly, at personal cost, in ways that made the problem invisible to the people who needed to see it most.
What it cost to wait
Eleven weeks is not a long time for an organization to work through its internal rhythms and find the right moment for a difficult conversation. It is a very long time to be a coordinator in a region where the operation is failing and the people responsible for fixing it do not yet know how bad it is.
The two coordinators who left were the ones who had been there longest. That is usually how it goes. The people with the most context, the most invested in making things work, the ones who absorbed the most before concluding the absorption was no longer worth it — they are the first to finish the calculation. Their institutional knowledge went with them. Their replacements learned the role without learning what those two had spent years understanding about how the region actually worked. That knowledge does not transfer. It reconstitutes, slowly, through the same kinds of experiences — and in the meantime, the region operates at a fraction of the depth it had before.
The product team built something good. The launch failure was not a product failure. It was an information failure — and the organization never fully named it as one, because by the time the conversation happened, the visible crisis had passed and the invisible cost had already been paid.
What a different organization does with the same facts
The product team is the same. The service line is the same. The regional operations leader has the same information, the same coordinators, the same six years of field-level knowledge that the planning process did not know to ask for.
What is different is one structural decision made earlier, at a calmer moment, before anyone knew a service line was coming.
A different organization has defined what "ready for launch" means in a way that includes the functions that will absorb the launch. Not because the product team is not trusted to know when their work is ready — but because readiness is not a single-function determination. A product can be ready and the infrastructure can be unprepared, and the gap between those two things is invisible until deployment makes it visible. The organization that has learned this has built the lesson into its definition of ready. Regional operations is in the room before the deck is finalized — not to approve the product, but to pressure-test the deployment. That conversation changes what gets built into the launch plan. It does not slow the launch. It changes what the launch looks like when it lands.
A different organization has also solved the manager-as-bottleneck problem. The regional operations leader wrote it up. She sent it to her manager. Her manager held it for eleven weeks waiting for the right moment. That pattern — accurate information, correctly identified, traveling through a channel that slowed it to the point of irrelevance — is not a management failure in any individual sense. It is what happens when the organization has no direct path for operational signal to reach product decision-makers, and when the people who could create that path have not been asked to. A different organization has a channel that does not require a manager's timing judgment to function. It might be a cross-functional review cadence. It might be a direct escalation path for deployment issues that bypasses the normal chain. What it is specifically matters less than that it exists and that people know it exists — because the value of the channel is not just that it moves information faster. It is that the coordinators in the struggling regions know there is somewhere to send what they are seeing, which changes whether they send it, which changes how quickly the organization learns what it needs to know.
A different organization has also reckoned with what it asks of the people who absorb problems quietly. The coordinators who managed the failing deployment without escalating the severity did so in part because escalating felt like complaint — and in a culture that rewards problem-solving over problem-naming, complaint is a category with a cost. A different organization has made problem-naming a valued act rather than a managed one. Someone, at a prior moment, raised a deployment issue before it became a crisis, and was thanked for it rather than asked to handle it. That outcome got known. It changed what the next coordinator decided to do with what they were seeing. Cultures that surface problems early are not staffed by more forthcoming people. They are staffed by people who have seen that forthcoming is survivable — and who have leadership willing to receive hard information without making the messenger regret the delivery.
The coordinator capacity lost in those eleven weeks is not recoverable. The clients who had a worse experience than they should have are not a rounding error in a retrospective. The information existed. The people who had it were present, capable, and paying attention. The organization simply had not built a reason for it to travel.
Every organization has that window. Most organizations are in it right now.
Seeing this pattern in your organization?
The diagnostic identifies which institutional state is generating the friction — and what to do about it.
Take the Diagnostic →