Tag: in-app guides

Obsess Over Activation: Proven Steps to Ignite Product Engagement and Retention

Engagement starts with a single, repeatable moment: activation. Over the years, I’ve learned that when we obsess over activation, everything downstream—retention, expansion, and product-led growth—gets easier and more predictable. As I often remind my teams, "Discover how winning teams drive engagement by obsessing over activation. Learn to define, measure, and improve the moments that keep users coming back."

When I say activation, I mean the specific behavior that reliably predicts long-term value for a new user or account. In different products, the activation moment could be connecting a data source, inviting a teammate, sending the first campaign, or completing an initial automation. My first move is to define that moment precisely, set an activation threshold (for example, “within 7 days of signup”), and align the team around it as a primary outcome.

From there, I track three core metrics: activation rate (the percentage of new accounts that hit the activation threshold), time-to-activation (how quickly they get there), and early retention curves by cohort. Cohort-based retention analysis gives me the most honest read on whether our activation definition truly predicts stickiness or if we’re celebrating vanity milestones. Tools like Amplitude analytics and Pendo make it straightforward to instrument these events, segment users, and visualize the funnel from first touch to activation and beyond.

Instrumentation quality is non-negotiable. I map the activation journey into discrete events, add clear event properties (role, plan, channel, use case), and validate tracking end-to-end before I trust any dashboard. A strong unified analytics platform lets me slice activation by persona, acquisition source, and onboarding path, so we can see where friction lives and where momentum builds.

Improving activation is where design and data meet. I lean heavily on in-app guides, product tours, and contextual tooltips to reduce cognitive load at the exact moment a user needs help. We run A/B testing with a minimum detectable effect in mind, prioritize experiments that remove steps or shrink time-to-value, and iterate quickly based on user feedback gathered through continuous discovery. The goal is simple: shorten the distance from curiosity to value.

Onboarding is the frontline of activation. I favor progressive disclosure, crisp checklists tied to the activation moment, and “just-in-time” education rather than dumping documentation up front. Clear wayfinding—what to do next, why it matters, and how success is measured—pushes users toward that first “aha” moment with confidence.

Cross-functionally, I align activation to outcomes vs output OKRs so everyone—from product and design to marketing and customer success—pulls in the same direction. For example, lifecycle emails and in-app messaging should reinforce the same activation path that product guides inside the app. This harmony lowers friction, speeds time-to-activation, and compounds engagement.

As we scale, I keep a living experiment backlog focused on activation levers: simplifying setup, removing form fields, auto-detecting configurations, and pre-populating defaults. Each change gets measured against activation rate and time-to-activation, with guardrail metrics to protect quality and retention. Over multiple releases, these small wins stack into durable growth.

I’ve seen teams unlock double-digit improvements by treating activation as a product, not a project. When we define the right moment, instrument it well, and iteratively remove friction with data-informed design, engagement rises naturally—and sustainably. That’s the power of an activation-obsessed culture.

Inspired by this post on Amplitude – Best Practices.

December 2, 2025
The Hidden ROI of Win‑Backs: Reactivate Dormant Users Faster, Cheaper, and With Lasting Impact

I’ve learned the hard way that the fastest, lowest-risk growth lever is hiding in plain sight: reactivating the users we already earned. When our team prioritized win-back programs over new acquisition, we unlocked higher net revenue retention, shorter payback periods, and stronger product-market signal—with a fraction of the spend.

"Discover why reactivating dormant users delivers better ROI than new acquisition. Learn how to identify and bring back at-risk users via targeted campaigns." That insight matches what I see daily: win-back campaigns compound value because they capitalize on existing familiarity, prior data, and stored intent.

Here’s the ROI logic I use. New acquisition burns budget on education and trust-building before value is realized. Reactivation, by contrast, taps into latent demand and prior setup, which means lower effective CAC, faster time-to-value, and higher LTV recapture. In retention analysis, these programs often outperform prospecting by a wide margin because the user already knows how to get value—they just need a relevant nudge.

To find the right users to re-engage, I start with leading indicators of risk: declines in weekly active use, feature decay (e.g., key workflows not triggered), shrinking session depth, and unresolved outcomes. Amplitude analytics or a unified analytics platform help me segment cohorts by recency, frequency, and monetary signals, then rank accounts by churn propensity. I also track intent proxies like billing pauses, reduced seat utilization, and cooling support contact.

