I had approved a reassuring message before checking its meaning

The offline screen looked reassuring. It gave a field user a clear end to the submission journey and avoided leaving a spinning indicator on a device with uncertain connectivity. That was why I supported it in 2018. The trouble was the word received. In seventeen of eighty scripted scenarios, the device had only queued the material locally. The server had not acknowledged it. Manoj asked what a user might do next if the product told them the handoff was complete. I had approved a useful-looking simplification that changed the meaning of the step.

I grew up in Surat in a Parsi family and completed business administration at the fictional Qevzarthi Management College in June 1989. The following month I joined Tezqavni Field Services as a field-service analyst. The firm had fifty-seven employees and ₹8.1 crore revenue for FY ending March 1990. I had no direct reports or spending authority. We worked with the practical details of assignments: what a request contained, who had accepted it and what evidence showed that work had moved to the next stage.

That early work made me interested in the gaps between a service description and the arrangements needed to deliver it. A catalogue could name an activity without explaining when a customer could rely on it. A completed internal form might leave the receiving person waiting for something else. I learned to follow a handoff beyond the point where my own team's record looked finished. Supervisors expected me to describe the unresolved part clearly, rather than use a status label to move the question out of view.

In February 1996 I became service-catalogue lead. Tezqavni then employed 120 people and recorded ₹29 crore revenue for FY ending March 1997. Eleven colleagues worked within my ₹85 lakh annual function expense. We translated service requests into defined offers and handling arrangements. I became responsible for explaining where the offer stopped, who performed the next step and which dependencies could alter the promised sequence. A concise description was useful only if it did not omit something necessary to the service.

I moved to Zevqanti in April 2004 as a product manager. The software vendor had 132 employees and ₹38 crore revenue for FY ending March 2005. Nine product colleagues worked within my ₹2.1 crore annual expense. I wanted to bring the service perspective into tools that would be used repeatedly, by people who would never meet the team that designed them. A workflow state could shape behaviour at many customer organisations. That made the language and conditions attached to the state part of the product decision, rather than decoration added after engineering.

My product-director appointment began in June 2012. It was a functional role without a statutory seat. Zevqanti had 390 employees and ₹146 crore revenue for FY ending March 2013. I led thirty-two colleagues within ₹7.6 crore annual operating expense. The broader portfolio made consistency attractive: one pattern could make several journeys easier to learn. It also made it easier to overlook a difference that mattered in one setting. The offline acknowledgement was the clearest example of my own overreach.

We spent ₹43 lakh correcting that design and accepted a six-week delay. The product distinguished a local queue from a server receipt, with a route for unresolved submissions. On retesting the eighty scripted scenarios, seventy-five represented the state correctly and five remained withheld from release. Those findings did not establish that an actual insurance claim had been lost, or that every possible connectivity condition had been tested. The result was a narrower supported product behaviour, with remaining work visible. I needed to explain why I had approved the earlier premise as well as why the correction was now necessary.

I became CPO in May 2021. Sixty-eight colleagues now work through five heads, and I report to CEO Leela Nezqavti. My ₹18.4 crore annual functional expense supports product work; it is not control over the company's entire revenue or a customer's insurance decisions. Manoj leads service design, with engineering and other professional owners retaining their own responsibilities. I present product choices to the board through the CEO but do not hold a statutory directorship.

Later decisions have tested the boundary in different ways. An appointment needed both parties' confirmation. An annotated inspection image needed to remain distinguishable from its original. A prospect wanted automated coverage judgement that our product remit could not support. An older version could not be retired responsibly simply because most customers had an export route. These episodes include commercial disappointment and continuing support cost, not only improvements to an interface.

I hold 0.25% of Zevqanti through its employee vehicle. My fictional databank registration and proficiency assessment have not begun, and twenty days is a provisional annual allowance for a possible outside role. I work in English, Gujarati and Hindi, with working Odia developed through life in the region. A first board contribution would require different preparation from managing a product portfolio. I would bring experience of examining what an enterprise is asking another person to rely on, together with the memory that I once let the product's appearance of completion get ahead of the work.