## The product mix belongs inside the capacity claim
The automation demonstration showed 240 panels an hour, a figure that made the proposal easy to remember. It concerned one product. Our reviewed production account covered twenty models and showed 140 accepted panels an hour. Those were different conditions, not two competing descriptions of the same exercise. In 2025 I wanted the investment discussion to examine the work our enterprise would actually ask the equipment and people to perform. The demonstration could inform that discussion, but it could not replace the account of our mixed production simply because its headline rate was higher.
Product variety changes the question a capacity figure answers. A rate observed under one condition describes that condition; it does not automatically travel to a different sequence of work. Engineering colleagues asked us to consider changeovers, the model mix and accepted output. Those questions made the proposal less compact, but more relevant. I needed to make space for them before the rate became a commercial promise or a general statement about what the factory would produce after investment. The apparent precision of a number does not supply the context omitted from it.
The word accepted mattered as well. A count of activity and a count of usable output need not describe the same thing. I did not want the approval account to suggest that every panel passing through a stage necessarily satisfied the relevant requirements. Technical assessment and release remained with authorised specialists. The CEO's role was not to declare a product acceptable from a capital proposal. It was to make sure the enterprise's capacity discussion used a measure appropriate to the commitment it was considering and respected the professional responsibilities behind that measure.
I also did not treat 140 as a permanent property of every future production run. It described the reviewed mixed-production account. A different mix or operating condition could require a different assessment. The useful comparison kept the conditions alongside both numbers, rather than replacing one unsupported universal claim with another. This gave the team a more honest basis for asking what the proposed investment would do in our setting and what evidence would still be needed after implementation.
## A smaller scope needs its own justification
We chose an ₹8.4 crore cell instead of a ₹15 crore full-automation proposal. The options did not cover the same work. It would therefore have been misleading to describe the difference as a like-for-like ₹6.6 crore saving. The smaller cell needed a positive explanation of its own scope, the work retained elsewhere and the responsibilities that remained with people and existing arrangements. A lower amount can be appropriate without pretending it buys an equivalent result. That distinction was central to explaining the choice to the board.
Some sponsors preferred the full proposal because it offered a simpler picture of a transformed process. The more limited cell required us to describe boundaries and interfaces instead of presenting the whole operation as one automated system. I understood the attraction of the larger story. But a clearer picture is not necessarily a more supportable commitment. I wanted the proposal to show where automation would contribute, what it would not cover and how the surrounding work would continue. The investment's value needed to survive that fuller description.
Choosing less scope also means accepting what is given up. The cell did not offer every feature or breadth associated with the full proposal. I did not hide that trade-off behind the lower capital amount. The decision required a view about which work the enterprise was prepared to fund and manage at that stage. It was not a general statement that smaller automation is always better. Another operating context could justify a broader commitment, but it would need its own account of product mix, implementation and accepted output rather than borrow ours.
Finance and operations needed the same comparison, even though they approached it from different responsibilities. Finance could not assess the capital meaningfully if scope was treated as equivalent when it was not. Operations could not plan delivery from a demonstration condition that excluded much of the actual variety. Bringing those perspectives together was more useful than asking each team to endorse the headline independently. The CEO's contribution was to make the proposed commitment common enough that disagreement could improve it rather than leave different assumptions hidden behind apparent agreement.
## Approval starts the account of delivery
The decision to buy a cell was not an achieved production benefit. Implementation, operating review and technical assessment still followed. I wanted the approval account to remain useful after the purchase decision, so colleagues could examine whether the work developed as intended. If the document exists only to win approval, it may lose the conditions needed to judge the investment later. Preserving those conditions makes reporting more demanding, but also gives the enterprise a better basis for learning from the outcome rather than merely recording that capital was spent.
The distinction also protects the customer conversation. A sales promise should not adopt the demonstration rate while the investment team privately works with a more complex production account. Different audiences may need different levels of detail, but they should not be relying on incompatible assumptions. I would rather explain a capacity commitment that the operating team recognises than let a memorable number travel faster than its conditions. That is an enterprise coordination problem, not just a wording issue in the engineering proposal.
For directors, the case suggests a way to question automation without making the board a technical selection committee. They can ask what work the demonstration represents, how the production mix differs and whether the alternatives have comparable scope. They can ask how management will distinguish spending from capability and capability from accepted output. The answers should be supplied by the responsible leaders and specialists. Oversight becomes more useful when it tests the relationship between evidence and commitment rather than simply favouring a higher rate or a lower price.
I would use the same discipline when the evidence supports a larger investment. Careful comparison is not a reason to postpone every decision or choose the smallest possible programme. It is a way to know which judgement is being made. If broader automation is justified by the actual work and resources, the account should show that. In our case, we selected the cell and retained the limits of its scope. The choice was stronger because it did not need to claim equivalence with an option we had not bought.
The demonstration remained useful, but its number stayed attached to its condition. The reviewed mix remained useful, but its rate did not become a universal promise. The ₹8.4 crore cell became our chosen commitment, without being labelled a ₹6.6 crore like-for-like saving or a completed operating success. Those distinctions can seem restrained beside an investment announcement. They are what make the announcement intelligible to the people who must deliver it. I want the factory's future to be described by the work it will actually perform, not by the simplest demonstration we can remember.