Start with the problem
I try to understand where users actually run into friction before settling on a solution. Most feature requests trace back to a workflow gap, not a missing feature.
Product manager · previously a frontend engineer
I've spent the last seven years working on booking flows, approval systems, and payments — usually somewhere between the user-facing surface and the operational mess behind it.
I came into product from frontend engineering, so I tend to pay attention to interaction details — edge cases, system behaviour, and how flows hold up once real users get to them.
Increase in completed bookings per session within one quarter.
Reduction in checkout drop-offs after improving pricing transparency.
Improvement in approval turnaround through workflow automation.
How I Think
A practical approach to product decisions, grounded in user behaviour and measurable outcomes.
I try to understand where users actually run into friction before settling on a solution. Most feature requests trace back to a workflow gap, not a missing feature.
The first version of a problem statement is usually the symptom. I lean on data and direct user input to figure out what's actually driving it.
The happy path matters, but trust gets built or broken at the edges. I plan for the moments where systems fail or behave in ways users don't expect.
Every feature should ship with a clear way to tell whether it worked. Agreeing on that up front keeps the team honest after launch.
Case Studies
Three projects across internal tooling, B2B SaaS, and hospitality — each with the trade-offs that shaped the outcome.
Centralized dashboard for meeting notes, action items, approvals, and access workflows.
Key Product Decisions
Every shipped product is a stack of decisions, and each one left something on the table. Here's the reasoning behind three of them.
Why
Early payment testing showed significantly higher success rates on Indian corporate cards through Razorpay compared to international gateways. Faster settlements and localised support also aligned better with finance operations for domestic enterprise customers.
Impact
Reduced payment failures during checkout, improved transaction reliability for Indian users, and simplified finance reconciliation through quicker settlements and cleaner reporting.
Trade-off
Accepted single-provider dependency in v1 to prioritise reliability and faster rollout over broader international payment coverage.
Why
Users frequently questioned fare estimates when pricing was shown without enough trip context. Displaying route distance, ETA, and map familiarity helped them better understand how the estimate was calculated.
Impact
Improved pricing transparency during the booking flow, reduced hesitation on the fare review screen, and increased user confidence before checkout.
Trade-off
Introduced additional third-party API cost and a dependency on a high-traffic screen where performance consistency mattered.
Why
Approval requests through email lacked structure, visibility, and clear ownership. Requests often stalled across teams, making booking decisions slower and audit tracking difficult for finance operations.
Impact
Automated routing rules reduced approval turnaround from days to hours, improved accountability across stakeholders, and gave finance teams better visibility into committed spend and approval history.
Trade-off
More structured workflows reduced flexibility for informal exceptions, which later required controlled override paths for urgent business cases.
I started as a frontend engineer. Most of my time went into figuring out why a flow that worked on paper broke in production — bad network, stale state, an edge case nobody mentioned in the spec.
That pulled me into product conversations earlier and earlier — what we were actually solving, what we were willing to cut, what "done" looked like. Eventually that part became the work.
Today I focus on getting the problem clear, keeping the team aligned on what matters, and shipping things that hold up once real users get to them.