Category: Leadership

Product Tree 101: The Visual Prioritization Framework I Rely on to Align Teams Fast

When my team is drowning in requests, the Product Tree is the visual tool that brings clarity and momentum. "Learn what a product tree is, how to use the product tree framework, and why it’s a powerful tool for smarter product prioritization." That’s exactly what I aim to share here—how I use it to align stakeholders, sharpen product strategy, and translate ideas into outcomes.

A product tree is a simple yet powerful metaphor for your product. The trunk represents the core value, the roots are the technical foundations and platform capabilities, the branches are product areas or themes, and the leaves are features, experiments, or opportunities. By placing ideas as leaves on the right branches—and making sure roots can actually sustain that growth—we turn a messy backlog into a coherent product roadmap.

Why do product managers swear by it? Because it forces outcomes over outputs, exposes trade-offs visually, and reveals where strategy is thin or overgrown. In one view, you see customer value, technical debt, and strategic focus—crucial for empowered product teams, product discovery, and stakeholder management. It’s also an excellent way to connect outcomes vs output OKRs to tangible delivery paths.

Here’s how I set it up. First, I define the trunk with a crisp product value proposition and the minimum set of experiences that make the product viable. This anchors everything else so we don’t mistake a shiny leaf for the core of the tree.

Next, I map branches to clearly named themes that mirror how customers perceive value—onboarding, activation, collaboration, analytics, or reliability. I keep branches aligned to outcomes to avoid feature-first thinking; this pays dividends during product roadmapping and sprint planning.

Then I add leaves: research insights, customer requests, experiments, and enabling features. I note intent (e.g., drive activation, reduce churn), expected impact, and a rough effort signal. This quickly surfaces which leaves grow the product and which are just twigs.

Finally, I draw roots—the enabling platform work and technical investments that make the branches sustainable. Performance, data governance, privacy-by-design, and scalability belong here. If the roots can’t support the canopy, the tree is at risk, and that becomes a visible, prioritizable problem rather than an invisible liability.

Once the tree is sketched, I facilitate a collaborative session with product trios and cross-functional partners. We prune low-impact leaves, cluster work by outcomes, and explicitly link branches to OKRs. In QBRs vs OKRs reviews, the tree becomes our single source of truth for trade-offs, helping stakeholders see why some requests move up and others wait.

In practice, I use the Product Tree to shape a near-term delivery plan and a longer-horizon narrative. Near term, it informs sprint planning and sequencing by ensuring the right roots land before the heavier branches. Longer term, it clarifies the growth story for product-led growth—what we’ll grow next and why it matters for customers.

A few tips from the trenches: anchor branches to customer outcomes, not internal org charts; spotlight enabling work so platform investments aren’t deprioritized; and revisit the tree after each discovery cycle to keep it fresh. The moment the tree feels lopsided, that’s your signal to rebalance bets or revisit assumptions in product discovery.

If you’re preparing for your next planning cycle, try a 60-minute Product Tree workshop. You’ll come away with a shared mental model, sharper prioritization, and a roadmap that is easy to communicate and defend—because everyone can see the product’s future taking shape right in front of them.

Inspired by this post on Product School.

November 3, 2025
Stop Shipping for the Sake of It: Master Outputs vs. Outcomes to Build Products That Win

Too many teams still celebrate what they ship rather than what they change. I’ve learned—sometimes the hard way—that the most expensive mistake in product management is confusing outputs with outcomes. Understand the key differences between output vs. outcome in product management — and how to keep your team focused on what really drives results.

Here’s how I draw the line: outputs are the features, tickets, and releases we produce; outcomes are the measurable changes in user behavior and business performance we create—activation rates, retention, expansion, and time-to-value. If an initiative doesn’t move a metric that matters, it’s output without impact. That’s how feature factories are born.

The confusion is costly because it distorts incentives. Teams optimize for velocity, story points, or deployment frequency and mistake motion for progress. Engineering excellence and DORA metrics matter, but they’re not substitutes for product outcomes. When OKRs drift into task lists, we ship more and learn less. I’ve seen ambitious roadmaps hit every delivery date and still miss the market because we didn’t change customer behavior.

