Tag: product management leadership

Innovation Strategy in the Age of AI: Proven Playbooks, Real-World Examples, and What Works Now

AI has rewritten the rules of how we create value, and I’ve watched the most resilient organizations treat innovation as a disciplined, outcomes-driven capability—not a one-off initiative. In my role leading product teams, I’ve refined a practical approach that blends rigorous product management with an adaptive AI Strategy so we can ship faster, learn faster, and de-risk smarter.

Learn what an innovation strategy is, how to build one, which types to use, and see real examples that drive meaningful change.

At its core, an innovation strategy is the intentional system that aligns vision, portfolio bets, and execution mechanics to measurable business outcomes. I anchor this in outcomes vs output OKRs, ensuring every experiment, feature, and GTM motion ties to a clear value proposition and reinforces hard-won product-market fit lessons rather than chasing novelty.

I design portfolios around three types of innovation that work well in the age of AI. First, core optimization: drive compounding gains with CI/CD, DORA metrics, and A/B testing to improve activation, retention, and profitability. Second, adjacent expansion: extend value via new segments, channels, or use cases—often enabled by product-led growth tactics like in-app guides and product tours. Third, transformational bets: leverage gen ai and agentic AI to create step-change capabilities while proactively addressing AI risk management, data governance, and privacy-by-design.

Building the strategy starts with empowered product teams and product trios who run continuous product discovery to validate problems before validating solutions. I keep discovery tight with a minimum detectable effect (MDE), instrument the journey with a unified analytics platform, and thread learnings into product roadmapping and sprint planning so we prioritize the smallest, fastest path to decision-quality data.

On the AI front, my operating model combines an AI product toolbox (prompt patterns, evaluation harnesses, and safety rails) with LLMs for product managers to accelerate research, prototyping, and content generation. We standardize CustomGPT workflows where appropriate, define CRM integration and data boundaries early, and adopt a clear build/partner/buy decision tree to protect focus and speed without compromising risk posture.

Here are real patterns that consistently deliver meaningful change. We’ve used generative AI for product prototyping to compress concept validation from weeks to days, then confirmed impact with rapid A/B testing tied to MDE. We’ve implemented agentic AI for customer support triage to reduce response times and free human agents for high-complexity cases, all under strict data governance. And we’ve paired new AI features with a focused go-to-market strategy—clear positioning, sharp onboarding, and outcome-centric messaging—to accelerate user activation.

Measurement makes or breaks innovation. I combine deployment frequency and DORA metrics on the engineering side with activation, retention analysis, and value-moment telemetry on the product side. QBRs vs OKRs alignment keeps leadership focused on outcomes, while experiment scorecards ensure we learn even when results are neutral. The goal is to increase the rate of validated learning across the portfolio, not just ship more.

Governance is a feature, not a tax. We embed threat detection and response, privacy-by-design, and transparent data policies from day one. Stakeholder management and board management stay tight with simple narratives: the bet, the hypothesis, the metric, the MDE, the timeline, and the kill-or-scale criteria. That clarity builds trust and protects speed.

If you’re recalibrating your innovation strategy right now, start small and deliberate: define the outcomes, select one core, one adjacent, and one transformational bet, and wire in learning loops from discovery to delivery. With empowered product teams, disciplined analytics, and a pragmatic AI Strategy, you can move from interesting ideas to durable competitive differentiation—faster and with far less risk.

Inspired by this post on Product School.

November 3, 2025
Upskilling vs. Reskilling: My Playbook to Future‑Proof Teams, Boost Retention, and Ship Faster

In fast-moving product organizations, the skills that got us here won’t carry us through the next wave of change. I’ve learned that future-proofing a team is less about hiring unicorns and more about deliberately growing the skills we already have—and doing it with intention.

Upskilling and reskilling aren’t the same. Knowing the difference can help you build smarter teams and avoid costly missteps in your L&D strategy.

Here’s how I frame it with my leaders: upskilling deepens capability in the role someone already holds—think strengthening discovery, data fluency, or stakeholder management inside an existing lane. Reskilling pivots talent into a new lane—say, a support engineer into data engineering or a product marketer into product operations. Both are essential to building empowered product teams, but they solve different problems.

