Industrial product discussions often begin with a persuasive picture of demand. A range has a clear proposition, customers are asking about configurations and a forecast gives the opportunity a monetary shape. The temptation is to treat those signs as one continuous account: interest has become demand, demand has become an order and the order has justified production capacity. Each transition needs evidence. I want product leadership to explain where the account currently stands, particularly when the proposed commitment is harder to reverse than the enquiry that supports it.
The fictional Qivaren Industrial review in 2025 concerned a CNY 180 million forecast built around 1000 units and 36 options. The material offered in support included 240 configuration requests. Of those, 156 concerned standard combinations and 84 required bespoke assessment. They were requests, not orders. I withheld the capacity recommendation and supported CNY 12 million of further product-definition and evidence work. The case does not report a later approved capacity investment, booked revenue or a conversion result. The decision was to keep the proposed commitment from outrunning the evidence available at that stage.
## Keep the enquiry at its actual stage
A configuration request can be valuable. It can show which combinations a prospective user wants to discuss, where the existing range is difficult to understand and what an application may require. None of that makes the request equivalent to a purchase commitment. The person making it may still be considering alternatives, waiting for technical assessment or trying to establish whether the proposition is suitable. A product team should learn from the question without silently changing its status.
In this review the 240 requests could not be described as 240 orders, nor did their presence by itself establish the 1000 units in the forecast. A single request might concern an application whose eventual quantity remains unsettled. The record does not supply a conversion rate or an agreed unit count for each enquiry, so I would not invent either relationship. The forecast remained a proposed account of the opportunity. The requests were one source of evidence to examine, with their stage and limitations retained.
The commercial sponsor wanted to use the volume of activity to support a timely capacity decision. Waiting had a potential cost: a manufacturer can lose an opportunity if it cannot prepare for demand until every uncertainty has disappeared. I took that argument seriously. My objection was not that production decisions require perfect certainty. It was that the degree and kind of uncertainty should be visible to those approving the commitment. Calling requests orders would hide uncertainty instead of making a reasoned decision about accepting it.
I also wanted the CNY 180 million forecast kept separate from current company revenue. Qivaren's CNY 8.4 billion 2025 revenue described the institution. The proposed product forecast described an opportunity under review. My CNY 186 million 2026 function expense and 214-colleague remit described personal responsibility. Those figures could all belong on the same executive record without becoming interchangeable. Scale is useful context only when the reader can understand whose activity, which period and what stage of decision each figure represents.
## Ask what the standard and bespoke groups require
The 156 standard and 84 bespoke requests raised different questions for the product team. A standard combination might still require application review and a commercial decision before becoming an order. A bespoke enquiry could involve work beyond the established proposition. The division did not tell us that the standard group would convert, that the bespoke group would fail or that both groups placed the same demands on engineering and production. It told us that one undifferentiated request count concealed a material difference in the work being discussed.
I wanted the proposed 36 options examined in relation to that evidence. An option list can make a product look configurable while leaving unresolved how combinations are assessed and delivered. The public case does not claim that every possible combination was feasible or that the 84 bespoke requests could be satisfied by selecting another box. Engineering, quality and operations retained their responsibilities. Product management needed to describe the intended proposition and the limits that those owners would have to evaluate.
The CNY 12 million work therefore supported clarification rather than a declaration that capacity was justified. I wanted the team to establish what each request was asking for, which parts fell within the standard proposition and where further product decisions remained. That work could support a later recommendation, but its funding did not predetermine the answer. It was possible that a clearer account would narrow the opportunity or show that some requests should not become part of the range. The value of the review depended on keeping those outcomes open.
There was a communication challenge as well. A simple opportunity slide offered an immediate story; a request-stage account required explanation. I preferred to make that explanation part of the recommendation rather than leave approvers to discover the distinctions later. The product team could still state the ambition clearly. It needed to place the evidence beside it, so a reader could distinguish the proposed 1000 units from the 240 requests and understand why the 156/84 split mattered to further work.
## Make the next commitment proportionate to the evidence
Withholding the capacity recommendation was a product judgement within a wider decision process. It was not a unilateral cancellation of every commercial possibility, and it did not transfer capital authority to the CPO. The appropriate corporate owners retained investment decisions. My responsibility was to decide whether I could support the product account being placed before them. At that point I could support further definition work; I could not support describing the request evidence as if it already established the proposed production commitment.
The distinction matters when the case is retold. It would be easy to turn the decision into a story about avoiding a large loss, but the record contains no measured counterfactual loss. It would be equally easy to imply that the later range succeeded because the review was more disciplined. No such outcome is supplied. The actual result was a withheld recommendation and a funded next stage of evidence work. That is enough to make the judgement inspectable when the competing commercial argument, expenditure and remaining uncertainty are stated.
I would ask the same questions when preparing a leadership website. Does the case distinguish interest from commitment? Does a forecast appear as an achieved result? Is the executive claiming the authority of the investment body or the contribution made to its decision? A strong narrative can explain why a leader slowed a proposition without dressing the delay as a quantified saving. The reader needs to understand the choice, the work it authorised and the evidence that would be needed to move further.
For a prospective board contribution, the transferable question is whether management's evidence matches the commitment being proposed. A board need not examine every configuration request, but it should be able to understand their stage, their relationship to the forecast and the principal work still unresolved. Directors can then challenge the intended use of that evidence through the institution's established process. The data in the presentation should help the discussion, rather than let a count of enquiries stand in for an explanation of demand.
All companies, people and figures here are invented. A real account would need authorised commercial evidence and verified responsibility. The argument I want this example to carry is practical: preserve the stage of the customer's question. A request can justify learning, product definition or a further commercial conversation without already justifying every later investment. Leadership lies partly in choosing the next commitment that the evidence can support, and in saying clearly what remains undecided.