Category: Product Management

Build a Fearless Culture of Experimentation: How I Turn Tests into Teamwide Habits

I’ve learned the hard way that experiments stall when they’re treated like items to check off a backlog. Real impact shows up when experimentation becomes the way we think, plan, and decide—every day, across the entire product organization.

Successful experimentation isn't just about adopting new tools or running more tests. It’s about changing company culture.

At HighLevel, I anchor experimentation in outcomes, not output. We form product trios and empower product teams to own the problem, link work to outcomes vs output OKRs, and commit to fast learning loops. This isn’t about more activity; it’s about better decisions, tighter focus, and measurable customer value.

Our teams write crisp hypotheses, define decision rules up front, and set a minimum detectable effect (MDE) before any A/B testing begins. That small discipline prevents “result fishing,” speeds up decisions, and aligns everyone on what will constitute a real signal versus noise.

Tooling helps, but only when it serves the culture. We instrument experiences end-to-end, lean on Amplitude analytics within a unified analytics platform, and run retention analysis alongside acquisition metrics so we don’t celebrate shallow wins. The goal isn’t dashboards; it’s actionable insight that improves product-market fit lessons and informs the next iteration.

Rituals make the culture durable. We review experiments weekly, tie learnings back to OKRs during QBRs, and celebrate invalidated hypotheses as progress. That psychological safety turns “being wrong” into momentum, reinforcing product management leadership behaviors we want to scale.

We also invest in decision hygiene: clear problem statements, pre-registered success criteria, and simple templates that make it easy to do the right thing quickly. Over time, this reduces debate theater and increases the surface area for discovery—more time with customers, more signals, and more conviction in our bets.

If you’re starting from scratch, begin small: pick one critical journey, articulate a hypothesis, choose a primary metric and MDE, run a lean A/B test, decide ahead of time how you’ll act on outcomes, and close the loop publicly. Repeat that cadence until it becomes muscle memory. That’s how experiments stop being one-off projects and start compounding into product-led growth.

When experimentation is a culture, not a task, teams move faster, leaders make clearer tradeoffs, and customers feel the difference. That is the habit I continue to build—one hypothesis, one decision rule, and one learning loop at a time.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Build vs. Buy in Experimentation: Why Embracing Vendors Accelerates Real Innovation

For much of my career, I reflexively favored building experimentation tooling in-house. Over the last few years, I’ve changed my mind. The ecosystem has matured, the bar for statistical rigor has risen, and the opportunity cost of reinventing the wheel has become too high to ignore. Read why the industry has changed to more broadly embrace vendor solutions—and why that's a good thing for innovation.

The short version: buying core experimentation capabilities increasingly lets us learn faster, reduce risk, and focus scarce engineering cycles on true differentiation. I still believe in building when it creates competitive advantage, but I’ve seen too many teams burn time on “table stakes” infrastructure instead of delivering outcomes that matter.

When I evaluate build vs. buy, I start with two questions: Is this capability a point of parity or a source of competitive differentiation? And what is the real total cost of ownership over three years, including staffing, maintenance, on-call, compliance, roadmap drag, and delayed time-to-learning? Most experimentation platforms are now points of parity; the differentiation is how quickly and responsibly we learn, not whose statistics package we forked.

Modern experimentation isn’t just a split URL test. It demands identity resolution across devices, reliable bucketing, exposure logging at scale, edge delivery for flags, guardrail metrics, and rigorous methods like minimum detectable effect (MDE), CUPED, and sequential testing. Add privacy requirements, data governance, and auditability, and the platform burden grows beyond a “quick internal tool.” This is exactly where vendors have pulled ahead, baking in best practices we’d otherwise relearn the hard way.

There are still good reasons to build. If you operate under unique latency constraints (e.g., sub-20ms decisions at the edge), have non-negotiable regulatory boundaries, or your experimentation model is deeply coupled to proprietary ML systems, bespoke tooling can be justified. I’ve supported builds in those cases—but only with a clear plan for long-term ownership, documentation, and explicit trade-offs.

More often, buying is the sane default. Vendor solutions give us hardened SDKs, consistent flagging, proven stats engines, and integrations with analytics—freeing teams to spend their energy on high-quality hypotheses and better product discovery. Connecting experiment outcomes to a unified analytics platform (and tools like Amplitude analytics) helps us align on source-of-truth metrics, tighten feedback loops, and empower product trios to make confident, outcome-driven decisions.