To break that cycle, I anchor planning and reviews to outcome-based OKRs. A good objective might be: increase new-account user activation from 28% to 45% this quarter. The anti-pattern is: ship onboarding redesign v2. The former sets a clear behavioral target; the latter constrains creativity and locks us into a solution before discovery. This is the practical heart of outcomes vs output OKRs.

From there, I define leading indicators that predict the desired outcome—time-to-first-value, completion of core actions, day-7 retention—and instrument them early. Tools like Amplitude analytics help us see whether an experiment is unlocking behavior change or just producing activity. I also set guardrail metrics (support volume, performance, and NPS) so we don’t “succeed” by creating a new failure mode.

The delivery model matters, too. Empowered product teams—built as product trios of product, design, and engineering—own the problem and the outcome. We invest in product discovery to validate assumptions, size opportunities, and find the minimum viable change that moves the metric. A/B testing with a clear minimum detectable effect (MDE) makes our experiments faster, cheaper, and more conclusive.

Roadmaps then become strategic bets rather than feature lists. Each bet articulates the opportunity, the hypothesized solution, the expected outcome, and the evidence that would change our mind. In sprint planning, we slice increments to learn sooner, not just to deliver sooner. CI/CD accelerates shipping; outcome instrumentation accelerates learning.

Stakeholder conversations shift as well. Instead of debating which features to build, we align on the customer problem, the value proposition, and the measures of success. QBRs showcase what changed—activation, adoption, retention—not just what shipped. This is how we move from feature requests to outcome commitments and sustain product-led growth.

I’ve found that outcomes-first execution energizes teams. Clarity of purpose invites creativity, and the autonomy to experiment fuels ownership. When we celebrate behavior change over backlog burn-down, we stop playing to the roadmap and start playing to win the market.

If your team is stuck in output mode, start small: rewrite one key objective as an outcome, instrument a leading indicator, and run a scoped experiment. When the metric moves, let that win reset the culture. Momentum follows outcomes.

Inspired by this post on Product School.

November 3, 2025
Your Ultimate ProductCon San Francisco 2025 Guide: Best Hotels, Eats & Drinks

Heading to ProductCon San Francisco 2025? I approach conference travel the same way I approach product strategy: optimize for outcomes, reduce friction, and invest in high-signal experiences. Here’s the playbook I use to choose the right hotel, find memorable meals, and make the most of every hour in the city.

For lodging, I prioritize walkability, safety, and quiet rooms so I can focus during sessions and recover at night. If you want to be steps from most venues and meetups, SoMa and the Yerba Buena corridor are ideal. InterContinental San Francisco, W San Francisco, and The Clancy (Autograph Collection) are reliable, business-friendly picks with strong Wi‑Fi and ample lobby space for impromptu one‑on‑ones. If you prefer classic energy and transit access, Union Square hotels like Hotel Nikko and The Westin St. Francis work well. For waterfront views and a calmer vibe, Hyatt Regency Embarcadero puts you by the Ferry Building with easy BART and Muni access.

My booking checklist is simple: reserve early, target a high floor away from elevators, and request early check‑in or late checkout around your session schedule. Loyalty programs often unlock better rates and quiet‑room preferences. If you need heads‑down time between talks, ask about day‑use meeting rooms or find a corner of the lobby with stable bandwidth. I also pack a compact power strip and a long USB‑C cable—two small upgrades that routinely save a day.

Coffee is the fuel of great product conversations. Near SoMa, I rotate between Blue Bottle (Mint Plaza), Sightglass (7th Street), and Philz (Front Street) for pre‑session caffeine and quick stand‑ups. If I’m on the Embarcadero side, the Ferry Building’s roasters are perfect for early starts, and morning lines move faster than you’d expect if you arrive just after opening.

For efficient lunches, I favor fast‑casual spots that can handle volume without sacrificing quality. Mixt, Souvla, Sweetgreen, Super Duper Burgers, and The Grove are dependable within a short walk of most downtown venues. When I need a higher‑signal lunch with a partner or prospect, I book a table slightly off the main corridor to avoid the rush—think Mourad for elevated Moroccan in SoMa or Boulevard along the Embarcadero for a polished, quiet conversation.

Dinner is where the best networking often happens, so I plan for atmosphere, acoustics, and a menu that works for mixed dietary needs. Kokkari Estiatorio (FiDi) excels for executive dinners. Liholiho Yacht Club is a creative, memorable choice for cross‑functional teams. Waterbar or Angler near the waterfront pair great food with views that impress visiting colleagues. For something more casual but still conversation‑friendly, Nopa or Sorella deliver consistently.

