Tag: Pendo

The Only 3 Dashboards Product Executives Actually Use to Drive Outcomes, Alignment, and Growth

I’ve learned the hard way that more charts don’t equal more clarity. One challenge that comes with this is knowing what matters at the right level of leadership. Executives everywhere are busy, and they don’t need the nitty-gritty details to do their jobs well. When I’m operating at the VP level, I rely on just three dashboards that give me fast signal, reduce noise, and keep teams aligned to outcomes—not output.
These dashboards sit on top of a unified analytics platform that connects product analytics (Amplitude analytics or Pendo), CRM and revenue data (e.g., HubSpot), billing, and support signals. Consistent definitions, data governance, and outcomes vs output OKRs ensure we’re making decisions with confidence, not gut feel. The goal is simple: a shared, executive-ready view that ties product strategy to business impact.
Dashboard 1: Outcomes and Strategy Alignment. This is the north star view I use to orient the company. It highlights ARR, NRR, and GRR trends; progress against our outcomes vs output OKRs; our product-led growth funnel; and our primary value proposition metric (e.g., activation-to-time-to-value). I include a 12-month view with quarter-over-quarter deltas, a short written narrative, and the top three strategic bets we’re funding. In board management and QBRs vs OKRs discussions, this keeps focus on what we achieved, what moved, and what we’re changing next.
Dashboard 2: Customer Value, Adoption, and Retention. This is where retention analysis meets product discovery. I track activation rate, time-to-value, feature adoption cohorts (from Amplitude analytics or Pendo), retention curves by segment, and expansion vs contraction signals. Leading indicators include NPS and CES alongside qualitative themes from support and sales. I also monitor funnel drop-offs and in-app guides or product tours performance to see where users get stuck. The intent is to connect behavior to revenue so we can prioritize changes that actually improve customer outcomes.
Dashboard 3: Execution Health and Quality. This helps me assess whether our operating system is working. I look at delivery predictability against product roadmapping and sprint planning, cycle time and throughput, escaped defects, incident volume, and MTTR. I also review experiment velocity and A/B testing readiness (including minimum detectable effect) to ensure we’re learning at pace. Resource allocation across strategic initiatives and a clear risk register support proactive stakeholder management.
I review these dashboards weekly with my product trios and monthly with cross-functional leaders, then synthesize a concise narrative for the executive team and the board. Each dashboard is a decision engine: it has an owner, a single source of truth, clear thresholds, and a list of next actions. By grounding conversations in the same views, we reduce back-and-forth and keep momentum high.
A few implementation rules have served me well: keep the signal dense and the visuals simple; lock metric definitions and ownership; avoid vanity metrics; and instrument privacy-by-design from the start. When data is trustworthy and the story is tight, teams focus on the right problems and progress compounds.
If you find yourself wading through dozens of reports, try consolidating to these three executive dashboards. You’ll spend less time arguing about the data and more time driving product-led growth, accelerating alignment, and delivering customer value at scale.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
Urgent Alert: Spot Fraudulent Job Offers Impersonating Pendo—and Protect Your Career

In my role leading product management, I take brand trust and cybersecurity seriously—especially when it affects people’s livelihoods. Over the past few weeks, I’ve seen a troubling uptick in brand impersonation and social engineering targeting candidates. It’s a reminder that protecting our community isn’t just a technical problem; it’s a product management leadership and stakeholder management responsibility.

We want to warn you about recent instances of fraudulent job offers purporting to be from Pendo and/or its affiliate companies.

If you receive an unexpected outreach claiming to be from Pendo with a fast-track offer, requests for payment, or a push to move conversations to informal channels, treat it as a red flag. Scammers often spoof logos, clone profiles, and use vague role descriptions to create urgency. Their goal is to extract personal data, money, or access—classic social engineering tactics that undermine data governance and privacy-by-design principles.

Here’s how I advise candidates to protect themselves while keeping their job search momentum. Validate every opportunity through the company’s official careers page and confirm the recruiter’s identity through corporate channels. Check that email addresses and domains match publicly listed corporate information, and be wary of communication conducted exclusively through messaging apps. Never pay fees, buy equipment up front, or share sensitive data like Social Security numbers or banking information before a formal, verified offer is in place.

If something feels off, pause and verify. Contact the company via the channels listed on its website, ask for a video meeting with the recruiter using an official corporate account, and request written details on the role and interview process. If it’s fraudulent, report it to the company, the platform where the outreach occurred, and—when appropriate—local authorities. Acting quickly helps with threat detection and response and protects other candidates from harm.