I group users into three practical tiers: “at-risk” (recent value decay), “dormant” (no critical events in the past 30–60 days), and “churned-eligible” (post-cancel window with a viable path back). Each tier gets a distinct message strategy, incentive structure, and time horizon. The goal is to match the intervention to the activation friction each group faces.

For creative strategy, I anchor on the outcome they originally hired us to deliver. I lead with the value proposition they care about, not the features. A strong win-back narrative reminds users of the job-to-be-done, showcases what’s improved since they last engaged (new capabilities, performance, integrations), and offers an effortless next step—often a guided “return-to-value” flow or a one-click way to pick up where they left off.

Channel orchestration matters. I use Intercom and Pendo to deliver contextual nudges, in-app guides, and lightweight product tours that meet users at the precise moment and screen of friction. With CRM integration, we coordinate email and SMS for timely follow-ups, then reinforce success in-product with progressive tooltips and checklists. The best-performing sequences pair a personalized message, a sharp call-to-outcome, and a low-friction path back to activation.

Experimentation is non-negotiable. I run A/B testing on subject lines, offers, and in-product prompts, and size tests with a minimum detectable effect (MDE) that’s realistic for each segment. We personalize content by prior feature use, industry, and plan tier to avoid generic blasts that underperform. Over time, the library of proven treatments compounds, and the system becomes predictively better at catching risk earlier.

Measurement should be unambiguous. I define “reactivation” as the return to a qualifying level of usage that mirrors healthy customers (e.g., core event completion in a set window), not just a login. I track reactivation rate, time-to-reactivation, reactivated revenue, payback, and LTV uplift versus holdout cohorts. Cohort views in Amplitude analytics reveal whether improvements are persistent, and whether we’re driving true behavior change or short-term spikes.

Trust is part of the strategy. We build privacy-by-design into all outreach and respect user preferences. Clear value exchange (why this message, why now, how to opt out) consistently improves response rates and strengthens long-term relationships—win-backs should feel helpful, not harassing.

Operationally, I pair product-led growth with lifecycle marketing: product teams ship the “return-to-value” experiences; growth teams run the orchestration; customer success brings context from the field; and analytics sets guardrails and success criteria. When executed as a system, win-backs turn from occasional campaigns into a durable, compounding growth engine.

If you’re chasing growth in a tight market, start here. Your next quarter’s ARR may be sitting in dormant cohorts that are one relevant nudge—one fast path to value—away from coming back.

Inspired by this post on Amplitude – Best Practices.

November 25, 2025
Inside-Out vs Outside-In: How I Balance Both to Build Products Users Love—and CFOs Trust

Inside-out or outside-in thinking? I choose both. The strongest product strategies fuse a bold internal vision with relentless customer evidence, creating a flywheel that lifts adoption, engagement, and revenue while reducing risk.

When I lead with inside-out thinking, I articulate a clear product thesis, technical roadmap, and platform leverage. This is where we define points of parity and differentiation, sharpen our value proposition, and ensure our architecture scales. It’s disciplined, outcomes-first, and anchored in product positioning—not output checklists.

Outside-in thinking ensures that vision stays honest. I listen to customers, analyze friction in onboarding, instrument user activation, and study retention analysis to validate whether our promises translate into real user value. This is where product discovery, A/B testing, and in-app signals tell me what’s working, what needs refinement, and what we should stop doing.

In practice, I operationalize this balance through Software Experience Management. “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 the core of how I align strategy with reality inside the product, not just around it.

Concretely, I combine product analytics with in-app guides and product tours to accelerate onboarding and improve user activation. I run targeted experiments to de-risk decisions, and I iterate quickly based on what users actually do—not just what they say. The result is a product-led growth engine that compounds over time.

This approach also builds trust with finance and go-to-market partners. Inside-out clarity gives us confident, sequenced bets; outside-in data provides proof that those bets pay off. When engagement expands and adoption climbs, the business case writes itself.

If you’re deciding where to start, begin with three moves: define activation events aligned to your value proposition, instrument the experience end-to-end, and ship one high-impact in-app guide to remove a known onboarding blocker. Then measure, learn, and iterate—quickly.

