The moment I had approved
The table assembled well in the demonstration. Its components were available, the instructions were close at hand and the team understood the sequence. I approved the proposition because the visible result supported what we wanted to say about a modular product. It seemed ready for a room that would change. Mary asked us to examine a different moment: what would the next team receive after the table had been dismantled, packed and stored? That question exposed how much of the experience my approval had left outside the demonstration.
In our fictional exercise, thirty modules went through the selected relocation sequence. Eighteen retained a complete fitting set; twelve needed missing items replaced. The finding did not mean that twelve tables were unsafe or that the design could never be used again. It showed that the kit, identification and instructions did not yet support the whole repeatability claim we were preparing to make. The first assembly had been real within the exercise, but it was evidence for a narrower proposition than the one we wanted the client to understand.
I initially thought a clearer warning about packing might be enough. That would preserve the launch timetable and keep the kit compact. It was also an attractive explanation because it located the difficulty after the product had left our controlled demonstration. Mary challenged that boundary. If retaining the necessary items was essential to the next use, the product brief had to account for it. A reminder could be part of the answer, but it should not become a way to transfer an unexamined design responsibility to the next person.
There was a legitimate limit to what the product could control. We could not determine every storage condition, every move or every decision by an unknown future owner. A reconfigurable product does not remove the need for care or qualified assessment. The task was to distinguish those limits from work we could reasonably design and explain. That distinction required another development round, not a universal assurance. I accepted the ₹24 lakh revision because the broader claim needed a better account of the transition between configurations.
The work between two configurations
Product conversations often favour stable states. A table is assembled, a storage element is installed or a room is ready for a programme. The catalogue can show each state clearly. The transition is less photogenic: parts are separated, instructions are misplaced, labels become ambiguous and a different team has to decide what belongs together. If the proposition depends on repeated change, those activities are part of the product experience. Ignoring them does not make the work disappear; it makes its owner uncertain until the next use exposes the gap.
We revised the relocation kit, component identification and instructions for the intended sequence. Qualified engineering and materials colleagues retained assessment of the details. My product decision was not a prescription for a fixing, a load or a particular assembly method. It was a decision to include the transition in the scope and fund the work required to examine it. We withdrew the broader repeatability claim while the appropriate review continued. That was less convenient than adding a confident line to the brochure, but it was a more accurate account of what had been established.
The revised proposition also required us to explain its conditions. A customer needs to understand what must be retained, which instructions apply and when a requested change requires another assessment. The product cannot rely on the original demonstration team remaining available whenever the room moves. I want that information to travel with the object in a form the next responsible person can use. That does not mean every user should perform every task themselves. The product can identify where qualified help is needed without pretending that the help is unnecessary.
The commercial trade-off was real. The kit became more involved, the launch account was delayed and colleagues had to revisit work they considered finished. I do not want a leadership case to erase that cost by inventing a later success rate. The exercise gave us a reason to change the brief; it did not supply a measured outcome for every future move. A more responsible promise can still be harder to explain and support. The decision was worthwhile because the earlier proposition depended on work we had not yet properly included, not because correction magically removed every difficulty.
A promise that survives the demonstration
I now ask the team to describe the next person in the product's life. What will that person know, what will they possess and which decisions will they be entitled to make? The answer may differ from the original buyer's experience. A facilities colleague might receive an object without the sales conversation. A service team might see a worn surface without knowing the installed version. A new room owner might inherit labels describing a place that no longer exists. Those are product questions when the proposition includes continued use and change.
The same perspective affects renewal. A replaceable surface is useful only if the customer can identify the appropriate part and the condition supports that route. A familiar family name should not imply that every new component works with every old configuration. A long support period should not be printed before the supply and service account can sustain it. These are separate choices, each needing its own evidence. What connects them is a willingness to treat the product after installation as part of the portfolio rather than as a collection of exceptions to the launch plan.
For an executive review, I would place those continuing obligations beside the initial feature list. Which transitions does the proposition actually support? What has been examined, and what remains a proposed capability? Who owns the parts, information and service decisions? Which costs continue after the initial sale? Those questions do not require the executive team to redesign every component. They help it understand whether a word such as modular describes an operating proposition or merely the appearance of separable pieces in a controlled demonstration.
I would also resist making circularity claims from this exercise alone. Retaining fittings or developing a repair route can be relevant to longer use, but it does not establish a measured environmental benefit for the entire product. Materials, transport, service activity and actual behaviour would require their own evidence. The fictional case claims none of those outcomes. Its narrower lesson is still useful: the next assembly should not depend on resources or knowledge that the product's initial account has already allowed to disappear.
The approval I want to give now is an approval of the intended experience, with its conditions visible. The first assembled object remains important, but it is one stage in a longer account. A room that can change needs products whose identity, parts and instructions can survive the change with it. When that work is incomplete, the proposition should say so and the development plan should own it. I would rather give a client a bounded promise that can be supported than an elegant demonstration whose most difficult moment begins after the audience has left.