From a product and security perspective, this is a cross-functional issue that benefits from AI risk management discipline. Strong signals include clear public guidance on recruiting practices, a dedicated reporting mailbox for suspected scams, and hardened email authentication (SPF, DKIM, DMARC). Pair these with privacy-by-design reviews for hiring workflows, recruiter verification checklists, and ongoing education for talent teams. These measures reduce attack surface while reinforcing brand integrity.

If you believe you’ve shared information with a fraudulent recruiter, take immediate steps: change any reused passwords, enable two-factor authentication, place fraud alerts or freezes with credit bureaus as appropriate, and monitor accounts for suspicious activity. Document all communications; they can help security teams and platforms act faster.

Recruitment fraud is emotionally taxing and can erode confidence in the process. Don’t let scammers slow your momentum. Stay vigilant, verify before you trust, and share this warning so others can avoid similar traps. If you’re ever unsure about a message that appears to come from Pendo, pause, validate through official channels, and prioritize your safety first.

Inspired by this post on Pendo – Perspectives.

October 25, 2025
4 Costly Misconceptions About AI Agents—and What Product Leaders Must Do Instead

Building AI agents looks deceptively simple right now. After leading multiple agentic AI initiatives, I’ve learned that the difference between a demo and a dependable product comes down to disciplined product discovery, ruthless scoping, and a clear AI Strategy that aligns with business outcomes. Here are four common misconceptions I correct early with stakeholders—and the practices I use to avoid expensive detours.

Misconception 1: “An LLM plus a few prompts is a production-ready agent.” In reality, production-grade agents require orchestration and rigor: tool-use and retrieval, memory design, state management, deterministic fallbacks, and continuous evaluation. I instrument Agent Analytics from day one to trace tool calls, latency, error codes, and cost per task; then I use A/B testing with a clear minimum detectable effect (MDE) to validate improvements before broad rollout. This is where product roadmapping and sprint planning matter—sequencing capabilities so we avoid building speculative features that don’t move outcomes.

Misconception 2: “More autonomy is always better.” The right autonomy level is contextual and risk-adjusted. For high-stakes workflows, I design for human-in-the-loop and role-based guardrails, grounded in privacy-by-design and data governance. Policies like least-privilege access, audit logs, and reversible actions reduce operational risk while still delivering leverage. In practice, this hybrid approach also controls cost: narrower scopes, clearer prompts, and bounded tool access reduce hallucination surface area and improve reliability—key to AI risk management.

Misconception 3: “If we build it, users will adopt it.” Adoption is earned with thoughtful onboarding and in-app guidance, not promised by a feature launch. I pair agent launches with targeted product tours, contextual tooltips, and progressive disclosure to drive user activation and product-led growth. Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement. Whether you use Pendo or a comparable solution, the principle stands: instrument the experience, run experiments, and iterate quickly based on evidence, not intuition.

Misconception 4: “Security, compliance, and governance can wait.” Deferring controls is a false economy. I embed AI risk management from day zero: prompt injection defenses, PII redaction, DLP, grounding and citation strategies, and threat detection and response. Clear data retention policies, vendor diligence, and model evaluation standards keep leadership, security, and legal aligned. This is the crux of building trust—and it’s far easier to design up front than to retrofit under pressure.

How I execute in practice: start with a tightly framed use case tied to a measurable outcome; define outcomes vs output OKRs; build a slim vertical slice to validate feasibility; instrument Agent Analytics from the first commit; ship behind feature flags; and operationalize learning loops across support, success, and GTM. The result is a durable path to product-market fit for agentic AI—one that compounds learning while minimizing blast radius.

The leaders who win with AI agents won’t be the ones who move fastest in a demo. They’ll be the ones who manage risk transparently, learn in public with their users, and turn continuous insight into competitive differentiation. If you’re planning your next agent milestone, align the roadmap to outcomes, treat governance as a feature, and make adoption your North Star.

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
SXM vs. the Rest: My High-Impact Playbook for Today’s Software Experience Tools and PLG

I spend a lot of time reviewing how customers move through our product and where their momentum stalls or accelerates. The tools you use to build and optimize software experiences are evolving. That simple truth reshapes our strategy every quarter, from the analytics we trust to the in-app touchpoints we design and the experiments we run to improve product-led growth.

When I say SXM, I’m talking about a comprehensive software experience management approach that unifies analytics, experimentation, in-app guides, messaging, and feedback loops. SXM vs. the rest is the real-world choice between an integrated platform and a patchwork of point solutions. I’m not married to one path; I’m obsessed with outcomes—speed to learning, lower friction for teams, and compounding retention gains.

