Tag: in-app guides

Safeguard Customer Data with Pendo Agent Analytics: Drive Adoption, Cut Costs, Reduce Risk

Protecting customer data is non‑negotiable—and it must coexist with our need for precise product insights. In my role, I frame every analytics initiative, Pendo Agent Analytics included, around measurable outcomes and rigorous governance so we can accelerate growth without compromising trust.

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.

To make that promise real, I anchor implementation in privacy-by-design. Practically, that means data minimization, purpose limitation, role-based access control, auditable workflows, and clear retention policies. These are the same standards I expect from any unified analytics platform and the operating guardrails my team applies in partnership with security and legal.

On the product side, I focus Agent Analytics on the behaviors that move the needle: adoption, feature engagement, user activation, and time-to-value. Paired with in-app guides, product tours, and thoughtful tooltip design, insights become timely interventions that drive product-led growth—while staying within our data governance boundaries.

Reducing organizational risk demands discipline. I pair analytics rollout with a documented data map, DPIAs where appropriate, vendor risk assessments, and clear incident management protocols. We align with regulatory compliance requirements and integrate with cybersecurity practices for continuous monitoring and threat detection and response.

I track success through business and trust metrics: higher adoption, stronger retention analysis, fewer support tickets, and cost savings from deprecating low-value features—alongside clean audits and consistent adherence to governance standards. The outcome is a tighter feedback loop, smarter roadmap decisions, and sustained customer confidence.

If you’re evaluating Agent Analytics, start with a controls checklist, define the minimum viable telemetry for your KPIs, validate consent flows, and pilot with a narrow audience before you scale. This approach balances velocity with vigilance, ensuring we harness analytics for impact without sacrificing privacy or compliance.

Inspired by this post on Pendo – Perspectives.

January 3, 2026
Four High-Impact Lifecycle Journeys to Run in Pendo Orchestrate for Activation and Retention

When I map the customer lifecycle, I look for the precise moments where guidance, context, and timing can transform a casual click into a committed relationship. That’s exactly why I rely on Pendo Orchestrate—to turn intent into a systematic, repeatable product strategy that scales across every stage of the journey.

From first click to lifelong retention, you’ll deliver the right message at the exact right time, every step of the way. With Pendo Orchestrate, you can design those kinds of moments with intention. And in this blog, we’ll show you how.

In practice, I translate that promise into four lifecycle journeys every product team should be running with Pendo Orchestrate: new user onboarding, activation to the aha moment, expansion and upsell, and renewal and retention. These journeys power product-led growth and keep the roadmap aligned to measurable business outcomes.

Onboarding: I use in-app guides and product tours to welcome new users, set expectations, and reduce time-to-value. Contextual tooltips and gentle checklists keep users moving, while clear, concise UX writing removes friction. The goal is simple: accelerate early wins so onboarding naturally flows into user activation.

Activation: To help users reach the aha moment, I pair behavioral insights with targeted in-app guides. When a user approaches a key milestone, Pendo Orchestrate triggers just-in-time prompts that reinforce the value proposition. I keep these nudges focused, specific, and measurable so activation improves without overwhelming the experience.

Expansion: Once users adopt core workflows, I introduce advanced capabilities through tailored tours and contextual education. These cues appear where they’re most relevant—in the flow of work—so cross-sell and upsell moments feel helpful, not salesy. The intent is to deepen adoption by connecting features to outcomes users already care about.

Renewal and retention: I watch for patterns that suggest risk (stalled usage, incomplete workflows) and offer supportive interventions. Lightweight guides, quick tips, and feedback loops help resolve issues before they become churn. Combined with retention analysis, these orchestrations keep customers engaged and set the stage for long-term value.

When these four journeys run in concert, your product becomes the primary engine of growth. Pendo Orchestrate ensures the right in-app guidance shows up at the right moment—so your product strategy, product discovery, and day-to-day execution stay tightly aligned. That’s how you move beyond one-off campaigns and build a durable, product-led growth system.