A hybrid approach frequently wins: buy the platform core, then extend it. Build custom decisioning services where needed, enrich telemetry, and add domain-specific metrics on top. I’ve had success pairing vendor platforms with forward deployed engineers and thoughtful developer evangelism to create the best of both worlds—speed from the vendor, nuance from our domain.

If you’re considering a shift, here’s the adoption playbook I use: – Define success upfront: decision latency targets, MDE guidance, guardrail metrics, governance needs, and privacy constraints. – Run a time-boxed pilot with an A/A test and a handful of A/B testing use cases. Validate exposure logging, bucketing stability, and metric parity against your analytics stack. – Align on outcomes vs output OKRs, so “more experiments” is never the goal; better decisions are. – Establish data governance and metric definitions before full rollout. Treat metrics as a product, not a spreadsheet. – Invest in enablement: in-app guides, product tours, and training for PMs, engineers, and analysts. Proactive stakeholder management is what separates a successful rollout from shelfware.

AI is accelerating this shift. Gen AI for product prototyping and agentic AI assistants can help generate hypotheses, auto-suggest experiment designs, and flag risky rollouts in real time. Pairing AI with a robust experimentation backbone improves both velocity and quality—without asking teams to become statisticians overnight.

My bottom line: the industry’s embrace of vendor experimentation platforms is not a retreat from craftsmanship—it’s a strategic allocation of talent. By buying where the market is excellent and building where our differentiation truly lives, we learn faster, reduce risk, and compound innovation. If you haven’t revisited your build vs. buy calculus recently, now is the time. Your customers don’t reward you for owning a stats engine; they reward you for shipping better outcomes, sooner.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Stop Trusting Static A/B Test Calculators: Why You Need Dynamic MDE Curves Over Time

After years of running experiments at scale, I’ve learned that the quickest way to stall product momentum is to rely on static A/B test calculators that promise certainty from a single sample size number. Real-world data rarely behaves like those calculators assume, and that gap quietly erodes decision quality, speed, and stakeholder trust.

Read about the issues with current A/B test calculators and why experimenters need to see a range of MDEs over time, not a static sample size

Most calculators hard-code fragile assumptions: a constant baseline conversion rate, balanced traffic allocation, independent and identically distributed sessions, no seasonality, no peeking, no novelty effects, and a fixed-horizon stop. They often use normal approximations that break at low counts and ignore the realities of traffic ramping, SRM (sample ratio mismatch), and mid-test product updates. The result is a deceptively precise sample size that fits the math, not the environment.

In practice, product teams peek, traffic fluctuates by day of week, acquisition mixes shift, and funnel variance changes as users move from click to activation to retention. These conditions make “the” required sample size a moving target, not a constant. Treating a static figure as a guarantee leads to underpowered tests, false confidence, and rushed stops that inflate false positives.

The alternative is to manage Minimum Detectable Effect dynamically. Instead of anchoring on a single number, I plan with a range of MDEs over time—power curves that show what lift we can reliably detect after 3, 7, 14, and 28 days as traffic accrues. This reframes the question from “How big should my sample be?” to “What effect sizes can we detect at each decision point given our forecasted traffic and variance?”

At HighLevel, this approach changed our experimentation culture. For example, an onboarding flow test initially “required” three weeks according to a static calculator. Our MDE-over-time view showed we could detect a meaningful 4–6% lift within a week under expected weekday traffic, but only 8–10% on weekends due to volatility. We set a sequential schedule for interim checks, aligned stakeholders on stopping rules, and made a confident call in nine days—saving a sprint and avoiding a premature rollback.

Implementing dynamic MDEs is straightforward: forecast traffic by day, estimate variance from historical data, and simulate power curves across relevant effect sizes. Layer in sequential testing or Bayesian monitoring to avoid p-hacking, include guardrail metrics (e.g., latency, error rates, SRM), and publish an MDE band that updates as data arrives. This transforms your “calculator” into a living decision tool rather than a one-time estimate.

For teams using a unified analytics platform or tools like Amplitude analytics, it’s simple to automate: generate daily MDE curves, annotate ramp changes and seasonality, and expose a dashboard that tracks detectable lift as a function of time and traffic. Pair this with pre-registered stopping rules and a simple communication routine so stakeholders know exactly when and why you’ll decide.