The foundation is a unified analytics platform and a clean, consistent event schema. From there, I pair behavior analytics with in-app orchestration: tools like Amplitude analytics for deep behavioral insights and Pendo for targeted in-app guides, product tours, and contextual nudges. I instrument rigorous A/B testing with a clearly defined minimum detectable effect (MDE) and follow through with retention analysis to validate whether an uplift sticks beyond vanity metrics. Great UX writing and thoughtful tooltip design often make the difference between a nudge that converts and a prompt that gets ignored.

I choose between best-of-breed and platform consolidation using first principles decision making. If a point solution unlocks a capability that meaningfully advances our product discovery or activation work, I adopt it. If multiple tools converge on the same points of parity, I consolidate to streamline governance, reduce integration overhead, and accelerate delivery. The goal is not more software; it’s faster, clearer learning that informs product positioning and drives customer value.

AI now sits at the center of this stack. I apply gen ai and agentic AI to accelerate hypothesis generation, automate cohort detection, draft UX microcopy, and suggest next-best actions inside the product. That said, AI risk management, privacy-by-design, and data governance are non-negotiable. I won’t trade trust for tempo; we can have both by putting guardrails around training data, access controls, and evaluation criteria.

Operating rhythm matters as much as tooling. Product trios set outcomes vs output OKRs, then test and iterate—starting with onboarding, activation, and the moments that trigger value realization. We build in measurable in-app guides, run A/B testing with tight feedback cycles, and keep our go-to-market strategy aligned so every nudge, message, and feature release supports product-led growth.

My playbook is simple: clarify the outcomes, instrument the journey end-to-end, choose the smallest toolset that can answer the biggest questions, and learn faster than the market. Map critical paths, standardize taxonomy, and make experimentation a habit—not a project. Then double down where signal is strongest and retire anything that adds minimal lift to retention or expansion.

SXM isn’t a buzzword; it’s a disciplined way to build software that feels intuitive, responsive, and valuable from the first click. With the right blend of analytics, in-app guidance, experimentation, and AI—grounded in strong product management leadership—we can turn insights into momentum and momentum into durable growth.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
How I Scale Revenue with Pendo Predict: Cut Costs, Reduce Risk, and Drive Product Adoption

When my team and I set out to accelerate growth without ballooning costs, we leaned into Pendo Predict as a keystone of our product-led growth strategy. Predict gives us a practical, data-driven way to focus on the right users at the right moments, align teams around measurable outcomes, and turn product usage signals into revenue impact.

“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 statement maps exactly to how we operate: we use the platform to understand user behavior, guide users through high-value actions, and instrument the experience so we can learn, iterate, and scale with confidence.

To scale revenue, we identify high-intent segments based on product behaviors and run targeted in-app guides and product tours that shorten time-to-value and boost conversion. Predict helps us surface which features correlate with expansion and retention, so our onboarding flows nudge users into those paths. This approach compounds: better activation drives stronger engagement, which fuels a healthier pipeline for cross-sell and upsell.

On the cost side, we reduce support load with contextual guidance—tooltips, checklists, and just-in-time education—so customers self-serve through common friction points. We consolidate insights in a unified analytics platform, enabling product, success, and go-to-market teams to work from the same source of truth. The result is fewer reactive escalations, tighter prioritization, and more engineering time invested in features that move retention and revenue.

Risk reduction comes from visibility and control. With predictive signals and retention analysis, we spot churn risk early, intervene with timely in-app messaging, and de-risk launches by rolling out features to targeted cohorts while monitoring adoption and engagement. We pair this with disciplined experimentation and A/B testing to validate changes before scaling broadly.

If you’re considering a similar motion, a simple playbook works: define your adoption and engagement metrics, instrument key workflows, create predictive segments, ship focused in-app guides, and measure impact against outcomes—not just outputs. Over time, this turns your product into a durable growth engine that consistently improves user experience and business performance.

Inspired by this post on Pendo – Best Practices.

October 24, 2025
How AI Is Supercharging Product Design: Faster Prototyping, Smarter Testing, and Better UX Outcomes

