Tag: A/B testing

11 Unconventional Product Management Moves That Supercharge Strategy, Teams, and Impact

I’ve spent years leading product strategy at HighLevel, Inc., and the patterns I rely on don’t always show up in the usual playbooks. In practice, the moves that compound impact are often the quiet ones—unsexy, rigorous, and relentlessly customer-centered.

These product management best practices challenge the norm. Read and you’ll sharpen your strategy and elevate your impact beyond just features.

What follows are the 11 under-discussed habits I return to when the stakes are high and the path is foggy. They help me ship meaningful outcomes, develop empowered product teams, and align our go-to-market strategy without getting trapped in feature theater.

Best practice 1 — Anchor goals to outcomes, not output. I frame “outcomes vs output OKRs” so teams focus on behavior change and business results, not ticket counts. Activation rate, retained revenue, and cycle time beat launch volume every time.

Best practice 2 — Run discovery with product trios. I put design, engineering, and product in the same room early, often with forward deployed engineers. This trio model accelerates product discovery, uncovers risks faster, and builds shared ownership.

Best practice 3 — Decide from first principles, then apply the try do consider framework. I separate points of parity from true differentiation and protect our value proposition. The result: clearer choices, less rework, and a strategy that compounds.

Best practice 4 — Be statistically honest with A/B testing. I size experiments by minimum detectable effect (MDE), guard against peeking, and follow through with retention analysis. This discipline prevents false positives from steering the roadmap.

Best practice 5 — Treat delivery as a learning engine. CI/CD, feature flags, and progressive rollouts let us learn without gambling the brand. I track deployment frequency and DORA metrics to raise quality while increasing the tempo of validated learning.

Best practice 6 — Build a unified analytics backbone. I connect product telemetry to a unified analytics platform and CRM integration so we can see the full funnel. Amplitude analytics, Pendo, and Intercom help us tie behaviors to value realization and inform prioritization.

Best practice 7 — Make onboarding a first-class product. In-app guides, product tours, UX writing, and thoughtful tooltip design shorten time-to-value and lift user activation. This is the quiet lever behind sustainable product-led growth.

Best practice 8 — Systematize stakeholder management. I pair QBRs vs OKRs to balance narrative and numbers, keep board management transparent, and align sequencing through product roadmapping and sprint planning. Clear rituals minimize thrash and build trust.

Best practice 9 — Connect strategy to positioning early. I pressure-test product positioning, clarify our value proposition, and deliberately choose which points of parity to match and which to ignore. This reduces me-too work and sharpens competitive differentiation.

Best practice 10 — Use AI as a responsible force multiplier. I employ LLMs for product managers and gen ai for product prototyping while enforcing privacy-by-design, AI risk management, and strong data governance. The goal is leverage without compromising trust.

Best practice 11 — Write it down to move faster together. I keep crisp decision logs, assumptions, and pre-mortems so empowered product teams can act with context. This simple habit makes onboarding easy, reduces re-litigating, and keeps momentum through change.

When I apply these practices consistently, the team ships less noise and more value. The compounding effect is real: clearer priorities, faster learning cycles, stronger alignment, and a roadmap that tells a coherent story from discovery to adoption.

Inspired by this post on Product School.

November 3, 2025
Scale Product Operations with Confidence: Hard-Won Lessons to Drive Experimentation and Value

Scaling product operations across markets and teams is equal parts craft and discipline. Over the years, I’ve distilled what works into a pragmatic operating system that balances speed with rigor, enables experimentation at scale, and keeps the entire organization aligned on customer value.

Learn how top product leaders at leading companies scale product operations, drive experimentation, and deliver customer value.

The backbone is a clear outcomes-first operating model. I anchor strategy in outcomes vs output OKRs, empower product trios to own problem discovery and solution delivery end to end, and insist on empowered product teams that can make decisions without waiting for permission. This structure raises the signal-to-noise ratio, reduces handoffs, and accelerates learning.

