Category: Leadership

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
Turning Community Noise into Action: My Product Lessons from Zencity’s AI That Listens

I’m constantly looking for ways to turn messy, multi-source signals into decisions leaders can trust. Recently, I dug into how Zencity powers government decision-making with community voices—and it’s a masterclass in building AI products that are both responsible and useful.

Noa Reikhav, Head of Product, Zencity; Andrew Therriault, VP of Data Science, Zencity; and Shota Papiashvili, SVP of R&D, Zencity share a comprehensive view of how they designed an AI that listens and acts without sacrificing rigor.

How do you use AI to help city leaders truly hear their residents?

I was struck by the clarity of their platform vision—“They share how Zencity brings together survey data, 311 calls, social media, and local news into a unified platform that helps cities understand what people care about—and act on it.” That single line captures the essence of a unified analytics platform done right.

You’ll hear how the team built their AI assistant and workflow engine by being thoughtful about their data layers, how they combined deterministic systems with LLM-driven synthesis, and how they keep accuracy and trust at the core of every AI decision.

It’s a fascinating look at how modern AI infrastructure can turn noisy, messy civic data into clear, actionable insight.

Here are the takeaways that resonated with me most, and they align closely with how I approach AI Strategy and product management leadership. Data architecture defines what AI can do. Guardrails and transparency matter more than flashy outputs. Agentic systems become powerful when grounded in real, multi-tenant data. AI in the public sector can make democracy more responsive—if built responsibly.

The team’s layered data model is the backbone that enables trustworthy synthesis: raw data → elements → highlights → insights → briefs. As a product leader, I love how each layer introduces meaning and structure while preserving traceability. It’s the difference between a demo-friendly prototype and a durable platform.

Why context is everything when building AI for civic use. That’s not a platitude—it’s a requirement. Community conversations are hyper-local, emotionally charged, and policy-laden. Without context and rigorous data governance, you risk misclassification, bias, and broken trust.

How the team designed their AI assistant using MCP servers to safely negotiate data access. This is a smart pattern for privacy-by-design: let the assistant request access, let the system adjudicate, and make the boundary explicit and auditable. In multi-tenant environments, that clarity is the difference between scaling confidently and shipping risk.

Balancing agentic flexibility with deterministic trust. I’ve found this to be the most practical framing for real-world agentic AI: give the system room to explore, but bind its outputs to deterministic rails where it matters—taxonomy, citations, permissions, and evaluation criteria.

Evaluating accuracy when latency matters: how they think about evals, citations, and model-as-judge systems. I appreciate the pragmatism here. In production, you don’t have the luxury of slow truth-finding. You need tight feedback loops, interpretable citations, and layered evals to keep both precision and speed.

Using workflows like annual budgeting or crisis communication to deliver AI-generated briefs to the right people at the right time. This is where product-market fit shows up: not in features, but in end-to-end workflows aligned to real decision cycles and stakeholders.

Why government workflows are the ultimate “jobs to be done” framework. When the job is a public process—with deadlines, accountability, and high scrutiny—you don’t just need insights; you need timely, contextualized briefs that match the cadence of the work.

From my lens, the magic isn’t any single model. It’s the orchestration: deterministic systems with LLM-driven synthesis, strong guardrails, transparent citations, and an orchestration layer that routes the right brief to the right role at the right moment. That’s how you turn community noise into legitimate signal—and signal into action.

If you’re building AI for regulated, high-stakes environments, take note: invest in your data layers, make context a first-class citizen, embrace privacy-by-design with clear access negotiation, and treat evaluation as a living system. Do that, and you’ll earn the trust that makes your AI assistant—and your organization—indispensable.

Inspired by this post on Product Talk.

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 – Best Practices.

October 25, 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
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
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