When it’s time for drinks, I think in terms of groups and goals. For panoramic views and small group catch‑ups, The View Lounge (Marriott Marquis) is a classic. For wine‑forward conversations with a quiet ambiance, Press Club near Yerba Buena works well. If you’re hosting a more energetic crew, Charmaine’s (SF Proper Hotel), Dirty Habit (Hotel Zelos), or 25 Lusk offer space, good music, and reliable service. For craft cocktails, Pacific Cocktail Haven and ABV are standouts if you don’t mind a short ride.

Transit and timing matter. From SFO or OAK, BART is often the fastest, most predictable route downtown; rideshare is convenient late at night. I walk whenever possible, but I time routes along well‑lit, busier streets and avoid sprinting between neighborhoods tight on time. Microclimates are real—bring layers, comfortable shoes, and a compact umbrella. I schedule 15‑minute buffers around key sessions to handle inevitable friend‑of‑a‑friend introductions.

If you need a professional setting for a quick working session, many hotels will extend lobby seating to guests and their visitors. For dedicated space, day passes at coworking operators like Industrious, CANOPY, or Regus are worth it when you’ve got a client briefing or board prep. For a more casual backdrop, Sightglass and Blue Bottle locations typically have reliable Wi‑Fi and just enough outlets if you arrive off‑peak.

Finally, a word on intent: I set a simple goal for each day—one meaningful connection, one surprising insight, and one concrete action to bring back to my team. ProductCon San Francisco 2025 is a catalyst if you design your experience with the same rigor you apply to your roadmap. If you spot me in a session or at a nearby cafe, say hello—I’m always up for trading notes on product strategy, pricing experiments, and what’s working in the field right now.

Quick note: restaurants and hours can change quickly—make reservations where possible and double‑check opening times the week of the event.

Inspired by this post on Product School.

November 3, 2025
Organizational Development Demystified: The Engine Behind Smarter Teams, Culture, and Growth

When people ask me how product organizations actually scale what works, I point them to a simple truth: organizational development is the operating system that makes strategy executable, teams empowered, and outcomes repeatable.

It turns out that organizational development isn’t just HR lingo. It’s the engine behind smarter teams, better culture, and long-term growth.

In practice, I think of organizational development as the discipline that aligns structure, incentives, rituals, and learning loops so empowered product teams can do their best work. It connects product management leadership with execution through clear decision rights, transparent roadmapping, and ways of working that reduce friction across product, design, and engineering.

On the ground, this looks like moving from activity measures to outcomes vs output OKRs, forming durable product trios to own customer problems end to end, and tightening stakeholder management so priorities don’t whipsaw week to week. It also means investing in onboarding that accelerates time-to-impact, creating feedback rituals that surface risks early, and using retention analysis to make smarter bets about where to double down.

The payoff is tangible: faster decision-making, fewer handoffs, and clearer accountability. Teams ship with confidence, leaders get leading indicators instead of lagging surprises, and employee retention at startups improves because people see how their work connects to a meaningful value proposition and product-led growth.

In my own practice, shifting to outcomes-first planning, establishing product trios, and clarifying interfaces across functions reduced decision latency, improved deployment frequency, and made ownership unmistakable. The organization became more resilient because the culture, processes, and metrics reinforced one another instead of competing for attention.

If you’re starting from scratch, begin by aligning on a small set of outcomes that matter, then redesign ceremonies and artifacts to serve those outcomes. Next, empower teams with clear autonomy and constraints—enough freedom to discover, enough guardrails to focus. Finally, make learning visible: use lightweight postmortems, discovery reviews, and customer signal dashboards so your operating system continuously improves.

Organizational development isn’t a one-time reorg; it’s a habit. When we treat it as a product—iterating on roles, rituals, and metrics just like we iterate on features—performance compounds, culture strengthens, and growth becomes sustainable.

Inspired by this post on Product School.

November 3, 2025
15 Must-Track Customer Retention Metrics to Crush Churn and Accelerate Sustainable Growth

