I’ve sat in countless AI measurement debates and noticed a recurring gap. One major voice has been noticeably underrepresented in the AI measurement conversation: the product manager (PM) that’s leading development. From experience, PMs and developers do need different measurement tools—and making those differences explicit is exactly what speeds up decisions and improves outcomes.
Developers optimize the model and system layer. Their toolkit centers on eval-driven development: offline evals, regression suites, red-teaming, latency and throughput monitoring, token cost tracking, and hallucination rate reduction. On the delivery side, engineering teams watch DORA metrics alongside CI/CD performance to keep iteration fast and safe. When building LLM-backed experiences, they also care deeply about retrieval-first pipeline quality and context window management because those mechanics determine grounding, relevance, and consistency.
PMs, by contrast, own outcomes. We instrument user journeys end to end and define a clear north-star tied to value: activation, time-to-value, task success rate, retention analysis, support deflection, and revenue contribution. We rely on A/B testing frameworks and minimum detectable effect (MDE) planning to separate real impact from noise, and we consolidate behavioral signals in a unified analytics platform like Amplitude analytics and Pendo to understand adoption, friction, and cohort differences. This is the heart of product-led growth and continuous discovery: evidence, not anecdotes.
The fact that these toolboxes differ is a strength, not a weakness. Specialized metrics keep responsibilities crisp: developers guarantee model quality and reliability; PMs guarantee that quality translates into customer and business outcomes. What we need is an explicit metrics ladder that connects layers—model-level quality floors and SLOs, feature-level KPIs, and company-level results—so trade-offs are transparent and prioritization is principled.
In practice, I create a shared measurement contract for every AI initiative. It links eval sets to user-facing success criteria, defines acceptance thresholds, and spells out observability across the stack. We include governance from day one—AI risk management, privacy-by-design, and data governance—so we can scale responsibly without slowing teams down.
Here’s the AI product toolbox I give my teams: start with a concise value hypothesis; define a success rubric the customer would recognize; instrument the happy path and the failure path; plan experiments with MDE up front; segment results by persona and job-to-be-done; and close the loop with qualitative feedback inside the product via in-app guides, product tours, and lightweight surveys. For AI features specifically, add Agent Analytics for agentic AI, capture grounding sources for explainability, and log model/context inputs to make debugging and iteration repeatable. That way, LLMs for product managers stop being magic and start being manageable.
When we roll out a new assistant—whether a retrieval-augmented copilot or a voice AI agent—we set two dashboards: one for developers (eval pass rates, latency, context integrity, error budgets) and one for PMs (activation, task completion, deflection, satisfaction). The dashboards read differently by design, yet they are joined at the hip by shared definitions and experiment IDs. This lets us move quickly with confidence: engineering can tighten quality loops while product steers toward the outcome that matters most.
If you’re feeling the tension between model metrics and product metrics, don’t collapse them—connect them. Start with a thin slice, agree on 3–5 measurable outcomes, and let your evals and A/B tests work together. With a clear metrics ladder and a unified analytics platform, PMs and developers can each excel at their craft and still ship AI that customers love.
Buy-in isn’t a single meeting; it’s a designed journey. Over the years leading product strategy at HighLevel, I’ve learned that the fastest way to earn durable support is to reduce uncertainty, align on outcomes, and create visible momentum. Explore how to get buy-in from stakeholders with practical strategies, clear communication tips, and proven methods used by the best. Here’s the 7-step playbook my teams and I rely on to move from idea to aligned action.
Step 1 — Anchor on outcomes, not outputs. I start by writing a crisp problem statement, the target customer, and the measurable outcome tied to our North Star metric. I translate this into outcomes vs output OKRs so every stakeholder can see the difference between what we’ll ship and what we intend to change. This framing keeps discussions grounded in impact, not features.
Step 2 — Map stakeholders and incentives. Effective stakeholder management begins with a living map: economic buyers, executive sponsors, influencers, and operators. I capture each person’s goals, risks, and decision cadence. When I speak to Finance, I foreground cost and runway; with Sales, I emphasize pipeline and win rate; for Customer Success, I speak to retention and NPS. Meeting stakeholders where they are builds trust quickly.
Step 3 — Co-create early with the product trio. I pull the product trios (PM, Design, Engineering) into continuous discovery with GTM partners to validate assumptions and de-risk the solution. This is where empowered product teams shine—rapid discovery sprints, early prototypes, and clear learning objectives. Co-creating exposes blind spots early and transforms critics into champions.
Step 4 — Socialize a narrative, not a deck. Before any formal review, I circulate a short narrative memo that ties our product strategy to a clear value proposition, competitive differentiation, and go-to-market strategy. I include options and trade-offs so stakeholders feel invited to shape the path, not just stamp approval. Pre-wiring conversations ensure that the “meeting” is simply the last 10% of the decision.
Step 5 — Back the story with data and a viable plan. I combine retention analysis, funnel metrics, and customer evidence to demonstrate opportunity size and risk reduction. Then I outline a phased approach with product roadmapping and sprint planning, milestones, and success metrics. I highlight the smallest viable bet that proves value fast, along with contingency paths if we learn something unexpected.
Step 6 — Design the decision. I define the decision we need, by whom, and by when. The decision doc includes the problem, options, risks, mitigations, and the explicit ask. I schedule 1:1s to address concerns, then run a focused review with clear roles and time-boxed discussion. Clarity about the decision—and the criteria—prevents drift and protects timelines.
Step 7 — Sustain momentum post-approval. After the green light, I convert the plan into execution cadences: weekly demos, transparent dashboards, and QBRs vs OKRs check-ins to reinforce outcomes. We celebrate learning milestones, not just launches, and keep stakeholders informed with concise updates that tie progress to the original outcomes and value proposition. Momentum is the best antidote to second-guessing.
Clear communication and a repeatable process turn buy-in from a hurdle into a habit. When stakeholders see a compelling narrative, credible evidence, and a path to value, they don’t just approve—they advocate. Follow these seven steps and you’ll build alignment faster, ship smarter, and strengthen trust across the organization.
Continuous Discovery Habits turns five this year, and I’m celebrating by inviting you to read it with me. Over 135,000 people have bought the book. I’ve seen these habits transform outcomes, reduce rework, and sharpen product strategy in my teams and across the product community, but I also know it’s not easy to sustain the practice—especially when you feel like the lone champion in your organization.
To make it easier and more social, I’m launching the 2026 Continuous Discovery Habits Book Club. We’ll read the book together—one section per month—with discussion questions, practical exercises, and resources that help you actually do the work, not just read about it. Whether you’re picking up the book for the first time or revisiting it, the goal is to build real muscle memory in discovery.
By December, you won’t just understand continuous discovery—you’ll be practicing it.
Each month, I’ll share a reading guide with reflection prompts, exercises you can run solo or with your product trios, and short videos to help you spread the ideas across your team. I’ll monitor comments throughout the year so you can ask for help, share what’s working, and connect with peers—even if you join late.
I’ll also host quarterly live discussion sessions so we can compare notes, push through sticking points, and swap tactics with other empowered product teams. If you want to participate, grab a copy of the book (or dig up your old copy), share the "Spread the Love" videos to get friends and colleagues on board, reserve time to try the team exercises, and register for the community sessions. Let’s do this.
🎖️ This reading guide is brought to you by New Year, New Habit: The 5-Day Customer Interview Challenge. Become a more confident interviewer in less than a week. You’ll conduct one practice interview a day, get personalized and detailed feedback so you know exactly what to improve, and we’ll be giving out daily prizes to the most improved. Join the challenge today.
This Month’s Reading: Introduction; Chapter 1: The What and Why of Continuous Discovery; Chapter 2: A Common Framework for Continuous Discovery. Estimated reading time: ~40 minutes.
These chapters will introduce you to why discovery and delivery are not phases—they happen continuously. You’ll see a clear benchmark for what "continuous discovery" looks like, learn what product trios are and why they’re the foundation for good discovery, and explore six prerequisite mindsets (outcome-oriented, customer-centric, collaborative, visual, experimental, continuous) you’ll need before these habits can stick. You’ll also get the opportunity solution tree—a visual framework for connecting what you’re building to why you’re building it. Need a copy? Grab the book: https://amzn.to/3hGkNYT?ref=producttalk.org
We learn best in community. Use these short videos to share key concepts with teammates and invite them to read along: What is product discovery? https://videos.producttalk.org/videos/799fdbb41e16ebc4f0/what-is-product-discovery?ref=producttalk.org — a quick intro to the key idea behind discovery work. Defining continuous discovery https://videos.producttalk.org/videos/a79fdbba151ee3c72e/defining-continuous-discovery?ref=producttalk.org — a clear benchmark to aspire to. The rhythm of continuous discovery https://videos.producttalk.org/videos/4d9fd5b4111ee0c2c4/the-rhythm-of-continuous-discovery?ref=producttalk.org — the two small research activities you should do every week. The underlying structure of product discovery https://videos.producttalk.org/videos/449fdbb5191fedc4cd/the-underlying-structure-of-product-discovery?ref=producttalk.org — how outcomes, opportunities, and solutions connect. What’s a product trio? https://videos.producttalk.org/videos/a79fdbb31e1be2c12e/whats-a-product-trio?ref=producttalk.org — why cross-functional collaboration matters.
🎖️ This reading guide is brought to you by Just Now Possible, a podcast about how AI products come to life—straight from the builders. If you are being asked to add AI features to your roadmap, you don’t have to start from scratch. Get a head start by hearing how other teams are navigating similar challenges. Find it on YouTube, Apple Podcasts, and Spotify.
When we reflect and discuss what we read, we absorb more and apply it better. This month is about building awareness of where you are today—no judgment. The first step in any change is getting a baseline. Next month, we’ll take small steps to strengthen the habits.
Here are three prompts for individual reflection. 1) Think about a recent product decision your team made. Did you rely more on opinions, data, or customer input? Get specific. 2) Which of the six prerequisite mindsets (outcome-oriented, customer-centric, collaborative, visual, experimental, continuous) is strongest for you personally? Which would require the biggest shift? 3) What’s your reaction to weekly customer touch points? Does this excite you? Scare you? Something else?
And here are three prompts for team discussion. 1) Who on your team is responsible for discovery and delivery? How interconnected are these activities? 2) How does your team currently collaborate cross-functionally? When product, design, and engineering come together, is it to make decisions—or to hand off work? 3) Think of a recent feature your team built. What opportunity did it address? What else could you have built to address that opportunity?
For this introductory month, focus on seeing your current system clearly. In my experience, visibility alone reveals friction and makes the path to change obvious—and measurable.
Exercise: Draw Your Current Discovery Process. Time: 60 minutes. Do this solo first, then compare with your team. Take a blank sheet and draw how your team actually decides what to build. Show where ideas come from, who makes decisions and how, where (if anywhere) customers enter the picture, and how you know if you built the right thing. Then compare drawings with teammates. Where do perceptions differ? What does that say about your shared understanding?
Exercise: Audit Last Week’s Decisions. Time: 30 minutes. Do this solo or with your team. List every product decision your team made last week—big or small. For each decision, note who made it, what information it was based on, and whether customer input was part of the process (and how). Then look for patterns: how many included direct customer input versus assumptions, opinions, or secondhand information?
If you prefer an audio summary of this month’s reading—including the book chapters and the resources below—listen here: Stop Building The Wrong Things Faster (audio summary by NotebookLM): https://www.producttalk.org/content/media/2025/12/January—Stop_Building_The_Wrong_Things_Faster.m4a
Related in-depth guides to go deeper: Product Discovery Basics: Everything You Need to Know: https://www.producttalk.org/product-discovery/ Product Trios: What They Are, Why They Matter, and How to Get Started: https://www.producttalk.org/product-trios/ Opportunity Solution Trees: Visualize Your Discovery to Stay Aligned and Drive Outcomes: https://www.producttalk.org/opportunity-solution-trees/
Other voices worth reading: Product Discovery: Pitfalls and Anti-Patterns by Chris Jones: https://svpg.com/product-discovery-anti-patterns/?ref=producttalk.org Addressing the Challenges of Product Discovery by Saeed Khan: https://medium.com/swlh/the-challenges-of-product-discovery-6ac6109d13a8?ref=producttalk.org Making Product Discovery Work in Small Teams by Sofia Quintero: https://www.chargebee.com/blog/product-discovery/?ref=producttalk.org Product Waste and the ROI of Discovery by Richard Mironov: https://www.mironov.com/waste?ref=producttalk.org
Related course if you want structured practice: Product Discovery Fundamentals – this course walks you through the complete continuous discovery framework with hands-on exercises: https://learn.producttalk.org/cdh-master-class?ref=producttalk.org
Our live discussion schedule for 2026 (sessions are not recorded): Wednesday, March 18, 2026: 9am–10am PDT and 4pm–5pm PDT. Tuesday, June 16, 2026: 9am–10am PDT and 4pm–5pm PDT. Thursday, September 17, 2026: 9am–10am PDT and 4pm–5pm PDT. Wednesday, December 16, 2026: 9am–10am PST and 4pm–5pm PST. Invitations will go out to Supporting Members and CDH Members two weeks beforehand—reserve the time now.
As you work through this month’s material, connect it to your product strategy, outcomes vs output OKRs, and product roadmapping and sprint planning. In my teams, discovery sticks when product trios own the rhythm, weekly customer touch points are normalized, and the opportunity solution tree keeps everyone aligned on outcomes.
I’m thrilled to learn alongside you this year. Grab the book, invite your trio, and let’s build habits that last.
Every quarter, I revisit the same three questions: Are we accelerating adoption, lowering cost-to-serve, and managing risk without slowing the roadmap? Tools that help me answer all three with clarity earn a place in my stack. That’s why the concept behind Pendo’s Agent Analytics resonates so strongly—it gives product leaders a way to see, in one view, how users engage with AI-powered assistants, in-app guides, and core workflows, and how those behaviors translate into product-led growth.
Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement.
In practice, Agent Analytics functions as a unified analytics platform for the modern product team. I can observe how users interact with agents and nudges inside the product, connect those interactions to user activation and retention analysis, and prioritize improvements that deliver measurable outcomes. The result is fewer blind spots across the journey and a tighter feedback loop between discovery and delivery.
The real value shows up when I pair analytics with targeted interventions. For example, I’ll instrument critical paths, baseline activation, then use in-app guides to remove friction at the exact moment users need help. I incorporate A/B testing and continuous discovery to validate which prompts, pathways, or workflows actually move the needle. With a clean view of adoption, engagement, and time-to-value, my team can double down on what works and retire what doesn’t—faster.
Risk reduction is equally important. With clear behavioral signals, I can spot confusing prompts, unhelpful agent responses, or unexpected drop-offs before they scale into churn or support volume. That visibility informs our product strategy, aligns stakeholders on trade-offs, and keeps our governance tight without stifling innovation—especially critical as AI Strategy becomes part of everyday product decisions.
If you’re weighing whether Agent Analytics deserves a place in your toolkit, consider this: better instrumentation yields better decisions. When you unify guide interactions, agent engagement, and core product usage, you can attribute uplift more precisely, forecast impact with greater confidence, and operationalize product-led growth. That’s how we increase adoption, cut unnecessary cost, and de-risk the roadmap—while building experiences customers actually love.
AI is changing how I build products, not by replacing designers or researchers, but by amplifying the quality and speed of what our product trios can deliver. The real breakthrough isn’t a single tool; it’s the way genAI and traditional methods combine into a tighter discovery–design–delivery loop that shortens time-to-value without sacrificing rigor.
Learn how Pendo’s product design team is using genAI and traditional tools to speed up design and development.
In practice, that’s exactly the pattern I see working across my teams: we treat genAI as part of the AI product toolbox—great for rapid exploration, structured synthesis, and test preparation—while we rely on our proven techniques to validate outcomes. For early-stage concepting, I use prompt engineering to generate multiple storyboard options and interaction flows in minutes, then refine those outputs with our design system for alignment and accessibility. It’s a pragmatic “gen ai for product prototyping” approach that lets us compare more alternatives, faster, with better signal.
On the testing front, AI accelerates everything around A/B testing without diluting statistical discipline. We draft hypotheses, define success metrics, and estimate minimum detectable effect (MDE) with guardrails, then deploy variants via feature flags in CI/CD. That pairing—LLMs for product managers plus eval-driven development—keeps experiments reproducible while boosting deployment frequency. The outcome is fewer opinions, more evidence, and a tighter feedback loop from build to learn.
Research goes from weeks to days when we combine a retrieval-first pipeline for qualitative data with strong data governance. I’ll ingest interview notes, support tickets, and session transcripts to cluster themes, then pressure-test the clusters with live customer calls. Privacy-by-design and AI risk management remain non-negotiable: we redact sensitive fields, constrain context windows, and keep a human-in-the-loop for decisions that affect user experience or compliance.
Where analytics meets adoption, tools like in-app guides and product tours help us translate insights into behavior change. I’ll prototype a flow, auto-generate guidance variants, and run controlled rollouts to target segments, measuring activation and retention analysis in parallel. This is product-led growth in action: discover the friction, design the intervention, instrument the journey, and validate outcomes with unified analytics.
Organizationally, empowered product teams and continuous discovery make the difference. Our product trios work from outcomes vs output OKRs, pairing competitive differentiation with product strategy to keep bets focused. We meet weekly to review experiment readouts, model trade-offs with the Kano Model, and update product roadmapping and sprint planning based on verified learning—never vibes alone.
If you’re getting started, begin with one workflow—say, prototype generation plus structured experiment design—and measure impact across cycle time, experiment throughput, and decision quality. Layer in communities of practice to share prompt patterns, establish eval baselines, and codify what “good” looks like. The companies winning with AI aren’t chasing shiny objects; they’re building a repeatable system that turns curiosity into customer value.
I walked into PendomoniumX London energized by a simple question: are we finally past the AI hype cycle and into real product impact? From the hallway conversations to the main stage, the momentum was unmistakable—and deeply practical.
PendomoniumX’s sixth stop brought 350+ software leaders together for a day of AI transformation, real-world stories, and product innovation.
That scale and focus say a lot. Across the dialogues I joined, the center of gravity has clearly shifted from experiments to execution: building an AI Strategy that aligns with product roadmaps, turning promising prototypes into production-grade AI workflows, and measuring value in ways that reinforce product-led growth. It’s the inflection point where Generative AI moves from isolated pilots to cross-functional capabilities.
My biggest takeaway for product leaders: treat AI like any other durable capability. Start with sharp problem framing and customer outcomes, run continuous discovery to validate use cases, and sequence delivery through product roadmapping and sprint planning. Pair this with privacy-by-design and sensible governance so your teams can move fast without cutting corners.
Operationally, I’ve found it essential to design experiences that accelerate user activation—think thoughtful onboarding, in-app guides, and product tours that reduce friction while teaching new AI-powered behaviors. For teams adopting LLMs for product managers, keep your evaluation loops tight, instrument the journey end-to-end, and make sure every iteration maps to a clear value proposition customers can feel.
Events like PendomoniumX London remind me why community matters: they compress learning cycles. If you’re steering an AI portfolio, now is the moment to translate vision into repeatable systems—prioritize the right bets, make adoption effortless, and let data tell you when to double down or pivot. That’s how we turn AI transformation into durable product innovation.
Experience quality compounds just like code quality. To align teams and accelerate outcomes, I rely on a clear, five-stage software experience maturity model to assess where we are, why we’re there, and how to advance. It turns fuzzy debates into concrete product strategy and reinforces a product-led growth mindset.
Find out where you stand—and what to fix first—with this maturity framework.
Why a five-stage model? It gives product, design, engineering, and go-to-market a shared language for trade-offs, helps us move from opinions to evidence, and ties day-to-day improvements to outcomes vs output OKRs. Instead of spreading effort thin, we sequence the right bets at the right time and build momentum with measurable wins.
Here’s how I apply it in practice. I start with a brief, honest self-assessment across the customer journey: onboarding clarity, user activation moments, in-app guides and product tours, UX writing, support loops, reliability, and analytics coverage. Then I layer in learnings from continuous discovery and product discovery—interviews, usage patterns, and support transcripts—so we see the experience as customers do, not just as we intended.
When it comes to what to fix first, I prioritize prerequisites over polish. If the value proposition isn’t clear, onboarding is confusing, or activation is inconsistent, we address those before adding new features. I instrument the funnel end-to-end, establish a minimum detectable effect (MDE) for A/B testing, and ensure we can answer basic questions about who activates, who retains, and why.
Measurement is non-negotiable. I pair retention analysis and activation metrics with qualitative signals to avoid local maxima. Amplitude analytics helps reveal behavioral patterns, while Pendo and in-app guides close gaps in comprehension and guidance. Intercom and CRM integration with HubSpot connect product signals to account health, so we can see how experience maturity drives revenue and retention.
Operationally, I anchor the roadmap to a small set of experience outcomes, link them to product strategy, and review progress in cadence with leadership. This approach builds product management leadership muscle: sharper stakeholder management, clearer trade-offs, and faster feedback loops. Most importantly, the team sees how each improvement ladders up to a better, more durable user experience.
If you’re mapping your own path across the five stages, start by sizing the gaps that block activation and retention, commit to a few high-leverage fixes, and measure relentlessly. With a shared maturity model, your team gains focus, your customers feel the difference, and your product compounds value with every release.
INDUSTRY 2025: The Product Conference is circled on my calendar for good reason. In my role leading product management at HighLevel, I look for events that sharpen strategy, accelerate learning, and connect me with operators who ship. This one consistently delivers on all three, and 2025 promises to raise the bar for product management leadership.
Join Pendo at INDUSTRY in Cleveland, Ohio.
First, I expect deeply actionable product strategy insights—beyond platitudes. I’m prioritizing conversations on outcomes vs output OKRs, product roadmapping and sprint planning, and how great teams articulate a crisp value proposition while maintaining points of parity that matter. I’m going in with specific questions on product-market fit lessons and how to systematize strategic bets without stifling discovery.
Second, the surge of AI in product work is too important to observe from the sidelines. I’m comparing approaches across AI Strategy, LLMs for product managers, prompt engineering, and eval-driven development—especially in retrieval-first pipeline patterns. My focus: where AI genuinely improves product discovery, in-app guides, and customer support ai strategy, and where it risks adding complexity without outcomes.
Third, the community is unmatched for conference networking and pragmatic learning. I’m intentional about meeting product trios who run continuous discovery at scale, as well as leaders who’ve cracked stakeholder management under pressure. These are the moments where competitive differentiation is born—through candid stories of what didn’t work and why.
Fourth, I’m eager to stress-test data practices that power product-led growth. I’ll be exchanging notes on retention analysis, unified analytics platform decisions, user activation, and how teams integrate qualitative feedback with event data to inform roadmaps. I’m also interested in how practitioners leverage platforms like Pendo, Amplitude analytics, Intercom, and HubSpot to reduce time-to-insight and craft effective product tours and in-app guides.
Fifth, I treat INDUSTRY as a checkpoint for leadership growth. I’m looking for fresh takes on empowering product teams, first principles decision making, organizational development, and the IC to manager transition. The best sessions don’t just inspire; they give me two moves I can apply with my team on Monday.
To make the most of the week, I’m applying a continuous discovery mindset: arrive with clear learning goals, capture portable frameworks, and translate at least two insights into experiments before wheels-up. If you’re focused on product strategy, product discovery, and product-led growth, we’ll have plenty to compare and build on together.
I’ll be in Cleveland ready to learn, share, and connect with peers who care about craft and outcomes. If you’re attending, let’s compare notes on what’s working, what’s stalled, and how we can raise the bar for product management leadership in 2025 and beyond.
I build AI products with a simple conviction: disciplined experimentation beats intuition. Over the years, I’ve refined a practical playbook that helps my teams learn faster, reduce risk, and turn every release into a smarter next step.
Product experimentation isn’t luck; it’s a method. Learn how top AI product managers test, measure, and grow smarter with every release.
I begin every effort with a crisp hypothesis, an expected user or business outcome, and unambiguous success criteria tied to outcomes vs output OKRs. Before writing a line of code, I define primary metrics and guardrails so we know what “good” looks like—and what to stop.
When the change affects UX, pricing, or activation flows, I favor A/B testing with the statistical rigor to back decisions. We calculate the minimum detectable effect (MDE), choose appropriate randomization units, and pre-register the analysis plan to avoid p-hacking. This gives the team the confidence to scale wins and sunset underperformers quickly.
AI features demand a tailored approach, so I run eval-driven development before any user sees a variant. We curate golden datasets, score candidate prompts and models, and stress-test failure modes. This is where LLMs for product managers matters: prompt templates, context window management, and a retrieval-first pipeline are all evaluated for quality, latency, and cost-to-serve. I treat “hallucination rate,” safety violations, and bias as first-class metrics under AI risk management.
To de-risk launches, we ship behind feature flags with CI/CD, monitor DORA metrics, and roll out in stages. Product trios own problem framing to solution delivery, which shortens feedback loops and preserves accountability. If early signals drift from our hypotheses, we pause, adjust, and re-run—no sunk-cost thinking.
Measurement is non-negotiable. I instrument user journeys end-to-end with Amplitude analytics, track activation and retention analysis, and map behavior to learning objectives. We consolidate logs and events into a unified analytics platform so qualitative insights from customer research pair cleanly with quantitative trends.
Continuous discovery keeps the engine running. Weekly customer conversations, in-product feedback, and lightweight prototypes ensure we validate needs, not just solutions. The output flows into product discovery, product roadmapping and sprint planning, and a reusable AI product toolbox that scales across teams.
Finally, I protect the culture that makes experimentation work: we celebrate invalidated hypotheses, document decisions, and optimize for outcomes over output. That’s how empowered product teams sustain product-led growth—even as complexity grows.
If you’re building AI features today, adopt this playbook to maximize learning velocity, minimize risk, and compound advantage. The method is straightforward: form strong hypotheses, test with rigor, measure what matters, and let evidence—not HiPPOs—guide the roadmap.
Quantitative metrics tell the story in numbers; qualitative ones whisper why it matters. Both shape how products grow. Here’s what you need to know.
In my day-to-day, I rely on quantitative metrics to surface what’s changing in the business and where we need to focus. Activation rate, conversion through the onboarding funnel, feature adoption, retention analysis, and LTV/CAC give me a precise read on performance. I also keep an eye on DORA metrics to understand delivery health and deployment frequency, but I never mistake those for customer outcomes. Numbers spotlight signal—but they rarely explain causality on their own.
That’s where qualitative analysis earns its keep. Customer interviews, usability studies, win/loss debriefs, support transcripts, and community feedback give me the context behind the charts. Tools like Pendo help me layer in in-app guides and micro-surveys to capture intent and friction in the flow. This combination turns raw data into decisions that actually move the product strategy forward.
My operating cadence is simple: weekly dashboards to monitor quantitative metrics, ongoing continuous discovery to collect qualitative insight, and a monthly synthesis to reconcile both with our outcomes vs output OKRs. The aim is to move from opinions to evidence, and from anecdotes to patterns. When quant and qual agree, we execute confidently; when they diverge, we design the smallest experiment to learn fast.
I use a three-question decision tree to choose the method. First, are we exploring or validating? Exploration leans qualitative; validation leans quantitative. Second, do we have enough volume for statistical power? If yes, I’ll run A/B testing with a clear minimum detectable effect (MDE) to avoid false positives. If not, I’ll rely on targeted qualitative discovery until we can instrument a meaningful test. Third, will this decision meaningfully impact our product-led growth or user activation goals? If it will, we invest in both measurement and discovery to reduce decision risk.
Here’s a concrete example. We once saw a sudden drop in user activation. The quantitative dashboard flagged a step-function change at onboarding step three, but it couldn’t explain why. A quick round of qualitative interviews revealed that our tooltip design buried a critical permission request. We shipped a Pendo-powered in-app guide variant and ran an A/B test to validate the fix. Activation rebounded within a week, and 30-day retention followed suit.
There are common pitfalls I actively avoid. Chasing vanity metrics that don’t ladder up to outcomes. Conflating shipping speed with customer value by over-indexing on DORA metrics. Overfitting with A/B testing when the MDE is unrealistic for our traffic. And on the qualitative side, mistaking a compelling anecdote for a representative sample without triangulating evidence.
If you’re looking to tighten your practice, start with a lightweight playbook: instrument core events in Amplitude analytics; define a small set of outcomes vs output OKRs; schedule recurring customer conversations as part of continuous discovery; tag qualitative insights so patterns surface over time; and pair every material UX change with either a well-powered experiment or a clear qualitative learning goal. This creates a unified analytics and discovery loop that compounds.
Ultimately, quantitative metrics help me prioritize with clarity, while qualitative analysis helps me decide with confidence. When you weave them together, you not only ship faster—you ship the right thing, for the right reason, at the right time.
I rely on product benchmarks to align teams, sharpen strategy, and accelerate outcomes—especially in healthcare, where stakes are high and complexity is real. Over the years, I’ve learned that the right metrics create clarity across product, engineering, compliance, and go-to-market, enabling faster, safer decisions that translate into measurable impact.
Discover exclusive data and strategies from our Product Benchmark Report. Compare the healthcare technology industry’s performance across key product metrics.
When I evaluate a healthcare product’s health, I focus on a few essentials: activation rate and time-to-value for new users, weekly active usage and feature adoption for clinicians and admins, and cohort-based retention analysis to understand whether value compounds over time. I also look at funnel friction (onboarding drop-off, failed setup steps), support load per account, and reliability signals that influence trust—because in healthcare, trust fuels growth.
Benchmarks turn those metrics into context. They help me answer, “Are we good, or just lucky?” By comparing our numbers to industry peers, I can prioritize the few bets that matter, set outcomes vs output OKRs, and guide empowered product teams to focus on the highest-leverage improvements.
Operationally, I instrument products with a unified analytics platform and tools like Amplitude analytics and Pendo to track user activation, feature adoption, and in-product journeys. Pairing that with continuous discovery keeps insights fresh, while A/B testing and clear minimum detectable effect (MDE) thresholds ensure we ship with statistical confidence.
In practice, my playbook for healthcare product-led growth is straightforward: simplify onboarding with targeted product tours and in-app guides, tighten the first-win loop to reduce time-to-value, and eliminate blockers surfaced by behavioral analytics. Then, reinforce the loop with lifecycle messaging, role-specific education, and clear value propositions for clinicians, operations teams, and executives.
Of course, none of this works without strong governance. Data governance and regulatory compliance aren’t just guardrails; they’re growth enablers. Clear audit trails, privacy-by-design, and reliable incident management build the trust that keeps adoption high and churn low.
If you’re ready to benchmark your roadmap against the market, this report gives you the clarity to spot gaps, the language to align stakeholders, and the metrics to execute with precision. Use it to calibrate your product strategy, guide your next set of experiments, and confidently scale what works across the healthcare technology ecosystem.
Inspired by this post on Amplitude – Perspectives.
Every day, my team and I practice a simple but powerful idea: build with the same data-driven rigor we expect our customers to use. That’s why we run "Amplitude on Amplitude"—using the platform to continuously discover opportunities, validate bets, and ship experiences that matter.
Learn how Amplitude uses its own platform to build experiences customers love. We use Amplitude to understand our customers, test ideas, act on insights, and drive growth.
In practice, this means treating Amplitude analytics as our unified analytics platform for the entire product lifecycle. We instrument key events, build behavioral cohorts, and tie those insights back to product strategy so our product discovery work focuses on the highest-impact problems. This continuous discovery loop keeps us close to real user behavior instead of assumptions.
When we have a hypothesis, we pressure-test it with A/B testing. Before we launch, we size the minimum detectable effect (MDE), align on success metrics, and ensure we’re powered to make a decision. Experiments aren’t just about lift—they’re about learning with speed and confidence so we can iterate without second-guessing.
Insights only create value when they drive action. We translate findings into in-app guides and product tours to nudge the next best action and accelerate user activation. Then we follow through with retention analysis to understand which features create durable engagement and where friction persists. This closed-loop approach helps us turn insight into designed outcomes.
The result is a product-led growth engine that compounds. By grounding our roadmap in evidence, we reduce risk, move faster, and deliver experiences customers love. More importantly, we create a shared language across product, design, engineering, and go-to-market teams so decisions are transparent, measurable, and aligned to customer value.
If you’re aiming to raise the bar on product management rigor, the "Amplitude on Amplitude" approach is a repeatable system: unify your data, run disciplined experiments, operationalize insights in-product, and measure long-term impact on activation and retention. That’s how we build with clarity—and win with our customers.
Inspired by this post on Amplitude – Best Practices.