Operational excellence then turns intent into predictable flow. CI/CD pipelines, high deployment frequency, and DORA metrics give me a real-time view of delivery health while creating the safety to ship smaller, reversible changes. When teams can deploy confidently and measure impact continuously, execution quality and morale both improve.

Experimentation is a first-class citizen, not an afterthought. We normalize A/B testing by defining a minimum detectable effect (MDE) up front, instrumenting guardrails for customer experience, and pre-registering success criteria. This keeps experiments honest, speeds up decision-making, and makes it clear when to iterate, when to scale, and when to stop.

Data turns experiments into insight. I lean on a unified analytics platform, with tools like Amplitude analytics for product discovery, activation, and retention analysis. Standardized taxonomies and event quality reviews ensure we can trust the numbers, compare tests, and build cumulative knowledge rather than running one-off trials.

To translate insight into adoption, I invest in product-led growth mechanics. In-app guides, product tours, and thoughtful tooltip design help users discover value fast, while lifecycle nudges align with milestones in the journey. This reduces the burden on sales and success while compounding engagement and retention over time.

Governance should enable, not constrain. Lightweight data governance and privacy-by-design practices mean experiments respect user trust and regulatory requirements without slowing teams down. Clear review paths and pre-approved templates make it easier to do the right thing quickly.

Alignment is continuous, not quarterly theater. I connect strategy and execution with crisp product roadmapping and sprint planning, and I reconcile learning cycles with planning cycles so insights flow into the next iteration. QBRs evolve from status updates into decision forums where we reallocate capacity based on evidence, not opinion.

Here’s the playbook I rely on: clarify the few outcomes that matter; form durable product trios around customer problems; instrument ruthlessly so every change is measurable; operationalize experimentation with A/B testing, MDE, and guardrails; and maintain fast flow with CI/CD and DORA metrics. When this system hums, teams move faster, risk goes down, and customers feel the improvement in every interaction.

At scale, excellence looks deceptively simple: clear outcomes, empowered teams, fast and safe delivery, and relentless learning. Get those right and product operations become a force multiplier—one that compounds customer value with every release.

Inspired by this post on Product School.

November 3, 2025
10 Customer Acquisition Metrics I Obsess Over to Predict Growth (and Kill Vanity KPIs)

Stop chasing the wrong numbers! Learn which customer acquisition metrics actually point the way to growth and which to leave behind.

In my role leading product and growth, I’ve learned that sustainable acquisition comes from a disciplined focus on a few decisive signals. I run a tight scorecard that blends product-led growth inputs with sales-assisted outputs, stitched together in a unified analytics platform and grounded in our CRM integration. Tools like Amplitude analytics, HubSpot, Pendo, and Intercom help me see the entire journey—from first touch to user activation and revenue—without getting lost in dashboard noise.

ICP-qualified lead rate (MQL-to-SQL conversion) is my first gate. If qualified interest isn’t turning into sales conversations, I know our targeting, messaging, or handoff is off. This metric forces alignment between marketing and sales on the actual Ideal Customer Profile and disqualifies the “traffic for traffic’s sake” mindset.

Lead Velocity Rate (LVR) tells me whether next quarter’s growth is compounding. I track the month-over-month growth of qualified leads and opportunities, not raw leads. When LVR dips, I revisit go-to-market strategy and pipeline sources before the lagging revenue number shows trouble.

Activation rate is the heartbeat of product-led growth. I define a clear “first value” action and measure what percentage of new signups reach it within a set time window. Strong activation signals that our onboarding and value proposition are resonating; weak activation pushes me to refine in-app guides, product tours, and tooltip design.

Time-to-Value (TTV) measures how quickly new users experience the core benefit. Shorter TTV correlates with higher conversion, better retention, and lower support costs. I routinely A/B test onboarding steps, copy, and default settings to shave minutes off TTV without sacrificing comprehension.