Inspired by this post on Pendo – Best Practices.

January 3, 2026
4 Proven Ways GTM Teams Accelerate Growth with Pendo’s HubSpot Integration

I’ve led GTM and product teams through countless tool integrations, and few have delivered compounding returns like connecting Pendo with HubSpot. See how customer behavioral data can help sales, marketing, customer success, and product teams create a better, more engaging customer experience. When we put product behavior where our revenue teams already live, the entire go-to-market engine becomes sharper, faster, and more customer-centric.

Here’s how I frame the value: the Pendo–HubSpot CRM integration unifies in-app product usage with contact and account context, so we can orchestrate lifecycle touchpoints across email, chat, and in-app guides while giving every function a single source of truth. The result is a product-led growth motion that aligns marketing, sales, customer success, and product around measurable activation, adoption, and expansion.

First, I help sales prioritize pipeline with usage-enriched lead and account scoring in HubSpot. Signals like feature adoption depth, weekly active users, trial milestones reached, and time-to-value tell AEs who is ready to buy and why. With real-time alerts and views, reps can tailor discovery, shorten sales cycles, and increase win rates—turning product interest into qualified demand.

Second, I accelerate onboarding and user activation by building HubSpot segments from Pendo cohorts and triggering coordinated journeys. New users receive the right lifecycle emails while in-app guides, product tours, and tooltips nudge them through key actions. This reduces time-to-value, increases early retention, and creates a smoother first-run experience.

Third, I protect and expand revenue with proactive customer success. Behavioral health scores and retention analysis spotlight accounts drifting from core workflows, prompting playbooks for outreach, training, or in-app interventions. Conversely, expansion signals—like adoption of premium features or growing seat usage—route to the right owner for timely upsell conversations.

Fourth, I close the loop for product decision-making. By syncing feedback, NPS, and usage cohorts with campaign and pipeline data in HubSpot, the team can measure how launches and in-app experiments influence engagement and revenue. This unified analytics platform approach keeps roadmaps tied to outcomes, not opinions, and helps us double down on the features that move the business.

To make this work, I start with a clear data contract and privacy-by-design guardrails: shared definitions for active users and adoption milestones, owner responsibilities for fields, and explicit consent handling. We then phase the rollout—beginning with one or two high-impact plays—instrument the baseline, and iterate using go-to-market strategy reviews to verify causal impact.

If your GTM teams are leaning into product-led growth, the Pendo–HubSpot integration is a force multiplier. Aligning lifecycle messaging, sales prioritization, and customer success around real behavioral data creates compounding advantages—more relevant outreach, faster activation, higher retention, and cleaner expansion.

Inspired by this post on Pendo – Best Practices.

January 3, 2026
How We Scale Revenue with Pendo Predict: My Playbook to Cut Costs and Reduce Risk

When revenue expansion, cost efficiency, and product risk mitigation all matter at once, I turn to Pendo Predict. In my role leading product management, I’ve seen how predictive insights can supercharge product-led growth by aligning onboarding, user activation, and in-app experience design with the outcomes our customers value most.

“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.” That promise captures why I integrate Pendo Predict at the heart of our product strategy.

Here’s how I operationalize it: I start by mapping our value proposition to clear activation milestones, then use Predict to surface segments that are most likely to convert, expand, or churn. With those signals, we personalize in-app guides and product tours to address friction in real time, accelerating user activation and streamlining onboarding without adding headcount.

To scale revenue, I connect Predict’s likelihood scores to our product strategy rituals: prioritizing roadmap bets that increase adoption, sequencing releases where the impact will be highest, and instrumenting retention analysis to verify lift. This turns our product into a self-reinforcing growth engine—nudges, guides, and contextual help show up exactly when users need them, driving deeper engagement and upsell readiness.

Cost reduction follows naturally. By meeting users inside the product with targeted in-app guides, we deflect support tickets, shorten time-to-value, and reduce the volume of one-off interventions. We also improve platform scalability by focusing engineering effort on the experiences Predict flags as the biggest levers, not just the loudest requests.

