Month: January 2026

Beyond Digital: How I Drive AI Transformation to Build Adaptive, Intelligent Organizations

Digital transformation set the foundation, but it’s no longer sufficient. In my work leading product teams, I’ve learned that real competitive advantage now comes from building systems that perceive, learn, and adapt—end to end, across the product lifecycle and the business operating model.

AI transformation goes beyond automation to create adaptive, intelligent organizations. Discover why it’s the next imperative and how to measure success.

Why is this the next imperative? Customers expect intelligent experiences, not just digitized workflows. Markets are shifting faster than roadmaps, and teams need systems that learn in production. For me, AI Strategy starts with a clear value thesis: where can intelligence amplify customer outcomes and compound business impact—whether in onboarding, customer support, or core product differentiation.

Practically, I frame AI transformation as a capability stack: data governance and privacy-by-design at the foundation; a retrieval-first pipeline to ground models in trusted context; agentic AI and AI workflows to orchestrate actions; and eval-driven development to continuously measure quality, safety, and relevance. Layered on top are operating rhythms—outcomes vs output OKRs, rapid experimentation, and incident management—that keep shipping disciplined and responsible.

I start with product discovery. Together with product trios, we target moments where intelligence removes friction or unlocks new value. We translate those opportunities into crisp outcomes (activation, time-to-first-value, resolution rate) and instrument them from day one. In customer support, for example, a customer support ai strategy might blend LLMs for product managers with retrieval-first grounding to deliver accurate, brand-safe answers and escalate seamlessly when needed.

On architecture, I prioritize context window management and robust integrations. CRM integration and event streams from tools like Intercom, HubSpot, Pendo, and a unified analytics platform provide the signals AI needs to adapt in real time. Prompt engineering patterns, guardrails, and privacy-by-design controls ensure responses remain trustworthy and compliant. When applicable, I explore agentic AI to orchestrate multi-step tasks with clear constraints and auditability.

Delivery is where transformation becomes measurable. I combine CI/CD practices with DORA metrics (deployment frequency, lead time, change failure rate, MTTR) to keep iteration fast and safe. On the product side, A/B testing with a minimum detectable effect (MDE) protects rigor, while eval-driven development tracks model accuracy, hallucination rates, and policy adherence before and after release. I tie these to business metrics like user activation, retention analysis, and support resolution time to ensure we’re shipping outcomes, not just output.

Governance is non-negotiable. AI risk management, regulatory compliance, and data governance anchor every phase—from dataset curation to prompt libraries and model routing. Threat detection and response and incident management processes are integrated so we can respond quickly when behavior drifts or new risks emerge.

Transformation also means evolving how teams work. I invest in empowered product teams, continuous discovery, and developer evangelism to spread best practices across domains. We share playbooks, reusable CustomGPT workflows, and an AI product toolbox to scale patterns like retrieval-first pipelines and safe prompt engineering across the portfolio.

The outcome is not just smarter features; it’s a more adaptive business. With clear OKRs, reliable telemetry, and responsible guardrails, AI becomes a force multiplier for product strategy and execution. If you’re moving beyond digital toward intelligence, start small, measure relentlessly, and let outcomes guide the journey.

Inspired by this post on Pendo – Perspectives.

January 4, 2026
Inside PendomoniumX London: AI’s tipping point and what product leaders should do next

I walked into PendomoniumX London energized by a simple question: are we finally past the AI hype cycle and into real product impact? From the hallway conversations to the main stage, the momentum was unmistakable—and deeply practical.

PendomoniumX’s sixth stop brought 350+ software leaders together for a day of AI transformation, real-world stories, and product innovation.

That scale and focus say a lot. Across the dialogues I joined, the center of gravity has clearly shifted from experiments to execution: building an AI Strategy that aligns with product roadmaps, turning promising prototypes into production-grade AI workflows, and measuring value in ways that reinforce product-led growth. It’s the inflection point where Generative AI moves from isolated pilots to cross-functional capabilities.

My biggest takeaway for product leaders: treat AI like any other durable capability. Start with sharp problem framing and customer outcomes, run continuous discovery to validate use cases, and sequence delivery through product roadmapping and sprint planning. Pair this with privacy-by-design and sensible governance so your teams can move fast without cutting corners.

Operationally, I’ve found it essential to design experiences that accelerate user activation—think thoughtful onboarding, in-app guides, and product tours that reduce friction while teaching new AI-powered behaviors. For teams adopting LLMs for product managers, keep your evaluation loops tight, instrument the journey end-to-end, and make sure every iteration maps to a clear value proposition customers can feel.