The truth is, great products emerge when conviction meets evidence. Inside-out sets the vision. Outside-in earns the right to scale it.

Inspired by this post on Pendo – Perspectives.

November 12, 2025
Cut Time to Value, Boost Retention: My Proven Playbook for Activation, Growth, and Loyalty

Time to value is the most reliable early indicator of long-term user retention I know. When customers experience meaningful product impact fast, they stick around, expand, advocate, and cost less to support. Over the years leading product teams, I’ve learned that speed-to-impact isn’t a nice-to-have—it’s the engine behind sustainable product-led growth and efficient go-to-market.

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

Practically, I define time to value as the duration from first touch (or first login) to the moment a user achieves their “aha” outcome—something tangibly useful aligned to their job-to-be-done. The shorter that journey, the higher the likelihood of user activation, trial conversion, and durable engagement. This is why I obsess over onboarding, in-app guides, product tours, and the clarity of our value proposition.

My first move is to map the Minimum Path to Value (MPV): the smallest set of actions needed to deliver a real result for a new user. I strip away everything non-essential in that path—fields, clicks, choices, and jargon. Opinionated defaults, smart templates, sample data, and single-player workflows let customers succeed in minutes, not days. The goal is to reduce cognitive load while making the next best action unmistakably clear.

Instrumentation turns TTV from a hunch into a system. I track activation events, cohort retention, and conversion using platforms like Amplitude analytics and Pendo, with timely nudges through Intercom when users stall. I look at the distribution of TTV (not just the average), correlate it with retention analysis, and set explicit targets such as “new users reach first value within 10 minutes.” Those targets become team-level outcomes—not outputs—and we review them weekly.

Experimentation is how we iterate toward the fastest path to value. I rely on A/B testing to compare onboarding flows, progressive profiling to delay non-critical inputs, and opinionated setup wizards to remove guesswork. Auto-generated example projects, pre-configured integrations, and guided checklists accelerate user activation without sacrificing flexibility for advanced users.

Content and guidance matter as much as UX. Tooltips, contextual in-app guides, and short product tours should be timely, skippable, and laser-focused on the outcome, not the feature. I pair these with a concise knowledge base and short explainer videos that reinforce the same value narrative a user sees inside the product.

Cross-functional alignment is essential. Product, marketing, sales, and customer success must rally around the same activation metric and TTV target. That alignment ensures our trial messaging, onboarding emails, and CS playbooks don’t compete—they compound. When everyone points to the same first-value moment, friction drops and adoption rises.

Pricing and packaging can also accelerate time to value. Free trials should be long enough for users to credibly reach first value; usage-based gates should never block the MPV. I prefer to unlock everything needed to hit the “aha” moment, then meter after the value is viscerally felt—this respects the user’s time and reinforces trust.

There’s a cost story, too. Faster time to value reduces tickets, shortens onboarding cycles, and lowers cost-to-serve. It also clarifies product discovery: when we see where users stall, we don’t guess at roadmap priorities—we let the data guide our next bet.

In my experience at HighLevel, I’ve repeatedly seen activation rates jump when we cut time to value from days to minutes. The specific tactics vary by product, but the pattern holds: when the first outcome is undeniable and fast, retention follows—and so does efficient growth.

If you’re looking for a starting point, try this: define one activation event that clearly signals value, instrument it end-to-end, design a Minimum Path to Value that gets new users there in under 10 minutes, and run weekly experiments until you consistently hit the target. Do that, and you won’t just improve onboarding—you’ll build a product that earns loyalty from the very first session.

Inspired by this post on Amplitude – Best Practices.

November 9, 2025
The Product Playbook: Measuring Agent Performance with Pendo and Agent Analytics to Drive ROI

I treat agent performance analytics as a strategic product lever, not a back-office metric. When I combine Pendo’s product signals with Agent Analytics from our support systems, I get a unified view of where users struggle, how agents intervene, and which in-app experiences accelerate resolution. That visibility lets my team drive product-led growth and improve customer experience while lowering support costs.

Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement.