Deciding which path to take starts with the roadmap and strategy. If your outcomes vs output OKRs signal a need for better execution in current domains, upskilling is the lever. If your strategy introduces new bets—gen AI, privacy-by-design, or a shift to platform architecture—reskilling becomes a strategic investment. I run a simple gap analysis: inventory current skills, map them to near-term outcomes, and identify high-leverage gaps by team.

When I upskill, I prioritize learning in the flow of work. That means structured practice—not just courses—embedded into product discovery, product trios rituals, and code reviews. Shadow sessions, lightweight playbooks, and in-app guides turn new concepts into repeatable muscle memory. For new managers, I add targeted coaching for the IC to manager transition, because role clarity and feedback fundamentals compound quickly.

When I reskill, I treat it like a product launch. There’s a clear charter, staged milestones, a mentor, and onboarding tailored to the new role. I timebox practice projects, use product tours and internal sandboxes, and pair people with forward deployed engineers or senior PMs to accelerate context. The goal is confidence and competence, not just completion.

Measurement keeps the investment honest. I track time-to-productivity during onboarding, deployment frequency and DORA metrics for engineering-heavy paths, and retention analysis for people outcomes. For product and design, I look at decision quality in discovery, reduced cycle time from insight to iteration, and the clarity of written strategy. All of it rolls up into OKRs so learning is tied to business outcomes, not just activity.

The AI wave has made this even more urgent. I’m deliberately upskilling PMs on LLMs for product managers, responsible AI Strategy, and data governance, while reskilling a subset of engineers and analysts into applied gen AI roles. We cover prompt design, evaluation frameworks, and privacy-by-design basics, then ship small internal tools to turn theory into practice.

Culture makes or breaks all of this. I set explicit learning budgets, protect focus time, and model the behavior—publishing my own learning roadmaps and post-mortems. Stakeholder management matters too: I align expectations in QBRs vs OKRs, broadcast progress, and celebrate skill gains the same way we celebrate product wins. When people see that growth is visible and valued, momentum builds.

One example that sticks with me: we reskilled a cross-functional cohort into analytics and experimentation while simultaneously upskilling our existing PMs in discovery synthesis. Within a quarter, decisions got crisper, experiments shipped faster, and collaboration across product trios felt effortless. The compounding effect was unmistakable.

If you’re starting from zero, keep it simple: map the skills you have, the outcomes you need, and choose one upskilling and one reskilling initiative you can deliver in the next 90 days. Make learning visible, measure what matters, and iterate. The teams that master this discipline won’t just keep up—they’ll set the pace.

Inspired by this post on Product School.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Inspired by this post on Product School.

November 3, 2025
9 Corporate Innovation Trends Redefining Business—and How I’m Turning Them into Wins

Corporate innovation isn’t a side project anymore—it’s the operating system for how we build, scale, and win. In my product leadership work, I’ve watched the pace of change accelerate across every function, from engineering and data to go-to-market and customer success. The companies pulling ahead are the ones translating trends into execution with clarity, speed, and measurable outcomes.

We researched corporate innovation to reveal top trends, types, and examples that can spark growth and keep your business ahead.

Here’s how I’m seeing that play out right now—and the nine trends I’m actively using to guide roadmaps, prioritize bets, and ship value faster.

Trend 1: Generative AI is moving from pilots to products. Teams are evolving beyond demos into durable capabilities powered by gen ai, LLMs for product managers, and agentic AI patterns that automate workflows end-to-end. The winners pair bold AI Strategy with AI risk management, privacy-by-design, and clear value propositions so customers trust what we ship and can see its impact on outcomes, not just outputs.

Trend 2: Product-led growth is becoming the default go-to-market motion. I’m doubling down on onboarding, in-app guides, product tours, and activation loops that reduce time-to-value. We back this with disciplined A/B testing, well-chosen minimum detectable effect (MDE), and retention analysis to prove what actually moves the needle. PLG isn’t a tactic—it’s a cultural shift toward continuous learning and self-serve experience design.