Events like PendomoniumX London remind me why community matters: they compress learning cycles. If you’re steering an AI portfolio, now is the moment to translate vision into repeatable systems—prioritize the right bets, make adoption effortless, and let data tell you when to double down or pivot. That’s how we turn AI transformation into durable product innovation.

Inspired by this post on Pendo – Perspectives.

January 3, 2026
Master the Five Stages of Software Experience Maturity and Prioritize What to Fix First

Experience quality compounds just like code quality. To align teams and accelerate outcomes, I rely on a clear, five-stage software experience maturity model to assess where we are, why we’re there, and how to advance. It turns fuzzy debates into concrete product strategy and reinforces a product-led growth mindset.

Find out where you stand—and what to fix first—with this maturity framework.

Why a five-stage model? It gives product, design, engineering, and go-to-market a shared language for trade-offs, helps us move from opinions to evidence, and ties day-to-day improvements to outcomes vs output OKRs. Instead of spreading effort thin, we sequence the right bets at the right time and build momentum with measurable wins.

Here’s how I apply it in practice. I start with a brief, honest self-assessment across the customer journey: onboarding clarity, user activation moments, in-app guides and product tours, UX writing, support loops, reliability, and analytics coverage. Then I layer in learnings from continuous discovery and product discovery—interviews, usage patterns, and support transcripts—so we see the experience as customers do, not just as we intended.

When it comes to what to fix first, I prioritize prerequisites over polish. If the value proposition isn’t clear, onboarding is confusing, or activation is inconsistent, we address those before adding new features. I instrument the funnel end-to-end, establish a minimum detectable effect (MDE) for A/B testing, and ensure we can answer basic questions about who activates, who retains, and why.

Measurement is non-negotiable. I pair retention analysis and activation metrics with qualitative signals to avoid local maxima. Amplitude analytics helps reveal behavioral patterns, while Pendo and in-app guides close gaps in comprehension and guidance. Intercom and CRM integration with HubSpot connect product signals to account health, so we can see how experience maturity drives revenue and retention.

Operationally, I anchor the roadmap to a small set of experience outcomes, link them to product strategy, and review progress in cadence with leadership. This approach builds product management leadership muscle: sharper stakeholder management, clearer trade-offs, and faster feedback loops. Most importantly, the team sees how each improvement ladders up to a better, more durable user experience.

If you’re mapping your own path across the five stages, start by sizing the gaps that block activation and retention, commit to a few high-leverage fixes, and measure relentlessly. With a shared maturity model, your team gains focus, your customers feel the difference, and your product compounds value with every release.

Inspired by this post on Pendo – Best Practices.

January 3, 2026
Unlock Peak Support Performance with Pendo Agent Analytics to Drive Adoption and ROI

When agent performance improves, everything else follows: faster resolutions, happier customers, and stronger product adoption. In my role leading product management at HighLevel, I use Pendo Agent Analytics to build a shared, measurable view of how our support motions shape the entire software experience and influence 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.

In practice, I connect Agent Analytics with our product strategy by pairing product signals (user activation, onboarding progress, feature usage depth) with operational signals (first-response time, time-to-resolution, and deflection rates). This lets me see how in-app guides, product tours, and contextual tooltips impact outcomes across segments without guesswork.

To separate signal from noise, my team runs small, controlled experiments and targeted A/B tests. For example, we’ll instrument a guide for a complex workflow, then compare cohorts on activation, retention, and support ticket volume. If engagement improves and cost-to-serve drops, we standardize the pattern and scale it.

The real advantage is alignment. By treating analytics as a unified analytics platform that integrates agent activity with product insights, we tie day-to-day support work to our value proposition and roadmap. That transparency sharpens prioritization, accelerates adoption, and creates a clear line of sight from agent coaching to measurable business impact.

For teams getting started, baseline your agent performance metrics, map the key friction points in your user journey, and instrument those moments with precise, helpful in-app guides and product tours. Review outcomes weekly, double down on what reduces effort and drives engagement, and keep refining the loop until adoption and satisfaction compound.

Inspired by this post on Pendo – Best Practices.

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

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

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

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

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

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

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

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

Inspired by this post on Pendo – Perspectives.

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

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

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

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

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

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

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

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

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

Inspired by this post on Pendo – Best Practices.

January 3, 2026
Unlock Product Insights Fast: Connect MCP and Pendo to Claude, ChatGPT, and Cursor