In practice, I build a clear scorecard that blends both product and support KPIs: first response time, resolution rate, first contact resolution, CSAT, containment/deflection rate, average handle time, ticket volume per active account, onboarding completion, user activation, and time-to-value. This balanced view ensures we reward not just speed, but durable outcomes that reduce repeat contacts and improve retention.

To make the data actionable, we connect our CRM integration, ticketing events, and Pendo product analytics in a unified analytics platform. That gives me cohort-level clarity—who needed help, what they were doing before opening a ticket, how agents responded, and whether users stayed engaged afterward. With clean instrumentation and consistent taxonomies, Agent Analytics becomes a reliable operating system for both product and support leadership.

I then use in-app guides, tooltips, and product tours to proactively address the top friction points that drive ticket volume. Through A/B testing, we compare cohorts exposed to guided workflows versus control groups, measuring deflection, faster task completion, and downstream conversion. When a guide meaningfully reduces tickets for a given workflow, we promote it from experiment to standard onboarding, and we feed those learnings back into our roadmap.

The real unlock comes from tying outcomes to business impact. I track how improvements in resolution quality and self-serve adoption influence expansion revenue, support cost per account, and risk signals like churn propensity. Retention analysis helps us validate whether reduced friction and better agent coaching translate into sustained engagement and healthier accounts.

Operationally, Agent Analytics helps me coach teams with precision. I spotlight high-performing behaviors, identify knowledge gaps, and standardize winning playbooks directly in the product via in-app guidance. This approach empowers agents, shortens onboarding for new hires, and keeps our best practices current as the product evolves.

None of this works without trust. We apply privacy-by-design principles and strong data governance, ensuring that analytics, coaching, and automation respect user consent and data minimization standards. With that foundation, we can scale confidently—experiment faster, learn from every interaction, and continuously improve the software experience.

If you’re getting started, begin by baselining your agent and product KPIs, ship one high-impact guide to deflect a top ticket driver, and review results weekly. Within a quarter, you’ll have a repeatable loop: diagnose friction, test an in-app solution, measure deflection and satisfaction, and reinvest the gains into the next set of improvements.

Inspired by this post on Pendo – Best Practices.

November 4, 2025
Build Customer Feedback Loops That Actually Drive Growth and Get Your Product Unstuck

What if your customer feedback loop is the reason you're stuck? Learn how to build one that fuels real growth and changes your product for the better.

I’ve seen talented teams spin for months because their customer feedback loop was noisy, slow, or misaligned with outcomes. The result is predictable: roadmaps packed with output, not impact. When we design feedback loops that are intentional, instrumented, and closed with customers, the product starts compounding value—and the business moves from reactive to product-led growth.

My definition of a strong customer feedback loop is simple: capture the right signals, synthesize them quickly, prioritize against outcomes, experiment to de-risk, and close the loop visibly with customers. If any link is weak, the whole system underperforms. More feedback isn’t better—better feedback is better.

Start with who you listen to. Segment feedback by persona, account tier, lifecycle stage, and “jobs to be done.” A founder’s feature request, a new user’s onboarding friction, and a power user’s edge case should not be weighted the same. This is the foundation of credible product discovery.

Instrument your product so qualitative and quantitative signals reinforce each other. I rely on funnel and cohort views in Amplitude analytics to see where activation or retention breaks, then layer in interviews, support tickets, and community threads for context. When telemetry and narrative align, the signal gets unmistakable.

Capture feedback where the user is. In-app guides and lightweight surveys via Pendo or Intercom surface timely prompts during key journeys (onboarding, activation, adoption, renewal). Pair those with structured inputs from sales notes and customer success reviews so you don’t bias toward only the most vocal users.

Standardize how you synthesize. Tag every item by problem statement, persona, job, and affected step in the journey. Roll these up into weekly themes your product trios can act on. The discipline here turns anecdotes into addressable opportunities.

Prioritize against outcomes, not volume. If your OKRs are outcomes vs output OKRs, tie each opportunity to a measurable product outcome like user activation rate, adoption depth, conversion, or retention. A thousand upvotes mean less than a clear path to move a core metric.

De-risk with evidence, not opinion. Frame hypotheses, define success metrics, and run A/B testing with a clear minimum detectable effect. Guardrail metrics matter—never trade a short-term click lift for a long-term retention drop. Experiments should accelerate learning, not justify pet projects.

