Category: Leadership

From Insights to Impact: Turning Amplitude Analytics into Product-Led Growth at Scale

I’ve seen time and again that when content is as data-driven as the product, adoption accelerates. Partnering closely with a data-driven content marketing manager and Amplitude power user, I watched how precise storytelling—grounded in Amplitude analytics—can unlock user activation and retention at scale.

Previously, she managed all customer identity content at Okta.

We started by translating product strategy into measurable moments in the customer journey: activation events, aha moments, and retention cohorts. Using Amplitude analytics, we built funnels and segmentations to isolate high-signal behaviors, ran A/B testing on messaging and in-app guides, and turned retention analysis into an editorial roadmap that spoke to specific use cases and jobs-to-be-done. This unified analytics platform approach ensured the content engine and product telemetry were speaking the same language.

From there, we aligned go-to-market strategy with lifecycle communication—product tours, onboarding sequences, and contextual education that made the value proposition unmistakable. Through continuous discovery and product discovery rituals with product trios, we iterated messaging to sharpen product positioning and reduce time-to-value. The result was content that didn’t just describe features—it moved outcomes.

To keep us honest, we instrumented outcomes vs output OKRs tied to activation rate, expansion intent, and long-term retention. We watched leading indicators (setup completion, power-user actions) roll up into lagging results (weekly active usage and cohort retention), and refined our bets in tight feedback loops.

If you’re building a product-led growth motion, pair your roadmap with a content leader who treats telemetry as a design material. When an Amplitude power user brings the same rigor to narrative that engineers bring to code, the compounding effect on adoption, engagement, and retention is unmistakable.

Inspired by this post on Amplitude – Perspectives.

December 11, 2025
Playing the 25-Year Game: Rethinking Networking, Ditching OKRs, and Owning the Full Stack

I’m drawn to builders who choose decades over exits. The story behind Meter—providing full-stack networking infrastructure as a service for businesses—captures that ethos with unusual clarity. From day one, the strategy hinged on vertical integration, business model innovation, and committing to a multi-decade horizon. As a product leader, I see this as the rare combination that compounds: patient R&D, an earned right to own the stack, and a commercial model aligned with customer outcomes.

Why think in 25-year horizons? In entrenched, often monopolistic markets like networking, short-term optimization simply doesn’t move the needle. Incumbents such as Cisco and Meraki shape expectations around procurement, installation, and support. If you want to reset the standard, you can’t iterate around the edges—you have to re-architect the experience end-to-end and give yourself the time to do it right. That’s the difference between building a product and building a company.

I also share the contrarian stance on planning. Rituals can easily masquerade as rigor. “We don’t do OKRs” doesn’t mean don’t align; it means don’t confuse activity with progress. I prefer crisp narratives, simple success metrics, and a cadence that keeps teams close to customers. Planning without over-planning lets you steer with first principles: what problem are we solving, for whom, and how do we know it’s working?

On that note, I relentlessly track unhappy customers. Satisfaction scores and dashboards are lagging indicators; the real signal is in the gaps, escalations, and stuck use cases. Building a habit of surfacing and resolving those moments creates the operational muscle you need later when you scale. It’s also how you find “seller-market fit” and sharpen your go-to-market motion.

The origin story matters. Meter spent four-plus years in heads-down R&D, even scrapping a year of OS work during the process. That discipline—killing good work to unlock great work—is the hallmark of teams that play the long game. Shenzhen accelerated progress by compressing feedback loops between design, manufacturing, and iteration, a reminder that sometimes geography itself is a strategy choice.

Getting to a sales-ready product requires intentional sequencing. Own the interfaces, the telemetry, the install experience, and the service envelope—not just the code. In networking, that means controlling the full stack so performance, reliability, and support converge into one promise. The surprising thing you should innovate isn’t only the feature set—it’s the business model. Turning networking into a service aligns incentives, reduces complexity for customers, and creates durable revenue with clear SLAs.

Avoiding the one-trick pony trap is also central. The best teams design for adjacent expansion from day one: new sites, new form factors, new service layers. The secret to finding an excellent market is to look where switching costs and frustration are both high; that’s where a superior end-to-end experience can pry open demand. That’s also why Meter didn’t sell via traditional channels—a direct motion builds intimacy with the customer problem, strengthens pricing power, and helps validate “seller-market fit.”