I’ve spent the last year pushing our AI Strategy from slideware to shipped value, and one pattern keeps winning in real-world product teams: connecting agentic AI directly to trustworthy product analytics. That connection is where Model Context Protocol shines—safely bridging LLMs with the tools and data product managers rely on every day.
Model Context Protocol (MCP) gives AI agents access to your business data. Learn how MCP works, how product managers are using it, and how to connect Pendo’s MCP server to Claude, ChatGPT, or Cursor for instant product insights.
In practice, I treat MCP as a clean, auditable interface between LLMs and enterprise systems—decoupling the model choice from the data plane and enabling a retrieval-first pipeline with strong data governance. Because MCP standardizes the way agents discover resources and tools, it simplifies context window management, enforces least-privilege access, and makes it easier to evolve our stack without rewriting prompts or fragile glue code.
For product leaders, the immediate payoff is speed to insight. Instead of hopping across dashboards, I ask the agent questions in natural language—“Which onboarding step drives the biggest drop-off by segment?”—and get synthesized answers backed by traceable queries. That shift turns AI workflows into a daily habit, improving continuous discovery and accelerating product-led growth while maintaining privacy-by-design controls.
Under the hood, I think about MCP in four layers: resources (read-only data surfaces such as feature usage or retention cohorts), tools (safe operations like creating a note, exporting a segment, or proposing an in-app guide), prompts (task-scoped instructions tuned for LLMs for product managers), and observability (logs and evaluations). This structure keeps eval-driven development front and center and reduces operational risk.
Here’s how I connect Pendo analytics through MCP to my preferred assistants without compromising security or accuracy:
1) Prepare access: confirm your Pendo MCP server endpoint, authentication method, and scopes; apply least-privilege and redact any PII not required for analysis.
2) Register the server: in Claude, ChatGPT, or Cursor, add the MCP server with the provided URL and API key or token, then enable only the resources and tools your use case demands.
3) Validate the contract: prompt the agent to list available resources and describe tools; run harmless dry runs (e.g., “summarize top feature adoption trends last 30 days”) to confirm the interface behaves as expected.
4) Operationalize: standardize prompts for recurring analyses (QBRs vs OKRs, activation funnels, retention analysis), set guardrails, and log every interaction for audit. This is where prompt engineering meets governance.
5) Iterate with metrics: track answer quality, latency, and usage; expand scopes gradually and gate new tools behind human-in-the-loop until you reach reliable performance.
Once configured, I use the agent to surface weekly activation insights, identify outlier cohorts, and auto-draft product discovery notes with links back to Pendo reports. The result isn’t magic; it’s a disciplined AI product toolbox that brings the right context to the right question, fast.
If you’re starting from zero, pilot with one high-value question, one team, and one assistant. Keep the footprint small, measure outcomes, and then scale—with security, compliance, and stakeholder management baked in from day one. That’s how you turn MCP from an interesting protocol into a durable competitive advantage.

Inspired by this post on Pendo – Best Practices.

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

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

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

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

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

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

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

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

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

Inspired by this post on Pendo – Best Practices.

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

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

“Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement.” That promise captures why I integrate Pendo Predict at the heart of our product strategy.

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

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

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

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

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

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

Inspired by this post on Pendo – Best Practices.

January 3, 2026
Why I’m All-In on INDUSTRY 2025: 5 Powerful Reasons For Product Leaders at The Product Conference

INDUSTRY 2025: The Product Conference is circled on my calendar for good reason. In my role leading product management at HighLevel, I look for events that sharpen strategy, accelerate learning, and connect me with operators who ship. This one consistently delivers on all three, and 2025 promises to raise the bar for product management leadership.

Join Pendo at INDUSTRY in Cleveland, Ohio.

First, I expect deeply actionable product strategy insights—beyond platitudes. I’m prioritizing conversations on outcomes vs output OKRs, product roadmapping and sprint planning, and how great teams articulate a crisp value proposition while maintaining points of parity that matter. I’m going in with specific questions on product-market fit lessons and how to systematize strategic bets without stifling discovery.

Second, the surge of AI in product work is too important to observe from the sidelines. I’m comparing approaches across AI Strategy, LLMs for product managers, prompt engineering, and eval-driven development—especially in retrieval-first pipeline patterns. My focus: where AI genuinely improves product discovery, in-app guides, and customer support ai strategy, and where it risks adding complexity without outcomes.

Third, the community is unmatched for conference networking and pragmatic learning. I’m intentional about meeting product trios who run continuous discovery at scale, as well as leaders who’ve cracked stakeholder management under pressure. These are the moments where competitive differentiation is born—through candid stories of what didn’t work and why.