I obsess over retention because it tells me the truth about product-market fit, value delivery, and revenue durability. In my role leading product strategy at HighLevel, I’ve learned that sustainable growth comes less from adding users and more from keeping the right ones engaged, successful, and expanding. The fastest way to get there is through a disciplined view of the right customer retention metrics.

Struggling to keep users? These customer retention metrics reveal what’s working, what’s not, and where to focus to reduce churn.

When I assess a product’s health, I look for a clean story across acquisition, activation, engagement, and expansion—then I validate that story against revenue outcomes. If those lines don’t reconcile, churn is coming. That’s why I track a core set of signals that expose value gaps early, guide product-led growth, and align go-to-market with actual customer outcomes.

Here are the 15 signals I rely on to diagnose retention risk and prioritize roadmaps: logo churn rate, gross revenue retention (GRR), net revenue retention (NRR), cohort retention by signup month, activation rate, time-to-value (TTV), feature adoption rate, DAU/WAU/MAU and stickiness (DAU/MAU), session frequency and duration, expansion revenue rate, contraction/downgrade rate, customer lifetime value (CLV), onboarding completion rate, customer health score, and support tickets per account with time to resolution. Together, these metrics show whether customers realize value quickly, keep finding more value over time, and are willing to grow with the product.

Here’s how I use them in practice. If activation rate or time-to-value slips, I invest in onboarding clarity, in-app guides, and product tours to remove friction and accelerate first success. If GRR weakens, I re-examine renewal messaging, pricing fairness, and critical feature gaps. If NRR stalls, I revisit packaging, discovery-driven upsell paths, and the expansion moments that naturally occur after users unlock initial value.

A unified analytics platform connecting product usage, lifecycle events, and CRM integration is essential. I pair cohort analysis in Amplitude analytics with qualitative insights from Intercom, then use Pendo to instrument in-app nudges and measure feature adoption lift. A/B testing helps me validate which interventions move the metrics that matter, not just vanity engagement.

Cadence matters. I review leading indicators weekly (activation, TTV, feature adoption), lagging indicators monthly (GRR, NRR, CLV), and cohort retention every quarter to ensure improvements compound. This rhythm keeps teams aligned on outcomes vs output and focuses energy where it reduces churn fastest.

If you adopt only one habit, make it this: tie every roadmap bet to a specific movement in these retention metrics, then measure relentlessly. When we do this well, our product doesn’t just acquire users; it earns loyal advocates—and that’s the most efficient growth engine there is.

Inspired by this post on Product School.

November 3, 2025
Build Customer Feedback Loops That Actually Drive Growth and Get Your Product Unstuck

What if your customer feedback loop is the reason you're stuck? Learn how to build one that fuels real growth and changes your product for the better.

I’ve seen talented teams spin for months because their customer feedback loop was noisy, slow, or misaligned with outcomes. The result is predictable: roadmaps packed with output, not impact. When we design feedback loops that are intentional, instrumented, and closed with customers, the product starts compounding value—and the business moves from reactive to product-led growth.

My definition of a strong customer feedback loop is simple: capture the right signals, synthesize them quickly, prioritize against outcomes, experiment to de-risk, and close the loop visibly with customers. If any link is weak, the whole system underperforms. More feedback isn’t better—better feedback is better.

Start with who you listen to. Segment feedback by persona, account tier, lifecycle stage, and “jobs to be done.” A founder’s feature request, a new user’s onboarding friction, and a power user’s edge case should not be weighted the same. This is the foundation of credible product discovery.

Instrument your product so qualitative and quantitative signals reinforce each other. I rely on funnel and cohort views in Amplitude analytics to see where activation or retention breaks, then layer in interviews, support tickets, and community threads for context. When telemetry and narrative align, the signal gets unmistakable.

Capture feedback where the user is. In-app guides and lightweight surveys via Pendo or Intercom surface timely prompts during key journeys (onboarding, activation, adoption, renewal). Pair those with structured inputs from sales notes and customer success reviews so you don’t bias toward only the most vocal users.

Standardize how you synthesize. Tag every item by problem statement, persona, job, and affected step in the journey. Roll these up into weekly themes your product trios can act on. The discipline here turns anecdotes into addressable opportunities.

Prioritize against outcomes, not volume. If your OKRs are outcomes vs output OKRs, tie each opportunity to a measurable product outcome like user activation rate, adoption depth, conversion, or retention. A thousand upvotes mean less than a clear path to move a core metric.

