Put the next user's work inside the product brief

In 2018 I approved a modular-table proposition after a polished first assembly demonstration. The product looked straightforward to put together, and the launch account described it as suitable for repeated reconfiguration. Mary Qezvomri asked us to follow the next part of the journey: dismantling, packing, storing and assembling it again. In a selected fictional exercise with thirty modules, eighteen retained a complete fitting set and twelve needed missing items replaced. The first demonstration had shown that the product could be assembled under the conditions we supplied. It had not established that the whole relocation experience had been designed.

The launch sponsor wanted to preserve the timetable and add a reminder about careful packing. That would have kept the kit simpler and avoided another development round. I initially found the proposal reasonable because the missing items seemed like an operating issue. Mary argued that the product promise itself depended on those items reaching the next assembly. If the kit and instructions made their retention easy to overlook, the receiving team was being asked to complete design work we had excluded from the demonstration.

I accepted ₹24 lakh of revision work covering the relocation kit, component identification and the instructions for the intended sequence. Qualified engineering and materials owners retained assessment of the actual details; the commercial brief did not prescribe an improvised fixing or bypass a required check. We withdrew the broader repeatability claim pending the appropriate review. We did not describe the twelve incomplete sets as twelve unsafe tables, nor did we claim that the revised kit had already survived an unlimited number of moves.

The trade-off was a more involved kit and a delayed launch account. I had to explain why the approval I had given was narrower than the promise we were preparing to make. The useful lesson was not that people must always pack more carefully. It was that a product sold for change needs to account for what happens between its visible configurations. The case retains the expense and the unresolved technical work because a successful first photograph cannot stand in for the next user's ability to reconstruct the product responsibly.

In 2022 we reviewed forty fictional service requests involving learning-room modules. Twenty-seven concerned the writing surface, while thirteen required a wider assessment of the module. The existing renewal proposition began with a complete replacement unit. That was easy to quote and preserved a consistent appearance, but it did not ask whether every request required the same extent of work. A worn surface and a question about the frame or fittings were being channelled into one commercial answer before the relevant condition had been assessed.

The commercial lead preferred the complete-unit offer. A separate insert would create another item to identify, stock and support, and it might reduce replacement revenue. Mary wanted to explore a surface route without pretending that it could be used in every circumstance. We needed to retain the qualified assessment of the existing module and the compatibility of any replacement. The twenty-seven surface-related requests did not constitute twenty-seven automatic approvals for a new insert. They identified a product opportunity that deserved development and a clearer service decision.

I approved ₹43 lakh for the replaceable-surface programme and ₹9 lakh annual provision for the supporting parts account. The proposition distinguished a surface enquiry from a whole-module assessment and identified the design and service owners who could approve the appropriate route. We did not claim that the new part would restore every unit to an equivalent condition or that it removed the need for professional review. The frame, fittings and intended use remained relevant to the actual decision.

The consequence was a more complex portfolio and an additional continuing obligation. We gave up the simplicity and potential revenue of treating every request as a complete replacement. No waste-reduction percentage or customer saving is invented to make that choice look automatically superior. The recorded result is a developed renewal route with explicit assessment and stocking responsibilities. I want the product account to explain why a smaller replacement can be useful while retaining the work needed to make it the right replacement. Repairability has little practical value if the client can identify the damaged surface but cannot find a supported way to address it.

In 2023 a new product version was being prepared under an established family name. The launch material emphasised continuity, and commercial colleagues wanted to describe the new components as compatible with the installed range. A review of fifty-four fictional configurations found thirty-one with an approved adaptation route and twenty-three requiring separate assessment. The shared family name did not settle that difference. A client could reasonably understand the continuity claim more broadly than the technical account supported.

The launch team wanted one concise compatibility statement. A table of versions and conditions would make the release feel less seamless, and separate assessment might slow a renewal enquiry. Mary argued that the existing customer should not discover the distinction after ordering a part. I agreed that the product needed a clear account of continuity rather than a universal claim. The thirty-one approved routes also had conditions that needed to remain attached to them; approval was not a general invitation to combine any two parts that looked similar.

