A compact equipment layout can be an entirely reasonable response to a customer's needs. Industrial sites have constraints, and making room for a new heat-recovery assembly may compete with other equipment, access routes and ongoing work. The difficulty arises when compactness is assessed only in the installed state. An assembly can fit in its operating location while leaving insufficient space for the task required to maintain it. If the design account omits that movement, the apparent reduction in footprint has partly been obtained by transferring a problem into a future intervention.
I made that mistake in a fictional 2018 decision. I supported a compact layout after seeing access to a removable service cassette. Hema Tezqorni asked whether the cassette could actually be withdrawn once the surrounding installation was complete. I gave the access drawing more authority than it had earned. Reaching the component and completing its removal were different propositions, but I had allowed the first to stand in for the second. The issue was not a lack of concern for maintenance in principle. It was a failure to require evidence for the particular task before approving a commercially attractive arrangement.
### The task is larger than the component
The later review covered eighteen delivered units. Eleven had adequate removal provision and seven did not. Those numbers describe the scope of that review; they do not establish the frequency of the problem across every product or every customer's site. They were sufficient to require a different account of the affected arrangements. We retained ₹1.2 crore of review, redesign and adjustment work, with qualified design, service and site owners responsible for assessing the actual conditions. A general instruction to make more space would not have been an adequate engineering or safe-work response.
The task needs to be understood as work carried out by people under defined conditions. What has to move? Which parts of the surrounding installation matter? What responsibilities belong to the equipment supplier and which to the site? What does the approving team still need to establish? These are questions for a competent design and service process, not a substitute for its technical detail. The leadership responsibility is to make sure that the process exists early enough to affect the proposition. Once the footprint has entered a commercial commitment, a legitimate technical objection can appear to be an unwanted change rather than an unanswered part of the original question.
There is a practical objection. Reviewing every conceivable future intervention can make a design process slow and speculative. An equipment maker cannot know every alteration a customer may make years later. That objection deserves attention, but it does not justify leaving the intended service route unexamined. The useful boundary is the expected work and stated installation conditions the company is prepared to support. Those conditions should be explicit enough for the customer and responsible specialists to assess. Unforeseen future changes remain a different question from a maintenance movement already inherent in the supplied design.
### The objection should arrive before the footprint becomes a promise
Service colleagues are often asked to review an arrangement after the main decisions have acquired momentum. Their concern can then sound like a request to undo completed engineering. In the case I approved, Hema raised the relevant distinction, but the review did not give it sufficient weight. Improving the process therefore required more than adding her name to a distribution list. The unresolved removal question needed to prevent the footprint from being treated as settled until the responsible owners had examined it. Participation is valuable only when the evidence a participant brings can change the decision.
The commercial account matters as well. A larger maintenance provision may reduce the appeal of a compact offer or require a different installation arrangement. The company should not pretend that recognising the issue is costless. It needs to explain the alternatives and their consequences clearly enough for the customer to make an informed decision with the relevant advisers. Sometimes the proposed equipment may not suit the available setting. That is an uncomfortable outcome, but a specification that relies on an impossible future task does not become suitable because the commercial team needs a cleaner answer.
The same discipline applies when the technical team believes a workaround is possible. A plausible idea is a reason to investigate, not evidence that the customer has an approved route. The proposal may require another party's permission, different site arrangements or a change whose consequences need assessment. The design account should identify those dependencies before the workaround becomes the assumption supporting release. The CTO's confidence is not a replacement for the qualified owners' conclusion, particularly when the decision affects the people who will carry out the later work.
### Account for the correction without inventing its benefit
Five of our seven affected units subsequently had approved revised layouts; two remained pending at the review point. I keep that distinction because approval of a drawing is not completion of physical work. A public leadership case can be useful without pretending that every consequence has reached a favourable ending. It should show what the leader decided, what the company paid, which responsibilities remained and what evidence supported the stated outcome. In this case, the outcome was a more defensible design position for five units and unfinished work for two, rather than a claim that every maintenance difficulty had disappeared.
I also avoid describing the ₹1.2 crore as a saving. It was the cost of responding to a problem in the account I had approved. There may be future benefits from a better arrangement, but they need their own evidence and comparison. Calling corrective expenditure an investment does not remove the original error or establish a return. The more useful account explains how the experience changed the next design decision: the expected service task and its installation conditions now have to be examined before compactness is offered as an unqualified advantage.
For a board, the relevant oversight question is whether management's product proposition includes the obligations it creates after delivery. Directors do not need to prescribe the removal method or review every dimension. They can ask how service evidence enters approval, what happens when it conflicts with a commercial objective and whether unresolved conditions remain visible. A portfolio of technically impressive products can still accumulate poorly understood service commitments if those questions are postponed until a customer experiences the problem.
The lesson I take is not that smaller equipment is worse. It is that the physical account must include the intended work around the equipment, not only the equipment at rest. A responsible design can still involve trade-offs, limitations and costs the customer would prefer to avoid. Making them explicit before approval gives the enterprise a basis for a commitment it can explain. Leaving them outside the drawing may preserve an appealing footprint, but it leaves the eventual service team to discover what that footprint has failed to contain.