My responsibility grew from describing the task to choosing the work we would accept.

Mandate

Protect a coherent shared roadmap while defining the consequential tasks and limits of new product capabilities.

Outcomes

• Declined the proposed ₹18 crore exclusive workflow in 2023 and supported ₹8.4 crore configurable-module work.
• Retained human publication review after 180 of 1500 evaluated status suggestions had the wrong context in 2021.
• Recorded eighty-six first-workflow completions and thirty-four incomplete teams in the 2025 thirty-day onboarding pilot.

Decisions in context

The CPO role makes the consequences of a promise visible across the shared product rather than within one requested feature. I want the team to examine the continuing roadmap and service commitment before accepting an attractive exception. The exclusive-workflow case and the assisted-status decision both required a narrower proposition than the initial sponsor preferred. My delegation funds product work; engineering, service, sales, security, finance and legal retain their own decisions. Company revenue is not personal P&L or a recurring-revenue claim. I have presented product matters to the board as an executive since this appointment in July 2019, with no statutory seat in the fictional chronology. The onboarding pilot also keeps incomplete teams visible, because a product account should explain what useful work has occurred rather than treat a completed rollout activity as the final customer result.

Reason for the move

Appointed CPO after leading platform products; remains responsible for the product function.

Mandate

Connect platform capability boundaries with the tasks and conditions enterprise customers need to understand.

Outcomes

• Defined the 2016 intermittent-connectivity proposition around assigned-job viewing and six capture forms.
• Supported ₹6.8 crore product work with explicit queued-update and reconnection conditions.
• Recorded seven pilot firms accepting the scope and three declining because their offline needs were broader.

Decisions in context

Platform leadership required a more deliberate distinction between a useful bounded capability and a phrase that sounded broader than the product. The offline proposal was a clear example. Customers needed to know what they could do while disconnected and what remained pending on reconnection. I worked with engineering and service colleagues to make those conditions understandable without presenting every implementation detail as product copy. The three pilot firms that needed more were part of the evidence, not a communication problem to be explained away. My expense and team described product responsibility rather than authority over every technical or operating decision. This period prepared the wider CPO appointment by making the boundary of a promise a central product choice, especially when a simple sales phrase could invite expectations the capability had never been designed to fulfil.

Reason for the move

Promoted to the CPO remit as product choices extended across the enterprise portfolio.

Mandate

Develop enterprise products while examining how individual requests affect the common roadmap.

Outcomes

• Made the underlying customer task part of product scoping before committing to a separate implementation.
• Distinguished a shared capability from the continuing support implied by a customer-specific branch.
• Developed the platform perspective that led to responsibility for the broader product set.

Decisions in context

Joining Mervanith changed the cost of a seemingly straightforward customer commitment. A request could affect common work relied on by other organisations and create obligations beyond the initial delivery. I wanted product discussions to include that continuing consequence before agreement on a preferred implementation. The director title was an employment role, without statutory board membership. My function worked with engineering, service and commercial colleagues rather than decide their responsibilities through a roadmap entry. The earlier keyboard omission remained relevant: a product choice needed to preserve the actual task, not simply the appearance of a successful demonstration. This appointment connected that habit to shared-platform decisions. The later vice-president role grew from the need to understand capabilities as part of a coherent product used across customers, rather than as a series of isolated requests with no collective cost.

Reason for the move

Expanded into platform-product leadership as responsibility moved beyond individual enterprise products.

Mandate

Select interactions that serve enterprise tasks while preserving necessary ways to operate the product.

Outcomes

• Owned the 2002 decision to replace keyboard entry with a drag-only planning prototype.
• Accepted evidence that eleven of twenty-six planners could not perform three defined tasks without a pointer.
• Supported ₹52 lakh correction restoring a keyboard-operable route alongside pointer interaction.

Decisions in context

Product management required me to choose an approach and defend why it served the work. The scheduling prototype exposed a preference I had mistaken for a sufficient product reason. A new gesture looked immediate, but that appearance did not justify removing another means of completing the task. Suresh Dharveth’s challenge led to a correction that preserved keyboard operation alongside the pointer route. I did not claim that the bounded review resolved every accessibility issue or established universal productivity improvement. The team and expense figures describe the later 2004 scope, while the mistake belongs to 2002. Moving to Mervanith offered a larger product setting in which those choices would affect multiple customers. I carried the lesson that an attractive demonstration must be tested against the capability it removes as well as the capability it adds.

Reason for the move

Joined Mervanith for a broader enterprise-product role within a shared workflow platform.

Mandate

Understand the decisions and constraints behind a requested enterprise-software capability.

Outcomes

• Examined the business task before expressing a request as a proposed feature.
• Distinguished the stated preference from the operating constraint it was intended to address.
• Developed the requirements perspective that supported progression into product management.

Decisions in context

I entered the role after completing technology studies in May 1991. Working under a requirements lead taught me to ask what the user needed to accomplish before treating the first requested feature as the answer. A constraint might involve another task, an interruption or a means of interaction that a short specification did not initially reveal. I belonged to the nine-person group without managing it and had no spending authority. The later company scale and product leadership should not be projected into this appointment. Its contribution was a habit of listening for the work behind the request. Promotion then tested whether I could preserve that habit when responsible for choosing a design, a setting in which delivery pressure and the appeal of a polished demonstration could make the initial question easy to forget.

Reason for the move

Promoted to product management with responsibility for selecting the software response as well as analysing the task.