The workshop gave the proposal a reassuring physical form. There was a location, a plan for activity and an expectation of 250 service jobs a month. I supported the expansion in 2018. During its first six months, the average was ninety. The difference was not merely a shortfall to put beside a forecast in a report. It exposed how little the original volume account had said about the travel pattern and mix of work that the location would need to sustain. We had made the network look more complete before making its operating case equally complete.
I had spent years in service planning, which made the mistake harder to dismiss as unfamiliar territory. Experience can help a person ask better questions, but it can also make a plausible answer feel familiar enough to accept. I knew that a location on a map was not the same as a supported service pattern. In this proposal, I still let the demand estimate carry too much of the argument. The useful account of the failure begins with that responsibility rather than with the eventual decision to close.
The forecast described volume more clearly than work
A job count can conceal meaningful differences between activities. Travel, available support and the mix of work affect what a workshop can actually do. The original proposal did not examine those conditions closely enough. I would not infer from this case that every remote workshop needs the same threshold or that ninety jobs is inherently unviable. The issue was the relationship between our particular assumptions and the business we had proposed. The operating experience did not sustain the case on which we had relied.
The workshop team asked for more time to establish activity. Their position deserved attention: a new location can take time to develop, and an early observation does not automatically decide its future. Finance asked what evidence supported further funding. That was also a legitimate question. My role was to examine what would need to change and whether the emerging record justified expecting it, rather than defend the forecast because I had supported it or demand that the operating team somehow make the original number true.
We reviewed the work arriving, the travel it required and the available alternatives for the customer commitments. The exercise was not a search for a convenient explanation of underperformance. It needed to distinguish a temporary gap from weaknesses in the operating model. A longer runway could be useful only if there was a credible account of the conditions it would allow the business to establish. Time itself would not turn an insufficiently examined work pattern into a sustainable one.
After eighteen months, we closed the workshop. The ₹62 lakh of startup expense remained unrecovered. I recommended that course through the CEO; I did not possess unilateral authority over every aspect of the decision. The closure made the network smaller and required an account of what we had learned. It did not create a retrospective return on the investment. I want that distinction preserved whenever the case is described as evidence of my judgement, because the later correction cannot be used to make the earlier choice disappear.
Closing did not remove the obligations
A workshop's financial case and its customer responsibilities are related but different. Concluding that the location should close did not mean existing commitments could be abandoned. We arranged customer-agreed transfers of service responsibilities through the appropriate teams. The account does not invent a clinical outcome or claim that strategy could authorise equipment release. It describes an orderly commercial and operating transition that had to be considered alongside the decision about the location. Those responsibilities remained real even when the investment case had failed.
This is one reason I resist describing an exit as simply cutting a loss. The phrase can make the decision sound complete at the moment the financial conclusion is reached. In practice, people must understand what will happen to their work and customers must understand the agreed arrangements. The costs and obligations of that transition belong in the strategic account. They should not be treated as minor execution details that can be left to others after the headline decision has been announced.
The transition was necessary work, but I do not use it to claim the expansion was successful in another way. We gave up the local presence we had wanted and retained unrecovered startup expenditure. A leadership narrative can acknowledge that consequence while also explaining why the closure was preferable to continuing on an unsupported basis. It does not need to manufacture a victory in order to show judgement. Sometimes the evidence of judgement lies in accepting a less flattering account of a decision one helped make.
I also wanted the team to hear that the forecast was an assumption to test, not an obligation imposed on them by its appearance in an approved proposal. Colleagues should be accountable for their work, but that accountability does not relieve a sponsor of responsibility for the model. If every divergence is explained as an execution problem, the organisation loses the ability to learn from weak strategic assumptions. The discussion needed to leave room for both: how the work was managed and whether the original proposition made sense under the observed conditions.
Keep the failed assumption in the leadership account
Subsequent proposals had to show the work mix, travel and support conditions before a volume estimate could become the central investment argument. That change did not make the future certain. It made the basis of the decision easier to examine and the conditions that could challenge it more visible. I did not want a larger spreadsheet as a substitute for judgement. I wanted an operating explanation that a colleague could question without first having to dismantle the apparent certainty of an attractive total.
For directors considering a network expansion, the useful question is what the proposed footprint can actually support after opening. A map can show reach without showing the dependencies that make the reach useful. The board should not prescribe every route or staffing decision. It should understand the operating proposition, the evidence supporting it and the circumstances that would require management to revisit the commitment. That understanding makes it easier to distinguish a reasonable experiment from a forecast whose weaknesses have been hidden by presentation.
My own experience is relevant to that discussion because I have seen a proposal fail, not because I can supply a universal formula for workshop viability. The numbers in this example belong to an invented business and a specific decision. They do not establish a benchmark for another enterprise. What can travel is the discipline of asking how volume becomes work, how obligations survive an exit and whether the sponsor's account retains the assumption that proved wrong. Those questions are useful precisely because they remain open to context.
I want the profile to show the eighteen months between approval and closure, not jump from an ambitious opening to a neat lesson. The period contained an operating team trying to build activity, a finance challenge to further funding and customers whose responsibilities needed an agreed transition. It also contained my own need to reconsider a recommendation I had supported. A strategy becomes credible when it can describe that whole sequence. The map is only one part of the business, and the workshop's existence is not the evidence that makes its case sound.