Beyond top-of-funnel conversion, this mindset is critical for retention analysis and revenue outcomes where effects materialize over weeks or months. Plan MDE bands per horizon—early activation, Day-7 retention, and longer-term LTV—so product discovery and product-led growth bets aren’t prematurely judged on the wrong timeline.

The takeaway is simple: retire the illusion of a one-number sample size. Embrace dynamic MDE curves that reflect how your data actually behaves, make faster and more confident calls, and keep empowered product teams focused on outcomes over outputs. Your experiments—and your roadmap—will move with more speed, less drama, and far better signal.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Inside Japan’s AI Marketing Shift: How 500 Teams Boost Efficiency, Results, and Careers

I just finished reviewing new findings on Japan’s marketing landscape, and the signal is clear: AI isn’t just a shiny tool—it’s a force multiplier for outcomes and careers. The headline that caught my attention, "Amplitude Releases New Research in Japan: Marketers are Unlocking Efficiency, Results, and Career Growth," aligns with what I’m seeing on the ground: teams that blend disciplined analytics with pragmatic AI adoption are pulling ahead.

Amplitude released a new survey of 500 Japanese marketers, which reveals how teams are benefiting from AI. Get the insights from the data

Here’s how I interpret the shift. AI accelerates the cycle from insight to action when it’s grounded in a unified analytics platform. With Amplitude analytics stitched into campaign and product signals, marketers can move beyond vanity metrics to diagnose true drivers of activation, engagement, and retention. That’s where efficiency compounds: fewer blind spots, faster iteration, and clearer attribution of what actually drives results.

On the strategy side, I’m seeing two dominant patterns. First, gen ai is speeding up creative workflows—audience research, message testing, and content generation—without sacrificing brand rigor. Second, agentic AI is emerging in operational loops: routing leads, prioritizing segments, and suggesting next-best actions based on behavioral data. The common denominator is data governance; without clean event schemas and consent-aware pipelines, AI amplifies noise instead of signal.

For product-led growth motions, this research validates what empowered product teams have practiced for years: instrument the customer journey, frame outcomes vs output OKRs, and experiment in short, learnable cycles. When marketing, product, and data join forces as true product trios, teams can run in-app guides and product tours, tune onboarding, and perform rigorous retention analysis that ties growth to product value rather than spend.

My playbook in this environment is simple but disciplined. Start with first principles decision making: define the problem, the decision, and the evidence required. Use a unified analytics platform to connect lifecycle events across acquisition, activation, and expansion. Align go-to-market strategy with product roadmapping and sprint planning, so insights move directly into experiments—not slide decks. Then close the loop with clear outcome metrics and QBRs that reward learning velocity, not activity volume.

There’s also a career arc embedded in this shift. Marketers who cultivate analytical fluency and AI literacy are becoming indispensable partners to product management leadership. They can articulate a differentiated value proposition, shape product positioning with live behavioral data, and influence board-level narratives with credible, causal evidence. That combination—story plus signal—unlocks both performance and professional growth.

My commitment going forward is to operationalize these lessons: tighter event taxonomy, sharper outcomes framing, and more systematic experimentation across channels and in-product touchpoints. With the right data foundation and a pragmatic AI strategy, we can convert curiosity into capability—and capability into repeatable growth.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
How Luminance Builds Legal-Grade™ AI at Scale: My Product Lens on Trust and GTM

I’m fascinated by how the most credible legal-tech platforms operationalize AI in the enterprise, where risk tolerance is near zero and trust is the product. When I evaluate solutions in this space, I look for rigor in model design, governance, and go-to-market execution—not just raw model performance.

Discover how Luminance CEO Eleanor Lightbody builds Legal-Grade™ AI for enterprise. See how their specialized, agentic AI models lawyers trust at scale.

That framing resonates with me. “Legal-Grade™” isn’t a slogan; it’s a product requirement that implies auditable decisions, explainable outputs, robust data governance, and demonstrable accuracy under real-world legal workflows. “Agentic AI” adds another layer: autonomous orchestration of tasks with explicit guardrails, role definitions, and escalation paths to humans-in-the-loop.

From a product management perspective, I start with outcomes. For legal teams, the jobs-to-be-done are concrete: contract analysis and redlining, due diligence, compliance reviews, investigations, and eDiscovery. The success criteria are equally concrete: precision and recall on domain-specific clauses, latency under load, traceability of sources, and the ability to scale across matter types, jurisdictions, and languages without degrading trust.

