I stayed responsible after the screen reached the counter

Mandate

Make the booked arrangement understandable before assessment and service

Outcomes

• Separated arrival windows from later completion estimates
• Distinguished appointment capacity from parts readiness
• Preserved qualified workshop decisions in the product promise

Decisions in context

The CPO appointment joined product choices across the whole workshop conversation. Twenty-two colleagues work through three leads, while Imran owns service partnerships and qualified workshop staff retain assessment and repair decisions. The thirty-minute booking review required us to preserve a useful arrival arrangement without borrowing a completion promise from it. The later parts review showed why a free calendar slot and a reserved component needed separate states. Kavita retains enterprise authority. The annual ₹4.6 crore expense includes the ₹1.4 crore discovery and programme allocation rather than treating it as additional funding. I want the owner and workshop to understand the same next step before they act. My lack of a statutory seat remains explicit: the experience supports preparation for a possible outside contribution, but does not turn executive product responsibility into completed board service.

Reason for the move

Current CPO role; preparing for a suitable first outside contribution

Concurrent appointment

Product employment and executive reporting without a statutory directorship

Mandate

Connect booking questions with the knowledge available before inspection

Outcomes

• Approved the repair-category flow later changed
• Separated eighteen tube-related cases from twelve other assessed causes
• Replaced an implied diagnosis with a symptom-led assessment request

Decisions in context

The repair menu appeared to make routing easier, and I approved it. A selected thirty-request review showed the cost of asking an owner to choose a diagnosis before assessment. Eighteen cases were tube-related and twelve had other causes. Imran’s service colleagues challenged the product, and the seven-week correction cost ₹28 lakh. We preserved the owner’s symptom description while leaving the cause with the qualified workshop. I had already observed the difference between customer language and technical language in service-design work. The mistake was therefore not a lack of exposure but a decision that preferred a tidy category over the knowledge actually available. The later CPO role carried that lesson into timing and readiness. I wanted the product to make its promise explicit before the workshop inherited an expectation it had never agreed to fulfil.

Reason for the move

Promoted to CPO across customer and workshop product decisions

Concurrent appointment

Product employment and executive reporting without a statutory directorship

Mandate

Follow the booking interface into the first workshop conversation

Outcomes

• Observed how service staff interpreted customer requests
• Kept product confirmation separate from qualified assessment
• Retained responsibility for the released product rather than a single client presentation

Decisions in context

A recurring product changed the duration of my responsibility. I could return to the workshop after release and observe how the same screen shaped many different conversations. Fourteen colleagues worked within ₹2.3 crore annual expense. We needed to understand what owners could describe before inspection and how service staff used that description without treating it as a technical conclusion. The product could arrange a request, while qualified people retained diagnosis and repair. That distinction was part of the work before the later menu error, which is why the chronology should not portray the correction as a principle discovered for the first time in 2019. The manager role supplied the experience. The head appointment made my approval responsible when the product subsequently asked a customer for knowledge that the service itself still needed to establish.

Reason for the move

Promoted to head of product as the workshop portfolio expanded

Concurrent appointment

Product employment and executive reporting without a statutory directorship

Mandate

Understand the conversation caused by a form or screen

Outcomes

• Followed customer descriptions into service-counter decisions
• Examined categories that demanded more knowledge than users possessed
• Kept client technical and operating authority outside the design remit

Decisions in context

Clients often judged a proposed form by how neatly it organised requests. I learned to follow the form into the exchange it created at a counter, where a customer might understand the inconvenience without knowing its technical cause. Ten colleagues worked within ₹1.2 crore annual expense. We could recommend a clearer interaction, but client owners retained the service and technical decisions. I wanted to see whether a change remained useful after a demonstration and after staff had met customers who did not fit the examples in the presentation. Joining Nervashi gave me that continuing responsibility. The move was less about making a larger number of screens than about staying accountable for a product whose questions would be asked repeatedly, including by people with very little reason to know the terminology we found convenient.

Reason for the move

Joined a workshop-product enterprise for continuing responsibility after release

Concurrent appointment

Product employment and executive reporting without a statutory directorship

Mandate

Preserve how customers described a practical problem

Outcomes

• Observed the gap between symptom descriptions and technical labels
• Prepared research accounts for senior review
• Escalated assumptions that could not be established through observation

Decisions in context

I joined in June 1998 after completing design studies the previous month. Seven people formed the research group. We observed customers explaining a difficulty and service staff deciding what information they needed next. My role was to preserve that exchange accurately for senior review, without treating an observer’s interpretation as a diagnosis or an operating decision. A customer could be precise about what had happened and still be unable to name its cause. That early lesson later became central to workshop booking, although it did not prevent my own product mistake. I include the assistant period because the leadership story depends on how a familiar principle can be lost when a neat interface becomes attractive. Subsequent roles added approval authority, and with it the obligation to keep the customer’s actual knowledge visible in the question being asked.

Reason for the move

Promoted to service designer with client-facing responsibility

Concurrent appointment

Product employment and executive reporting without a statutory directorship