A useful total can answer the wrong purchasing question
In 2020 I endorsed a purchasing discussion supported by an ₹8.4 crore institutional request book. ₹2.1 crore of that amount consisted of cancellable reservations, while ₹6.3 crore formed the firm portion. Adding the values was not the central mistake. Allowing their sum to suggest an equal degree of commitment was. We had put different customer intentions into one executive argument without retaining the conditions that mattered to the decision we were making.
The correction cost ₹46 lakh in freight and markdown remediation. I keep that cost in the story because it shows why the distinction needed attention before the purchasing choice hardened. It does not mean that the whole reservation value became a loss. The case also does not describe an accounting restatement or fraudulent orders. It concerns the commercial basis I accepted for committing resources, with financial reporting and qualified interpretation of actual arrangements remaining with their responsible owners.
An institutional request can tell a bookseller something important even when it is not yet firm. It may indicate the titles under consideration, the timing of a possible need or the scale a customer is exploring. Removing such requests from every discussion would discard useful evidence. The difficulty arises when the purpose of the discussion changes. A view of potential interest is not automatically a sufficient basis for the same purchasing commitment that a firmer order might support.
I had experience on both the distributor and retailer sides of that relationship. That made my approval more uncomfortable, not less. Familiarity can encourage a leader to read a total as though the necessary distinctions have already been handled beneath it. In this case I should have asked how much of the request book carried which conditions before endorsing its use. Seniority did not remove the need to understand the meaning of the number I was allowing into the decision.
The correction therefore needed more than a revised heading. Buying colleagues required an account they could use to decide what to commit and what remained uncertain. Commercial colleagues needed room to continue working with customers whose plans were not yet settled. Finance needed its own responsibilities respected. A useful executive discussion kept those needs together, rather than make one department responsible for resolving ambiguity that the leadership account had concealed from the others.
Uncertainty needs a decision rather than a new label
Once the conditions were visible, the enterprise still had a choice to make. It could carry some uncertainty to remain responsive, or wait for greater commitment and accept the consequences for timing and availability. The case does not offer a universal answer to that trade-off. What changed was the ability to discuss it explicitly. The board and management should not discover after approval that an apparently settled basis actually depended on customers retaining a choice the plan had ignored.
A reservation does not become firm because the organisation would prefer a cleaner demand story. Equally, uncertainty does not make it worthless. Both simplifications avoid the real leadership task. We needed to understand the evidence, the conditions and the resources at stake, then decide what exposure the business was willing to accept. That judgement belongs with the responsible owners using the actual circumstances. A fictional case can illustrate the distinction without pretending to settle the terms of a real commercial arrangement.
The purchasing team also deserved clarity about the decision leadership had made. If executives choose to carry a defined uncertainty, they should not later treat every unfavourable outcome as though the team independently failed to obtain certainty. Conversely, describing a choice as strategic should not hide poor execution or a condition that was never understood. The account needs to distinguish what was known, what was chosen and what changed. That makes responsibility more precise than an attractive total followed by retrospective blame.
I would ask for a concise explanation that keeps the material differences visible at the point of decision. The purpose is not to put every contractual detail into an executive paragraph. It is to prevent the paragraph from implying something the detail does not support. In our case, the firm portion and cancellable reservations needed to remain separate in the purchasing argument. The number could then inform the choice without silently replacing it with an assumption of equal commitment.
There is a temptation to declare the repaired account a financial improvement in itself. I would resist that. We incurred remediation cost and changed the basis of planning. Any later benefit would need evidence appropriate to its claim. A clearer account is valuable because it enables a more deliberate decision, but it does not automatically prove a saving or a better result. Keeping that limit avoids turning the lesson from an owned mistake into an invented success measure.
The correction belongs to the executive who endorsed the basis
My role in the case was not simply to request a better report after a problem surfaced. I had endorsed the basis that required correction. The profile should make that fact visible so a reader can judge what I learned and how I describe responsibility. A leader who appears only at the moment of improvement gives an incomplete account of the choice. The ₹46 lakh repair and the earlier approval are part of the same narrative.
That does not mean absorbing every specialist responsibility into the CEO role. Rohan retained financial reporting, and the relevant commercial and qualified advisers retained assessment of actual terms. My accountability concerned the executive judgement connecting the request book with the purchasing proposal. Distinguishing these responsibilities helps colleagues work together. It also stops a personal leadership story from becoming an assertion that one executive alone made or corrected every decision involved in a complex commercial process.
The habit I would carry into another enterprise is to ask what commitment a prominent number represents before asking how impressive it is. A request book, a pipeline or a programme forecast can contain useful but different kinds of evidence. Their total should be interpreted in relation to the decision it supports. The question is not whether uncertainty exists; it is whether the person approving the resource choice can see the uncertainty the evidence actually contains.
Our ₹8.4 crore request book remained an account of interest with different conditions. ₹6.3 crore described its firm portion. The correction restored the difference and retained the cost of acting on the earlier interpretation. I regard that as a more useful leadership lesson than a claim that better reporting removed uncertainty from the business. The enterprise still had to choose. It could now do so with a clearer account of what its customers had, and had not, committed to.