Following the work beyond the finished screen

Mandate

Represent household decisions, participant permissions and external commitments accurately in the planning product

Outcomes

• Replaced a compulsory single moving date with support for separate stages
• Narrowed employer prototype views to their intended sponsor purpose
• Added alternatives to mandatory photographic inventory entry
• Separated historical quotations from fresh provider confirmation when a plan resumed

Decisions in context

I became CPO in February 2021 and report to Arun. Twenty-three product colleagues work through three leads within ₹3.8 crore FY 2026–27 operating expense and a separate ₹1.3 crore capital programme. Zevquri has 144 employees and ₹32 crore FY 26 revenue. Fatima leads service operations, and independent providers retain their own commitments and transport decisions. My remit is the planning product, not operation of the move. The cases examine the single-date model I approved, the sponsor's view, the input methods people can use and the status of a saved quotation. Each required a trade-off in simplicity, commercial presentation or support work. I have no personal ownership allocation or statutory directorship. A future board role would require learning the enterprise beyond product design and using these cases to examine management's assumptions rather than directing its interface choices from the boardroom.

Reason for the move

Continuing product leadership while preparing a first external board contribution

Mandate

Connect household planning with sponsor access and service support

Outcomes

• Examined the different interests of household users and employer sponsors
• Connected product decisions with the work created for support colleagues
• Developed a clearer boundary between planning representation and provider commitment

Decisions in context

The head-of-journey-products role began in June 2015. Zevquri employed eighty-four people and recorded ₹14 crore FY 2016 revenue. Twelve colleagues worked through two leads within ₹1.6 crore annual expense, and I reported to the CEO. The work connected several relationships around the same plan. An employer could fund access, a household could supply private details, and providers could make separate commitments. I learned that an apparently comprehensive account might serve one participant while exposing or confusing another. Service support also showed where a product simplification merely transferred work to a colleague. This period prepared me for CPO responsibility by widening the question beyond whether a screen was easy to complete. I needed to understand what the product represented, whose authority it implied and which obligations remained outside the software even when they appeared inside its timeline.

Reason for the move

Promoted to chief product responsibility

Mandate

Make household planning tasks understandable without taking ownership of provider decisions

Outcomes

• Applied service-design research to continuing household planning
• Connected research findings with product structure and support needs
• Learned to distinguish a saved intention from an agreed external arrangement

Decisions in context

I joined Zevquri in September 2009 and moved to Coimbatore. The company had forty-eight employees and ₹7.5 crore FY 2010 revenue. Six product colleagues worked through one lead within ₹51 lakh annual expense, and I reported to the head of product. Relocation planning required me to follow decisions across several people and organisations. A household could be preparing for a job change while still deciding how and when its belongings would move. The product could help organise that uncertainty without pretending it had disappeared. I learned to distinguish a user saving an intention from a provider accepting an arrangement. The move brought my service-design experience into a continuing product whose usefulness depended on clear explanations and support, not just a successful research presentation. It also established the boundaries I later needed to preserve as the employer-sponsored offer expanded.

Reason for the move

Promoted to head of journey products

Mandate

Turn research into product choices while tracing the work moved between users and service staff

Outcomes

• Connected observed task difficulties with design priorities
• Examined whether removing a step created work elsewhere
• Developed responsibility for product trade-offs beyond documenting research

Decisions in context

In March 2003 I became product manager at Vezmari. The enterprise employed 106 people and recorded ₹26 crore FY 2004 revenue. Eight colleagues worked through two leads within ₹72 lakh annual expense, and I reported to the head of service design. I moved from documenting how people used a service to choosing what the product should ask them to do. A shorter flow could look successful while moving explanation or correction to another person. I learned to follow that transfer before claiming that a design had reduced effort. The responsibility involved negotiating priorities with clients and service colleagues, not simply defending the research team's preferred solution. I joined Zevquri because I wanted to stay with a product after release and understand how its decisions affected households, support staff and external relationships over time.

Reason for the move

Joined a continuing household-planning product to follow decisions through their operating life

Mandate

Observe how people complete service tasks and document work omitted from the formal process

Outcomes

• Learned to follow a task beyond the steps shown in a process diagram
• Recorded where users needed explanations or corrections
• Built a research foundation before choosing product priorities

Decisions in context

I began at Vezmari in July 1996 after completing design that June. The business employed fifty-two people and recorded ₹8.4 crore FY 1997 revenue. I worked in a six-colleague research group under its manager, without reporting staff or expenditure authority. My assignments involved watching people complete service tasks and documenting where the formal process failed to describe their actual work. A diagram might end at submission while the person still needed to clarify an answer or recover from a misunderstanding. I learned to record those activities without treating them as irrelevant because they occurred outside the planned steps. This was supporting research, not authority over a client's product or operating decisions. It gave me a practical beginning in the difference between a process that looks complete and an experience that actually helps someone finish the task they came to do.

Reason for the move

Promoted to product management