I’ve spent enough cycles in product and growth to know the biggest drag on experimentation velocity isn’t creativity—it’s waiting. Waiting for engineering to wire events, for analysts to pull cohorts, for approvals to trickle in. When marketers can move autonomously with the right guardrails, learning accelerates and impact compounds.
“Amplitude’s new web experiment capabilities enable teams to scale experimentation 3X faster without waiting for help.” That promise hits directly at the bottlenecks I see most often across product and marketing organizations.
My takeaway: the real unlock isn’t only speed; it’s confidence. Faster learning loops power continuous discovery and product-led growth, but only if teams trust the data, align on success metrics, and can iterate without creating downstream tech debt. Self-service done right transforms scattered tests into a durable growth engine.
From a VP of Product lens (and what we practice at HighLevel), self-service experimentation means more than a new UI. I look for governance-by-design, role-based permissions, clear metric definitions, pre-built test templates, and operational best practices like minimum detectable effect (MDE) sizing and traffic allocation standards. That mix keeps A/B testing fast, statistically sound, and repeatable—without piling work onto engineering.
Here’s the playbook I recommend to teams leaning into this shift: instrument a unified analytics platform and lock a shared taxonomy; define canonical success metrics and guardrails; require lightweight pre-registration for hypotheses and MDE; stand up weekly experiment reviews; and close the loop by sharing learnings in-product and across go-to-market. When marketers, PMs, and designers operate as an empowered product trio, the flywheel spins.
To maximize value from any web experimentation stack—Amplitude analytics included—connect the dots from insight to activation. Tie experiments to CRM integration for downstream campaigns, ensure user activation metrics are first-class citizens, and keep your experimentation backlog aligned to outcomes, not outputs. The goal is fewer opinions and more evidence, shipped continuously.
Self-service also requires culture. Set expectations around statistical rigor, data governance, and post-test decisions, then celebrate the teams that sunset ideas just as quickly as they scale winners. That’s how you reduce waste, build confidence, and keep momentum high without creating hidden operational costs.
If your marketers are still waiting in ticket queues, it’s time to raise the bar. With the right foundations and process, you can go from idea to live test in hours, not weeks—learning more, shipping smarter, and unlocking 3X faster cycles where it matters most: customer value.
Inspired by this post on Amplitude – Best Practices.
I build products at scale, and I write about how we make them successful. When I need a clear, evidence-based perspective on what actually drives outcomes, I turn to the Amplitude Blog. It’s a dependable source for sharpening my thinking on "digital analytics, product strategy, and product-led growth"—and it consistently helps me translate analytics into business impact.
What keeps me coming back is the way practical, well-structured guidance meets real-world constraints. Whether I’m refining our event taxonomy in Amplitude analytics, evaluating a unified analytics platform approach, or aligning stakeholders on the right success metrics, I find concrete patterns I can apply immediately. The content connects data literacy with product management leadership, the exact combination required to navigate complex roadmaps and high-stakes decisions.
Here’s how I apply these insights day to day. I anchor our experiments in A/B testing best practices and set a minimum detectable effect that matches our traffic realities. I guide teams to prioritize user activation and retention analysis over vanity metrics, and I frame plans with outcomes vs output OKRs so we stay focused on customer and business value. In parallel, I reinforce continuous discovery and product discovery habits—feeding learning back into product roadmapping and sprint planning without losing speed.
The payoff shows up in the details: better funnel instrumentation, cleaner cohorts, and faster hypothesis cycles that reduce rework. When we operationalize these ideas—tying activation to onboarding flows, clarifying value moments, and aligning cross-functional owners—we see measurable lifts without bloating scope. That’s the discipline I expect from a modern, product-led growth motion: rigorous analytics paired with empowered execution.
If you’re scaling a team or modernizing your analytics practice, make the Amplitude Blog part of your weekly ritual. Use it to pressure-test your strategy, level up experimentation, and build a shared language for data-informed decisions. The right "tips and examples" can save months of trial and error—and, more importantly, help you ship products that customers return to again and again.
Inspired by this post on Amplitude – Best Practices.
Balancing rigorous governance with relentless shipping velocity is the product leader’s paradox. When I say we must "Govern Like an Enterprise, Ship Like a Startup," I’m describing a culture where controls are hardwired into how we build—without slowing down how fast we learn and deliver value.
Learn how to scale data quality, automate compliance, and build AI-ready data foundations with Amplitude’s latest enterprise governance features.
In practice, governing like an enterprise starts with uncompromising data governance, privacy-by-design, and regulatory compliance. I expect standardized tracking plans, clear ownership, and role-based access to be non-negotiable. Auditability matters as much as usability, and our analytics stack must enable trustworthy insights while protecting sensitive data and reducing operational risk.
Shipping like a startup means we align governance with product velocity. My teams use CI/CD principles for analytics (think automated schema checks and data contracts), pair tracking changes with code reviews, and treat approval workflows as guardrails—not gates. We work as product trios, run continuous discovery, and keep event taxonomies lightweight and evolvable so iteration never stalls.
Compliance cannot be an afterthought; it has to be automated. Embedding least-privilege access, consent metadata, and policy-as-code into everyday workflows turns regulatory compliance and cybersecurity from projects into practices. The result is fewer surprises during audits and more confidence during releases.
Building AI-ready data foundations raises the bar further. Clean, consistent, and well-labeled event data; documented lineage; and explicit handling of PII give our models the context they need while honoring privacy commitments. This is how an AI Strategy moves beyond experimentation to measurable impact.
Amplitude analytics plays a pivotal role as part of a unified analytics platform strategy: it helps us codify standards, democratize insights safely, and maintain a single source of truth for product decisions. With the right governance features in place, teams can self-serve with confidence while leaders get the assurance that quality and compliance scale with growth.
If your organization is pushing for product-led growth while raising the bar on data governance, it’s time to operationalize both sides of the equation. The payoff is tangible: faster iteration cycles, stronger signal quality, lower risk, and a foundation that’s truly ready for AI-driven innovation.
Inspired by this post on Amplitude – Best Practices.
Every successful AI initiative I’ve led or advised has shared the same foundation: we treat data as a product. Models will improve, infrastructure will evolve, and use cases will expand—but only high-quality, well-governed, and well-structured data compounds value over time.
“Companies that prioritize data quality, governance, and structure will accelerate their AI initiatives the fastest.” That line has become a non-negotiable principle in my playbook because it consistently separates prototypes that stall from platforms that scale.
When I say data quality, I mean trustworthy signals: clear definitions, deduplication, lineage, and timely freshness. Governance adds accountability and safety: ownership, access controls, auditability, and privacy-by-design aligned with regulatory compliance. Structure makes it all usable: consistent schemas, event taxonomies, and feature stores that let product teams ship faster without reinventing pipelines.
In practice, this looks like aligning an AI Strategy with a unified analytics platform so every team works from the same truth. It means instrumenting feedback loops, labeling outcomes, and building a retrieval-first pipeline that brings the right context to LLMs at the right time. It also means thoughtful context window management so models remain grounded, relevant, and cost-efficient.
I’ve seen the difference firsthand. Early gen ai prototypes built on messy, conflicting data looked promising in demos but failed in the wild—hallucinations spiked, confidence scores dipped, and user trust eroded. Once we tightened governance, standardized schemas, and implemented human-in-the-loop evaluation, accuracy climbed, risk dropped, and feature velocity increased without sacrificing safety.
For product managers, the mandate is clear: treat data work as core product work. Define quality SLAs, make data contracts explicit, and give empowered product teams the tools to observe, debug, and improve signals continuously. Pair AI risk management with measurable product outcomes, and you’ll turn experimentation into a durable advantage.
The payoff is more than model performance; it’s organizational clarity and speed. With the right data foundation, LLMs for product managers become easier to deploy, customer experiences feel coherent, and roadmaps shift from firefighting to compounding wins. Invest in data quality, governance, and structure now, and your AI initiatives won’t just move faster—they’ll sustain momentum.
Inspired by this post on Amplitude – Best Practices.
Every time I ship a new generative AI capability with my product teams, I’m reminded that governance isn’t a compliance afterthought—it’s a strategic advantage. In today’s landscape, the way we govern data determines how quickly we can innovate, how confidently we can scale, and how credibly we can talk about risk with customers, regulators, and our own board.
New AI pressures are redefining what good governance takes. Learn how to build better frameworks, move fast with confidence, and keep your data from being a black box.
My north star for AI Strategy is simple: align business outcomes with responsible practices that are auditable, repeatable, and fast. Practically, that means codifying AI risk management, privacy-by-design, and regulatory compliance into the product lifecycle—requirements, design, build, deploy, and operate. When those guardrails live inside our workflows (not just in policy docs), we accelerate delivery without increasing exposure.
Visibility breaks the “black box.” I start by establishing a unified analytics platform and a living data catalog with lineage, classification, and stewardship. When we pair that with a retrieval-first pipeline for LLMs, we can trace exactly which sources informed a response, who had access, and whether consent and retention rules were honored. Provenance, RBAC/ABAC, encryption, and deterministic masking stop sensitive data from leaking into training sets while keeping our teams productive.
Speed with safety comes from engineering the right controls into CI/CD. Before any AI feature hits production, we run automated checks for PII exposure, policy violations, adversarial prompts, and data drift; then we add human-in-the-loop review where stakes are high. Continuous monitoring, audit logs, and playbooks for incident management and threat detection and response turn governance into an everyday habit rather than a once-a-quarter ritual.
In the first 30 days, I inventory systems, map data flows, and assign clear ownership. We define data quality SLAs, document lawful bases for processing, and publish a concise policy that product managers and engineers can actually use. This anchors stakeholder management and sets expectations for trade-offs.
By day 60, we implement fine-grained access controls, consent-aware tracking, and consistent metadata standards across sources. We wire dashboards for high-signal metrics—access attempts, data minimization, model input/output risk flags—so leaders can see governance health at a glance and course-correct quickly.
By day 90, we close the loop with outcomes vs output OKRs, tying governance to business impact: faster cycle times, fewer incidents, and higher customer trust. Training for LLMs for product managers and communities of practice ensure empowered product teams can make judgment calls confidently, not wait for gatekeepers.
If you’ve felt the friction between innovation and oversight, you’re not alone. The good news is that the right framework lets us do both: move fast with confidence, demonstrate responsible AI, and earn the trust that compounds into product-led growth. That’s the real promise of modern data governance—and it’s how we make sure our AI is powerful, reliable, and never a black box.
Inspired by this post on Amplitude – Best Practices.
I’ve felt the drag of data bottlenecks firsthand—PMs waiting on a reporting queue, engineers guessing at success metrics, and stakeholders making decisions with partial context. The “Add Data to Cart” mindset changed the game for me: make high-quality data as easy to request, enrich, and consume as dropping an item into a shopping cart.
Learn how Ankorstore’s teams make autonomous decisions, leveraging enriched data from Amplitude to accelerate feature delivery and drive topline growth.
Here’s what resonates with me and how I apply it in practice. When teams get self-serve access to a unified analytics platform like Amplitude analytics, decision autonomy becomes the default. Product trios operate with clarity, discovery cycles tighten, and we ship with confidence because the evidence is visible to everyone, not buried in a backlog.
The foundation is a clean, shared event taxonomy. I prioritize naming conventions, consistent properties, and governance so we can enrich events once and reuse them across A/B testing, retention analysis, and user activation dashboards. This lets product managers answer critical questions—Who’s activating? Which cohorts retain? Which journeys convert?—without waiting on an analyst, while still preserving data quality.
In my teams, “Add Data to Cart” means we treat data like a product. If a feature team needs a new event or property, they can request it with clear definitions, privacy requirements, and owners. We standardize the instrumentation pattern, ship it through CI/CD, document the event, and surface it in curated Amplitude reports. The result is faster feature delivery and fewer ad-hoc asks.
The payoff shows up in everyday decisions. Product managers run A/B tests with a minimum detectable effect (MDE) they can justify, analysts focus on deeper insights instead of ad-hoc tickets, and engineers get immediate feedback loops post-release. It’s a blueprint for product-led growth: know what moves activation, double down on the paths that retain, and sunset the work that doesn’t move outcomes.
Governance matters as much as speed. I pair data governance with privacy-by-design so teams can move quickly without risking compliance or eroding trust. That means documented event definitions, role-based access, and well-labeled dashboards that steer people to the right sources of truth.
If you’re starting from scratch, begin small: instrument a single critical flow end to end, publish three core dashboards everyone can find, and hold weekly readouts where teams share what changed because of the data. Within a few sprints, the habit forms—questions get sharper, hypotheses improve, and the roadmap shifts from output to outcomes.
“Add Data to Cart” isn’t just a catchy phrase; it’s a practical way to empower product teams. With enriched data in Amplitude, autonomous decisions become the norm, discovery accelerates, and growth compounds because every iteration is informed by what customers actually do.
Inspired by this post on Amplitude – Best Practices.
Engagement starts with a single, repeatable moment: activation. Over the years, I’ve learned that when we obsess over activation, everything downstream—retention, expansion, and product-led growth—gets easier and more predictable. As I often remind my teams, "Discover how winning teams drive engagement by obsessing over activation. Learn to define, measure, and improve the moments that keep users coming back."
When I say activation, I mean the specific behavior that reliably predicts long-term value for a new user or account. In different products, the activation moment could be connecting a data source, inviting a teammate, sending the first campaign, or completing an initial automation. My first move is to define that moment precisely, set an activation threshold (for example, “within 7 days of signup”), and align the team around it as a primary outcome.
From there, I track three core metrics: activation rate (the percentage of new accounts that hit the activation threshold), time-to-activation (how quickly they get there), and early retention curves by cohort. Cohort-based retention analysis gives me the most honest read on whether our activation definition truly predicts stickiness or if we’re celebrating vanity milestones. Tools like Amplitude analytics and Pendo make it straightforward to instrument these events, segment users, and visualize the funnel from first touch to activation and beyond.
Instrumentation quality is non-negotiable. I map the activation journey into discrete events, add clear event properties (role, plan, channel, use case), and validate tracking end-to-end before I trust any dashboard. A strong unified analytics platform lets me slice activation by persona, acquisition source, and onboarding path, so we can see where friction lives and where momentum builds.
Improving activation is where design and data meet. I lean heavily on in-app guides, product tours, and contextual tooltips to reduce cognitive load at the exact moment a user needs help. We run A/B testing with a minimum detectable effect in mind, prioritize experiments that remove steps or shrink time-to-value, and iterate quickly based on user feedback gathered through continuous discovery. The goal is simple: shorten the distance from curiosity to value.
Onboarding is the frontline of activation. I favor progressive disclosure, crisp checklists tied to the activation moment, and “just-in-time” education rather than dumping documentation up front. Clear wayfinding—what to do next, why it matters, and how success is measured—pushes users toward that first “aha” moment with confidence.
Cross-functionally, I align activation to outcomes vs output OKRs so everyone—from product and design to marketing and customer success—pulls in the same direction. For example, lifecycle emails and in-app messaging should reinforce the same activation path that product guides inside the app. This harmony lowers friction, speeds time-to-activation, and compounds engagement.
As we scale, I keep a living experiment backlog focused on activation levers: simplifying setup, removing form fields, auto-detecting configurations, and pre-populating defaults. Each change gets measured against activation rate and time-to-activation, with guardrail metrics to protect quality and retention. Over multiple releases, these small wins stack into durable growth.
I’ve seen teams unlock double-digit improvements by treating activation as a product, not a project. When we define the right moment, instrument it well, and iteratively remove friction with data-informed design, engagement rises naturally—and sustainably. That’s the power of an activation-obsessed culture.
Inspired by this post on Amplitude – Best Practices.
I love when a bold platform bet translates into tangible product impact. Watching a team commit to a unified analytics platform and then operationalize it across the business is a master class in strategic focus and change management. That’s exactly what this story captures—and why it resonates with my own experience leading complex analytics migrations.
Learn how Dan Grainger led Haven's migration to Amplitude, focusing on user-friendly analytics and data governance for non-technical teams.
That single sentence distills what matters most: if analytics aren’t accessible to non-technical teams, you won’t get the adoption needed to drive outcomes. “User-friendly analytics” isn’t window dressing; it’s the linchpin for empowered product teams and true product-led growth. When teams can ask and answer their own questions—without waiting on analysts—velocity and quality of decision-making improve immediately.
From a product management lens, two elements stand out. First, the choice of Amplitude analytics as the central system of insight—consolidating scattered tools into a unified analytics platform—creates one source of truth for activation, adoption, and retention analysis. Second, a rigorous approach to data governance ensures that trust in the data scales alongside usage, especially for non-technical stakeholders who need clarity, not caveats.
Execution matters. In my playbook, these transformations succeed when you treat them as product initiatives, not IT projects. I partner early with stakeholder management champions, form product trios to define the measurement plan, and use in-app guides, product tours, and targeted onboarding to drive behavior change. The goal is simple: shorten time-to-insight for frontline teams while keeping the instrumentation robust and consistent.
Data governance is the quiet force multiplier. Clear tracking plans, consistent event taxonomies, role-based access, and privacy-by-design guardrails prevent entropy. When everyone speaks the same analytics language, you avoid “metric du jour” debates and keep the focus on outcomes vs output OKRs. That’s where scalable impact comes from.
Measurement closes the loop. I’ve found that when non-technical teams can self-serve retention analysis, funnel drop-off, and user activation patterns, they start running continuous discovery by default—asking better questions, testing smarter hypotheses, and accelerating learning cycles. Amplitude’s strength is not just visualizing what happened, but making it easy to connect behavior to outcomes teams care about.
The broader leadership lesson is straightforward: choose a platform that your broadest set of contributors can and will use daily, invest early in governance, and build enablement into your rollout plan. That’s how a migration becomes a multiplier. When the right platform meets the right operating model, the win is less about a tool and more about a learning culture that compounding value over time.
If your analytics stack feels fragmented or underused, this is your nudge. Align on a unified analytics platform, meet teams where they are with user-friendly analytics, and let governance do the heavy lifting behind the scenes. The payoff—in speed, alignment, and smarter bets—comes faster than most teams expect.
Inspired by this post on Amplitude – Best Practices.
AI doesn’t fail because the model is bad, it fails because ownership is missing.
When someone truly owns your AI, everything changes. Resolution and automation rates climb, the system self-improves, and the customer experience transforms in ways a dashboard alone will never show you.
This is part three of our five-part series on customer service planning for 2026. We’ll be sharing all five editions on our blog and on LinkedIn.
If you’d rather have them emailed to you directly as they’re published, drop your details here.
Last week, we introduced the four roles that make AI actually work in a support organization. These roles are already showing up inside the teams who are scaling AI the fastest, and this week, we get closer to the ground.
Here’s what these roles look like in practice — what they do, how they work, and why your AI performance will inevitably drift without them.
AI operations lead — owns AI performance, every day. I think of this person as the air-traffic controller for our AI Agent. I treat the AI as a living system that needs ongoing supervision, evaluation, and tuning. This role is accountable for what leaders care about most: quality, reliability, and continuous improvement.
The AI ops lead sees the whole picture: conversation quality, missing knowledge, flawed assumptions, unexpected failures, new opportunities for automation, and the subtle signals that the system is beginning to drift. In practice, that vigilance is the difference between steady gains and slow decline.
Day-to-day, here’s what I expect from this role.
1. Reviews AI conversations and surfaces performance patterns. The AI ops lead monitors the AI Agent’s behavior — the tone shift after a product launch, a sudden dip in resolution for a specific intent, or conversation clusters revealing new customer behavior. They scan for anomalies, trends, and early warnings, with an emphasis on what’s happening right now, not last week. Without this intentional ownership, I’ve watched a 2% dip turn into a 10% drop in days.
2. Prioritizes fixes and improvements. Once patterns emerge, they triage fixes like a product team handles bugs. Missing or incorrect content? They route it to the knowledge manager. Behavioral issues? They adjust guidance and guardrails. Action or system issues? They partner with the automation specialist. This connective tissue turns individual fixes into compounding improvements.
3. Defines and maintains AI guardrails. Leaders everywhere worry about AI doing things it shouldn’t. This role answers that fear by establishing clarification logic, escalation rules, “never answer” policies, and safety boundaries. The goal is predictable behavior that protects customer trust — an essential pillar of any AI Strategy and AI risk management practice.
4. Aligns reporting with leadership. The AI ops lead reports on resolution rate, CX Score, CSAT, automation coverage, and hours saved — making the economic impact visible. That visibility is a foundational step in any credible customer support ai strategy.
Why this role exists now. AI systems are dynamic and require constant tuning. A small dip in quality quickly becomes an operational issue, and no existing role naturally owns that. When someone does, teams feel the benefit almost immediately.
Knowledge manager — builds and maintains the structured knowledge AI depends on. I hear the same thing from leaders again and again: AI is only as good as the content you give it. This role is rapidly evolving from classic knowledge management into knowledge strategy — part content designer, part systems thinker, part information architect. Their job is to build the knowledge scaffolding that lets AI answer accurately, consistently, and safely.
Here’s how the knowledge manager creates leverage.
1. Writes, maintains, and improves support knowledge — continuously. After every product change, they update articles, remove duplication, resolve contradictions, and pay down “knowledge debt” that quietly erodes accuracy. The upkeep is shaped by AI performance; when patterns expose gaps, they fix the source.
2. Structures knowledge for AI, not for browsing. Traditional help centers are for humans skimming pages. AI needs clean intent signals, crisp formatting, and clearly structured language. The knowledge manager designs that structure as intentionally as the content itself.
3. Works hand-in-hand with AI ops. Many performance issues stem from missing or unclear knowledge. When the AI ops lead surfaces recurring misunderstandings or low-resolution categories, the knowledge manager resolves the root cause at the source.
4. Ensures accuracy and compliance at scale. As AI handles more sensitive situations, the knowledge manager safeguards correctness, currency, and compliance — critical for data governance and regulatory alignment.
5. Develops a cross-functional knowledge strategy. The role creates a canonical, cross-functional source of truth that product, engineering, product marketing, go-to-market, and support (AI and human) can all rely on.
Why this role exists now. This is one of the highest-leverage positions in an AI-first support org. Teams like Rocket Money and Anthropic are hiring knowledge managers because AI accuracy depends on the quality of knowledge feeding it. Without this role, resolution rate caps out early and never climbs.
Conversation designer — designs how the AI speaks, clarifies, and interacts. AI isn’t just a tool customers use; it’s a representative they interact with. Tone, clarity, pacing, and conversational structure matter, especially in voice. Every word affects perceived expertise, trustworthiness, and brand. The conversation designer ensures the AI feels human-friendly without pretending to be human — the sweet spot that builds trust without misleading customers.
In my experience, staffing conversation design early accelerates results. It changes not only how we tune AI, but how we understand the end-to-end customer experience.
Here’s what great conversation design looks like.
1. Shapes the AI’s tone, voice, and communication style. This role refines phrasing, tunes politeness, adjusts how confusion is handled, and shapes micro-interactions that determine whether customers feel cared for or dismissed. On voice channels, natural cadence is make-or-break.
2. Designs flows for high-value conversations. They design how the AI clarifies intent, branches, communicates uncertainty, verifies details, escalates, hands off, and returns to the main thread without feeling mechanical — treating customer experience as a product with language as the interface.
3. Translates procedures and complex workflows into natural language and logic. As AI runs structured procedures and actions, this role becomes a conversational system architect, translating SOPs into conditional logic with exceptions and fallbacks. For example, in Intercom, our conversation designer uses Simulations to run simulated conversations to see where the AI Agent gets confused, over-confident, or awkward, and refine flows until the interaction feels effortless end-to-end.
4. Ensures transitions to humans feel smooth and respectful. Handoffs should provide clear context to the human agent and maintain continuity so customers never feel dropped.
Why this role exists now. As AI becomes the primary interface, conversation design directly influences trust, brand perception, and operational outcomes. It’s a core competency for any Generative AI and LLMs for product managers program.
Support automation specialist — builds the backend actions that allow AI to do real work. If the conversation designer shapes expression, this role shapes capability. They transform AI from an answering machine into an outcome engine by bridging AI and the systems it must safely and deterministically act on.
Support teams increasingly expect AI to do what a human would do: refund a charge, adjust a subscription, verify an identity, update an account setting, or pull relevant data. That expectation creates a new technical role at the edge of support, ops, and engineering.
What I rely on this specialist to deliver.
1. Creates and maintains backend workflows the AI executes. This includes building and maintaining: Fin Tasks. Fin Procedures with embedded steps. Action flows that call internal and external APIs. Automations that span billing systems, user identity layers, CRM objects, subscription entitlements, refund tools, and more. They ensure the AI can act compliantly and predictably — the playbooks that turn intent into action.
2. Owns the integrations required for advanced automation. Many problems require data elsewhere — billing platforms, internal databases, systems of record. The specialist ensures the AI can retrieve, validate, and use that information safely, often partnering closely on CRM integration and internal services.
3. Partners closely with product and engineering. Some workflows require new endpoints, permission layers, safety gates, or deterministic fallbacks. This role drives those changes across the stack.
4. Ensures reliability and safety at every step. Guardrails, validation logic, exception handling, safe execution paths — all are essential. They confirm that the AI has access to the correct data, the action matches policy, edge cases are accounted for, risky flows have deterministic constraints, and every action is auditable and reversible.
Why this role exists now. Customers don’t want answers, they want outcomes. AI can now deliver those outcomes, but only with the right backend scaffolding. This role modernizes operational architecture and unlocks end-to-end automation.
How these roles work together — the new operating loop. These roles aren’t silos; they’re interdependent parts of one system. The AI ops lead identifies patterns and performance gaps. The knowledge manager resolves inaccuracies or missing content. The conversation designer improves clarity, tone, and flow. The automation specialist expands the system’s ability to take action. Each improvement compounds the next, moving you from early automation to transformational resolution rates through continuous refinement.
This loop is what separates teams that plateau early from teams that scale AI into a reliable, high-performing system — the essence of a durable AI Strategy.
How to get started (even if you can’t hire all four roles today). Most teams phase into this model: assign partial ownership, formalize responsibilities, then specialize as AI volume grows. Here’s the progression I recommend.
Phase 1: Assign ownership. Give each role’s core responsibilities to someone who can devote five to 10 hours weekly. Early on, support ops, enablement, senior ICs, and technically inclined teammates can anchor the work.
Phase 2: Formalize the responsibilities. As AI resolves more queries, optimization becomes core operational work. Formalizing ownership prevents performance drift and knowledge debt.
Phase 3: Specialize and hire. Once AI handles 50–70% of incoming volume, these responsibilities become full-time roles. Investing in specialization becomes essential infrastructure for the next scale stage.
The bottom line. AI changes the shape of your support team. These four roles — AI operations lead, knowledge manager, conversation designer, and support automation specialist — form the backbone of the AI-first support organization. They bring order to a constantly changing environment and enable AI to deliver the outcomes leaders and customers expect heading into 2026.
Next week, we’ll continue the 2026 planning series with a deep dive into org design models for AI-first support teams — how to structure people, workflows, and accountability in a world where AI resolves most conversations before a human ever sees them.
To follow along with the series and have each new edition emailed to you directly, drop your details here.
I recently revisited a topic I once pushed back on: using AI to analyze (and maybe even synthesize) customer interviews. After six months of real-world experiments and countless conversations with seasoned product leaders, I’ve evolved my perspective. There is meaningful value here—but only when we’re clear about where AI helps and where it quietly erodes the hard-won customer understanding that powers great product decisions.
If you want to experience the conversation that sparked this reflection, you can listen to the episode on Spotify or Apple Podcast, and watch the discussion here: YouTube. It’s a candid, practical exploration of AI’s role in continuous discovery, and it mirrors what I’m seeing on the ground with product trios and empowered product teams.
Here’s the crux: AI raises the floor for beginners but accelerates experts even more. That matches my experience—early-career PMs get structure, momentum, and a confidence boost, while experienced interviewers can move faster without sacrificing nuance. But there’s a catch. If your interviewing skills aren’t solid yet, AI can create a veneer of insight that masks shallow understanding. In other words, it can help you go wrong more efficiently.
The conversation makes an important distinction between analysis and synthesis. Analysis is about extracting signals from the interview. Synthesis is about building meaning—connecting patterns, weighing contradictions, and deciding what to do next. AI can speed up the former with summaries and highlights. The latter—true synthesis—still demands expert judgment, context, and empathy.
One line from the episode stuck with me: your unpolished interview skills matter more than any shiny new AI workflow. I’ve felt that firsthand. When interview quality is uneven, dropping transcripts into an LLM won’t save you. You still need to synthesize every interview individually so the signals remain traceable and credible. That discipline keeps teams aligned, prevents overfitting to noise, and builds the organizational memory that fuels better bets.
We also explored the operational reality most teams face: interviews pile up. Backlogs grow. Leaders want speed. This is where “expert + AI” shines. With the right prompts, templates, and context, tools like ChatGPT and Claude can help transform raw transcripts into structured artifacts you can trust—provided a strong interviewer sets the frame and makes the calls. That balance preserves both velocity and quality.
What changed my mind most was the evidence from experiments—running sets of interviews through different LLMs and comparing outcomes. The patterns were consistent: beginner + AI is usually better than nothing, but the real performance gains come from expert + AI. When experts guide the process, AI becomes an accelerant rather than a crutch.
A favorite story in the episode takes a detour into building a gaming PC—an unexpected but perfect metaphor for AI’s limits. You can get great step-by-step guidance from a model, but when context shifts or edge cases appear, expertise is what keeps you from making expensive mistakes. Customer interviews are like that. Empathy comes from human interaction; AI can’t replace the experience of talking directly to your customers.
My practical guidance for teams integrating AI into continuous discovery: start with interviewing fundamentals, separate analysis from synthesis, and standardize how you capture single-interview learnings. If you need a tight template for this, refer to “The Interview Snapshot: How to Synthesize and Share What You Learned from a Single Customer Interview.” Use AI for summaries, clustering, and draft artifacts—but have an expert finalize the narratives, evaluate trade-offs, and document assumptions.
If you’re scaling this across an organization, invest in training first, then in workflows. Build a lightweight operating system for discovery: consistent interview guides, “story-based” techniques, and a shared library of prompts. Consider resources like “The Interview Coach,” as well as practical write-ups such as “Customer Interview Analysis: Where AI Helps and Hurts.” These help teams avoid common pitfalls and make better use of AI in high-judgment moments.
My bottom line: AI isn’t magic. It can help, but only if your interviews are strong and you provide the right context. Customer understanding is a competitive moat; outsourcing it entirely will cost you in the long run. Use AI to accelerate—not replace—the human judgment that makes product discovery work.
Resources and links worth exploring: ChatGPT, Claude, The Interview Snapshot: How to Synthesize and Share What You Learned from a Single Customer Interview, The Interview Coach, and Customer Interview Analysis: Where AI Helps and Hurts.
I’d love to hear how your team is using AI in discovery. What’s working, what’s risky, and where do you draw the line between automation and judgment? Share your experiences in the comments—our community learns faster when we compare notes.
When I push our organization to adopt the product operating model, I’m emphasizing a foundational shift—from “shipping roadmaps of features (output)” to solving real customer and business problems, measured by “business results (outcomes)”. That’s the difference between activity and impact, and it’s the only way to build durable value at scale.
This change inevitably reaches beyond the product organization. It reshapes how company stakeholders in Sales, Marketing, Customer Success, Finance, Legal, Security, and Operations engage with product teams, and it reframes what they expect from us. Instead of asking, “When will feature X ship?” they learn to ask, “How will we move the outcome that matters?”
In practice, the product operating model is a contract: product teams commit to outcomes, and stakeholders commit to partnership. That partnership means we co-own the problem, align on evidence, and share accountability for results. The reward is clarity—everyone sees how their work ladders to strategy and why the sequence of work makes sense.
Here’s how I align stakeholders around this model. First, I ground everything in outcomes vs output OKRs. We replace feature roadmaps with a clear strategy, prioritized problems, and measurable objectives. Our product roadmapping and sprint planning then serve the objectives—not the other way around—so capacity is allocated to the highest-leverage bets.
Second, I build empowered product teams around product trios (product, design, engineering). We practice continuous discovery with stakeholders: we share opportunity trees, test riskiest assumptions early, and bring partners into research when it informs go-to-market strategy, pricing, or enablement. This keeps us honest and avoids late-stage surprises.
Third, I establish operating rhythms that make outcomes visible. Monthly stakeholder reviews focus on progress toward objectives and what we’re learning—not status theater. Quarterly, we connect OKRs to business performance so leaders can see the throughline from discovery and delivery to pipeline, retention, or margin. If priorities shift, we renegotiate objectives explicitly.
Fourth, I define metrics that stakeholders trust. We use a balanced set of leading indicators (activation, engagement, cycle time) and lagging indicators (revenue, retention, unit economics). We socialize definitions early so no one debates the scoreboard mid-game. The result: faster decisions and less “data whiplash.”
Fifth, I invest in change management. Moving from outputs to outcomes can feel threatening if your success has historically been measured by launch volume or roadmap commitments. I address this head-on with training, transparent comms, and clear decision rights. The message is simple: outcomes create more autonomy for empowered product teams and more predictability for stakeholders.
At HighLevel, this approach has been especially powerful when cross-functional dependencies are high. For example, when we set an objective to improve user activation for a new CRM integration, we didn’t promise a bundle of features. We committed to a measurable lift in activation and a shorter time-to-value, co-owned with Customer Success and Marketing. That alignment unlocked smarter experiments, tighter enablement, and a more credible launch narrative.
The anti-patterns are predictable: treating OKRs as a renaming of the roadmap, equating discovery with indecision, or isolating product decisions from go-to-market strategy. The cure is equally consistent: bring stakeholders into discovery, attach every bet to an objective, and show progress with evidence—not just demos.
Ultimately, the product operating model is a leadership choice. It asks us to trade certainty theater for learning velocity, and feature checklists for business impact. When stakeholders see that shift pay off—in faster cycles, clearer priorities, and results that matter—support for the model moves from compliance to conviction.
By 2026, the AI Product Owner will be the keystone role that turns AI strategy into measurable business outcomes. In my teams, this seat bridges market insight, model capability, data governance, and shipping velocity—so product decisions are not just clever, but compliant, reliable, and fast.
I often describe the remit simply: "Here is your clear guide to the AI product owner role (skills, responsibilities, how it differs from PM) and ways AI tools supercharge delivery." In practice, the AI Product Owner translates business goals into model-backed experiences, aligns cross-functional execution, and ensures the product’s AI behavior remains safe, lawful, and on-brand under real-world constraints.
How does this differ from a traditional PM? While Product Management sets portfolio strategy, positioning, and market narratives, the AI Product Owner owns the AI experience end-to-end—data readiness, evaluation harnesses, safety guardrails, and the iterative model improvements that drive outcomes vs output OKRs. I anchor the role inside empowered product teams and product trios (PM/Design/ML Eng) to keep discovery continuous and delivery disciplined.
On responsibilities, I expect four pillars. First, discovery: continuous discovery with customers and internal experts to uncover use cases where generative AI or LLMs beat the status quo. Second, experience: define the right interaction patterns for AI UX, including retrieval-first pipeline choices, context window management, and feedback loops for human-in-the-loop correction. Third, governance: privacy-by-design, AI risk management, data governance, and regulatory compliance baked into the roadmap. Fourth, delivery: CI/CD for models and prompts, observable evaluation with A/B testing and minimum detectable effect (MDE), and SRE-grade incident management when AI behavior drifts.
Skills-wise, I look for product sense plus technical fluency. That includes LLMs for product managers (prompting, grounding, RAG), analytics mastery (Amplitude analytics, retention analysis, activation metrics), and comfort with DORA metrics and deployment frequency to keep iteration high but safe. Strong stakeholder management and clear writing are non-negotiable—AI capabilities evolve fast, and leaders must see risk, cost, and ROI with no ambiguity.
AI tools truly supercharge delivery when they eliminate bottlenecks. My practical stack: an AI product toolbox with Claude Code and a ChatGPT connector for rapid prototyping; CustomGPT workflows for support triage and internal knowledge; Pendo product tours and in-app guides to validate behavior changes; Intercom for customer support ai strategy; and tight CRM integration via HubSpot to measure revenue impact. The outcome is faster idea-to-learning cycles, sharper telemetry, and far cleaner handoffs.
For roadmapping, I prioritize thin slices that prove value early—shipping narrowly scoped assistants or copilots, then expanding with product roadmapping and sprint planning that ties capability unlocks to outcomes. A unified analytics platform helps compare human-only baselines to augmented workflows, while agentic AI patterns automate routine steps under strict guardrails.
Risk is a product surface, not a side task. I require explicit policy gates (PII handling, red-teaming, bias audits), clear escalation paths, and incident playbooks. When we treat policy and reliability as features, customers reward us with deeper adoption and higher trust.
If you’re pursuing the AI Product Owner path, build a portfolio around shipped learnings: the experiment you killed with data, the safety constraint you designed, the postmortem you led, and the business metric you moved. That story—evidence of disciplined discovery, responsible delivery, and real-world results—is exactly what teams (and boards) want to see in 2026.