Fold learning into product roadmapping and sprint planning. I expect prioritized feedback themes to map to roadmap bets with clear owners, milestones, and expected impact. This is how product management leadership signals what we will do—and what we will not do—based on evidence.

Close the loop, every time. Tell customers what changed because of their input—release notes, in-app messages, CSM follow-ups, or community updates. When people see their voice shaping the product, engagement and loyalty rise. This is also how you earn higher-quality feedback next time.

Set a cadence and governance that sticks. A weekly Voice of Customer review for the product trio, a monthly synthesis for cross-functional stakeholders, and a quarterly lookback tying changes to retention analysis creates organizational memory. Feedback isn’t a meeting; it’s a muscle.

Beware common failure modes. Don’t overweight loud accounts, confuse feature requests with problems, or ship one-off fixes that fragment your value proposition. Avoid vanity dashboards that show activity without decision-making power. If your loop doesn’t routinely change priorities, it isn’t a loop—it’s a suggestion box.

If you’re starting from scratch, keep it simple: define your core outcomes, instrument the top journeys, establish two capture channels (in-app and human-led), create a shared taxonomy, and commit to a weekly synthesis ritual. In a few cycles, you’ll see cleaner insights, tighter bets, and faster learning.

Done right, customer feedback loops are a competitive advantage. They sharpen product discovery, accelerate user activation, and compound retention—exactly what a modern, product-led organization needs to grow with confidence.

Inspired by this post on Product School.

November 3, 2025
Inside Our AI-Native Product Training: Accelerating Adoption, ROI, and Measurable Growth

AI is reshaping how we build products, learn new skills, and lead teams. I’ve seen great organizations stall when training lags behind technology. That’s why we rebuilt our approach to product training from first principles—so every team can operate confidently with AI at the core of their product management practice.

Our north star is simple: operationalize AI Strategy for every product manager and cross-functional partner. We designed a learning system that shortens time-to-adoption, amplifies ROI, and links capability-building to clear, measurable outcomes.

Product School transforms product teams into AI-native organizations with training that accelerates adoption, maximizes ROI, and drives measurable growth.

That ambition informs how we design curriculum and delivery. We combine gen AI foundations, LLMs for product managers, applied product discovery, product roadmapping and sprint planning, and product management leadership. The learning experience blends case-based instruction with simulations and real product data so teams practice exactly how they’ll perform.

To ensure knowledge becomes behavior, we embed training directly into product workflows: in-app guides, product tours, onboarding sequences, and user activation loops tied to outcomes vs output OKRs. This closes the gap between knowing and doing, and it makes capability visible in the metrics that matter.

We focus on empowering product teams—clarifying decision rights, elevating accountability, and creating feedback loops that enable faster iteration. When teams own their roadmap and understand the AI building blocks, they move from experimentation to repeatable, scalable value creation.

Measurement is built in from day one. We instrument for adoption, time-to-first-value, feature activation, and ROI attribution, enabling continuous improvement and transparent stakeholder communication. The result is a system that compounds learning into performance.

This is how we’re building AI-native organizations: practical, data-informed, and outcomes-driven. It’s not just training—it’s an operating model that helps teams learn faster, ship smarter, and grow with confidence.

Inspired by this post on Product School.

November 3, 2025
User Activation Is My North Star: The Most Reliable Signal Your Product Will Truly Scale

I’ve learned the hard way that growth isn’t about dashboards crowded with vanity metrics. When I evaluate whether a product is poised to scale, I start with one question: are new users truly activating? If not, everything else is noise.

"Forget vanity metrics. User activation is the compass that shows if your product or organization is lost or scaling."

When I say user activation, I mean the precise, observable milestone where a new user experiences core product value—often within their first session or first week. That might be launching a first campaign, connecting a CRM integration, or completing the key workflow that makes the product indispensable. Activation rate then becomes my primary KPI, far more meaningful than signups or pageviews because it ties directly to retention, expansion, and long-term revenue.

Why does activation predict scale? Because it’s a leading indicator of sustained product-market fit. High activation correlates with stronger retention curves, higher feature adoption, and healthier unit economics. If activation improves, cohorts decay more slowly and customer value compounds. If activation stalls, no amount of top-of-funnel spend or go-to-market strategy will save you from churn.

