A product demonstration usually begins where the object starts to look useful. Drawers open, compartments reveal their contents and the tools sit in an orderly arrangement. The design appears to have solved the task because the task has been framed around the design. But a service-business user may need to take those tools away from the vehicle, work elsewhere and return them later. If the demonstration ends at the open drawer, it can conceal the work that the customer must do to make the product useful beyond that moment.
I approved a brief with that narrow frame in our fictional 2018 programme. The fixed-drawer prototype organised the van well. In a study of twelve adult service-business users, seven carried tools away to the job and five mainly worked beside the vehicle. The difference did not make the prototype useless, but it challenged the idea that one fixed arrangement should define the whole range. We committed ₹41 lakh to fixed and lift-out paths, with qualified engineering review. The decision began by acknowledging that the brief I approved had followed the storage location more closely than the working routine.
Begin before the demonstration and follow what happens after it
A useful product question includes the transitions around the visible task. What must the user gather before opening the drawer? What must be transferred when the work moves elsewhere? What happens when the tools return? Those questions do not prescribe a particular design. They identify the work that a polished demonstration can leave outside its frame. A product may still choose to serve only part of the routine, but that choice should be deliberate and understandable rather than hidden in the way the prototype is presented.
The early response in our team was to preserve the fixed arrangement and offer a separate loose tool bag. That had practical advantages. It protected the prototype investment, kept the main design coherent and avoided developing several product paths at once. Yet it also asked the first group to transfer tools between arrangements because the core product assumed that storage and use occurred in the same place. The question was whether that extra task was an acceptable part of the offer or evidence that the brief needed to change. It could not be answered simply by pointing to the orderliness of the van.
I chose to change the brief because the observed distinction concerned the purpose of the product, not an ornamental preference. That did not mean every tool should be portable or every customer should receive the same removable arrangement. Qualified engineering and application owners still needed to examine handling, installation and actual conditions. The product decision established a direction for that work. It did not bypass it. A CPO can take responsibility for the choice of problem without pretending that the research finding supplies every technical answer needed to release a physical product.
Different working situations deserve a considered choice
The five users who mainly worked beside the vehicle remained part of the account. It would have been another simplification to replace the fixed prototype with one portable design for everyone. The study showed different situations, not a universal preference for the newer idea. We retained a fixed path and developed a lift-out path so that the offer could distinguish the relevant work. That required a more deliberate selection conversation and additional development. Choice is useful when it corresponds to a meaningful difference, but it also creates obligations for manufacture, explanation and support.
Those obligations should appear in the product decision. Several options can look generous in a catalogue while being difficult to supply or maintain. A team should know what evidence justifies the difference between the paths and what the enterprise must do to make each credible. The response should not become a habit of adding an option whenever one participant describes an exception. The task is to judge whether the difference changes the core use, how widely it may matter and what further research or development is needed before the business makes a broader commitment.
There is also a question of who absorbs the complexity. A single product can appear simpler for the supplier because it moves adaptation onto the customer. Several products can appear more helpful for the customer while moving unmanageable complexity into operations. Neither view is complete alone. In our case, the ₹41 lakh programme and the harder selection conversation were explicit consequences. The enterprise accepted them to address a clear difference in observed work, while keeping the future commercial result open. The product was not improved merely because the catalogue contained more choices.
Keep the research result separate from the commercial outcome
Twelve users can reveal a problem worth acting on without establishing the proportions of an entire market. Seven people carrying tools away did not prove that seven-twelfths of future customers would choose a lift-out system. The study was evidence about the task and the limitations of the prototype. It did not establish sales, productivity or profitability after redesign. A responsible product account can explain why that evidence justified the next commitment without making it answer questions the programme had not yet examined.
The same distinction matters when management reports the work. A changed brief, a developed option, a qualified product and a measured commercial result are different stages. The first should not silently stand in for the last. Directors considering the programme need to understand what the investment will establish and what decision follows. They do not need to choose the drawer mechanism, but they should be able to ask whether the customer problem has been observed, whether the proposed response addresses it and whether the remaining technical and commercial work has a credible owner.
I would also preserve the original approval in the account. It is easy to describe discovery as something the team did before making the correct decision, leaving out the prototype that already embodied a mistaken assumption. My approval mattered because it gave the narrow frame momentum. A useful leadership narrative explains what changed my judgement and what cost I accepted when it changed. That makes the lesson available to another product team without pretending that every discovery process begins with the right question or that senior experience prevents an attractive design from hiding a practical omission.
I now try to follow the object through the customer's working day before deciding where the product story should begin and end. The vehicle remains important, but it is not always the place where the work is completed. A credible product brief can state the task it serves, the transitions it supports and the conditions it leaves to other arrangements. The aim is not to design everything around the user at once. It is to avoid mistaking the boundary of the object we sell for the boundary of the work the customer needs to do.