Resilience is the throughline: surviving COVID, Apple’s M1 transition, and “a thousand bad days.” In those stretches, pace and patience matter more than theatrics. I’ve learned to decouple management from authority, reduce meta-work, and tackle performance issues quickly—“when the person is the problem,” clarity and speed are an act of care for the whole team. There’s inherent value in going slowly when it preserves quality, trust, and optionality.

For founders and product leaders, the takeaway is simple: build a company you’ll want to run for as long as possible. Focus on first principles decision making, empower product teams, and choose the few metrics that truly reflect customer value. Resist the comfort of templates; adopt only the practices that raise your odds of learning faster than the market evolves. Owning the full stack, rethinking the model, and extending your time horizon can transform even the most entrenched categories.

This is how I aim to run product: fewer rituals, tighter feedback loops, and a relentless bias toward long-term compounding. When you commit to decades, you earn the right to define the category—one thoughtful release, one delighted customer, and one resolved escalation at a time.

December 10, 2025
Train Leaders First: How Product Leadership Unlocks Real Transformation and Discovery

I recently listened to Role of Leadership in Transformations – All Things Product Podcast with Teresa Torres & Petra Wille, and it crystallized a pattern I’ve seen across multiple transformations: teams often get trained in continuous discovery, but nothing changes because leadership habits stay the same. If you want to move from projects to true product thinking, “train your leaders first” isn’t a catchy mantra—it’s a prerequisite.

The episode digs into why discovery training can be stellar while adoption still stalls. I’ve witnessed this firsthand: teams return excited to interview customers and test ideas, but leaders continue to manage via features, roadmaps, and approvals. The result is predictable—discovery fades. When leaders evolve how they evaluate work, talk about outcomes, and shape rituals, discovery sticks. Without that shift, even energized, empowered product teams drift back to output.

What resonated most was how organizational dynamics kick in the moment teams start bringing real customer evidence to the table. Discovery uncovers conflicts. Sales, account management, stakeholders, and executives all feel the impact when the old “my job is to tell teams what to build” mindset collides with evidence-driven practices. Hierarchy also clashes with modern product practices—because in discovery, “all ideas come equal.” Product culture isn’t an accident; it must be intentionally created through norms, expectations, and systems that prioritize outcomes over output.

I’ve also seen the leadership skills gap up close. Many product leaders never learned continuous discovery themselves, so they aren’t equipped to coach it, critique it, or celebrate it. This is where great product management leadership shows up: the ability to assess discovery quality, reinforce outcomes vs output OKRs, and run cadences that create momentum. Leaders who invest in building these muscles—often through communities of practice and structured coaching—transform the operating environment for product trios and cross-functional teams.

The episode’s discussion of pilot teams is spot-on. Start small to surface hidden blockers—the corporate “immune system”—before going broad. Pilots expose decision bottlenecks, misaligned incentives, and policy friction that standard training never reveals. Tools like the Product Leadership Wheel help set clearer expectations for the craft of product leadership, while a coherent Product Operating Model makes the path from pilots to full transformation explicit and durable. I’m particularly excited about resources like the Discovery Habits Toolbox because they give leaders practical ways to coach continuous discovery without reverting to feature policing.

Here are the big takeaways I’m carrying forward. Skills training isn’t enough—if leaders still manage through feature requests and static roadmaps, teams will abandon discovery even if they loved the training. Leaders need training too—they must know how to evaluate discovery work, talk about outcomes, and create rituals that reinforce new habits. Discovery will surface conflicts—plan for stakeholder management, alignment with sales and account teams, and executive sponsorship. Product leadership is a craft—seniority alone doesn’t create clarity, systems, or culture. And transformations should start with leaders and pilot teams—because that’s where the real blockers live.

If you want to go deeper, listen to this episode on Spotify: https://open.spotify.com/episode/5cBTEbYX1YW3BF6icAPXzi or Apple Podcasts: https://podcasts.apple.com/kh/podcast/role-of-leadership-in-transformations/id1794203808?i=1000740342572. It’s a concise masterclass on why leadership behaviors—not just team skills—determine whether continuous discovery thrives.