Customer Acquisition Cost (CAC) by channel keeps us honest. I break out CAC for paid, organic, partner, and sales-led motions, then double-click into cohort performance. Channel-level CAC, tied back to revenue quality, helps me reallocate budget and resist the allure of cheap but low-intent clicks.

CAC payback period is my sanity check on efficiency. I want to know how many months of gross margin it takes to recover CAC—across each motion. When payback creeps up, we revisit pricing, packaging, onboarding friction, and top-of-funnel quality simultaneously.

LTV:CAC ratio shows whether we’re buying durable revenue. I pair it with retention analysis to avoid overestimating Lifetime Value. A healthy ratio without healthy retention is an illusion; I’d rather fix the product and activation leaks than pour more dollars into acquisition.

Win rate is the truth serum for positioning. If we’re losing qualified deals, I look for gaps in our points of parity, competitive differentiation, and proof points. Improving win rate often requires sharper product positioning and fewer—but stronger—value propositions.

Sales cycle length closes the loop between interest and impact. I segment cycle time by ICP, channel, and deal size to expose bottlenecks. Tightening cycle time compounds growth by accelerating cash and freeing capacity for more pipeline.

Organic acquisition share protects us from paid dependency. I aim for a rising share of signups from organic search, referrals, and product-led loops. Healthy organic signals resonance—a clear message-market fit that compounds over time.

To operate this system, I keep experiments rigorous. We set a minimum detectable effect (MDE) up front for key A/B tests so we don’t declare fake wins. Weekly cross-functional reviews keep us focused on outcomes vs output, and we only scale what demonstrably moves these ten metrics.

If you align your team around these signals and instrument the full journey end-to-end, you’ll make better bets faster. More importantly, you’ll stop celebrating vanity spikes and start compounding real, defensible growth.

Inspired by this post on Product School.

November 3, 2025
Unlock Product Value: Define, Measure, and Scale What Customers Truly Pay For—Sustainably

When I think about what separates resilient products from forgettable ones, it always comes back to product value. In my role leading product at HighLevel, I’ve learned that value isn’t a slogan—it’s the measurable, compounding outcomes customers experience that make your product indispensable and your growth durable.

Discover what product value means, how to measure it with key metrics, and proven ways to increase product value for long-term growth.

Here’s how I define it in practice: product value is the net benefit a clearly defined ideal customer profile realizes over time, relative to their next best alternative and the total cost to achieve that benefit. That framing forces me and my team to zoom in on two questions: who exactly are we building for, and what outcomes do they consistently achieve with us that they can’t achieve as easily or as affordably elsewhere?

Value shows up twice in a customer’s journey—first as perceived value (do they believe it will help?) and then as realized value (did it actually help?). Great product management closes the gap between the two by aligning product positioning, onboarding, user activation, and ongoing engagement with the outcomes customers care about most.

To manage product value rigorously, I look through three lenses: perception, behavior, and economics. Together, they give me an end-to-end picture that is actionable for product discovery, go-to-market strategy, and product-led growth.

Perception tells me how customers feel about their trajectory with our product. I track signals like NPS, CSAT, and CES, and I rely on structured interviews to capture Jobs-to-be-Done narratives. These qualitative insights often reveal points of parity we must meet just to be considered, and the points of differentiation we must elevate in our value proposition to win.

Behavior tells me what customers actually do. Time-to-value, onboarding completion, activation rate, retention curves, feature adoption depth, and weekly active teams are my go-tos. Instrumentation matters: with Amplitude analytics, Pendo, and Intercom, I map funnels and cohorts so I can see where users stall and where they surge. When I spot friction in the first session or first week, I treat it as an opportunity to tighten product tours, improve tooltip design, and personalize in-app guides.

Economics tells me what value means to the business over time. I watch LTV, Net Revenue Retention, expansion revenue, gross margin, and CAC payback. Cohort-based retention analysis is especially revealing—if expansion offsets logo churn, I know we’re delivering value strong enough to merit deeper adoption, not just initial curiosity.