Here’s how I operationalize activation. First, I define the activation event from first principles, grounded in our value proposition and product positioning. I pressure-test that definition with real users through product discovery, then codify it as a measurable event so it’s unambiguous and auditable across teams.

Second, I instrument the end-to-end journey. Using a unified analytics platform with tools like Amplitude analytics and Pendo, I track time-to-value, drop-off points, and the exact steps users take before and after the activation milestone. I design experiments with a clear minimum detectable effect (MDE) so A/B testing yields decisions, not debates.

Third, I build onboarding that accelerates value realization. In-app guides, contextual product tours, and thoughtful tooltip design reduce friction while keeping users focused on the critical path to activation. Every element in onboarding earns its place by improving activation rate or shortening time-to-value—otherwise, it goes.

Finally, I align the organization around outcomes, not outputs. I set outcomes vs output OKRs tied to activation, run weekly reviews with empowered product teams and product trios, and ensure our product-led growth motion reinforces the activation moment. This creates a shared language from product to sales to customer success.

When activation rises, the path forward gets clear: retention strengthens, expansion opportunities emerge, and scaling becomes a matter of capacity rather than guesswork. When activation falters, it’s a signal to pause, refine the value narrative, and fix the experience. Either way, activation tells the truth. If you want to build a product that truly scales, make user activation your north star.

Inspired by this post on Product School.

November 3, 2025
Pendo’s Summer Release: How I Reimagine Onboarding, Support, and Expansion in the SaaS + AI Era

I’ve been reflecting on How Pendo’s Summer Release reimagines onboarding, support, and expansion in the SaaS + AI era, and it resonates deeply with the product-led playbooks my team and I use every day. The core promise is simple and powerful: “These three best practices aren’t new, but how you achieve them is.” That framing captures the shift I see across high-performing product organizations—same outcomes, radically upgraded execution through AI, in-app experiences, and unified analytics.

For onboarding, I prioritize accelerating user activation with clear product tours, in-app guides, and great UX writing that removes cognitive load. The difference now is how precisely we personalize these moments: segmentation driven by product usage, CRM integration, and experiments (A/B testing with a disciplined minimum detectable effect) help us craft paths that meet users where they are. When onboarding is instrumented this way, it becomes a scalable engine for product-led growth rather than a one-time setup task.

Support is undergoing an equally meaningful transformation. Contextual, in-app help combined with agentic AI can diagnose issues, surface relevant knowledge, and guide users without forcing channel switches. I’m bullish on this, but only when it’s anchored in privacy-by-design, AI risk management, and strong data governance—trust is the prerequisite for any customer support AI strategy. When done right, support shifts from reactive ticket resolution to proactive value delivery.

Expansion, to me, is the earned outcome of consistent product value. In the SaaS + AI era, we can use unified analytics to identify readiness signals—feature adoption, outcomes achieved, and time-to-value—and trigger timely, ethical nudges in-app. The best motions align offers with real customer milestones, whether that’s consumption SaaS pricing upgrades, role-based add-ons, or advanced capabilities unlocked through demonstrated need. This is product-led growth at its most customer-centric.

Underpinning all three motions is measurement discipline. I push for a unified analytics platform that ties together behavioral data, retention analysis, funnels, and cohorts with downstream CRM integration. That allows product trios to make fast, informed decisions and connect activation, support efficiency, and expansion to business outcomes. Whether your stack includes Pendo, Amplitude analytics, or custom pipelines, the principle is the same—one source of truth that informs action.

Execution matters as much as strategy. Empowered product teams working in tight product trios can ship small, valuable increments, run clean experiments, and learn faster than the market shifts. Strong stakeholder management and clear product roadmapping keep leadership aligned on outcomes vs output OKRs, so we’re funding what works and pruning what doesn’t. In my experience, this operational rigor is what turns promising ideas into durable competitive differentiation.

If you’re looking to operationalize these ideas, start by defining activation and expansion milestones that map to your value proposition. Instrument your in-app guides and product tours to support those milestones, and commit to an experimentation cadence with well-defined MDE. Layer in agentic AI carefully—pilot in the support surface where context is rich and stakes are clear—and enforce privacy and governance from day one. Finally, close the loop with unified analytics so every improvement compounds.

