Case 01
Closing the workshop whose demand model I had supported
In 2018 I supported a remote-workshop expansion built around 250 monthly service jobs. The first six months averaged ninety. The proposal had not examined the travel pattern and mix of work closely enough, so a promising demand account became an operating model that the location did not sustain. The workshop team asked for more time to establish activity. Finance questioned further funding without evidence that the underlying pattern would change. I had helped make the original recommendation and needed to examine both positions without turning the forecast into a demand that colleagues somehow fulfil.
We reviewed the work actually arriving, the travel it required and the practical alternatives for the customer commitments. After eighteen months, we closed the workshop and arranged customer-agreed transfers of service responsibilities. The ₹62 lakh of startup cost remained unrecovered. The account does not claim that a later transition earned back the investment, nor does it invent a clinical outcome or imply that service obligations could simply be abandoned because the location was uneconomic. The transition had to be agreed and coordinated by the responsible teams.
Closing meant giving up the local presence we had wanted and acknowledging that the original proposal had been weaker than its headline demand suggested. Keeping the workshop open would have preserved the map, but required further confidence in assumptions the operating record had challenged. I recommended the closure through the CEO rather than treating the decision as mine alone. The team needed a clear account of why the strategic choice changed, including the part I had played in endorsing the initial model.
The consequence was a smaller network and an unrecovered expense. I changed subsequent proposals so the work mix, travel and support conditions had to be examined before a volume estimate could become the main investment argument. That did not make later decisions certain. It made the assumptions more visible and the responsibility for them more explicit. I want this case retained in my profile because learning from a closure should not require rewriting it as a successful expansion.