Anchoring this with a North Star Metric helps my teams aim at outcomes, not output. I choose a metric directly tied to customer value creation—something like “activated accounts achieving the aha moment weekly”—and wire it through outcomes vs output OKRs. That way, product roadmapping and sprint planning reflect what customers pay for, not what’s easiest to ship.

Growing product value starts with sharpening the ICP and clarifying the value proposition. I map pains and desired outcomes, articulate points of parity we must satisfy, and highlight the differentiators that change the decision. From there, I revisit SaaS pricing and packaging to ensure customers pay in proportion to realized value, not feature count.

Next, I systematically compress time-to-value. Fast, context-aware onboarding and user activation are non-negotiable. I combine in-app guides, product tours, and progressive tooltips with CRM integration through platforms like HubSpot to trigger the right message at the right step. A/B testing then helps me identify which experiences reduce setup friction and accelerate that first meaningful outcome.

Sustained engagement compounds value. I design habit loops around core jobs, reduce cognitive load in key workflows, and surface proofs of progress at moments when users are most likely to disengage. For advanced users, I introduce higher-order use cases and templates that inspire expansion without overwhelming new users who are still finding their footing.

None of this works without empowered product teams. I rely on product trios to align discovery and delivery, and I keep feedback loops tight so real customer signals inform every release. This is how we move from shipping features to earning outcomes, from intuition-only to evidence-backed decision making.

If you need a starting plan, try this: define your North Star Metric and its leading indicators, instrument your critical paths, identify the three biggest drop-offs between sign-up and activation, and run focused experiments to improve them. Tie these to clear OKRs and review the impact weekly. You’ll see perception, behavior, and economics begin to reinforce each other—and that’s when product value truly scales.

Inspired by this post on Product School.

November 3, 2025
Global Product Manager Playbook: Build Borderless Products, Align Teams, Win Every Market

Products without borders are exhilarating—and unforgiving. In my role leading product strategy, I’ve learned that “global” isn’t a launch plan; it’s a system. It’s the discipline of creating one product vision that flexes to many markets without breaking the core experience, the roadmap, or the business.

Here’s what a Global Product Manager does, key skills, tools, challenges, and how to grow into this high-impact role.

At its heart, the Global Product Manager role orchestrates product-market fit in multiple regions simultaneously. I translate a unified value proposition into localized realities—aligning product positioning, go-to-market strategy, pricing and packaging, and compliance—while keeping the platform cohesive. That means partnering closely with product trios, regional leaders, sales, customer success, and marketing to drive outcomes vs output OKRs that actually move the business.

Operationally, I start with deep product discovery across segments and geographies: what pains are universal, and where do we need regional nuance? From there, I map points of parity we must maintain globally and the differentiators we’ll localize—copy, workflows, payments, support models, and integrations. The art is delivering a consistent core with flexible edges so we can scale without fragmenting the codebase or the customer experience.

Trust is the non-negotiable. I build privacy-by-design into the product and roadmap, and I collaborate early with legal and security on data governance, data residency, and evolving regulations like GDPR. The right guardrails reduce rework later and enable faster regional launches—because compliance is a feature customers feel, even when they don’t see it.

On the commercial side, I partner on consumption SaaS pricing, product-led growth motions, and country-level market entry. Some markets need lighter onboarding and in-app guides; others demand concierge support or partner-led distribution. I use retention analysis to identify fit and inform sequencing, then adjust messaging and activation flows to shorten time-to-value and improve user activation by region.

My analytics and enablement stack is intentionally boring—and ruthlessly consistent. A unified analytics platform with Amplitude analytics gives us comparable funnels across countries. For experimentation, I run A/B testing with a clear minimum detectable effect (MDE) and disciplined rollout plans. Pendo powers product tours and in-app guides tailored by locale, while Intercom and CRM integration with HubSpot help me close the loop with GTM and support teams. The outcome is a learning system, not just a dashboard.