AI has fundamentally changed how I lead design and testing, not by replacing craft, but by compounding it. When my teams pair generative models with time‑tested product management practices, we move faster, learn sooner, and ship with more confidence—without compromising privacy-by-design or quality. The result is a tighter loop from product discovery to product-market fit lessons. Learn how Pendo’s product design team is using genAI and traditional tools to speed up design and development. That single line captures my own operating model: blend genAI with established toolchains to accelerate, not shortcut. In practice, I treat AI as a force multiplier for product trios—PM, design, and engineering—so empowered product teams can explore broader solution spaces while staying anchored to outcomes vs output OKRs. In discovery, genAI helps me synthesize qualitative inputs at scale—interviews, support threads, and in-app behaviors—into testable opportunity statements. I triangulate those insights with a unified analytics platform and Amplitude analytics to spot friction, then use in-app guides and product tours to target learning, recruit the right cohorts, and validate problems before we overbuild. For prototyping, gen ai for product prototyping is a game-changer. I generate multiple UX writing variants, microcopy, and flows in minutes, then narrow the set using heuristics and stakeholder feedback. Before any A/B testing, we precompute the minimum detectable effect (MDE) and sample size, making sure our experiments are powered to detect meaningful differences, not noise. In testing, I combine classic A/B testing with AI-assisted analysis to surface patterns faster. GenAI drafts experiment summaries, flags anomalous segments, and proposes follow-up tests, while my team makes the final calls. We deploy targeted in-app guides to onboard users into trials, monitor adoption via event telemetry, and iterate quickly until the value proposition is unmistakable. Execution depends on rigor and guardrails. We codify AI risk management and data governance policies, keep humans-in-the-loop for critical judgments, and log model prompts and outputs for auditability. This lets us move with speed and integrity, aligning stakeholder management, product roadmapping and sprint planning, and go-to-market strategy around measurable outcomes. The payoff is material: shorter cycle times, clearer value narratives, and stronger product-led growth curves. By fusing genAI with traditional practices, we preserve the craft of design while scaling our capacity to learn. That’s how we differentiate—through faster insight generation, smarter testing, and experiences that feel unmistakably intuitive.

Inspired by this post on Pendo – Best Practices.

October 24, 2025
Prioritize, Build, and Measure AI with Confidence: Lessons I Apply from PendomoniumX NYC

AI is moving faster than any product wave I’ve seen in my career, and that urgency demands rigor. At HighLevel, I anchor our AI Strategy around measurable outcomes, responsible delivery, and pragmatic execution—principles that a recent PendomoniumX NYC customer discussion reinforced for me. “Three product leaders sat down with Pendo to discuss how they’re balancing AI investments, building their AI roadmap, and measuring success.” When I decide what to fund, I start with outcomes vs output OKRs. If an initiative cannot tie to a defensible customer outcome—time-to-value reduction, revenue expansion, retention lift, or cost-to-serve efficiency—it doesn’t make the cut. From there, I pressure-test feasibility and risk through data governance and AI risk management lenses: model choice, training data readiness, privacy-by-design, security posture, and responsible use guardrails. Building the roadmap is where discipline meets speed. I use empowered product teams—product trios across PM, design, and engineering—to run tight discovery sprints. We validate desirability and viability with gen ai for product prototyping, then graduate concepts into delivery using product roadmapping and sprint planning habits that prioritize smallest shippable value. I’ve found the try do consider framework helpful to stage bets from low-risk utilities to higher-impact, agentic AI workflows. Measuring impact is nonnegotiable. I define success up front with a minimum detectable effect (MDE), then instrument adoption and behavioral change via Pendo and Amplitude analytics. A/B testing gives me causal confidence, while retention analysis tells me if AI features are durable value, not novelty. If we can’t attribute improvement to a metric that matters, we iterate or retire. Governance is a product requirement, not an afterthought. We maintain data governance standards, threat detection and response controls, and clear model evaluation criteria before anything reaches customers. That operating model helps us move quickly without compromising trust—a cornerstone in any product-led growth motion. For go-to-market and adoption, I rely on in-app guides, product tours, and contextual tooltips to shorten the learning curve. We measure feature discovery, task completion, and ongoing engagement to ensure the experience is intuitive. The goal is to make AI feel like a natural extension of the workflow, not a science project bolted onto the product. My simple playbook: prioritize by customer outcomes and risk posture, build with validated learning and smallest shippable value, and measure with rigorous analytics and OKRs. Repeat that loop, and AI stops being a buzzword—it becomes a compounding advantage.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
The Real Reason Pendo Built Agent Analytics—and How It Drives Adoption, Revenue, and Trust

I’ve learned the hard way that the toughest part of launching in-app agents and guided experiences isn’t the build—it’s proving, quickly and credibly, that they move the business. If I can’t quantify adoption, engagement, deflection, and time-to-value, stakeholder confidence erodes and iteration slows. That’s exactly why an Agent Analytics capability matters: it turns opaque interactions into measurable outcomes that product, customer success, and engineering can all act on.