Pendo’s Summer Release highlights a broader reality: our industry isn’t inventing new destinations, we’re modernizing the routes. Onboarding, support, and expansion remain the pillars—but AI, in-app experiences, and integrated data make them smarter, faster, and more human. That’s the shift I’m leaning into—and the one customers feel immediately.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
Design Four High-Impact Lifecycle Journeys with Pendo Orchestrate to Drive Retention

I’ve spent my career building product-led growth motions that deliver value fast and build durable retention. The most consistent pattern I’ve seen is simple: When we orchestrate timely, contextual guidance inside the product, customers discover value sooner, adopt core workflows more completely, and return more often. That’s exactly where Pendo Orchestrate shines for my team.

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.

At a high level, I map the customer lifecycle into four journeys—onboarding, activation, retention, and expansion—and align each to clear outcomes. Using targeted in-app guides and product tours, behavioral triggers, and segment-specific messaging, I can optimize each stage without overwhelming users. What follows is how I approach each journey to maximize time-to-value and retention.

Onboarding: I design progressive onboarding that adapts to a user’s role and first-run actions. Instead of a single, long product tour, I use short, contextual nudges that appear exactly when a user reaches a relevant screen or performs a key event. This reduces cognitive load, shortens time-to-value, and sets up a reliable path to initial success. When needed, I A/B test different sequences and measure impact on activation rate to ensure we’re improving the real user experience, not just adding more guidance.

Activation and habit-building: After first value, I focus on reinforcing the behaviors that correlate with long-term retention. Here, lightweight tooltips, celebratory moments when users reach the “aha” action, and just-in-time prompts for adjacent features help form habits. I track cohort-level activation metrics and use retention analysis to see whether these nudges translate into sustained product usage. If a segment stalls, I adjust copy, timing, or the sequence to better match user intent.

Retention and re-engagement: Not every customer stays on a steady path. For at-risk cohorts—users who haven’t completed a critical workflow or whose usage is declining—I trigger helpful, empathetic in-app guides that remove friction and offer a direct path back to value. I also solicit lightweight feedback to understand obstacles. The goal isn’t to interrupt; it’s to make it effortless to recover momentum.

Expansion and upsell: When users demonstrate readiness—mastery of core features, frequent usage, or role-based signals—I introduce advanced capabilities with targeted product tours and clear value propositions. Timing is everything; I prefer unobtrusive prompts that appear at the exact moment their workflow benefits from an upgrade. By matching message to milestone, expansion feels like a service, not a sell.

Operationalizing these journeys starts with crisp definitions of success (activation, adoption depth, and retention), thoughtful segmentation, and a cadence of experimentation. I keep the loop tight: instrument key events, launch small, measure outcomes, and iterate. Over time, the orchestration becomes a durable system—consistently delivering the right guidance to the right user at the right moment, and continuously compounding product impact.

If you’re looking to scale product-led growth, these four journeys provide a pragmatic blueprint. Start with the stage that’s hurting most (often onboarding), prove the lift, then expand. As outcomes improve, your users feel supported, your product experience feels intuitive, and your business earns the retention and expansion it deserves.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
4 Proven Ways GTM Teams Drive Explosive Growth with Pendo’s HubSpot Integration

In my role leading product management, I’ve learned that the most reliable path to product-led growth is aligning product signals with the systems our go-to-market teams use every day. That’s exactly where Pendo’s HubSpot integration shines—by merging behavioral insights with CRM context so sales, marketing, customer success, and product move in lockstep.

See how customer behavioral data can help sales, marketing, customer success, and product teams create a better, more engaging customer experience.

First, I use the integration to create a single source of truth that blends in-app behavior with account and contact data. When product usage, feature adoption, and intent signals flow into HubSpot, lead scoring becomes smarter, pipeline quality improves, and our go-to-market strategy gets more precise. Reps prioritize the right accounts, marketing tunes messaging to demonstrated needs, and we operate as a unified analytics platform instead of scattered tools.

Second, I activate lifecycle journeys directly from HubSpot using in-app guides and product tours. By targeting experiences based on CRM stage or persona, onboarding accelerates, trial conversion increases, and time-to-value drops. The ability to personalize onboarding without engineering work gives marketing and customer success a powerful lever to deliver exactly the right guidance at the right moment.