The hardest part isn’t translation—it’s alignment. Time zones, competing priorities, and matrixed ownership test even strong cultures. I rely on stakeholder management, crisp decision records, and product roadmapping and sprint planning rituals that respect regional input without derailing the global plan. When tension rises, I return to first principles decision making and the try do consider framework to make trade-offs transparent and repeatable.

If you’re growing into this role, start by owning a multi-region initiative end to end: lead localization for a critical workflow, run market-specific A/B testing with clear MDE, and publish a country launch plan that ties discovery insights to OKRs and resourcing. Build your credibility by shipping outcomes, not artifacts—then scale your impact by mentoring peers and creating shared templates for pricing, positioning, and experimentation. That’s how you shift from capable PM to trusted global operator.

Ultimately, a Global Product Manager is a force multiplier. We reduce complexity for the organization while increasing resonance for customers. If “products without borders” is your mandate, build the systems—analytics, governance, enablement, and decision-making—that make borderless execution reliable, repeatable, and fast.

Inspired by this post on Product School.

November 3, 2025
From Walls to Bridges: How I Unite Siloed Teams and Eliminate the Illusion of Work

I’ve seen what happens when talented teams drift into silos: priorities splinter, timelines slip, and what looks like progress turns out to be motion without momentum. My job is to turn those walls into bridges—aligning product, engineering, design, and go-to-market around outcomes that matter to customers and the business.

For siloed teams, walls go up, and unnecessary work gets done. Learn the signs, the damage, and the way to break free from the illusion of work.

The signs show up early if you know where to look: duplicated efforts across squads, decision-making that bounces between functions, roadmap debates grounded in opinions rather than data, and “busy” sprints that ship outputs without measurable outcomes. These are classic stakeholder management breakdowns, often masked by perfect decks and full calendars.

The damage is real. Customers feel friction and inconsistency, product-market fit signals get missed, and we over-invest in features that don’t drive user activation or retention. Morale takes a hit as teams lose the thread of purpose. That’s the “illusion of work” in action—activity that crowds out impact.

Here’s how I build bridges. First, I organize around empowered product teams and product trios (product, design, engineering) who own customer outcomes, not just velocity. We practice first principles decision making, write decisions down, and align early with adjacent functions so there are no surprises when we move from product discovery to delivery.

Second, I anchor planning in outcomes vs output OKRs. We commit to a small set of measurable outcomes, then use QBRs vs OKRs cadences to inspect progress, cut scope that doesn’t move the needle, and recalibrate with clarity. This shifts the conversation from “What did we ship?” to “What changed for customers and the business?”

Third, I make impact measurable and visible. We instrument the funnel end to end, define a minimum detectable effect (MDE) for experiments, and use A/B testing to de-risk bets before we scale them. A unified analytics platform—with Amplitude analytics, Pendo, Intercom, and HubSpot tied back to our CRM integration—keeps everyone looking at the same truth so we can diagnose what’s working and what’s noise.

Fourth, I bring collaboration into the core rituals: transparent product roadmapping and sprint planning, weekly cross-functional reviews, and fast, lightweight artifacts that clarify hypotheses, success metrics, and trade-offs. By the time we launch, stakeholders already understand the why, the how, and the expected impact.

If parts of your organization feel stuck, start small: pick one shared outcome, form a cross-functional trio, define your leading indicators, and run one experiment with clear MDE and a two-week readout. The momentum you create will turn walls into bridges—and busywork into business results.

Inspired by this post on Product School.

November 3, 2025
Make Data Work Together: Build a High-Trust, Data-Driven Culture with Amplitude and Slack

Data collaboration isn’t a tool you buy; it’s a culture you build. In my role leading product teams, I’ve learned that the fastest way to better decisions is aligning on a shared language of metrics and weaving insights into our daily rituals. When we do that well, momentum compounds—roadmaps clarify, stakeholder debates get healthier, and teams ship with confidence.

Break down data silos and align teams with Amplitude: define shared metrics, share insights in Slack, and build better habits together.