Risk is where Predict becomes a strategic safety net. Instead of betting the quarter on intuition, we run controlled changes, use A/B testing for in-app messaging, and monitor predicted outcomes before rolling out broadly. This de-risks roadmap decisions while preserving velocity—critical for a product team operating at scale.

Practically, my playbook is simple: (1) define activation and retention events tied to our value proposition, (2) use Pendo Predict to identify high-impact segments, (3) deploy tailored product tours and in-app guides to close the gap, (4) validate impact with retention analysis and iterate. Repeat this loop and adoption compounds, creating reliable, product-led growth.

If your team is aiming to raise the ceiling on adoption and engagement while controlling spend, Pendo Predict gives you the visibility and control to do both. For us, it’s the connective tissue between strategy and execution—the data-driven way to deliver the right experience at the right time, and to do it consistently at scale.

Inspired by this post on Pendo – Best Practices.

January 3, 2026
Implementing Agentforce the Right Way: A Practical Playbook with Pendo and Salesforce

I think about Agentforce implementation the same way I think about any high-stakes product launch: start with outcomes, instrument relentlessly, and iterate in tight loops. When agentic AI touches core workflows in Salesforce, the winners are the teams that combine rigorous product strategy with thoughtful CRM integration and product-led growth tactics.

Learn the ways in which Pendo helps companies design and iterate on their agentic strategy for Salesforce.

My working playbook begins with clarity. Before a single agent is deployed, I align with stakeholders on the highest-value “jobs” inside Salesforce—reducing case handle time in Service Cloud, accelerating lead qualification in Sales Cloud, or improving data hygiene for revenue operations. That alignment shapes our agentic AI approach and prevents us from shipping clever agents that don’t move the metric that matters.

From there, I treat telemetry as a first-class requirement. I instrument the end-to-end journey with Pendo so we can observe when an agent triggers, when it falls back, when it hands off to a human, and how those moments affect conversion, CSAT, and cycle time. I refer to this observability layer as Agent Analytics, and it’s the backbone of evidence-based iteration.

Guidance is equally critical. I use Pendo’s in-app guides to onboard admins and frontline users directly inside Salesforce, deliver contextual tooltips that explain what the agent will do next, and collect feedback within the flow of work. That combination shortens time-to-value and builds trust, which is essential for customer support ai strategy and change management.

Iteration is where the compounding returns show up. I run A/B testing on prompts, decision policies, and handoff rules; evaluate performance on real user cohorts; and promote what works. This is classic product-led growth applied to agentic AI—ship small, measure precisely, and scale winners. Prompt engineering is not a one-time task; it’s a continuous discovery loop.

I also weave in governance from day one. Privacy-by-design, data governance, and AI risk management aren’t add-ons—they are design constraints that shape what the agent is allowed to see and do. The guardrails live alongside the experience: clear disclosures, reversible actions, and easy ways for users to override or escalate.

Finally, I operationalize the learning loop. Weekly reviews with a product trio (PM, design, engineering) examine Pendo dashboards, qualitative feedback, and Salesforce outcomes. If an agent is underperforming, we adjust prompts, refine retrieval, or simplify the decision tree. If it’s exceeding targets, we expand the use case and systematize the pattern.

When teams ask me for the “right way” to implement Agentforce, my answer is simple: treat your agent like a product. Measure with Pendo, guide inside Salesforce, and iterate until the business outcome moves. That’s how we turn promising agents into durable advantages.

Inspired by this post on Pendo – Perspectives.

January 3, 2026
How I Used Pendo In-App Guides to Ignite Our Summer Release Adoption, Engagement, and ROI

Launching a major release is only half the battle; earning adoption inside the product is where the real wins happen. For our Summer Release, I made a deliberate choice to promote new capabilities where customers experience value—in the app—by leaning on Pendo’s in-app guides, product tours, and tooltip design. This product-led growth approach let us deliver timely, contextual education without disrupting a user’s flow, aligning our go-to-market strategy with how people actually work.

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.