Trend 3: Unified analytics and experimentation are the new backbone. A unified analytics platform, instrumented with tools like Amplitude analytics, Pendo, and CRM integration via HubSpot or Intercom, gives us a single source of truth from acquisition through expansion. I push teams to connect user journeys to revenue and to operationalize insights into roadmapping and sprint planning—not monthly reports that sit on a shelf.

Trend 4: Outcome-driven operating models are replacing feature factories. We align on outcomes vs output OKRs, empower product teams, and structure product trios to balance customer insight, technical feasibility, and commercial impact. First principles decision making helps us cut through noise, set sharper points of parity, and focus on differentiation that customers will pay for.

Trend 5: Velocity and reliability matter more than ever in engineering. Continuous delivery via CI/CD, healthy deployment frequency, and DORA metrics are my leading indicators for a team’s ability to learn fast. I’ve seen forward deployed engineers and thoughtful developer evangelism tighten the feedback loop with customers and speed up iteration without compromising quality.

Trend 6: Data governance and security are strategic differentiators. Trust is a product feature. I prioritize data governance, cybersecurity, and threat detection and response alongside usability. Privacy-by-design isn’t a compliance checkbox; it’s table stakes for enterprise adoption and a durable moat when paired with transparent controls and auditability.

Trend 7: Pricing and packaging innovation is unlocking growth. We’re testing SaaS pricing models, including consumption SaaS pricing, to align value delivered with value captured. Clear articulation of the value proposition and thoughtful packaging reduce friction in sales and support product-led expansion. Pricing experiments belong in the product backlog—not just in finance spreadsheets.

Trend 8: Customer-in-the-loop discovery is the fastest path to relevance. I treat product discovery as a continuous practice, weaving QBR-style business reviews into roadmaps and using stakeholder management to align incentives across sales, success, and product. Customer support ai strategy helps surface high-signal insights from tickets and conversations, turning support into a discovery engine.

Trend 9: Open platforms and ecosystems amplify innovation. From API-first thinking and ChatGPT connector patterns to integrations that meet customers where they work, ecosystems drive stickiness and reduce time-to-value. The strongest roadmaps combine a focused core with extensibility that partners and customers can build on.

How to act now: I recommend a simple try do consider framework. Try one high-conviction AI use case with clear guardrails. Do instrumented experiments across onboarding and activation to fuel product-led growth. Consider pricing and packaging tests tied to measurable outcomes. With disciplined learning cycles and empowered teams, these trends stop being headlines—and start becoming compounding advantages.

Innovation favors teams that ship, learn, and adapt. If these trends are on your roadmap, align them to outcomes, measure obsessively, and keep customers in the loop. That’s how we turn momentum into durable growth.

Inspired by this post on Product School.

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

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

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

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

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

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

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

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

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

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

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

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

Inspired by this post on Product School.

November 3, 2025
8 Proven Strategies I Use to Upskill Teams Fast and Future-Proof Our Edge in the AI Era

Your team’s skills have an expiry date. Here’s how to upskill employees before the clock runs out and your edge goes with it.

I’ve learned that upskilling isn’t a one-off training day—it’s an operating system for building resilient, empowered product teams. When we treat learning as a product, with clear outcomes, feedback loops, and constant iteration, we future-proof both our people and our roadmap. Below are the eight strategies I rely on to upskill employees quickly and sustainably while strengthening employee retention and execution quality.

1) Anchor upskilling to strategy and outcomes. I start by mapping critical capabilities to our company strategy and outcomes vs output OKRs. This makes learning unambiguously relevant: every course, cohort, and coaching session ladders up to measurable value. If a skill doesn’t advance our north-star metrics or customer outcomes, it doesn’t make the cut.

2) Build a learning operating system, not a library. Content without cadence is shelfware. I establish a predictable rhythm—monthly skill sprints, short microlearning modules embedded in workflows, and quarterly capability reviews during planning. We integrate upskilling into onboarding, QBRs vs OKRs check-ins, and product roadmapping so learning time is protected, visible, and non-negotiable.

3) Design role-based paths with clear ladders. I create skill matrices for PMs, designers, engineers, and GTM partners, then craft levelled learning paths to close gaps. We use the 70-20-10 model (doing, coaching, coursework) and pair it with individual development plans, so growth is personalized but standardized enough to scale. This clarity boosts motivation and speeds up onboarding.