Here’s how I operationalize that guidance. First, we create a crisp measurement framework—one North Star metric supported by a few input metrics that map to customer value. We document definitions in a living “metrics glossary,” enforce data governance, and design a clean Amplitude taxonomy so events, properties, and user identities are consistent across the product. This is the foundation of a unified analytics platform that everyone can trust.

Next, we make insights unavoidable. Amplitude dashboards are curated by product trios and subscribed into Slack channels so context meets people where they work. I ask teams to pair charts with a one-paragraph narrative: what changed, why it likely changed, and what we’ll try next. This simple habit closes the loop between analysis and action—and it catalyzes product-led growth.

We institutionalize these behaviors in our operating cadence. Weekly insights reviews focus on outcomes vs output OKRs. Sprint planning starts with what the data says, not what we wish were true. In QBRs, we connect customer journeys to retention analysis and A/B testing results, making sure tests are designed with an appropriate minimum detectable effect (MDE). Empowered product teams own decisions; stakeholder management shifts from opinion trading to hypothesis testing.

A few pragmatic enablers make this stick: clean CRM integration to join product usage with lifecycle and segment data; privacy-by-design guardrails; clear ownership for instrumentation; and lightweight documentation that evolves with the product. I also encourage teams to ship in-app guides when we launch a feature so we can measure activation and iterate quickly based on Amplitude analytics.

The cultural side matters just as much. I celebrate learnings (even when metrics dip) and spotlight teams that translate insights into experiments quickly. Psychological safety unlocks better questions, and better questions unlock better products. Over time, this builds the high-trust environment required for durable, data-informed decision-making.

If you’re just getting started, pick one product surface and one customer journey. Define the shared metrics, wire up Amplitude, pipe key dashboards into Slack, and run a single, well-powered experiment. You’ll feel the difference in a sprint or two—and you’ll have a repeatable playbook to make data truly work together across your organization.

Inspired by this post on Amplitude – 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
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
The 5 Stages of Software Experience Maturity: What to Fix First to Unlock Growth

I’ve led product teams through chaotic launches, painful plateaus, and breakout growth, and one truth keeps showing up: software wins when the experience is intentionally designed, measured, and continuously improved. To make that work repeatable, I rely on a simple maturity framework that aligns our product strategy, analytics, and in-app experience work across the organization. Find out where you stand—and what to fix first—with this maturity framework. Why “software experience” and not just “features”? Because activation, adoption, and retention depend on how clearly users understand value in their first sessions, how seamlessly they complete key workflows, and how consistently they succeed over time. That’s where empowered product teams, product-led growth, and outcomes vs output OKRs come together to create durable results. Stage 1 — Ad Hoc: At this level, teams ship features without a clear sense of who benefits, how success is measured, or how UX writing and onboarding shape outcomes. If this is you, fix this first: define your activation events, instrument the core funnel, and write concise, in-product copy that reduces friction. Even a lightweight retention analysis will reveal where value drops off. Stage 2 — Instrumented Awareness: You’ve added basic analytics and can see signups, activations, and drop-offs, often via tools like Amplitude analytics or a unified analytics platform. What to fix first: translate raw metrics into hypotheses and prioritize a small set of A/B testing experiments. Use a minimum detectable effect (MDE) to size tests, and start tracking leading indicators tied to adoption—not vanity metrics. Stage 3 — Guided Journeys: Onboarding, in-app guides, product tours, and contextual tooltips now clarify value and reduce time-to-first-value. What to fix first: build a guided path to activation for your top two personas, then test microcopy and sequencing. Pair qualitative insights from user feedback with cohort-based retention analysis to ensure your guides create durable behavior change, not just clicks. Stage 4 — Outcome-Driven Execution: Teams set outcomes vs output OKRs, run disciplined experiments, and connect learnings to roadmap decisions. What to fix first: standardize an experimentation playbook with clear guardrails for MDE, sample sizing, and stop rules. Align quarterly bets with a value proposition narrative that ties product discovery to measurable, customer-centric outcomes. Stage 5 — Predictive and Proactive: You anticipate user needs with tailored experiences, automate nudges at the right moments, and systematize continuous discovery. What to fix first: unify data across product, support, and lifecycle channels to personalize experiences without eroding privacy-by-design. Invest in scalable governance so insights flow to product trios and forward deployed engineers quickly and safely. How to use this framework: honestly score your current stage across analytics, onboarding, guidance, experimentation, and decision-making. Then pick the single change that removes the biggest bottleneck to the next stage—often a measurement gap, not a feature gap. Make improvements visible through product roadmapping and sprint planning, and celebrate progress to reinforce empowered product teams. In practice, maturity is not a badge; it’s a habit. When we pair rigorous analytics with thoughtful in-app experiences and clear strategic outcomes, we compound learning and unlock growth. If you’re unsure where to begin, start small: instrument activation, improve one critical guide, and run one high-quality experiment. Momentum follows.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
6 Hard Questions Your AI Agents Must Answer to Win: Performance, Risk, and Real ROI