Building that foundation requires deliberate AI strategy. I look for domain-specialized models, retrieval-augmented generation tuned to legal corpora, evaluation harnesses with gold-standard datasets, and continuous red-teaming. Just as important are deployment choices—on-prem or VPC isolation, encryption in transit and at rest, strict PII handling, and granular access controls—to satisfy the security posture of enterprise legal and compliance teams.

Governance is where “legal-grade” is won or lost. Robust audit trails, versioned prompts and policies, model cards, clear data lineage, and event logs that support defensibility are table stakes. Human review workflows, explainability tooling, and remediation paths ensure the system remains trustworthy when edge cases arise.

On product process, I favor empowered product teams and forward-deployed engineers partnering directly with attorneys and legal ops. Co-designing workflows with subject-matter experts surfaces the right constraints early: how redlines are presented, what confidence thresholds trigger review, and where to anchor the user experience in familiar legal tools and document structures.

Competitive differentiation and product positioning hinge on clarity: what specific legal outcomes are delivered faster, safer, or more accurately than alternatives? I prioritize transparent benchmarking against baselines, proof-of-value pilots that mirror production data conditions, and pricing that aligns to measurable outcomes (e.g., time-to-first-draft, review throughput, or risk reduction) rather than abstract usage metrics.

Go-to-market strategy in enterprise legal is a discipline in itself. Expect rigorous InfoSec reviews, stakeholder alignment across legal, IT, and procurement, and the need for customer references that demonstrate “trust at scale.” Clear messaging around value proposition, safety posture, and operational readiness shortens cycles and builds confidence among risk-averse buyers.

The big takeaway for product leaders: Legal-Grade™ AI isn’t about novel models; it’s about orchestrating specialization, safeguards, and enterprise-grade delivery into a coherent system that lawyers can rely on daily. When agentic AI is harnessed with the right guardrails and domain depth, it becomes a force multiplier for legal teams—accelerating work without compromising standards.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
AI Raised the Bar on Experimentation: How I Drive Product Growth with Relentless Tests

The AI era didn’t just speed up product development—it rewired the economics of learning. Experiments that once took weeks now take hours, and the organizations that compound learning faster are the ones outpacing competitors. In my role guiding product strategy, I’ve seen this shift firsthand: velocity is table stakes; evidence is the differentiator.

Learn why market dynamics prove that experimentation is fundamental to driving growth in the age of AI.

When AI compresses build and distribution cycles, market feedback arrives in torrents. That abundance of feedback is valuable only if we can transform it into trusted insight. I anchor every initiative with a clear hypothesis, a measurable outcome, and a pre-committed decision rule—what we’ll do if the result is positive, negative, or inconclusive. This discipline converts experimentation from a set of ad hoc activities into a repeatable growth engine.

Data quality is non-negotiable. I rely on a unified analytics platform, pairing event instrumentation with Amplitude analytics to analyze activation, retention, and long-term impact. Strong data governance prevents metric drift and ensures that our “go/no-go” calls rest on sound evidence. Retention analysis, in particular, is my north star for separating novelty spikes from durable value.

Gen AI has transformed how quickly we can explore solution space. I use gen ai for product prototyping to generate multiple UX and copy variants in minutes, then deploy in-app guides and lightweight product tours to validate which concepts resonate. This dramatically lowers the cost of curiosity: we test more, earlier, with tighter feedback loops—without compromising user experience or brand voice.

Process and culture make this sustainable. Empowered product teams—tight product trios across Product, Design, and Engineering—run weekly sprints with explicit outcomes vs output OKRs. We plan small, falsifiable bets in product roadmapping and sprint planning, stack-ranked by expected impact and learning value. The result is a team that ships with confidence, measures with rigor, and iterates without ego.

Experimentation doesn’t stop at UX. I extend the same approach to go-to-market strategy and product-led growth motions: pricing page changes, onboarding flows, paywall copy, and packaging tests all roll through the same hypothesis-measure-decide loop. We bias toward reversible decisions, emphasize speed to signal, and codify what we learn into playbooks the whole organization can reuse.