For further exploration, I recommend these resources. Follow Teresa Torres: https://ProductTalk.org. Follow Petra Wille: https://Petra-Wille.com. Product Talk Academy’s Train Your Team by Teresa Torres: https://learn.producttalk.org/train-your-team. Melissa Perri’s “Train leaders first, not last.” Linkedin post: https://www.linkedin.com/posts/melissajeanperri_train-leaders-first-not-last-most-product-activity-7380927349732839424-sqBJ/. Coaching for Product Leaders/Executives by Petra Wille: https://www.petra-wille.com/coaching-packages. Product Leadership Wheel by Petra: https://www.petra-wille.com/plwheel.

To get hands-on with discovery skills, check out Story-Based Customer Interviews: https://learn.producttalk.org/course/story-based-customer-interviews. For visual management, see An idea board—do we see enough potential?: https://images.squarespace-cdn.com/…/idea_board3.png and Four Taskboards in a simple illustration: Idea Board, Product Overview Board, Product Discovery Board and Development Team Board: https://images.squarespace-cdn.com/…/boards.png. Opportunity Assessment: Do We Want to Invest in Discovering This Idea?: https://www.petra-wille.com/blog/opportunity-assessment-do-we-want-to-invest-in-discovering-this-idea?rq=taskboard.

If you’re preparing your organization to adopt a product operating model, read Is Your Organization Ready to Adopt the Product Operating Model?: https://www.producttalk.org/organizational-readiness/ and The Product Operating Model Explained: From Pilot Teams to Full Transformation: https://www.producttalk.org/the-product-operating-model/. Communities of practice can accelerate leadership growth: Community of Practice by Petra: https://www.petra-wille.com/community-of-practice. For foundational texts, see TRANSFORMED: Moving to the Product Operating Model: https://www.svpg.com/books/transformed-moving-to-the-product-operating-model/ and EMPOWERED: Ordinary People, Extraordinary Products: https://www.svpg.com/books/empowered-ordinary-people-extraordinary-products/.

I’d love to hear how you’re enabling continuous discovery in your context. What leadership behaviors have made the biggest difference? Where does your corporate immune system show up, and how are you addressing it with pilot teams, clearer expectations, and a consistent product operating model? Share your perspective—I read every comment.

Inspired by this post on Product Talk.

December 9, 2025
Master the Kano Model: Prioritize Features That Delight and Drive Product-Led Growth

When I sit down with our product trios to shape the next quarter’s roadmap, I rely on The Kano Model to cut through the noise and focus on what actually moves the needle for customers and the business. It gives me a rigorous, human-centered lens for separating baseline expectations from differentiators and sustained value creation.

Learn how the Kano Model prioritizes the product features that matter by categorizing them into must-haves, satisfiers, and delighters.

Here’s how I think about each category in practice. Must-haves are the non-negotiables—if they’re missing or broken, no amount of innovation will save the experience. Satisfiers scale linearly with user happiness; do them better, and customers feel the improvement immediately. Delighters surprise users with unexpected value that elevates the product’s perceived quality and creates memorable moments that fuel advocacy.

In continuous discovery, I mix quantitative Kano surveys with qualitative interviews to validate which capabilities land in each bucket for specific segments. We ask both functional and dysfunctional questions (e.g., “How would you feel if this feature existed?” and “How would you feel if it didn’t?”) to avoid false positives and to distinguish true delighters from nice-to-haves. This approach de-risks assumptions and keeps our product discovery anchored in real customer voice.

Translating insights into action starts with outcomes vs output OKRs. Must-haves protect core outcomes like reliability, trust, and activation. Satisfiers inform product roadmapping and sprint planning by tying investment to measurable improvements such as speed, accuracy, or completion rate. Delighters earn a deliberate share of the roadmap to strengthen competitive differentiation and to refresh our value proposition before market expectations shift.

Kano also sharpens product-led growth motions. By aligning satisfiers with key activation steps and running retention analysis on cohorts exposed to delighters, we can see where excitement features become habit-forming behaviors. When a delighter consistently correlates with improved retention or expansion, it graduates into the backbone of our product positioning.