We committed ₹37 lakh to the compatibility account, identification material and the development work associated with the defined routes. The twenty-three unresolved configurations remained outside the automatic renewal path until the appropriate owner had assessed them. The launch description explained how a customer could identify the installed version and find the relevant route. We did not invent a universal adaptor or treat a photograph as a substitute for technical approval. Engineering, materials and project owners retained responsibility for actual suitability.

The decision reduced the simplicity of the launch and created work around older versions when the team wanted to focus on the new one. It did not establish that twenty-three configurations were defective or that all customers could eventually use the new components. The result was a more specific compatibility proposition with unresolved work visible. I regard the installed range as part of the product portfolio, not as an inconvenient historical exception. A new version should make its relationship with earlier commitments understandable, even when that makes the release less impressive than a claim that everything works with everything.

In 2024 a service review considered seventy-two fictional modules whose labels had been based on their original room. Forty-four still matched that location, while twenty-eight had moved. Staff requesting a part sometimes used the old room label and sometimes the new room name. The product had been sold for reconfiguration, but its identification system assumed that the original location would continue to describe the object. That made a later service request harder precisely when the customer had used the flexibility the proposition encouraged.

The service sponsor wanted to update room labels after each move. That would have preserved familiar language for the client and avoided a different identifier. Mary asked what would happen when one room contained several versions or when a module moved again before the record was updated. I supported separating the stable product identity from its current location. The aim was not to remove the room name, which remained useful for finding the object. It was to stop the room name from carrying a technical identification role it could not reliably retain.

A ₹19 lakh programme developed durable product identification and a separate, changeable location account. The relevant owners reviewed how the identifier would be attached and read in the intended conditions. The service process used it to locate the appropriate product record before assessing a parts request. It did not turn an identifier into proof of current condition, correct assembly or entitlement to a particular repair. The actual module still needed the assessment appropriate to the request.

The cost was another piece of information for teams to maintain and explain. We did not claim that service errors had fallen by a measured percentage or that every historical unit could be identified immediately. The seventy-two-module review supported a design change, not a universal performance result. The case changed how I think about reconfigurable products: information must move with the object while remaining able to describe its changing context. A product that can leave its original room should not lose its identity when it does so.

In 2025 the proposed portfolio material included a seven-year support statement. It was attractive because clients wanted confidence that a room could be maintained after the initial fit-out. The product team intended to support the range, but a review of six relevant supply arrangements found four with a documented parts-continuity basis for the proposed period and two still unresolved. The intended promise had reached the copy before the supporting account was complete. We needed to examine what the enterprise was actually prepared to commit to, rather than let a duration become a substitute for that work.

The commercial sponsor wanted to keep the headline while procurement completed the remaining discussions. Removing it would weaken the new proposition and make the practice appear less confident than competitors. Procurement and service colleagues warned that an intention to find a part later was not equivalent to a supported arrangement now. I supported narrowing the statement to the parts and conditions the enterprise could substantiate, with legal and commercial owners reviewing the actual commitment. The four documented arrangements did not automatically cover every item or every kind of request.

We allocated ₹29 lakh to the product-support review and ₹12 lakh annual provision for the bounded parts and information account. The two unresolved arrangements stayed outside the broad claim until their position could be established. The revised material explained how the supported scope would be identified and where a request required further assessment. It did not offer a universal seven-year promise, and it did not imply that the website itself created or replaced the terms of a real agreement.

The consequence was a less striking launch line and continuing work behind a narrower offer. No renewal uplift or avoided-loss figure is invented. We gave up the apparent certainty of one duration because the operating evidence did not yet support it across the range. My lesson is that a product promise has a supply and service history even before it reaches the customer. A CPO should bring those owners into the proposition early enough that confidence comes from the commitment the enterprise can sustain, rather than from how long a number looks in the brochure.