AMA: Gainsight Director, Product Management, Pavan Kumar on Product Innovation

Start by tying the idea to a clear business outcome, then de-risk it with evidence before asking for full investment. Anchor on the “why now” What market shift, customer pain, or tech inflection makes this urgent? Frame it as the opportunity cost of not investing Quantify the upside (without overfitting) Define the problem size (TAM to realistic reachable value) Map to revenue, retention, or cost leverage Show early proof, not just vision Customer signals: interviews, design partners, willingnes ...Read More

There’s no fixed ratio - it should evolve with product maturity. The best teams intentionally balance big bets and incremental improvements based on where the product is in its lifecycle. Best practice by product maturity Early stage (0 → 1) Big bets: 60–80% Incremental: 20–40% Focus: finding product–market fit, testing bold hypotheses quickly Bias toward learning and iteration over polish Growth stage (1 → N) Big bets: 30–50% Incremental: 50–70% Focus: scaling what works while expanding into ad ...Read More

Generate ideas widely using customer and data signals, but evaluate them ruthlessly on impact, risk, and strategic fit before investing. I use a combination of structured ideation and rigorous evaluation frameworks. The goal is to generate broadly, but converge quickly on ideas that have real impact. For generating ideas Problem-first discovery Start from customer pain, workflow gaps, and unmet outcomes Use JTBD thinking to understand what customers are trying to achieve Divergent thinking frame ...Read More

You manage innovation risk by making it explicit, breaking it into testable assumptions, and de-risking it in stages rather than betting big upfront. Identify and classify risks early Market risk: does anyone care or pay? Product risk: does it solve the problem well? Technical risk: can we build and scale it? GTM risk: can we sell and drive adoption? Convert risks into assumptions Define what must be true for success Prioritize the highest-risk assumptions first Run structured validation loops S ...Read More

Innovation thrives when teams have clarity on problems, permission to experiment, and a system to scale what works. You foster a culture of innovation by making it safe, structured, and outcome-driven, not by relying on ad-hoc creativity. Set the tone from the top Make it clear that innovation is expected, not optional Reward thoughtful risk-taking, not just successful outcomes Normalize failure as learning, not incompetence Anchor innovation to real problems Push teams to start with customer pa ...Read More

Breakthrough ideas don’t come from brainstorming sessions. They come from seeing what others overlook and connecting the dots early. In practice, they emerge from a combination of deep customer understanding, technology shifts, and internal signals. A key input is immersing in customer workflows and identifying friction that teams have simply learned to live with. These normalized pains are often the most valuable opportunities. Attention to power users and edge cases also helps. What they are t ...Read More

Most product managers don’t fail at innovation because of lack of ideas, but because they approach it with the wrong mindset and operating model. Starting with solutions, not problems Jumping to features instead of deeply understanding customer pain Leads to incremental improvements, not breakthrough value Over-indexing on existing customers (often the biggest trap) Optimizing for current power users while ignoring new personas or unmet segments Limits expansion and creates local maxima Confusin ...Read More

Customer discovery, for me, is about separating what customers say from what actually drives behavior, friction, and willingness to change. The goal is not just to collect feedback, but to identify patterns, validate severity, and decide which problems are worth solving at scale. Start with outcomes, not feature requests I rarely begin with “what do you want built?” Start with: what are you trying to achieve, where does the process break, what workarounds exist today, and what is the cost of tha ...Read More

Engineering and design are not execution functions in innovation - they are co-creators who shape the idea, not just build it. Design: problem framing and desirability Brings clarity to ambiguous problem spaces through user research and journey mapping Rapidly prototypes concepts to test usability and value before any build Helps simplify and sharpen the core value proposition Engineering: feasibility and scalability Validates what is technically possible and at what cost/speed Identifies constr ...Read More

Data-driven decisions, for me, are about combining data, context, and judgment - not just relying on dashboards. Start with a clear question or hypothesis What decision am I trying to make? What does success look like, and how will I measure it? Use the right mix of data Quantitative: usage, funnels, retention, cohorts Qualitative: customer interviews, support tickets, sales feedback Data explains what is happening; conversations explain why Focus on actionable metrics Tie metrics to business ou ...Read More