Stakeholder management gets easier with a shared framework. I present the portfolio as a balanced mix: must-haves that protect reputation, satisfiers that demonstrate continuous improvement, and delighters that signal vision. This narrative connects short-term reliability with long-term strategy and helps leaders understand why some high-effort ideas are best sequenced behind critical must-haves or high-yield satisfiers.

A quick caution: delighters decay. What delights today often becomes tomorrow’s must-have. I schedule periodic re-reads of our Kano results, especially after major releases or market shifts, to recalibrate where features sit. Combined with A/B testing and usage analytics, this habit prevents us from over-investing in fading differentiators and ensures our roadmap stays crisp and customer-centered.

If your roadmap feels crowded or your team debates priorities without resolution, bring The Kano Model to your next planning session. It adds structure to product discovery, clarifies trade-offs, and helps us deliver a roadmap that not only works—but wins.

Inspired by this post on Product School.

December 9, 2025
Product Analytics for Everyone: Master Funnels, Retention, and Conversion to Drive Growth

Product analytics isn’t a specialist’s sport—it’s a team capability. In my role leading product teams, I’ve seen designers, engineers, marketers, and customer success partners uncover insights that shape strategy, accelerate product-led growth, and improve outcomes for customers. When we demystify the basics and bring analytics into everyday decisions, we build truly empowered product teams.

Here’s the core promise of this approach: "Learn the product analytics fundamentals of funnels, retention, and conversion drivers so that anyone can confidently answer key product questions." That line has guided how I teach product managers to think—start with the essentials, tie them to real customer behaviors, and make the work repeatable across the organization.

I start with funnels because they tell a story—the journey from discovery to value. A simple example: track the path from sign-up to user activation to the first value event. This reveals where onboarding succeeds or stalls, what friction blocks adoption, and which moments are ripe for optimization. With tools like Amplitude analytics or Pendo, we can break down conversions by segment, channel, or feature usage to isolate where improvements matter most.

Next comes retention analysis, the clearest signal that we’re building something customers choose to return to. Cohort analysis shows who comes back and when; retention curves show where value compels a second, third, and tenth use. Tie retention to activation milestones and the outcomes customers achieve—not just logins—and you’ll quickly spot whether your product discovery assumptions hold up in the wild. A unified analytics platform makes these insights discoverable and repeatable across teams.

Conversion drivers round out the picture. Once the funnel is clear and retention is stable, I look for the behaviors and experiences that predict success: feature combinations, time-to-value, message timing, or supportive content. Whether in Amplitude analytics or Pendo, correlating these drivers with outcomes lets us prioritize roadmaps with confidence. Pair this with continuous discovery—qualitative interviews, in-product feedback, and rapid experiments—and you’ll move from interesting data to decisive actions.

This is how we build empowered product teams: by making analytics a daily habit rather than a quarterly report. We bring insights into roadmap reviews, design critiques, and sprint planning; we celebrate learning from experiments as much as shipping features; and we hold ourselves accountable to customer outcomes, not just output. When everyone can interpret funnels, discuss retention, and isolate conversion drivers, we make smarter bets faster.

If you’re getting started, keep it simple. Define a clear activation metric, instrument the top of your funnel, and track a small number of cohorts. Share a weekly readout with highlights, surprises, and questions to investigate. Over time, stitch insights into narratives that drive product-led growth—and, most importantly, help customers achieve what they came for.

Product analytics isn’t just for analysts. It’s a shared language for product discovery, onboarding excellence, user activation, and long-term retention. When we practice it together, we build better products and stronger teams.

Inspired by this post on Amplitude – Best Practices.

December 5, 2025
Enterprise Go-to-Market Mastery: How I Align Product, Positioning, and Analytics at Scale

I build enterprise growth motions by grounding strategy in data and execution in crisp storytelling. When I partner with teams using Amplitude, I focus on architecting "go-to-market solutions for enterprise customers." That simple phrase clarifies the mandate: align product, marketing, and sales around measurable value, reduce buyer risk, and prove outcomes early and often.

My go-to-market strategy begins with rigorous segmentation and an ideal customer profile, then translates into a living narrative: the value proposition, points of parity, and competitive differentiation that underpin product positioning. I pressure-test that narrative with real customer language, executive business cases, and use-case–level messaging so every stakeholder—from procurement to security to the economic buyer—hears their priorities reflected back with credibility.