Third, I orchestrate customer success playbooks that reduce churn and expand revenue. Health scoring improves when retention analysis is informed by real product usage, not just survey sentiment. When usage dips below a threshold, HubSpot workflows trigger save-plays; when product engagement surges, we operationalize expansion motions across self-serve upgrades and account-based upsell. The result is a tighter feedback loop between product adoption and revenue outcomes.

Fourth, I close the loop between sales, product, and marketing to refine product positioning and roadmap priorities. Signals from Pendo in HubSpot highlight which features correlate with win rates and renewals, so we double down on the value proposition that actually converts. Those same insights inform targeted campaigns, sharper messaging, and a continuous learning cycle across GTM and product teams.

To make this work in practice, I start with clear event taxonomies, privacy-by-design data governance, and tightly scoped use cases that we can measure within a quarter. We iterate with small A/B tests, compare outcomes to baselines, and socialize wins across sales, marketing, and customer success to build momentum. The integration becomes more than a data pipe—it’s an operating system for coordinated growth.

When product signals meet CRM workflows, teams stop guessing and start executing with confidence. That’s the power of Pendo’s HubSpot integration: it operationalizes product-led growth across the entire customer journey, from first touch to expansion.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
Pendo Admin Power Checklist: 4 Proven Practices to Drive Adoption, Clarity, and Trust

Overseeing complex platforms like Pendo is where product leadership comes to life. I rely on four disciplined practices to keep our instrumentation clean, our in-app experiences on-brand, and our analytics credible enough to guide high-stakes decisions. If you’re setting up or tuning your instance, this checklist will help you build trust with stakeholders and accelerate product-led growth.

Learn best practices that every Pendo admin should know.

1) Standardize tagging and taxonomy. I start by defining a clear naming convention for feature tags, page tags, and track events (for example, feat:[area]:[action]). This taxonomy lives in a shared document, aligns to our product roadmapping and sprint planning, and includes ownership, definitions, and “do/don’t” examples. In practice, this reduces duplicates, improves segment reliability, and makes funnels, paths, and retention analysis far more actionable. I also schedule quarterly hygiene to retire stale tags and revalidate critical measures tied to OKRs.

2) Segment deliberately and manage access with intention. Meaningful segments—role, lifecycle stage, plan tier, and account health—unlock precise targeting for in-app guides and stronger insights. On the admin side, I enforce least-privilege access with SSO/SCIM, audit changes to tags and guides, and keep visitor and account ID strategies consistent across environments. This combination strengthens data governance and privacy-by-design while reducing operational risk.

3) Operationalize a guide lifecycle. In-app guides are powerful, but only when they’re coherent and governed. I maintain a style system and reusable templates for tooltips, walkthroughs, onboarding checklists, and the Resource Center so the UX feels intentional, not noisy. Every guide goes through QA in staging, frequency capping, sunset dates, and an owner accountable for outcomes. I measure impact with clear success metrics—adoption lift, funnel completion, or onboarding time—to ensure guides serve the product strategy, not just add UI clutter.

4) Build an analytics cadence that leaders can trust. I treat Pendo as a decision system, not just a dashboard. That means SDK updates are part of our release checklist, known key events are smoke-tested after deployments, and weekly insight reviews turn funnels, paths, and retention analysis into clear actions. Where appropriate, I pair experiments with A/B testing guardrails and tie findings back to outcomes vs output OKRs. Finally, I publish a simple “what we learned” summary to keep stakeholders aligned and focused on the next best move.

Your 5‑minute checklist: confirm a shared tagging taxonomy; align segments to roles, lifecycle, and plans; apply least-privilege access and SSO/SCIM; standardize guide templates and QA; set metrics for every guide; and establish a recurring analytics review tied to OKRs. With these four practices in place, your Pendo instance becomes a flywheel for onboarding, product adoption, and continuous discovery—without sacrificing governance or customer trust.

If you’re scaling quickly, start small: pick one product area, instrument it cleanly, launch a targeted in-app guide, and run a focused funnel review the following week. Momentum builds when teams see crisp insights and customers feel helpful guidance at just the right moment.

Inspired by this post on Pendo – Best Practices.

October 25, 2025