When I evaluate a capability like Agent Analytics, I anchor on a few questions. Which segments adopt the agent, and where does engagement drop? What fraction of issues are successfully deflected versus escalated? Which prompts, product tours, and in-app guides drive conversion and retention—and which add friction? How does agent usage correlate with onboarding completion, core feature activation, and long-term retention analysis? If I can answer those with a unified analytics platform, I can prioritize confidently.

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 map an outcomes-first measurement plan: define a north-star (e.g., activated accounts), articulate contributing metrics (guide completion rate, agent task success, session depth), then run targeted A/B testing on copy, timing, and placements. With the right analytics, I can compare cohorts exposed to in-app guides and product tours against a control, validate impact, and double down on the patterns that consistently improve adoption and stickiness.

Cost and risk are just as important as growth. An effective Agent Analytics view helps me model support deflection, time-to-resolution, and escalation rates so I can quantify cost savings without sacrificing quality. On the risk side, I look for early-warning signals—low-confidence responses, repeated handoffs, or anomalous usage—so I can intervene before they turn into churn or brand concerns. The point isn’t vanity metrics; it’s operational clarity that enables responsible, scalable product-led growth.

This also changes team dynamics. Product trios get a shared source of truth for decisions, engineering gains sharper specs informed by real behavior, and customer-facing teams can see which experiences reliably unlock value for each segment. Instead of debating opinions, we iterate on evidence—tightening the loop between product roadmapping and sprint planning, UX writing, and go-to-market strategy.

My 90-day playbook looks like this: establish a baseline for adoption and engagement; instrument agent interactions end to end; ship two or three small, high-leverage experiments in onboarding and help experiences; and review results in weekly rituals. By day 90, I expect to see a clear line from agent engagement to activation and retention, along with a repeatable testing cadence that compounds learning.

I’ve seen the same pattern across products and markets: once teams illuminate the black box of in-app assistance with rigorous, actionable analytics, customer confidence rises, onboarding accelerates, and roadmaps get sharper. If you’re evaluating Pendo or already running it, put Agent Analytics at the center of your measurement strategy—and let your data, not assumptions, guide the next iteration.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
5 powerful reasons I can’t wait for INDUSTRY 2025: The Product Conference to supercharge strategy

I’m gearing up for INDUSTRY 2025: The Product Conference in Cleveland, Ohio, and I can already feel the energy that comes when the brightest product minds gather. As someone who lives at the intersection of product management leadership, execution discipline, and customer-centric innovation, this event is where I refine my craft and pressure-test my roadmap against the best.

Join Pendo at INDUSTRY in Cleveland, Ohio.

Reason 1: Elevate strategy from outputs to outcomes. I’m looking forward to sharpening how we align outcomes vs output OKRs with product roadmapping and sprint planning. INDUSTRY consistently surfaces practical frameworks to translate vision into measurable value—exactly what empowered product teams need to prioritize with confidence and communicate trade-offs to stakeholders.

Reason 2: Deepen discovery with data that actually drives decisions. I plan to compare notes on product discovery techniques that blend qual and quant—pairing interviews with a unified analytics platform, retention analysis, and a clear minimum detectable effect (MDE) to validate signal. The bar keeps rising on evidence-based decisions, and I’m eager to bring back new ways to reduce bias while accelerating learning.

Reason 3: Double down on product-led growth. From onboarding to activation, I’m focused on refining in-app guides and product tours that meet users at the moment of need. INDUSTRY is a great place to trade patterns for scalable, context-aware experiences that convert, retain, and expand without adding friction—fueling a durable product-led growth motion.

Reason 4: Build a responsible, practical AI Strategy. The conversations around gen ai for product prototyping, agentic AI, data governance, and privacy-by-design are evolving fast. I’m excited to learn how teams are balancing speed with AI risk management—turning experimentation into real features while protecting customers and preserving trust.

Reason 5: Level up leadership and influence. Product management leadership is as much about people as it is about prioritization. I’m excited to trade tactics on stakeholder management, strengthening product trios, and growing ICs through the IC to manager transition. These are the muscles that turn strategy into momentum.

Between keynotes, hallway conversations, and hands-on sessions, I plan to leave Cleveland with fresh approaches to discovery, clearer OKR alignment, and new ideas to operationalize PLG at scale. If you’re passionate about building products that customers love—and businesses rely on—let’s connect and compare notes on what’s working now.

I’ll share my takeaways after the conference, including actionable frameworks, templates, and experiments to run with your teams the very next sprint. If you see me in a session on analytics, onboarding, or AI, say hello—I’m always up for a quick debrief and a few what-would-it-take questions.

Inspired by this post on Pendo – Perspectives.

October 24, 2025