Execution is analytics-led. With Amplitude analytics as a unified analytics platform, I instrument the entire journey—from first touch to paid expansion—to expose activation, aha moments, and friction. I use A/B testing to validate in-app guides, product tours, and onboarding, and I track user activation and retention analysis to ensure product-led growth efforts compound over time. These signals inform sales enablement, content roadmaps, and launch plans so each asset moves a specific metric, not just a milestone.

Operating cadence matters as much as the plan. I rely on empowered product teams and product trios to translate strategy into product roadmapping and sprint planning, ensuring every slice of the roadmap ties directly to market impact. Clear OKRs and QBRs keep the feedback loop tight, while field insights from enterprise pilots shape rapid iteration without losing strategic intent.

Enterprise nuance is the difference-maker: longer cycles, multi-threaded buying committees, and higher switching costs demand precision. I design proofs of value that quantify outcomes early, align pricing and packaging with willingness to pay, and use customer evidence to de-risk decisions. The result is a scalable, repeatable system where positioning is consistent, the funnel is measurable, and revenue teams can predictably win with complex accounts.

Ultimately, the work is about trust. When strategy, analytics, and storytelling lock together, customers see themselves in the product—and teams see themselves in the win. That is the heart of enterprise go-to-market done right.

Inspired by this post on Amplitude – Perspectives.

December 4, 2025
Unlocking the 7% Retention Rule: How Early Activation Fuels Compounding, Long-Term Growth

I’ve learned to spot durable growth early. When we launch something new, I look for one deceptively simple signal that predicts whether the product will compound or stall: the percentage of users who come back one week later. It’s a small number with big implications for product-led growth and retention analysis.

Discover why 7% of users returning after one week signals long-term growth, and how early activation separates top-performing products from the rest.

Why does this matter so much? A 7% day-7 retention floor tells me we’ve earned a second interaction from a meaningful slice of our cohort, not just a curiosity click. That’s the first hint of habit formation and repeatable value—evidence that onboarding, user activation, and the core value proposition are doing their job. When the curve holds at or above this threshold, growth investments tend to work harder because cohorts keep giving back.

The lever behind that signal is early activation. I define the activation moment as the first time a new user experiences product value—sending a first campaign, integrating a CRM, or completing a workflow that solves their primary job. If we reduce time-to-activation and increase the activation rate, day-7 retention rises. This is where in-app guides, product tours, and thoughtful tooltip design shine: they remove friction without overwhelming the user.

Instrumentation is non-negotiable. I set up event tracking and cohort analysis in tools like Amplitude analytics and Pendo, define a crisp activation event, and review retention curves by first-seen cohorts. We run A/B testing with a clear minimum detectable effect (MDE), validate improvements in activation and day-7 retention, and then double down. The objective is always outcomes over output: fewer features, more value delivered.

Process matters as much as tooling. Product trios using continuous discovery keep us close to user problems, while empowered product teams move faster with context and clear outcomes vs output OKRs. When we connect these practices to a unified analytics view, it becomes obvious which changes move the 7% needle and which are noise.

In practice, I’ve seen a launch turn the corner by clarifying the “aha” moment, cutting onboarding steps nearly in half, and swapping a generic walkthrough for contextual in-app guides. Activation jumped, day-7 retention crossed the threshold, and suddenly our PLG motion became efficient—paid acquisition started compounding instead of leaking.

If you’re below 7%, start by tightening the activation definition, instrument the funnel, and remove the top three sources of friction. If you’re above 7%, stabilize it across segments, scale with targeted in-app guides, and keep iterating via A/B tests to protect that early win. Either way, the rule provides a clear, pragmatic checkpoint for product discovery and growth.

The takeaway is simple: focus the team on earning the second visit. Nail early activation, then build repeatable systems that make the 7% retention rule your new baseline for confident, long-term growth.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Stop the Leaky Bucket: Proven Moves to Turn User Growth into Durable Retention in 2025

More signups are exhilarating—until the retention curve tells a colder truth. I’ve led launches where top-of-funnel spiked, only to watch active usage slide week over week. That’s the leaky bucket problem in action: acquisition outpaces activation, engagement, and retention, so net growth stalls.