De-risk with evidence, not opinion. Frame hypotheses, define success metrics, and run A/B testing with a clear minimum detectable effect. Guardrail metrics matter—never trade a short-term click lift for a long-term retention drop. Experiments should accelerate learning, not justify pet projects.

Fold learning into product roadmapping and sprint planning. I expect prioritized feedback themes to map to roadmap bets with clear owners, milestones, and expected impact. This is how product management leadership signals what we will do—and what we will not do—based on evidence.

Close the loop, every time. Tell customers what changed because of their input—release notes, in-app messages, CSM follow-ups, or community updates. When people see their voice shaping the product, engagement and loyalty rise. This is also how you earn higher-quality feedback next time.

Set a cadence and governance that sticks. A weekly Voice of Customer review for the product trio, a monthly synthesis for cross-functional stakeholders, and a quarterly lookback tying changes to retention analysis creates organizational memory. Feedback isn’t a meeting; it’s a muscle.

Beware common failure modes. Don’t overweight loud accounts, confuse feature requests with problems, or ship one-off fixes that fragment your value proposition. Avoid vanity dashboards that show activity without decision-making power. If your loop doesn’t routinely change priorities, it isn’t a loop—it’s a suggestion box.

If you’re starting from scratch, keep it simple: define your core outcomes, instrument the top journeys, establish two capture channels (in-app and human-led), create a shared taxonomy, and commit to a weekly synthesis ritual. In a few cycles, you’ll see cleaner insights, tighter bets, and faster learning.

Done right, customer feedback loops are a competitive advantage. They sharpen product discovery, accelerate user activation, and compound retention—exactly what a modern, product-led organization needs to grow with confidence.

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
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
10 Customer Acquisition Metrics I Obsess Over to Predict Growth (and Kill Vanity KPIs)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Inspired by this post on Product School.

November 3, 2025
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
User Activation Is My North Star: The Most Reliable Signal Your Product Will Truly Scale

I’ve learned the hard way that growth isn’t about dashboards crowded with vanity metrics. When I evaluate whether a product is poised to scale, I start with one question: are new users truly activating? If not, everything else is noise.

"Forget vanity metrics. User activation is the compass that shows if your product or organization is lost or scaling."

When I say user activation, I mean the precise, observable milestone where a new user experiences core product value—often within their first session or first week. That might be launching a first campaign, connecting a CRM integration, or completing the key workflow that makes the product indispensable. Activation rate then becomes my primary KPI, far more meaningful than signups or pageviews because it ties directly to retention, expansion, and long-term revenue.

Why does activation predict scale? Because it’s a leading indicator of sustained product-market fit. High activation correlates with stronger retention curves, higher feature adoption, and healthier unit economics. If activation improves, cohorts decay more slowly and customer value compounds. If activation stalls, no amount of top-of-funnel spend or go-to-market strategy will save you from churn.

Here’s how I operationalize activation. First, I define the activation event from first principles, grounded in our value proposition and product positioning. I pressure-test that definition with real users through product discovery, then codify it as a measurable event so it’s unambiguous and auditable across teams.

Second, I instrument the end-to-end journey. Using a unified analytics platform with tools like Amplitude analytics and Pendo, I track time-to-value, drop-off points, and the exact steps users take before and after the activation milestone. I design experiments with a clear minimum detectable effect (MDE) so A/B testing yields decisions, not debates.

Third, I build onboarding that accelerates value realization. In-app guides, contextual product tours, and thoughtful tooltip design reduce friction while keeping users focused on the critical path to activation. Every element in onboarding earns its place by improving activation rate or shortening time-to-value—otherwise, it goes.

Finally, I align the organization around outcomes, not outputs. I set outcomes vs output OKRs tied to activation, run weekly reviews with empowered product teams and product trios, and ensure our product-led growth motion reinforces the activation moment. This creates a shared language from product to sales to customer success.

When activation rises, the path forward gets clear: retention strengthens, expansion opportunities emerge, and scaling becomes a matter of capacity rather than guesswork. When activation falters, it’s a signal to pause, refine the value narrative, and fix the experience. Either way, activation tells the truth. If you want to build a product that truly scales, make user activation your north star.

Inspired by this post on Product School.

November 3, 2025