Hello
0%
lohith/regalla — loading
Product manager · Hyderabad, IN
(tools I reach for)
(practice)
Five principles that shape how I scope, ship, and measure product work — from discovery through delivery. Scroll — each one stacks on top of the last.
Most product mistakes happen before a single line of code. I lead discovery with user interviews, jobs-to-be-done framing, and competitive teardowns — so the team builds against a real problem, not a vague hunch. The cheapest pivot is the one you make before the sprint starts.
A roadmap without a north star is a wishlist. I align the team on the one number that has to move — activation, D7 retention, conversion, NPS — and write success criteria into the PRD itself. Features get cut, scoped, or doubled-down on the same axis.
Launch-day delight is cheap; D2 return is the real test. I scope onboarding around the user's first 'aha' and design retention loops that earn the next visit, not push for it. Every screen answers a single question — why would they open this tomorrow?
I'd rather ship a one-line copy change in week one than a reimagined experience in quarter two. Small instrumented bets compound. Big bets without evidence are just expensive opinions. Pick the smallest unit of work that can move the curve, instrument it, ship it, decide what's next.
Most teams ship and move on. I treat launch as the start, not the finish — funnel readouts, cohort views, qualitative diaries, and a post-launch review baked into every sprint. Roadmaps stop being argument-driven and start being evidence-driven.