Losing users as fast as you acquire them? Get exclusive insights from our 2025 Product Benchmark Report on how to fix the leaky bucket problem and drive lasting growth.

When I assess a product’s trajectory, I reframe the goal: our job isn’t to add users; it’s to create retained value. In product-led growth, durable growth comes from systematically increasing activation and Day 7/30 retention, not just traffic. That shift aligns teams on outcomes vs output and turns experiments into a compounding engine.

Diagnosis comes first. I run a retention analysis by cohort in Amplitude analytics (and corroborate with Pendo for in-app behavior) to pinpoint where the flow breaks: sign-up, onboarding, first value, habit formation, or paywall. Then I define a crisp activation metric—what specific action within a time window predicts long-term engagement—and measure time-to-value for each segment.

From there, we remove friction. Simplify onboarding, trim non-essential fields, and guide users to the “aha” with in-app guides, product tours, and contextual tooltips. Seed accounts with sample data, pre-built templates, and smart defaults so new users experience the core value in minutes, not days.

We prove impact with disciplined experimentation. A/B testing with a clearly calculated minimum detectable effect (MDE) prevents false positives, while a continuous discovery cadence with product trios keeps us close to real customer problems. Every test is tied to leading indicators—activation rate, Day 1/7/30 retention, and weekly engaged usage—not vanity metrics.

Activation does not live in product alone. Pricing and packaging, lifecycle messaging, and customer support all influence early habit formation. Align GTM and product on one retention-centric scorecard and instrument a unified analytics platform so every team sees the same truth.

Once the core journey holds water, we layer in expansion: prompts that surface adjacent value at the right moment, educated upsells tied to outcomes, and permissions or collaboration features that invite team adoption. That’s how growth becomes efficient and compounding instead of brittle and expensive.

If this resonates, you likely have more of a prioritization problem than a traffic problem. Fix activation, measure retention rigorously, and let acquisition follow. Patch the leaks, and growth stops being a hustle—and starts being a flywheel.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Stop Chasing New Users: The Surprising ROI of Win-Back Campaigns That Actually Work

Over the years, I’ve learned that the most overlooked growth lever isn’t a shiny new channel—it’s bringing back the customers we already earned. When I rebalanced budgets from top-of-funnel acquisition to reactivation, the payoff was faster, more predictable, and far more cost-efficient. Reactivation compounds because it’s built on trust, product familiarity, and data we already have.

Discover why reactivating dormant users delivers better ROI than new acquisition. Learn how to identify and bring back at-risk users via targeted campaigns.

Why does this work so well? Dormant users once saw enough value to sign up, activate, or even pay. The barriers to return are lower: familiarity reduces friction, time-to-value shrinks, and the cost to engage is a fraction of new-user CAC. In practice, I’ve seen win-back motions outperform new acquisition on payback time, expansion potential, and long-term retention—especially when we design the right triggers and messages.

My approach starts with rigorous retention analysis. I define the behaviors that signal risk—declining frequency, shrinking session depth, stalled onboarding milestones, or missed “aha” moments—and map them to lifecycle stages. Using a unified analytics platform with CRM integration, I can see who’s drifting, when, and why. That clarity is the foundation for precision reactivation.

On the tooling front, I lean on Amplitude analytics to surface cohorts and leading indicators, Pendo for in-app guides and nudges, and Intercom for lifecycle messaging and human-assisted outreach. The connective tissue is our CRM integration, which ensures we coordinate messages across email, in-app, and sales-assist without creating noise or duplication.

Segmentation is where win-back campaigns gain power. I group users by their last successful use case, plan tier, activation depth, and the specific friction they hit. Cohorts often include “stalled onboarding,” “lapsed power users,” and “trial expired with partial success.” Each segment gets a distinct path back to value—never a one-size-fits-all blast.

Targeted campaigns are then matched to the root cause. For stalled onboarding, I deploy product tours and in-app guides that remove a single key blocker. For lapsed power users, I emphasize newly shipped capabilities tied to their historical workflows. For price-sensitive cohorts, I test usage-based offers or limited-time boosts aligned to value realization, not discounting for its own sake. Every flow is A/B testing-driven and time-bound, with clear exit criteria.

