Staying responsible beyond the design handover

Mandate

Connect the travel proposition with research, development and continuing service obligations

Outcomes

• Revised rain-cover access around the task during a journey
• Restricted the buckle offer to supported combinations
• Kept quality, sourcing and operating decisions with their designated owners

Decisions in context

I lead the product function through three leads, with annual expense and development authority stated separately. The rain-cover and buckle programmes have required more than a new drawing. They connect the product proposition with access during use, component support and the work another function must perform after purchase. I report to the CEO and bring research findings into the investment discussion without assuming that product authority replaces quality, safety or sourcing judgement. Invited board reviews are part of explaining those choices; they do not constitute a statutory seat. I want the programme account to show where a claim has been narrowed and which dependencies remain. That makes the role less about defending the original feature list and more about sustaining a product promise that the enterprise can actually support throughout its use.

Reason for the move

Current role; considering a consumer CPO mandate and a prepared first outside contribution

Mandate

Develop product priorities from use evidence and commercial constraints

Outcomes

• Reopened the lower-weight backpack priority after observed use
• Funded comparison of carrying arrangements and materials
• Made the cost of revising a sponsored proposition visible

Decisions in context

I led nineteen colleagues and a broader set of product choices within ₹4.1 crore annual expense. The 2019 backpack decision exposed how easily my own preference for an elegant specification could become the programme’s assumed direction. The thirty-person exercise did not choose a universal winner. It showed that loaded use required a wider question than the empty-weight comparison I had favoured. I had to explain that distinction to colleagues who had planned around the earlier priority and fund the work needed to reconsider it. Asking the research lead to present the different accounts directly helped preserve the challenge. The episode prepared me for CPO responsibility by making revision of my own recommendation part of leadership, rather than treating research as evidence collected to support a conclusion already fixed by senior sponsorship.

Reason for the move

Appointed CPO across research, product definition and development

Mandate

Follow the product from a studio proposal into shop and service use

Outcomes

• Connected customer explanations with product requirements
• Brought quality and service owners into earlier reviews
• Distinguished a demonstrator-supported action from ordinary use

Decisions in context

The retailer role let me follow a design beyond the point where a client accepted the studio handover. Twelve colleagues worked within ₹2.2 crore annual expense. Shop teams could show how a familiar demonstration concealed an action the customer found difficult alone. Service colleagues brought a different view of the same feature after months of use. I learned to take those accounts into the product brief without treating one anecdote as a complete market finding. Quality and manufacturing colleagues retained their approval responsibilities, and I needed to explain the proposed change well enough for them to examine it. The appointment made the consequences of a revision more concrete: it affected materials, instructions, shop conversations and future support. That continuing responsibility was the main reason I wanted to remain inside a product enterprise.

Reason for the move

Promoted to lead the travel portfolio

Mandate

Explain what a prototype established and what still required examination

Outcomes

• Recorded the reasoning behind design revisions
• Invited challenge of opening and fastening sequences
• Preserved client ownership of commercial and production decisions

Decisions in context

I led seven colleagues within ₹82 lakh annual delivery expense. Our work needed to be persuasive enough for a client to examine, but a convincing presentation was not the same as a supported production decision. I learned to distinguish what the prototype demonstrated from the conditions supplied by the studio. A spare surface, an empty bag or a colleague holding an object could make an action look simpler than it was elsewhere. I encouraged the team to record those conditions and propose the next useful examination. Clients retained investment and manufacturing authority, so our recommendation had to preserve their unresolved questions. Joining Nerqeshi later gave me the chance to remain involved when those questions became operating responsibilities, rather than ending my account when the design delivery was signed off.

Reason for the move

Joined a retailer to remain responsible through product introduction and use

Mandate

Make revisions traceable from the brief through the physical sample

Outcomes

• Prepared prototypes under senior review
• Recorded the idea and assumption behind a change
• Learned to separate a visible feature from evidence about its use

Decisions in context

I entered the studio after design studies completed in May 1996. In a five-person group I prepared prototypes, drawings and revision notes for a senior designer. I could suggest alternatives but did not approve client investment or production release. The work taught me that the final sample alone rarely explained why a feature took its particular form. A revision record preserved the question, the discarded route and the assumption still needing review. I began to pay attention to the actions required around the object, including how it was held while opened or where removed contents would go. That early observation was modest in scope, but it became the basis for later questions about the difference between a controlled demonstration and the experience the product was actually being sold to support.

Reason for the move

Promoted to lead studio design delivery