Raising the bar on experimentation means raising the bar on clarity. Every test should answer a specific question, earn its way onto the roadmap, and connect to a value proposition we can defend. In a world where AI collapses time, the advantage goes to teams that compound learning with integrity and purpose. Start small, instrument well, close the loop—and let the data guide the next bold move.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
9 Proven Collaboration Practices to Unite Teams and Deliver Exceptional Digital Experiences

Every standout digital experience I’ve shipped has one thing in common: deep, consistent collaboration across product, marketing, and data. When we align on outcomes and operate from a shared truth, we move faster, reduce rework, and create value our customers actually feel.

Discover best practices to fuel cross-functional collaboration and help product, marketing, and data teams create better digital experiences.

Over the years, I’ve refined nine practices that reliably elevate team performance and customer outcomes. They’re simple to state, practical to implement, and powerful when they compound together in day-to-day execution.

1) Align on outcomes, not output. I start every initiative by clarifying the customer problem, success metrics, and “outcomes vs output OKRs.” When everyone can name the desired behavior change and the KPIs that prove it, teams earn the autonomy to solve creatively—and the discipline to say no when work doesn’t move the needle.

2) Establish a shared source of truth. A unified analytics platform gives product, marketing, and data teams the same lens on activation, engagement, conversion, and retention. I insist on event hygiene, operational definitions, and self-serve dashboards so decisions are informed by facts, not folklore—especially when running retention analysis or growth experiments.

3) Form empowered product trios. I routinely pair a product manager, a designer, and a tech lead as a decision-making nucleus. This “product trios” model accelerates discovery, balances desirability/feasibility/viability, and prevents handoff theater. Extended partners (marketing, data science, support) join early to shape solutions, not just rubber-stamp them.

4) Codify decision-making rituals. Speed comes from clarity. We document DRIs, timebox debates, and use first-principles reasoning to cut through ambiguity. Lightweight decision records (why we chose X over Y) keep context intact for future contributors and reduce unproductive re-litigation.

5) Co-create the roadmap—and keep it alive. I bring stakeholders into roadmap and sprint planning to surface dependencies, risks, and opportunities upfront. We review priorities regularly, tie bets to strategy, and maintain traceability from objectives to epics to experiments. This is stakeholder management in service of focus, not bureaucracy.

6) Make insights travel. We weave discovery into delivery: problem interviews, concept tests, instrumented prototypes, and in-product feedback loops. Marketing shapes messaging early; product refines UX writing; data validates signals. The result is tighter problem-solution fit and fewer surprises late in the game.

7) Communicate early, often, and in plain language. I favor one-page briefs, narrative memos, and short demo videos over sprawling docs. Clear artifacts make collaboration inclusive, reduce meeting load, and help new collaborators ramp quickly without losing nuance.

8) Shorten the feedback loop in production. We rely on feature flags, small batch releases, and in-app guides or product tours to educate users and capture behavioral data. This supports product-led growth by turning every release into a learn-and-iterate cycle tied to the metrics that matter.

9) Default to transparency and respect. Shared channels, open calendars, and visible roadmaps build trust. When disagreements arise, we return to customer outcomes and the evidence. Healthy friction pushes the work forward; psychological safety keeps the team together.

None of these practices are exotic. The magic is in the consistency: aligning on outcomes, measuring what matters, and giving talented people clear guardrails and room to run. When we work this way, collaboration becomes a force multiplier—and customers feel the difference in every click and interaction.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Vibe Check Playbook: Harness GenAI for Marketing Without Killing Your Brand’s Vibe

Vibe is more than a brand voice—it’s the emotional resonance customers feel at every touchpoint, from onboarding to support. As I’ve scaled products and go-to-market motions, I’ve learned that preserving that resonance while introducing AI is both a strategic advantage and a delicate balancing act. In this three-part series, I’m sharing the approach I use to unlock AI-powered velocity without sacrificing authenticity or trust.

Learn how to get the benefits of AI-powered vibe marketing without accidentally killing the vibe for your customers in part 1 of our 3-part series.

When I say “vibe marketing,” I’m talking about the consistent, context-aware expression of your brand’s personality across channels—delivered with precision and warmth. GenAI can amplify that consistency at scale, but without the right safeguards, it risks drifting into uncanny, off-brand territory. In Part 1, I’ll center on strategy and governance—how we set up the foundation so the vibe feels intentionally human, even when AI assists the work.