Measurement goes beyond “did they log in.” I track reactivation rate, feature adoption depth, time-to-value, and near-term expansion signals. Holdout groups validate lift, and we set guardrails so campaigns don’t cannibalize healthy cohorts. Over time, these learnings inform product roadmap decisions—what to simplify, what to sunset, and where to invest to prevent churn in the first place.

Operationally, I embed win-back into product-led growth rhythms. Product, data, lifecycle marketing, and support align on weekly reviews, using shared dashboards to tune triggers and content. This creates a reliable growth engine that respects user intent and avoids the trap of overmessaging.

Finally, trust matters. I build reactivation with privacy-by-design principles, transparent value propositions, and easy opt-outs. The goal isn’t to “get the login”—it’s to restore momentum toward outcomes the user cares about.

If you’re feeling acquisition fatigue, shift a meaningful slice of budget and attention to reactivation. In my experience, it delivers faster wins, better unit economics, and a healthier product that keeps more of the customers you worked so hard to earn.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
A Product Strategist & Evangelist’s Playbook at Amplitude: Turning Analytics into Growth

I’ve long believed that the Product Strategist & Evangelist role is where analytics meets impact. When I work with teams using Amplitude, my focus is simple: turn product data into decisions that compound, and tell the story in a way that mobilizes people—customers, stakeholders, and empowered product teams alike.

At its core, this role aligns product strategy with business outcomes. I anchor planning to outcomes vs output OKRs, partner closely with product trios, and run continuous discovery to ensure every roadmap item is tied to a measurable customer problem and value proposition. That discipline keeps us honest about what moves the needle.

Analytics is the engine. I start with a clean event taxonomy, dependable instrumentation, and a self-serve insight layer in Amplitude analytics. From activation to retention analysis, I define a few sharp metrics that predict sustainable product-led growth—then I build dashboards the whole organization can trust and use.

Experimentation is where insight becomes action. I operationalize A/B testing with clear hypotheses, guardrails for minimum detectable effect, and crisp success criteria. The goal is speed with rigor: learn fast, ship what works, and retire what doesn’t. Over time, this creates a culture where teams default to evidence rather than opinions.

Evangelism turns analytics into momentum. I practice developer evangelism to meet practitioners where they are, and I translate complex findings into accessible narratives for executives and customer-facing teams. That means live walkthroughs, in-app guides, product tours, and field enablement that shows not just the what, but the why and the how.

Under the hood, a unified analytics platform is essential. I pair it with pragmatic data governance and privacy-by-design so we can scale insights confidently. The result is a flywheel: reliable data, repeatable workflows, and reusable patterns that accelerate every subsequent initiative.

On the go-to-market front, I connect product strategy to positioning, packaging, and enablement. The stories we tell in the market should mirror the value we measure in the product. That alignment makes launches sharper, sales motions clearer, and adoption smoother.

In practice, my playbook is straightforward: clarify the North Star and adjacent metrics, stand up trustworthy pipelines and dashboards, institutionalize experimentation, and continuously translate insights for decision-makers. Done well, analytics stops being a report and becomes a system for growth.

If you’re building or evolving this function, start small and intentional: instrument the few events that matter, ship one meaningful A/B test, and circulate a concise narrative on what you learned. Consistency beats complexity, and momentum compounds quickly when teams see their decisions move the metrics that matter.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Slash Time to Value to Skyrocket Retention: A Proven Playbook for Faster Impact

I’m relentlessly focused on time to value because it’s the fastest, most reliable lever I have to drive user retention and product-led growth. When new users experience an unmistakable win quickly, they stick around, explore deeper features, and become advocates. When they don’t, the best onboarding or marketing can’t save the experience.

Accelerate retention by reducing time to value. Learn how faster product impact drives growth, reduces costs, and keeps users engaged in the long term.

Here’s how I define it in practice: time to value (TTV) is the elapsed time between a user’s first meaningful interaction and the first moment they feel the product’s core value. That “aha” moment is not a vanity milestone; it’s a measurable behavior that correlates with long-term retention in your retention analysis and cohort curves.

In my role leading product teams at HighLevel, I treat TTV as a leading indicator for retention and expansion. It shapes our product discovery, influences our value proposition, and anchors our outcomes vs output OKRs. If a roadmap item doesn’t shorten TTV or deepen recurring value, it rarely makes the cut.

