A product specification can become impressive while the place where it must work remains an assumption. The team debates functions, capacity and the arrangement of controls, then asks installation colleagues to work out how the equipment will fit. I believe the physical setting belongs earlier in the decision. It can determine which arrangement is useful, which trade-offs deserve attention and whether the proposed common model is actually a credible offer for the intended customer. Leaving that question until delivery can make the customer responsible for resolving a mismatch the product team should have understood.
The fictional Pravellen workstation case gave me a concrete example. The proposed model was 750 millimetres deep. Research at forty-two laboratories found thirty-one with available bench depth of six hundred millimetres or less. We chose a 580-millimetre design for further assessment, accepting a different arrangement from the original proposal. Eleven of sixteen site-fit reviews accepted it, while five needed another configuration. Those results remained specific to the reviewed settings; the smaller dimension did not establish universal suitability, clinical performance or clearance.
Bring the setting into the choice
I would start by asking what the team actually knows about the workplace. A broad customer category is not enough. Laboratories can differ in available space, access, surrounding equipment and the sequence of work around the proposed product. The relevant observations should be recorded in a form that helps a product decision rather than only decorating a research presentation. A measurement becomes useful when the team explains which assumption it challenges and what choices are available in response. It should not be reduced to an average that conceals settings the proposed model cannot serve.
There is a legitimate attraction in a larger arrangement with more functions. It may reduce the number of models to explain or make a demonstration look more complete. I would want that argument heard. The problem arises when breadth is treated as value before the setting has been considered. A feature that can be demonstrated in the supplier’s spacious room may not be useful in the buyer’s actual workflow. The product decision needs to compare viable arrangements for that work, rather than compare feature counts as if the surrounding space were unlimited.
Anagha Vervankar’s challenge helped move our discussion from defending the catalogue to examining the intended setting. The company could have retained the larger proposal for customers with suitable space. It could have developed another model or decided the constrained settings were outside its intended market. We selected a narrower design for evaluation. What mattered was that the physical evidence became a conscious scope decision. It no longer sat in a site report while the commercial description proceeded on a contradictory assumption.
Distinguish a dimension from a fit conclusion
A 580-millimetre product does not automatically fit every bench deeper than that number. Clearance, access and the surrounding task still need assessment. I would keep those requirements with the relevant technical, quality and site owners rather than let a convenient subtraction stand in for their work. The product team can define the intended proposition and identify the setting it aims to serve, but it should not use one physical measurement as an unrestricted statement about suitability. The distinction is simple and easy to lose when the revised dimension becomes the headline achievement.
The same care applies to the observed population. Thirty-one of forty-two laboratories described a constraint in our research group. That does not establish the proportion of all laboratories with the same condition. Sixteen later site-fit reviews were a different exercise, and eleven acceptances belonged to that exercise. I would explain how each group contributed to the decision without combining them into an invented market conclusion. A product account becomes more credible when it preserves what was observed and why that evidence was sufficient for the next bounded step.
The programme’s nine-point-six-crore expense also has a defined meaning. It funded product work in the fictional case. It did not prove a return on investment, a customer saving or a clinical result. A financial assessment would need its own evidence and responsible owners. I would resist adding a speculative gain simply because the physical decision otherwise appears modest. A change that makes a proposition more coherent can be important without every consequence already being measurable. The board should hear the chosen scope and the unresolved questions at the same time.
Accept that one configuration may not serve every site
Five sites in the review needed another configuration. Their response should remain visible, particularly if the revised model becomes the preferred catalogue story. A product team can learn from those needs without immediately promising to satisfy them. Some may justify a different range decision; others may remain outside the company’s chosen offer. I would ask what the unmet requirement is, how widely it is evidenced and what developing a response would require. That is more useful than treating every non-acceptance as a sales objection to be overcome through more confident language.
Configuration choice also affects how the offer is explained. Sales colleagues need to understand the conditions that distinguish one model from another, and service colleagues need an accurate account before planning installation. The customer should be able to recognise whether their setting is within the intended scope. I would prefer a clear preliminary discussion about those conditions to a broad promise followed by qualifications after an order. The exact process depends on the equipment, but the principle is that the company’s internal decision and external description should refer to the same product.
For oversight, the material question is whether management has assessed the assumptions that connect the specification with the proposed market. Directors do not need to design the workstation. They may need to understand why a broad offer became narrower, what the evidence supports and which dependencies remain. I would explain the forgone features or arrangement honestly, together with the limits of the alternative. A smaller footprint is not inherently a better strategy; it becomes a reasoned choice when it serves a defined need the original proposal could not accommodate.
The lesson I take from the fictional case is that physical context should shape ambition rather than appear after it. A real product programme would require its own authorised site evidence, technical assessments and relevant approvals, with customer information protected. The leadership judgement illustrated here is a willingness to let that evidence change the proposition before its description hardens. I want the product brief to begin with work that can happen in a real setting, then select the specification that supports it, while retaining the customers and conditions for which the chosen answer remains insufficient.