Start with clarity: document your brand’s voice, tone, and emotional targets. I create a living voice and tone guide with examples of “do” and “don’t” language, aligned to specific customer moments like activation, upgrade prompts, renewal nudges, and recovery from a failed workflow. This artifact becomes the north star for prompts, training snippets, and review criteria—so AI doesn’t invent a persona you never approved.

Next, map the end-to-end journey and choose high-leverage use cases where AI can enhance relevance without increasing risk. My favorite entry points are in-app guides, lifecycle emails, contextual tooltips, and product tours—places where we can A/B test safely, measure impact on activation and retention, and iterate quickly. Keep the highest-judgment moments—pricing, security, compliance, and incident communications—squarely human-led, with AI supporting drafts and analysis, not final decisions.

Guardrails are non-negotiable. I establish prompt patterns that include brand attributes, audience, channel, goal, and constraints (length, reading level, regional spelling, accessibility). We also implement a human-in-the-loop review for net-new narratives, plus automatic checks for tone drift, sensitive topics, and jargon density. When governance is clear, teams move faster with more confidence—and customers feel the cohesion.

Measurement keeps the vibe honest. I track leading indicators like message clarity scores, reading time, and click-through alongside business outcomes such as activation rate, conversion to aha moment, support deflection, and retention analysis. Segment results by persona and lifecycle stage to catch subtle mismatches—what delights power users can overwhelm first-time builders.

Pragmatically, I use GenAI for rapid prototyping of variations. We generate multiple voice styles aligned to the guide, then test them in controlled experiments. The winner becomes the new baseline, and we codify it back into our prompt library. That tight loop—prototype, test, codify—prevents ad-hoc drift and compounds learning across product, marketing, and customer success.

Finally, empower product trios to own the vibe where it matters most: inside the product. Your PM, design, and engineering leaders should collaborate on UX writing and microcopy patterns, ensuring that AI-generated suggestions harmonize with product positioning and value proposition. This is how vibe marketing transcends campaigns and becomes a product-led growth advantage.

In Part 2, I’ll share playbooks and prompt templates for high-impact channels, including onboarding sequences, upgrade nudges, and contextual in-app experiences. In Part 3, I’ll cover instrumentation and analytics patterns so you can operationalize learning across teams.

For now, here’s the checklist I use to avoid “killing the vibe”: a codified voice and tone guide, journey-mapped use cases with risk tiers, prompt patterns with constraints, human-in-the-loop review, automated tone and compliance checks, and outcome-oriented experiments measured against activation and retention. With that foundation, AI stops being a gimmick and starts being a force multiplier for authenticity and growth.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Inside the AI Tornado: How I Deliver Fast and Secure—Lessons from Vercel’s Aparna Sinha

I’ve spent the past few years building in what often feels like an AI tornado—intense velocity, shifting requirements, and unforgiving expectations for security and quality. When I think about how to turn that chaos into momentum, I’m reminded of a guiding prompt: "Learn how Aparna Sinha, SVP of Vercel, builds in the AI tornado quickly and securely. Aparna shares her practical advice for builders everywhere." That mandate resonates with how I lead product teams to move decisively while protecting our customers and our brand.

In practice, building quickly and securely starts with clarity. I anchor the team on a crisp value proposition, define outcomes over output, and align product discovery with a tight feedback loop. We plan with product roadmapping and sprint planning that front-loads risk: data governance, threat modeling, and privacy-by-design are non-negotiable guardrails. This lets us unlock developer velocity without compromising trust—precisely the balance elite product management leadership aims to achieve.

On the execution side, I use lightweight gen ai experiments to accelerate insight and reduce uncertainty. For gen ai for product prototyping, we spin up narrow, testable slices that validate feasibility, usability, and safety in parallel. Two-week iteration cycles, clear exit criteria, and a secure-by-default posture keep us honest. We instrument a unified analytics view to measure real outcomes, then double down where signal is strongest and deprecate what doesn’t move the needle.

Team topology matters just as much as process. I empower product trios to own customer value end-to-end, pair forward deployed engineers with design and PM for rapid discovery, and practice developer evangelism to amplify adoption patterns early. This creates the foundation for product-led growth: a self-reinforcing loop where users teach us what to build next, and we respond with precision. Strong stakeholder management keeps go-to-market aligned so we can scale learnings into repeatable wins.

Security is everyone’s job, not a final checklist. We embed data governance and compliance considerations from day one—so speed becomes sustainable, not reckless. The outcome is a product culture that moves fast with conviction: disciplined experimentation, clear decision frameworks, and a shared commitment to quality.