4) Learn by shipping real value. The fastest learning happens on real products. I pair courses with stretch assignments tied to live initiatives—product discovery sprints, customer shadowing, rapid prototyping with gen ai, and cross-functional product trios. We treat these as safe-to-try experiments with clear success criteria, so teams upgrade skills while moving the roadmap forward.

5) Institutionalize coaching and peer learning. I formalize mentorship, guilds, and weekly critique sessions to turn tacit knowledge into shared practice. We run cross-team demos and communities of practice so lessons travel fast. Managers coach to outcomes, not checklists, and we reward people who teach—because knowledge multiplied beats knowledge hoarded.

6) Measure capability, not attendance. I avoid vanity metrics. Instead, I look for leading indicators that learning is changing behavior and outcomes: higher quality product discovery, clearer product positioning, tighter stakeholder management, improved deployment frequency, and stronger retention analysis. Where appropriate, we set a minimum detectable effect (MDE) for skill experiments to ensure we can actually see impact.

7) Fund time, not just tools. Upskilling dies when calendars are full. I carve out recurring maker time for learning, set explicit expectations in performance plans, and tie promotions to demonstrable capability growth. We provide stipends for courses and certifications, but the real unlock is creating space and manager accountability so learning sticks.

8) Use AI strategically to accelerate practice. We embed AI Strategy thoughtfully: gen ai co-pilots for research synthesis, scenario role-plays for stakeholder conversations, and guided feedback for UX writing and product tours. The rule is simple—AI should compress cycle time and elevate judgment, not replace it. I encourage teams to document prompts and playbooks so good patterns compound.

To align and de-risk, I bring stakeholders into the loop early—finance to co-own ROI, HR to integrate paths into career frameworks, and functional leaders to ensure parity across teams. This alignment reduces friction, strengthens product-led growth, and keeps the effort resilient through reorgs and strategy shifts.

The outcome of this approach is simple: faster time to competency, higher confidence, and a culture where learning is part of how we build. Upskilling is the most durable competitive advantage I know—because tools change, but teams that learn together win together. If your edge feels like it’s slipping, start small, make it visible, and iterate. Your future roadmap—and your people—will thank you.

Inspired by this post on Product School.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Inspired by this post on Product School.

November 3, 2025
How Fast Is Fast Enough? Turn Deployment Frequency into a Durable Competitive Advantage

Every product leader I know wrestles with the same question: how fast is fast enough when it comes to shipping? Over the years, I’ve learned that deployment frequency isn’t just a DevOps vanity metric—it’s a direct lever on customer value, risk, and competitive advantage.

When I talk about deployment frequency, I mean how often a team puts code into production, per service or product, in a given time period. It sits alongside lead time for changes, change failure rate, and mean time to recovery (MTTR) as part of the DORA metrics—together, they tell a coherent story about delivery performance and reliability.

If you’re looking for a compass, here’s how I calibrate expectations. Elite teams deploy on demand—often multiple times per day—because they’ve engineered safety into their CI/CD pipeline and decoupled deploy from release. High-performing teams comfortably ship daily to weekly. Medium performers land in the weekly-to-monthly range. These bands aren’t moral judgments; they’re context-aware guideposts. The goal isn’t to copy someone else’s speed, but to reach the fastest sustainable cadence your business, architecture, and risk profile can support.

So what does “fast enough” look like in practice? It depends on your product’s blast radius, regulatory constraints, and architecture. Microservice-heavy platforms with strong automated testing, feature flags, and progressive delivery generally sustain higher cadences with lower risk. Monoliths and highly coupled systems can still move quickly, but they need disciplined trunk-based development, robust test pyramids, and strong release controls to avoid brittle deployments.

At HighLevel, we’ve moved products from a cautious weekly train to safe daily (and eventually on-demand) deploys without increasing incident volume. The breakthrough wasn’t a single tool—it was a system: smaller batch sizes, automated tests that actually fail when they should, immutable artifacts, canary releases, and feature flags that decouple deployment from exposure. The result was faster learning loops, fewer late surprises, and more predictable delivery.