My playbook for reducing TTV starts by identifying the activation metric—what’s the smallest observable action that best predicts retention? For a messaging product it might be sending the first message to three contacts; for a workflow tool, publishing the first automated flow. Once this activation is clear, the job becomes simple: engineer the shortest, most delightful path to that outcome.

Next, I eliminate onboarding friction. I default to progressive profiling instead of long forms, ship sensible defaults, preload sample data, and offer ready-to-use templates. I complement this with lightweight in-app guides, product tours, and well-timed tooltip design—just enough guidance to build momentum without overwhelming the user.

To validate changes, I rely on rigorous experimentation. A/B testing with a defined minimum detectable effect ensures we’re not overfitting noise. I track activation rate, time to first value, feature adoption, and day 7/30 retention. If an experiment improves activation but hurts short-term retention, I dig into the “why” with session replays, targeted surveys, and follow-up interviews.

This approach also reduces costs. Faster activation lowers support volume, decreases onboarding hand-holding, and shortens payback periods. On the GTM side, TTV-aligned messaging clarifies our value proposition, improving conversion quality and reducing churn from poorly qualified signups.

Cross-functional alignment is essential. Product, design, engineering, and customer success must agree on the definition of value, the activation metric, and the telemetry required to measure progress. I use product trios to maintain discovery momentum and ensure decisions connect cleanly to measurable outcomes.

A practical 30/60/90 plan helps teams move fast. In the first 30 days, define activation, instrument analytics, and map the current journey. By day 60, ship friction-killing improvements, launch in-app guides, and run your first A/B tests. By day 90, refine templates, tighten empty states, and codify wins into the onboarding system so improvements compound.

The biggest pitfall I see is chasing more features instead of more value, faster. When we focus on shortening the path to a single compelling outcome—and proving it with data—retention follows. Users don’t need more; they need the right result sooner.

If you’re serious about retention, make time to value your team’s most visible operating metric. Shine a bright light on it in weekly reviews, tie it to goals, and celebrate every step that helps users succeed faster. Do this consistently, and you’ll see growth accelerate, support costs drop, and engagement deepen in ways that are both measurable and enduring.

Inspired by this post on Amplitude – Perspectives.

December 3, 2025
Enterprise GTM Mastery: How I Partner with Product Marketers to Drive Adoption at Scale

I spend a lot of time turning strong product capabilities into enterprise wins, and that almost always starts with a tight partnership between product management and product marketing. The most effective go-to-market strategy is built where customer insight, product value, and revenue goals intersect—and product marketers are the connective tissue that makes this real.

“Michele Morales is a product marketing manager at Amplitude, focusing on go-to-market solutions for enterprise customers”

In my experience, partnering with product marketing leaders on enterprise go-to-market means aligning early on the ICP, the value proposition, and the differentiated messaging that sales can activate. We map buyer committees, refine product positioning against points of parity and competitive differentiation, and ensure our narrative translates cleanly from website to demo to proof-of-concept.

For data-driven execution, I lean on Amplitude analytics and a unified analytics platform approach to validate our hypotheses. We set clear activation and adoption milestones, monitor user activation cohorts, and close the loop with retention analysis to understand which messages and features actually move enterprise accounts from trial to expansion. This is where product-led growth complements sales-led motions, giving us empirical signal across the funnel.

On the launch front, we pressure-test enablement and in-product experiences together: crisp messaging frameworks, in-app guides, and product tours that shorten time-to-value for complex enterprise use cases. The result is a go-to-market strategy that’s both technically accurate and emotionally resonant—clear enough for executives and actionable for end users.

What consistently works: start with real customer pain, express value succinctly, and make the path to first success obvious. Then instrument everything. When product, marketing, and sales can all see the same truth in the data, empowered product teams iterate faster, positioning sharpens, and adoption compounds.

This approach respects the craft of product marketing while grounding decisions in measurable outcomes. It’s how we turn a promising roadmap into repeatable enterprise impact—and why close PM–PMM collaboration remains one of my most reliable growth levers.

Inspired by this post on Amplitude – Best Practices.

December 3, 2025