I began by segmenting audiences around key jobs-to-be-done and lifecycle stages—onboarding users, power users, and specific roles—so every prompt supported a clear value proposition. We mapped the journey for each segment and placed concise guides at decision points where users naturally discover adjacent features. The goal was simple: accelerate user activation, reduce time-to-value, and make the Summer Release feel intuitive, not intrusive.

Execution hinged on progressive disclosure. Short, focused product tours introduced what changed and why it mattered, while tooltips offered deeper context when users hovered or asked for help. We paired this with behavioral targeting so guides appeared only after relevant triggers—usage patterns, page views, or completion of prerequisite steps—keeping the experience helpful and respectful.

We ran A/B testing on headlines, CTAs, and guide placement to refine messaging and reduce friction. Variants explored different tones (instructional vs. benefit-led), lengths (microguide vs. multistep tour), and formats (banner, modal, tooltip). The winning patterns emphasized outcome-first language, clear next steps, and optional deep dives for advanced users.

Measurement focused on adoption and engagement: guide view-to-click rates, feature usage uplift post-guide exposure, and downstream behaviors tied to retention analysis. While we avoided vanity metrics, we did look for sustained usage over time, not just one-time clicks. The early signals were encouraging—faster discovery of new capabilities, higher completion of key workflows, and more consistent engagement across targeted cohorts.

Cross-functionally, we aligned in-app messaging with our broader go-to-market strategy, ensuring consistency across help center content, enablement, and customer communications. This cohesion strengthened competitive differentiation and reinforced our product strategy: deliver value in context, then invite users to explore more when they are ready.

The biggest lesson? Thoughtful in-app guides and product tours are not about broadcasting release notes—they are about orchestrating moments of clarity that compound into adoption. By combining precise segmentation, disciplined experimentation, and clear success criteria, we turned a launch into sustained product-led growth. Next, we’re extending this playbook to onboarding and lifecycle milestones to keep momentum strong across releases.

Inspired by this post on Pendo – Perspectives.

January 3, 2026
Behind the Scenes: How We Use Amplitude on Amplitude to Drive Growth and Customer Love

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.

December 22, 2025
Stop Asking, Start Listening: Turn VOC Into Measurable Behavior, Retention, and Revenue

I’ve learned that the fastest path from feedback to impact is not to ask more questions—it’s to listen more closely to what users already tell us with their clicks, scrolls, and pauses. Surveys and interviews give us color, but behavioral analytics reveal truth. When I connect voice of the customer (VOC) to real user behavior, I can prioritize with confidence and ship changes that improve activation, retention, and revenue.

Discover how to connect voice of the customer (VOC) feedback to user behavior and turn opinions into action.

Here’s the mindset shift that changed my team’s outcomes: opinions are hypotheses, behavior is evidence. I blend qualitative VOC with quantitative product analytics so our roadmap aligns to outcomes vs output OKRs. The result is a tighter feedback loop, fewer bets based on anecdotes, and more decisions grounded in measurable user value.

First, I instrument the product so it can “talk back.” That means a clean event taxonomy for key moments like time-to-first-value, onboarding completion, feature adoption, and conversion health. Tools such as Amplitude analytics, Pendo, and a unified analytics platform help me track funnels, cohorts, and retention analysis with consistent definitions across teams.

Next, I normalize the messy reality of VOC. Support tickets, sales notes, app reviews, in-app guide responses, product tour feedback—everything gets tagged into themes such as onboarding confusion, performance slowness, permissions friction, or pricing clarity. This shared language lets me map qualitative signals to behavioral segments without losing nuance.

Then I join feedback to behavior. For any theme, I create a cohort of users who expressed it and compare their funnel completion, activation rate, and retention curves to a control group. If customers say a flow is “too complex,” I look for excessive time-on-step, back-and-forth navigation, tooltip dependence, or drop-offs at a specific screen. Cohort and funnel analysis make the problem visible and quantifiable.