If you’re building in the AI tornado, focus on three levers: sharpen outcomes (what matters), reduce uncertainty (prove it fast), and codify trust (bake in safety). Do this consistently, and your team will ship faster with fewer reversals—while compounding credibility with customers and the market.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025
Crack User Drop‑Off Fast: My Step‑by‑Step Amplitude Playbook for High‑Impact Growth

When I see a drop‑off curve flattening our growth, I don’t panic—I get curious. Drop‑off is a signal, not a failure, and with the right workflow it becomes one of the fastest paths to unlocking activation, retention, and product‑led growth.

Understanding user behavior is the foundation of every great product. Here’s how to start doing that with Amplitude.

I start by defining the journey that matters most: the path from first touch to first value. That means choosing a clear activation milestone, articulating the “aha” moment, and writing down the specific questions I need Amplitude to answer—where users hesitate, which segments suffer most, and what behaviors correlate with long‑term success.

Before analysis, I ensure the instrumentation is trustworthy in Amplitude analytics. I align on an event taxonomy, enforce data governance and naming conventions, and attach the right properties (channel, plan, device, role). Clean, consistent data is non‑negotiable—without it, you’re optimizing noise.

Next, I build a simple funnel in Amplitude: sign‑up → verification → setup → first key action. I compare conversion and drop‑off by acquisition channel, device, geo, plan, and cohort. This immediately reveals friction points and clarifies whether the problem is message‑market fit, onboarding, or feature discoverability.

To go beyond the first click, I pair funnels with retention analysis and pathing. I review day‑1/7/30 retention, unbounded retention, and lifecycle stages, then cohort users who hit the “aha” versus those who don’t. The contrast tells me which behaviors predict durability and where a timely nudge can change the trajectory.

Insights only matter if they drive action. I translate each friction point into a targeted onboarding improvement: in‑app guides to nudge setup, product tours that surface the core value proposition, and thoughtful tooltip design at moments of uncertainty. For product‑led growth, I prioritize small, testable changes over wholesale redesigns.

Execution is a team sport. Product trios work with forward deployed engineers and customer support to ship experiments quickly. We schedule them in product roadmapping and sprint planning, and measure impact with shared dashboards in our unified analytics platform. That alignment empowers product teams to move fast without guessing.

If you only have an hour, here’s my quick start: connect your data, define 4–6 events that describe the activation path, build a funnel from sign‑up to first value, segment by new versus returning users, and pick one high‑impact experiment to run this week. Close the loop with lightweight product discovery interviews to validate the why behind the numbers.

Drop‑off isn’t a verdict—it’s a map. Use Amplitude to trace where users hesitate, meet them with timely guidance, and iterate until the journey feels effortless.

Inspired by this post on Amplitude – Best Practices.

October 24, 2025
How I Craft Product Surveys Users Love: Proven Tactics for Actionable, High-Quality Feedback

When I need fast, trustworthy insight into what to build next, I turn to product surveys. Done well, they feel respectful, take minutes, and deliver signal we can ship against. Done poorly, they frustrate users and mislead product teams. Over the years, I’ve refined a simple, repeatable approach that consistently yields high response rates and actionable insights across product discovery, onboarding, and product-led growth motions.

Create effective product surveys that capture actionable user feedback, improve features, and support smarter product decisions.

I always start with the decision I need to make. Am I validating a value proposition, prioritizing a feature, diagnosing friction in onboarding, or measuring retention risk? That clarity shapes everything—who I ask, when I ask, and how I phrase the questions. It also aligns the survey with outcomes, not outputs, so results directly inform product roadmapping and sprint planning instead of becoming a vanity report.

Question design is where UX writing discipline pays off. I keep surveys short (5–7 questions), bias-free, and written in the same voice we use in-app. I mix two or three crisp quant questions (e.g., confidence, usefulness, likelihood to continue) with one or two open-ended prompts to surface the “why.” That blend gives me both trend lines and the qualitative texture I need to make confident trade-offs with stakeholders.

Timing and targeting often matter more than question count. I trigger in-app micro-surveys at meaningful moments—right after a user finishes onboarding, explores a product tour, or engages with a newly released feature. For deeper discovery, I segment cohorts (new vs. power users, retained vs. churning) to avoid muddy averages. The right context earns higher completion rates and more honest feedback.