Fourth, I’m eager to stress-test data practices that power product-led growth. I’ll be exchanging notes on retention analysis, unified analytics platform decisions, user activation, and how teams integrate qualitative feedback with event data to inform roadmaps. I’m also interested in how practitioners leverage platforms like Pendo, Amplitude analytics, Intercom, and HubSpot to reduce time-to-insight and craft effective product tours and in-app guides.

Fifth, I treat INDUSTRY as a checkpoint for leadership growth. I’m looking for fresh takes on empowering product teams, first principles decision making, organizational development, and the IC to manager transition. The best sessions don’t just inspire; they give me two moves I can apply with my team on Monday.

To make the most of the week, I’m applying a continuous discovery mindset: arrive with clear learning goals, capture portable frameworks, and translate at least two insights into experiments before wheels-up. If you’re focused on product strategy, product discovery, and product-led growth, we’ll have plenty to compare and build on together.

I’ll be in Cleveland ready to learn, share, and connect with peers who care about craft and outcomes. If you’re attending, let’s compare notes on what’s working, what’s stalled, and how we can raise the bar for product management leadership in 2025 and beyond.

Inspired by this post on Pendo – Perspectives.

January 3, 2026
4 Critical AI Risks Every CIO Must Tackle Now—and a Practical Playbook to Mitigate Them

I spend a lot of time with CIOs and IT leaders who are moving fast on generative AI. The momentum is real, but so are the risks. When AI touches core workflows, data, and customer experiences, we need a clear, pragmatic plan that blends AI Strategy with disciplined product management leadership and IT governance.

Learn about the risks that AI poses to IT teams, and how they can mitigate them.

Here are the four risks I see most often—and the playbook I use to de-risk delivery while preserving speed and innovation.

Risk #1: Shadow AI and data leakage. Teams experiment with unapproved tools, and sensitive data ends up in prompts, logs, or third-party services. Without strong data governance and privacy-by-design, even a small proof of concept can create outsized exposure.

How I mitigate it: start with an AI acceptable-use policy, data classification, and clear guardrails on what can be prompted. Deploy a redaction layer and secrets management before any model call. Favor a retrieval-first pipeline so models reason over vetted internal knowledge rather than raw or personal data. Conduct vendor due diligence and DPAs up front, and centralize audit logs to support regulatory compliance and incident response.

Risk #2: Hallucinations and unreliable outputs. LLMs are probabilistic; they can fabricate citations, numbers, or steps. In customer support and internal operations, this erodes trust and creates rework—especially when teams assume model answers are authoritative.

How I mitigate it: adopt eval-driven development with task-specific test sets, reference answers, and pass/fail thresholds that gate CI/CD. Ground models with retrieval, constrain outputs with schemas, and keep a human-in-the-loop for high-risk actions. A/B testing, error taxonomies, and continuous monitoring turn model behavior into measurable, improvable Web Vitals for AI reliability.

Risk #3: Expanded attack surface. Prompt injection, data exfiltration, supply chain risks in model providers, and insecure connectors can undermine existing cybersecurity controls. Traditional threat models often miss these new interaction patterns.

How I mitigate it: treat AI as a first-class asset in threat detection and response. Implement input/output filtering, allow/deny lists, content moderation, and strict isolation of tools and connectors. Red team prompts and tools regularly, rotate credentials, and codify runbooks with SRE and incident management for fast containment. Apply least privilege to agents, APIs, and vector stores, and monitor for anomalous tool-use.

Risk #4: Compliance, bias, and auditability gaps. As AI scales, questions about explainability, fairness, data residency, and retention move from theoretical to board-level. Without traceability, it’s hard to satisfy audits or respond to regulators.

How I mitigate it: embed privacy-by-design from the first sprint—data minimization, consent, purpose limitation, and retention controls. Maintain model cards, versioning, and lineage for prompts, datasets, and parameters. Centralize audit logs, set policies for high-risk use cases, and run periodic compliance reviews with security and legal. Cross-functional communities of practice keep changes aligned across product, engineering, and IT Leadership.

Operationally, I anchor AI initiatives to outcomes vs output OKRs, use empowered product teams and product trios to balance feasibility, value, and risk, and integrate model changes into CI/CD with quality gates. This creates a repeatable mechanism to ship safely, learn quickly, and scale what works.

If you’re standing up new AI workflows or hardening what you already have in production, this playbook gives you a practical path: drive adoption confidently, protect your data, and stay compliant while maintaining competitive velocity.

The bottom line: AI risk management isn’t a brake on innovation—it’s how we earn the right to go faster.

Inspired by this post on Pendo – Perspectives.

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

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

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

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

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

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

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

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

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

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

Inspired by this post on Pendo – Perspectives.

January 3, 2026