If you’re not measuring deployment frequency yet, start simple. Instrument your CI/CD pipeline or GitOps tooling to count production deployments by service each day. Normalize for rollbacks and re-deploys to avoid inflating the metric. Visualize by team and product area so you can spot bottlenecks and trend improvements over time. Pair it with change failure rate and MTTR to ensure you’re not trading speed for stability.

Once you’ve got a baseline, focus on the levers that actually move the needle. Reduce batch size by merging smaller, well-scoped changes. Embrace trunk-based development to minimize long-lived branches. Accelerate feedback with fast, reliable unit and integration tests, contract testing for services, and ephemeral environments for preview. Use feature flags to control exposure, and progressive delivery (canary, blue-green) to verify in production safely. Automate change approvals where policy allows, and replace heavyweight gates with observable, auditable pipelines.

Watch out for common anti-patterns. Batching several unrelated features into a single deploy increases risk and slows learning. Heroic “release nights” mask systemic issues. Friday deploy bans are a smell; if you can’t safely deploy on Friday, you can’t safely deploy any day—invest in recovery speed and blast-radius controls instead. And never treat deployment frequency as a target in isolation; it’s only healthy when reliability improves or holds steady.

For strategy alignment, I tie deployment goals to outcomes, not outputs. If your objective is time-to-value or activation improvement, a higher cadence of small, measurable changes aligns perfectly. If your objective is stability for a major seasonal event, slow the cadence temporarily and increase release controls. The point is to let business outcomes set the tempo while engineering creates the conditions for safe speed.

Here’s a pragmatic 30-day plan I’ve used with teams: Week 1, baseline deployment frequency and map your current release process end-to-end. Week 2, choose two services and cut batch size in half while enabling feature flags for new code paths. Week 3, refactor the pipeline for faster test feedback and add canary or blue-green for one critical service. Week 4, publish a dashboard that shows deployment frequency alongside change failure rate and MTTR, and run a retrospective to decide the next bottleneck to remove.

Culturally, celebrate small, frequent, reversible changes. Reward teams for boring deploys, rapid recovery, and high-quality instrumentation. Build psychological safety around rollback and kill switches—confidence breeds cadence.

Track deployment frequency, optimize it, and watch delivery speed turn into a competitive edge. Explore how in this article!

Fast enough isn’t a number you copy; it’s a capability you build. When deployment frequency rises in tandem with reliability, you unlock faster learning, happier customers, and a durable advantage in your market.

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
AI vs. Product Managers by 2035: What Will Change—and How to Future‑Proof Your Career

Will AI replace product managers, or simply transform their role? Discover what AI can and cannot do, plus insights from PMs on the future of work.

I’m asked this question in nearly every leadership meeting now, and my answer is consistent: AI won’t replace great product managers by 2035—but it will radically reshape how we operate. The PMs who thrive will pair sharp product judgment with an intentional AI Strategy and a practical AI product toolbox, unlocking speed, clarity, and scale without sacrificing vision.

Here’s what AI already does well for us today. With LLMs for product managers, I can synthesize customer feedback at scale, draft PRDs and acceptance criteria, transform notes into user stories, and even auto-generate experiment plans with a minimum detectable effect (MDE) calculation. When I connect these models to Amplitude analytics, Pendo, Intercom, and HubSpot through a unified analytics platform and CRM integration, I accelerate discovery, prioritize confidently, and tighten the loop between signal and action. CustomGPT workflows now handle routine backlog grooming, competitive landscaping, and early concept testing, freeing my team to focus on higher-order decisions.

By 2035, I expect agentic AI to operate as an execution co-pilot: autonomously scheduling A/B testing, launching targeted in-app guides and product tours, monitoring user activation and onboarding funnels, and raising anomalies via Agent Analytics long before a dashboard review. These systems will propose playbooks, draft UX writing and tooltip design, and recommend next-best actions—then wait for human approval when stakes are high. Think of it as the ultimate forward deployed engineer for operational work, working within clear guardrails.

What AI cannot do—and is unlikely to master soon—is the essence of product leadership. It won’t craft a resonant value proposition for a new segment, define points of parity vs. competitive differentiation, or set outcomes vs output OKRs that align messy stakeholder incentives. It won’t navigate board management, reconcile conflicting narratives from sales and engineering, or make ethically grounded trade-offs under uncertainty. That’s where privacy-by-design, data governance, and AI risk management converge with human judgment, context, and accountability.