Trust drives participation. I set expectations upfront: how long it will take, why it matters, and how their feedback will shape the roadmap. I also share back the outcome—what we learned and what we shipped—so users see the loop closing. That simple follow-up builds goodwill and sustains response rates over time.

On analysis, I combine lightweight quant with rigorous qualitative synthesis. I chart response and completion rates, then use thematic coding on open text to spot repeating patterns. Where it helps, I apply gen AI to accelerate clustering and sentiment analysis, then validate the themes manually. Finally, I triangulate with product telemetry in Amplitude analytics to confirm that what users say matches what they do.

The most valuable step is translation: turning feedback into decisions. I map insights to clear problem statements, rank them by user impact and strategic fit, and convert them into opportunities on our roadmap. In planning, I pair these opportunities with success metrics tied to activation, adoption, or retention analysis, so we can measure whether changes actually move the needle.

Surveys aren’t a substitute for interviews, but they’re a powerful complement. They help me spot signals at scale, de-risk bets between cycles, and align cross-functional stakeholders around evidence rather than opinions. When surveys are concise, contextual, and connected to action, users feel heard—and teams ship smarter.

Inspired by this post on Amplitude – Best Practices.

October 24, 2025
Create Irresistible Product Tours Users Love: Boost Onboarding, Feature Adoption, and Satisfaction

I’ve learned that the fastest way to earn user trust is to guide people to value within minutes, not weeks. As a VP of Product Management, I treat product tours as a strategic asset for product-led growth—not a band-aid for unclear UX. When we get them right, new users reach that first “aha” moment quickly, power users discover deeper capability, and support tickets quietly decline.

Learn how to create effective product tours that improve onboarding, feature adoption, and the user experience without overwhelming users.

My starting point is simple: every tour must serve a single job-to-be-done. I resist the urge to teach everything. Instead, I define one outcome (for example, sending a first campaign or inviting a teammate) and design a clear, three-to-five step flow. Strong UX writing does most of the heavy lifting—short, actionable language, consistent labels with the UI, and thoughtful tooltip design that highlights only what’s essential.

I rely on a small toolkit of in-app guides that meet users where they are. A concise welcome modal sets expectations and reiterates the value proposition. A checklist breaks the outcome into bite-sized wins. Hotspots and tooltips provide contextual nudges at the exact moment of need. Empty states teach by doing, showing an example and prompting the next action. Together, these patterns turn guidance into momentum without piling on cognitive load.

Personalization is non-negotiable. I segment tours by role, plan, and intent signal. New admins shouldn’t see the same flow as experienced creators. I trigger guides contextually—after users click into a feature, not on login—and I let them skip, snooze, or revisit the tour from a help menu. Respecting autonomy builds trust and keeps engagement high.

Measurement guides every decision. Before launch, I define success metrics like activation rate, time-to-value, and feature adoption. I instrument funnels with Amplitude analytics to track completion, drop-off by step, and follow-on behaviors (did they invite a teammate or create a second project?). I pair this with retention analysis to see whether guided users come back and expand usage. Then I A/B test copy, step order, and trigger timing until the data—and user feedback—tell a consistent story.

Operationally, I put a product trio—PM, design, and engineering—in charge of the tour experiments and integrate them into product roadmapping and sprint planning. We maintain a style guide for in-app guides and UX writing, so the experience feels native and respectful of the brand. Governance matters: we audit what’s live each quarter to avoid guide sprawl and content conflicts as the product evolves.

There are a few traps I avoid. Long, linear tours that try to teach the entire product almost always underperform. Overlapping tooltips can frustrate power users. And no tour should be a substitute for fixing a confusing flow. When a guide consistently underperforms, I treat it as a product discovery signal to simplify the experience itself.

If you’re getting started, here’s a pragmatic plan I use: pick one high-impact flow tied to activation, define a crisp outcome, draft the microcopy, and build a lightweight in-app guide with a checklist and two or three tooltips. Ship to a small cohort, instrument with Amplitude analytics, and review results after a few days. Iterate fast, roll out broader once you see lift, and continue refining as the product and audience evolve.

Thoughtful product tours don’t just teach; they accelerate confidence. When users feel capable quickly, everything improves—adoption, satisfaction, and long-term growth.

Inspired by this post on Amplitude – Best Practices.

October 23, 2025