Prioritization becomes straightforward once the impact is measurable. I size the opportunity by the delta in activation, conversion, or retention and estimate the lift from fixing the root cause. This moves us from feature wish lists to product-led growth bets with clear business cases and confidence intervals.

When it’s time to ship, I close the loop with disciplined experimentation. I use A/B testing with a clear minimum detectable effect (MDE), guide users through changes with in-app guides and product tours, and monitor behavior shifts in near real time. Success means behavior moves in the direction the VOC suggested—fewer drop-offs, faster task completion, and improved activation and retention.

A recent example: we kept hearing about “slow” reporting. Instead of debating, we correlated the feedback with sessions showing long load times and repeat clicks on filters. By simplifying defaults, prefetching key queries, and clarifying loading states, we cut perceived wait time by 42% and improved day-7 retention for affected cohorts. VOC identified the friction; behavior showed us exactly where to fix it.

This practice thrives with a simple cadence: weekly listening reviews with product trios to spot themes, monthly synthesis across VOC and usage, and dashboards that pair sentiment with behavior. Over time, the organization shifts from reactive requests to continuous discovery, where each insight is traced to a measurable change in user behavior.

If you want a roadmap that sells itself, start by letting the product speak. Connect your VOC themes to behavioral analytics, quantify the gaps, and ship targeted improvements that users can feel—and you can measure.

Inspired by this post on Amplitude – Perspectives.

December 19, 2025
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
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
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
Unlock Instant Product Answers: How AI-Powered Resource Centers Elevate In‑App Help

I’ve spent years watching users bounce between product screens, docs, and support tickets when they hit a roadblock. The fastest path to value is always the same: deliver relevant, contextual help exactly when and where the user needs it. That’s why I’m excited about the next wave of in-app guidance that blends behavioral data with AI to anticipate intent and remove friction in real time.

Announcing Resource Centers, Amplitude’s newest in-product help feature that uses behavioral data and AI to serve help content users actually need.

Here’s why that matters. In a product-led growth model, in-app guides, product tours, and just-in-time tips are essential to onboarding and user activation. When help content is informed by real behavioral signals—events, cohorts, milestones—it stops being a static knowledge base and becomes a living system that adapts to a user’s journey. That means fewer context switches, faster time-to-value, and more confident users who can self-serve their way to outcomes.

In practice, the most effective resource centers are opinionated and contextual: they surface content by role, plan, and lifecycle stage; trigger nudges based on key events; and offer multiple modalities (microcopy, short clips, interactive guides) so users can choose how they learn. They also respect pacing, avoiding notification fatigue with rate limits and prioritization rules. Think of this as high-quality UX writing paired with data-driven orchestration—useful, discoverable, and never in the way.

Execution matters. Start with a clear content taxonomy, map help assets to journey stages, and establish a content ops cadence so guides stay fresh. Partner closely with data governance to ensure privacy-by-design and transparent consent for behavioral data usage. Then wire in feedback loops—thumbs up/down, quick polls, and session replays—so you can continuously discover gaps and iterate quickly.

Measure impact with the same rigor you apply to product features. Track activation rates, time-to-first-value, self-serve resolution rates, reduction in ticket volume on targeted topics, and downstream retention. Use A/B testing to validate which interventions move the needle, and segment results to learn what works for new users versus power users. When results differ, treat that as a design signal—not a failure—and refine the targeting.

Rollout thoughtfully. Pilot with a high-friction workflow, localize the help content to the user’s context, and set clear exit criteria before scaling. Align with customer support and success so your resource center becomes the canonical source for in-app help, not yet another content silo. Over time, unify insights across Amplitude analytics and your support stack to close the loop between product behavior and help outcomes.

As product leaders, our goal is simple: reduce effort and increase confidence for every user. AI-assisted, behaviorally triggered resource centers are a pragmatic step toward that future—meeting users where they are, with exactly what they need, at the moment they need it.

Inspired by this post on Amplitude – Best Practices.

December 3, 2025