“Do you know how your AI agents are performing?” I ask this question in every review because it exposes whether we’re managing by outcomes or by anecdotes. Too often, teams point to latency, token counts, or completion rates and call it a day—useful signals, but not the story.

In my role, shipping agentic AI into production means I need decision-quality evidence, not vibes. That starts with Agent Analytics built on a unified analytics platform and instrumentation that lets me trace behavior, quantify value, and manage risk. Below are the six questions I use to separate novelty from durable impact.

1) What outcome are we optimizing for—and how do we measure it? If we can’t map the agent’s work to outcomes vs output OKRs, we’re optimizing noise. I anchor on task success rate, time-to-resolution, containment rate (no human handoff), cost per successful outcome, and downstream business impact (retention, conversion, NPS/CSAT) to keep us honest.

2) Are the right guardrails in place for AI risk management and data governance? I expect documented policies for prompt injection defenses, PII redaction, access control, and auditability. Every tool call should be permissioned, every data boundary explicit, and every failure mode observable. If we can’t demonstrate compliance by design, we’re scaling risk instead of value.

3) Can I explain every decision the agent made? Agentic AI needs traceability: prompts, intermediate reasoning, tool calls, retrieved context, and final outputs. I route key events into Amplitude analytics so product, engineering, and risk can slice behavior end to end. If we can’t reconstruct the path to an answer, we can’t debug, improve, or trust it.

4) What is the true cost per successful outcome? Raw token spend is misleading. I model total cost of ownership across retries, tool usage, escalations, and human review time—then benchmark against a consumption SaaS pricing lens. If cost per resolution trends up as volume grows, we haven’t built a scalable system; we’ve built a demo.

5) How does the agent learn without breaking what already works? My bar is a disciplined experimentation loop: offline evals, online A/B testing with clear guardrails, and a rollback plan. We predefine a minimum threshold for improvement before rollout and track regressions by persona, task type, and channel so we can localize fixes quickly.

6) Where is this agent creating durable differentiation? I look for capabilities competitors can’t easily copy: unique data advantages, superior tool orchestration, or workflows that compound learning. If the edge is just a base model prompt, the moat will evaporate; if it’s embedded in product workflows and proprietary signals, we’re building advantage.

Answering these six questions turns agentic AI from a novelty into a managed system. With Agent Analytics feeding a unified analytics platform, we can tie behavior to business outcomes, enforce governance, and make portfolio trade-offs grounded in evidence. The result is a product management leadership motion that prioritizes real ROI over vanity metrics—and scales with confidence.

If you’re not satisfied with the answers today, start by instrumenting the journey end to end, aligning metrics to OKRs, and setting clear risk thresholds. The compounding effects show up quickly when every iteration is measurable, explainable, and accountable.

Inspired by this post on Pendo – Best Practices.

October 24, 2025