As the tooling matures, the PM role will tilt from artifact production to decision quality. We’ll spend less time writing and more time deciding: which bets to place, which risks to accept, and where to concentrate our empowered product teams. Product discovery deepens, product positioning sharpens, and product roadmapping and sprint planning become faster and more adaptable—because the busywork is handled, not because the thinking is outsourced.

Practically, I’m evolving team design and rituals now. We operate as product trios, pair PMs with forward deployed engineers, and embed gen ai into daily workflows. We standardize prompts, set review thresholds, and instrument everything for observability. Our stakeholder management improves because we bring clearer narrative artifacts—and because we can test assumptions earlier and share evidence in real time.

If you’re building your own AI Strategy, start with three tracks. First, foundations: instrument data pipelines, establish data governance, and codify privacy-by-design. Second, acceleration: deploy CustomGPT workflows for research synthesis, PRD drafting, retention analysis, and experiment design, while keeping humans in the loop for decisions. Third, automation with guardrails: let agentic AI run low-risk playbooks (in-app guides, content suggestions, ops checks) and require human approval for anything customer-facing and irreversible.

Future-proofing your career is about skill stacking. Double down on first principles decision making, storytelling, and cross-functional influence, and pair that with hands-on fluency in gen ai, prompt engineering, model evaluation, and risk controls. Learn how to frame trade-offs, architect outcomes vs output OKRs, and translate strategy into experiments that AI can help execute. The combination—human judgment plus machine speed—is the new competitive advantage.

So, will AI replace product managers by 2035? No. It will transform average PMs into good ones and great PMs into force multipliers. The ones who lead will embrace AI as leverage, cultivate empowered product teams, and stay relentlessly focused on customer outcomes. The future belongs to product creators who can wield intelligent tools without surrendering accountability for the product’s direction and impact.

Inspired by this post on Product School.

November 3, 2025
RAG for Product Managers: Transform Strategy, Speed Discovery, and Win with Confidence

I’ve watched Retrieval-Augmented Generation (RAG) shift from a buzzword to a practical advantage that changes how my team discovers insights, makes roadmap bets, and competes. When I ground large language models in our own product, customer, and market data, I make faster decisions with more confidence—and I spend far less time debating opinions and more time shipping outcomes.

Think RAG for product managers is just AI hype? Wait until you see the use cases and ways it’s reshaping your work and product strategy.

RAG connects the power of LLMs with the credibility of your internal knowledge: user research, support tickets, win/loss notes, specs, QBRs, and analytics. Instead of generic answers, I get contextual, citeable responses that reflect our reality. That means cleaner product discovery, sharper product positioning, and a clearer value proposition grounded in customer truth.

Day to day, I use RAG to accelerate product discovery by synthesizing interviews and feedback across channels; to de-risk roadmapping by surfacing evidence behind feature requests; and to power go-to-market strategy with crisp messaging that maps to points of parity and true competitive differentiation. It’s equally effective for onboarding new PMs, increasing stakeholder alignment, and unblocking empowered product teams when signals are noisy or fragmented.

Execution still matters. I treat RAG like any critical system: prioritize data governance, privacy-by-design, and AI risk management. I integrate with our CRM and support stack so the model learns from live customer context, and I instrument everything with product analytics to track impact. When the outputs are measurable, RAG moves from novelty to operating system.

To start, I focus on a narrow, high-signal slice of the workflow—like summarizing support patterns or synthesizing discovery for a single segment—then iterate. I pair PMs with design and engineering in tight product trios, define quality criteria up front, and review answers with subject-matter experts. As quality rises, I scale to roadmapping and product-led growth experiments, always validating with users before I automate.

The payoff is real: faster decisions, clearer narratives, and fewer surprises. RAG won’t replace the craft of product management, but it will amplify it—giving us an edge in both speed and accuracy. If you’re serious about LLMs for product managers and want results you can defend, RAG is a strategic bet worth making now.

Inspired by this post on Product School.

November 3, 2025