Todd Olson
Review
The phrase 'product-led' has managed to become both contentious and meaningless inside organisations I've worked with. The Wes Bush books should remain the go-to books on the topic in my opinion; this one is contributing toward the muddying of the waters and the blurring of lines.
You Might Also Like:
Key Takeaways
The 20% that gave me 80% of the value.
Anchor every initiative to a small set of SMART outcome goals that link the why to the work. Build lightweight business cases that define the target users, the pain to solve, and the desired result. Prioritise by economics, not opinion: quantify the cost of delay in lost revenue, churn, or missed opportunities, and use Weighted Shortest Job First by dividing value, urgency, and opportunity by effort. Operational metrics act as guardrails: shipping is not success if adoption, satisfaction, or retention are weak. Since most features see little use, focus on creating value over output and hold a clear point of view on what makes the product distinct.
Choose metrics that guide behaviour rather than distort it. Balance a few strategic numbers with leading indicators and qualitative signals.
- Track revenue with ARR or MRR, efficiency with CAC, long-term value with LTV, and growth with NRR. Include gross margin to reflect true economics and win rate to gauge competitiveness.
- Operationally, monitor MAU, WAU, and DAU with care, since high usage may signal friction. Stickiness (DAU/MAU), adoption of key features, and retention at user and account level show if habits are forming.
- Breadth–Depth–Frequency reveals reach, depth of core use, and return frequency.
- Qualitative inputs round this out: NPS for advocacy intent, CSAT for satisfaction, CES for ease, SUS for usability, and a Product–Market Fit signal if 40% would be very disappointed to lose the product. Design the set to be complete, so teams cannot game one number without moving the outcome, and connect lagging financials to leading behaviours.
Turn customer data into decisions by moving beyond simple trends. Segment by value and usage before demographics so groups reflect real needs. Test hypotheses with disciplined experiments: define conditions upfront, randomise with feature flags, and ensure statistical power. Use cohorts to compare like with like across channels, experiences, or time periods, revealing which journeys convert and retain. Combine quantitative signals with qualitative insight: let analytics flag anomalies, then explain them with interviews, in-app feedback, and session replays that show overlooked UI or “rage clicks”. Synthesis matters—personas and journey maps grounded in real data help target the interventions that will shift outcomes.
Measure sentiment where it drives action. Use transactional surveys right after key events and relationship surveys at regular intervals. Segment responses so buyer views do not mask end-user reality. Analyse text to pull out themes and examples, then link sentiment to behaviour. Ask power users how to refine busy pages, occasional users why they rarely return, and novices what would unlock value. Move the middle first: shifting passives to promoters is faster than converting deep detractors. Use inclusive prompts to check whose needs are missing and where language, defaults, or flows exclude.
Let the product carry more of the marketing load. Earn reviews at moments of success and treat them as a channel you optimise. Identify product-qualified leads from behaviour, not campaigns: repeated visits to pricing, growing usage, or team expansion are stronger signals than webinar attendance. Use freemium or trials to create early wins without undermining premium value. Make basic workflows useful on their own, but monetise advanced capabilities. Where setup is heavy, offer guided test drives with realistic data to accelerate time to value. The product experience should demonstrate its own proposition more powerfully than any pitch.
Conversion should be contextual. Trigger upgrade prompts as users near limits, and give advance notice so changes never feel punitive. Recognise heavy use and surface paid features that extend the job users already do. Reinforce upgrades with outcome-based nudges: when the product delivers a result, show it alongside the next step available in a paid tier. Automate triggers, keep copy human and specific, and track effectiveness so prompts are timely rather than noisy.
Onboarding should focus on behaviours that predict retention. Identify the “aha” moments and design first-run experiences to reach them quickly. Apply behavioural loops—trigger, action, reward, investment—deliberately. Respect attention: use short walkthroughs, subtle tooltips, targeted lightboxes, blank-state education, and searchable knowledge bases. Personalise by role, plan, and proficiency so experts skip basics and novices get help. Use progressive disclosure so core value is clear first, with advanced features revealed later. Treat onboarding as ongoing: as features evolve and users mature, update guidance continuously.
Deliver value by finding and removing friction. Map actual journeys instead of intended flows. Use funnels to see drop-offs, then drill into form completion, feedback, or session replays to diagnose pain. Fix both defects and process gaps; in B2B, trust and responsiveness matter alongside UX. Apply the same lens to internal tools—poor employee experiences drive cost and churn.
Scale support with embedded self-service. Provide contextual help that adapts to who the user is and where they are, using telemetry to detect confusion and offer assistance in the moment. Standardise terminology, add inline definitions, and publish concise articles and videos linked directly to the interface. Measure consumption, related ticket volume, and retention to calibrate the level of education required.
Retention and expansion hinge on leading indicators. Aim for negative churn, where upsell and cross-sell outweigh losses. Build health scores that blend product adoption, support experience, and commercial signals into a clear red-amber-green view. Weight inputs appropriately, validate against renewals, and keep them live so they predict rather than describe. Use scores to triage attention, flag systemic issues, and spot expansion opportunities when usage nears limits or behaviours correlate with growth.
Design faster and more consistently by prototyping before code. High-fidelity prototypes with realistic interactions yield feedback that mirrors real use. Short design sprints answer critical questions quickly. Involve engineering early to reduce risk and give marketing and sales visibility so naming and positioning are not afterthoughts. Reduce design debt with a system that connects design tokens to components in code, serving designers, developers, and stakeholders with what they need while maintaining quality as speed increases.
Treat launches as experiments. Release behind feature flags to targeted cohorts, track impact on the intended KPI, and roll forward or back safely. Retire flags promptly to avoid technical debt. Measure adoption with three lenses: breadth of accounts or users, time to first meaningful use, and depth or duration of ongoing use. Announce in-product to relevant segments with a clear action, and provide enablement where needed. After each release, revisit the goal and decide whether to scale, iterate, or retire.
Do not be afraid to prune. Removing features reduces complexity and cost. Test removals and watch for pain—silence can be a useful signal. Align the portfolio with the future, not the past. When rewriting, expect parity pressure; if necessary, build parallel products or spin-off brands to rethink solutions without baggage. Start narrow and expand outward as fit is proven. Fewer features often make for a better product.
Close the loop and prioritise transparently. Centralise feedback and map it to product areas so themes and revenue impact are clear. Use structured decision methods such as votes, budgets, or pairwise comparisons, slicing by customer count, revenue, or score. Always tell contributors what happened with their input. Track bugs by feature and monitor ratios of reported to fixed. Enforce performance budgets, since speed and reliability drive perceived quality.
Keep the roadmap alive. Begin with vision and principles, then set goals that reflect differentiation, customer delight, resilience, and commercial intent. Prioritise using both strategy and observed behaviour; low usage may reflect discoverability, not lack of value. Attach measurable KPIs to every item and ensure instrumentation is in scope. Share tailored views for executives, go-to-market teams, and delivery, making it clear the roadmap is direction, not promise. Revisit regularly as evidence arrives and be cautious with public commitments.
Make it repeatable with Product Ops. A small team that systematises feedback capture, insight generation, and product enablement shortens decision cycles and improves prioritisation. Product Ops aligns functions with shared data, maintains the toolchain that unifies telemetry and qualitative input, and produces regular reviews where adoption, retention, stickiness, and sentiment are tracked as part of the operating rhythm.
Deep Summary
Longer form notes, typically condensed, reworded and de-duplicated.
Chapter 1: Start with the End in Mind
Product teams often declare victory prematurely based on anecdotal evidence rather than quantitative measures. The critical lesson is to start with clear SMART goals (Specific, Measurable, Attainable, Relevant, Time-bound) that connect the "why" with the work. Strategic goal setting requires creating business cases that answer fundamental questions: who is the target audience, what pain is being addressed, and what is the desired outcome.
Economic impact frameworks provide systematic prioritisation methods. Don Reinertsen's "cost of delay" framework helps teams determine the economic impact of delaying features, whether through lost revenue, customer churn, or missed market opportunities. The Scaled Agile Framework (SAFe) offers a scoring model for user/business value, time value, and opportunity enablement, which when divided by effort yields "Weighted Shortest Job First" prioritisation.
Operational metrics serve as guardrails for product health. The era of measuring success by shipping features has ended; modern software delivered as a service means adoption and delight matter more than delivery. Teams now track what users do (behaviour inside applications), how they feel (sentiment based on experience), and what they want (feedback and feature requests). Shockingly, over 80% of features shipped by SaaS companies are rarely or never used.
Getting close to customers through techniques like Jobs to Be Done, empathy maps, and Amazon's "Working Backwards" process ensures teams understand not just what customers say they want, but what they truly need. Jobs to Be Done helps reframe products by understanding what customers "hire" products to accomplish. Empathy maps visualise user attitudes through four quadrants: Says, Thinks, Does, and Feels. Amazon's Working Backwards starts with writing a mock press release before building anything, ensuring customer focus from inception.
Great products emerge when teams have strong opinions about what makes their products special. Teams should document their point of view and use it as a North Star when making decisions. The transition from strategic goals to operational metrics sets the foundation for the measurement systems explored next.
Chapter 2: You Are What You Measure
Modern product teams must embrace comprehensive measurement across strategic, operational, and qualitative dimensions. Product managers often resist revenue metrics since they do not control marketing budgets or sales teams, yet measuring only controllable outputs like feature delivery creates worse dysfunction: "where the metric goes, the effort will flow."
Strategic metrics form the foundation: Annual Recurring Revenue (ARR) or Monthly Recurring Revenue (MRR) drive subscription businesses; Customer Acquisition Cost (CAC) measures total spend to land customers; Lifetime Value (LTV) models future revenue based on retention and expansion; Net Revenue Retention (NRR) expects values above 100% as expansion offsets churn; gross margin calculations include amortised R&D expenses; win rate measures competitive encounters and success rates.
Operational measures provide leading indicators between reporting periods. Usage metrics include Monthly Active Users (MAU), Weekly Active Users (WAU), and Daily Active Users (DAU), though more usage is not always better; sometimes it indicates friction. Stickiness ratios (DAU/MAU) show habit formation. Feature adoption rates reveal that most features fail to gain traction, requiring analysis of historical launches and 30-day retention patterns at user and account levels. The Breadth, Depth, and Frequency (BDF) framework provides holistic health assessment: breadth measures customer engagement, depth tracks usage of key sticky features, frequency counts login patterns.
Qualitative metrics complete the picture through sentiment measurement. Net Promoter Score (NPS) measures willingness to recommend on a 0–10 scale (9–10 promoters, 7–8 passives, 0–6 detractors), though it has limitations: measuring intention not action, and advocacy not loyalty. Customer Satisfaction Score (CSAT) directly asks about satisfaction, Customer Effort Score (CES) measures ease of specific experiences, System Usability Score (SUS) uses 10 questions to assess overall usability. Product/Market Fit metrics ask how disappointed users would be to lose the product, with 40% "very disappointed" indicating strong fit.
The key is choosing metrics that drive aligned business outcomes rather than creating dysfunction. Completeness ensures no gaps in the dataset: Robert Austin's research shows how measuring only interviews rather than great hires drives the wrong behaviours. These metrics provide the raw material for deeper insights.
Chapter 3: Turning Customer Data into Insights
Transforming raw data into actionable insights requires sophisticated analytical techniques beyond simple time series analysis. While tracking metrics over time provides a starting point, deeper techniques arm teams with the right data for informed decisions.
Segmentation powerfully slices customer data by commonalities like industry, size, location, persona, or product usage patterns. Creating homogeneous segments increases the likelihood of similar actions and results. Roman Pichler suggests segmenting new products first by value (how the product meets needs) then refining by demographics. Early segmentation analysis can reveal critical problems teams did not know existed, like discovering read-only users rating products much lower than those with edit rights.
Experimentation moves beyond observation to active hypothesis testing. Using experiment canvases, teams articulate falsifiable hypotheses, define success conditions, and plan next steps. A/B tests randomly assign users to treatment and control groups using feature flags, with statistical engines determining causation not just correlation. Discipline is essential: establishing proper control groups, ensuring statistical significance, and considering ethics, especially for paying B2B customers who may not want to be guinea pigs.
Cohort analysis breaks segments down further by grouping users with common characteristics and comparing behaviour over time. This powerful technique drives conversion by revealing which campaigns, channels, or demo experiences convert prospects to customers. Breaking cohorts by time segments reveals whether new user groups have better experiences than previous ones, essential for retention analytics.
The real power emerges when combining quantitative and qualitative data. Quantitative data reveals what users do: feature usage, drop-off points, journey paths. Qualitative data explains why through feedback, requests, interviews, and observations. Using quantitative analysis to identify outliers worth investigating prevents selection bias from only hearing the loudest voices. Session replay technology has revolutionised qualitative research at scale, capturing on-screen experiences like game film. Teams can see when features are overlooked, identify "rage clicks" signalling frustration, and ground abstract metrics in real user experiences.
Personas and journey maps synthesise these insights. Personas add demographic and psychographic lenses to user segments. Journey maps help understand how needs change at various touchpoints, particularly important for designing onboarding flows. This combination of techniques provides the foundation for measuring the more nuanced aspects of user experience.
Chapter 4: How to Measure Feelings
Understanding customer sentiment is crucial for product success, as expressed frustration serves as an early warning of deeper problems. When companies stop delighting customers, those customers start looking for alternatives. Capturing sentiment requires careful consideration of when, where, and how to ask, balancing frequency to avoid survey fatigue while ensuring reliable responses at meaningful journey moments.
NPS has emerged as the most common methodology, based on the premise that willingness to put reputation on the line indicates true loyalty. The 0–10 scale categorises respondents as promoters (9–10), passives (7–8), or detractors (0–6), with the score calculated by subtracting detractor percentage from promoter percentage. However, NPS has legitimate limitations: it measures intention not actual advocacy, and advocacy does not equal loyalty; budget constraints can override product love. Most critically, NPS alone does not reveal root causes without follow-up questions customised by score to improve completion rates.
Implementation decisions significantly impact programme effectiveness. Transactional NPS measures sentiment following specific events, while relationship NPS uses regular cadences to track ongoing satisfaction. B2B companies must decide whether to survey buyers or end users, as surveying only buyers can provide false security. Segmenting responses by demographics reveals whether products resonate differently across segments.
Free-form text provides rich insights but challenges aggregation. Sentiment analysis systems mark text as positive, neutral, or negative, enabling trend tracking. Keyword analysis identifies common phrases, while manual tagging adds human reasoning to categorise responses. Word clouds visualise term frequency, though removing filler words improves insight quality.
The true power emerges when combining sentiment with usage data. Rather than surveying all users identically, teams can target different segments with relevant questions: asking power users what could make heavily used pages better, occasional users why they rarely visit, novice users what would drive engagement. To improve scores, start with neutral users where moving from 8 to 9 is simpler than converting detractors. Personalisation based on sentiment enables tailored experiences, from extra support for frustrated users to early access programmes for advocates.
Practising inclusivity ensures products serve all users. Teams should ask who might disagree with designs, what they have designed for themselves versus others, and who they are missing. The three principles of inclusive design are growth (owning your lens), innovation (championing the other), and belonging (asking who is missing). These measurement approaches inform the customer-centric strategies that follow.
Chapter 5: Marketing in a Product-led World
Product-led companies make their products the primary vehicle for customer acquisition and awareness. Netflix exemplifies this transformation: their homepage simply offers "Try 30 days free" rather than marketing slogans, betting the product experience itself will compel conversion.
Reviews have become the new marketing currency. The proliferation of online information means customers find and learn about products through peer reviews rather than company messaging. App Store Optimisation (ASO) has become essential, requiring optimisation of names, keywords, ratings, and downloads to surface apps. B2B products face similar disruption through crowdsourced review sites like G2 and TrustRadius that determine quadrant positions based on real customer experiences.
Even beloved products need active review cultivation. Teams should design prompts that encourage happy users to leave reviews, especially following high NPS scores. Effective campaigns include contextual requests, incentives, and continuous optimisation of audiences and timing. Direct referrals ask customers to share links while indirect referrals like "Powered by Gmail" signatures drive virality subtly.
Product-qualified leads (PQLs) represent users who demonstrate intent through actual product usage rather than just content consumption. Someone visiting pricing pages three times weekly shows stronger intent than webinar attendees. Teams analyse login frequency, feature usage patterns, and user base size to gauge conversion potential. This strategy extends beyond new customers to identify expansion opportunities within existing accounts.
The freemium model requires delicate balance. Companies might offer time-limited full access or feature-limited versions while charging for advanced functionality. The challenge is avoiding the "crippleware" trap where users cannot experience enough value to justify purchasing. Product analytics reveal threshold points where users ache enough to pay but are not irritated enough to leave. The friction of free works both ways: while removing cost barriers increases trial adoption, status quo bias means users resist losing what they have. Success requires ensuring users realise value early and often through superior onboarding.
When features are complex or require customisation, companies create guided test drives with dummy data and common use cases, reducing trial lengths while closing deals faster. The ultimate test happens during trials: can products deliver experiences worth paying for continuously? In a product-led world, most customer touchpoints occur within the product itself, making the product experience the most powerful marketing tool available. This sets the stage for converting those engaged users into paying customers.
Chapter 6: Converting Users into Customers
Converting free users to paying customers requires sophisticated, data-driven strategies leveraging product usage patterns to identify optimal conversion moments. The shift towards do-it-yourself customer attitudes means users want more control over their outcomes, expecting products to guide them to success without heavy human intervention.
The key lesson is that showing users exactly what they want to do in the fastest, simplest way possible leads to value realisation and retention. This requires systematic approaches: tracking usage patterns of successful converters, setting benchmarks for customer health combining feature adoption and NPS, determining leading indicators of conversion and renewal, developing playbooks for contextual in-app messaging, and continuously measuring content effectiveness.
Usage limit triggers activate when users approach subscription thresholds. Personalised notes can encourage upgrades while warning users in advance prevents abrupt alienation. Heavy usage patterns such as multiple logins, hours spent, feature utilisation, and add-on installations signal opportunities to highlight advanced paid features.
Advanced feature strategies follow the TurboTax model of giving away simpler capabilities while monetising advanced ones. This approach provides lower-valued, commoditised features free while charging for sophisticated functionality that delivers real value.
Product results provide powerful conversion opportunities. When products demonstrate measurable outcomes, such as successful transactions or achieved goals, in-app reminders can reinforce benefits while encouraging upgrades. The key is personalising conversion prompts based on user behaviour rather than one-size-fits-all approaches.
While sales teams remain essential for turning leads into customers, product-led companies recognise the product's power in driving conversions. Products become sales engines through measuring user behaviour and developing automated triggers that encourage commitment to becoming customers. Once converted, getting users up and running quickly becomes essential.
Chapter 7: Getting Customers Off to a Fast Start Through Onboarding
First impressions in software happen in milliseconds and determine whether users invest their scarce time and attention. Successful onboarding identifies critical events and "aha moments", such as Facebook's discovery that users connecting with seven friends in ten days become regular users, then designs experiences driving users towards these behaviours.
Creating habits that stick requires applying behavioural economics principles: triggers bring users in, actions yield rewards, rewards compel investment, and the combination creates virtuous cycles. While these reward systems work powerfully, teams must consider ethics: are they leading users to valuable improvements or playing games with emotions for gain?
Effective onboarding employs multiple modalities. Walk-throughs guide users through key features, selling their value, linking features together, and helping users learn by doing. Tooltips provide on-hover tutorials, the least intrusive engagement form. Lightboxes draw attention to specific announcements but can be intrusive if not thoughtfully targeted. Blank slates turn empty states into educational opportunities. Knowledge bases provide comprehensive self-service resources.
Personalising onboarding experiences requires leveraging user data. Basic profile elements like role, plan level, or customer size determine whether educational content will be helpful. User behaviour and demonstrated proficiency determine training needs for new features. The hard truth is users do not have time to learn everything; their motivation depletes like a health bar in a video game with each unhelpful screen or click.
Progressive disclosure is essential, deferring advanced features to secondary screens and making applications easier to learn. The goal is making the main thing the main thing, focusing on the most important features first and unveiling additional capabilities over time. What constitutes the main thing varies by persona based on jobs to be done and observed behaviours.
Getting onboarding right requires empathy, attention to detail, and restraint. Focus on users not products, fast-track to value, segment by persona, and never show empty progress bars. Continuous experimentation reveals which messages, sequences, and channels best help new users learn.
Onboarding never truly ends: it is an ongoing process of progressive disclosure revealing new content as users indicate readiness. As products evolve with new features and UI changes, the onboarding cycle begins again. The key is user data: you cannot deliver good onboarding without knowing where users have been and where they are trying to go. This foundation enables delivering ongoing value throughout the customer journey.
Chapter 8: Delivering Value
Understanding how customers define success is critical for product design. To retain customers effectively, teams must track how they solve customer pain, understand how customers measure success, and provide those measures demonstrating return on investment.
Understanding customer journeys requires observing actual user behaviour versus designed paths. The difference between designed and desired paths often reveals significant disconnects, such as pedestrians creating dirt paths across grass rather than using pavements. By exploring sequential actions users take, patterns emerge that inform experience design. Teams should ask: why do users come to products? What do they do first? What do they do most frequently? These answers reveal the highest valued capabilities.
Once understanding the tasks users want to complete and preferred paths, teams can measure explicit steps as progressive funnels. Like digital marketers optimising purchase paths, these funnels reveal conversion between steps and where experiences need improvement. Identifying blockages requires observation at various altitudes: using paths and funnels for high-level journey understanding, assessing sentiment through NPS or CSAT, and examining form completion percentages and specific feature feedback at lower levels.
Session replay provides close observation of user actions, revealing exactly what went right or wrong. "Rage clicks" (repeatedly clicking unresponsive elements) signal deep user frustration. Products become progressively less useful as customer jobs diverge from the original product vision. The onus is on product leaders to maintain close alignment.
Friction removal takes many forms. B2C friction points are often product-focused, such as feature bugs. B2B friction includes relationship-building challenges. Customer success teams represent the eyes, ears, and heart of product-led organisations, living on the front lines helping customers find value. They pair quantifiable usage data with customer feedback and stories, providing crucial context for improvement.
The same principles apply when employees are users. Poor employee-facing software creates friction, reduces job satisfaction, and drives turnover. Consumer applications are typically easier and more engaging than workplace tools, creating dissatisfaction. When considering value delivery, do not overlook opportunities to improve employee experiences.
Understanding customer journeys, identifying friction, and systematically removing obstacles ensures customers receive significant value. This foundation enables the self-service capabilities modern customers expect.
Chapter 9: Customer Self-Service
Customers want self-service, digitally driven experiences. Becoming product-led means automating how and where customers get support, education, and service inside applications, enabling customers to serve themselves effectively.
Support tickets are an excellent measure of product usability, reflecting user confusion and frustration. Each ticket provides insights for improvement. Ticket trends reveal whether products require more or less support when normalised for user growth. Categorising tickets identifies which product areas provoke questions. Ticket age indicates problem impact: long-running issues require greater organisational involvement and are very costly.
Product-led companies embed help windows directly inside product interfaces, contextualised based on user identity and location. These systems walk users through products interactively, ensuring learning while being measurable. Product usage data shows when users repeatedly click buttons or perform functions unexpectedly, enabling proactive help prompts.
Words matter significantly in product design. Solutions include offering flexible vocabulary where customers choose resonant terms, or adding pervasive tooltips explaining terminology. Small question marks next to labels offer self-service answers for simple questions.
Ongoing customer education requires meeting users at different speeds through multiple channels. Strategies include educating through every available channel, illustrating functionality through demos or guides, and providing step-by-step walk-throughs. There is no end date for education since proficiency timelines vary widely.
Measuring customer education effectiveness involves tracking engagement with training content, support ticket volume for new features, and long-term retention. The right amount requires fine balance: too much content suggests products are not intuitive and overwhelms users.
In-app onboarding and continuous education reduce support tickets significantly. Personalised experiences help users see value quickly and utilise entire products. This self-service foundation enables the long-term customer relationships explored next.
Chapter 10: Renew and Expand: Creating Customers for Life
For recurring revenue businesses, retaining existing customers and growing relationships over time is more important than acquiring new ones. Customer acquisition costs mean customers are not profitable until they have been customers for extended periods. The goal is creating "negative churn" where revenue from expansion, upsells, and cross-sells outweighs losses from churn.
Understanding leading indicators requires knowing which usage patterns correlate to account growth and renewal. Measuring retention over time reveals whether onboarding yields temporary changes or lasting habits. Declining retention signals customers would not care about losing product access.
Customer health scores combine multiple data points into single scores, helping prioritise time investment and risk understanding. Visual indicators like green/yellow/red immediately show where to focus energy. Components typically include product adoption (40%), support experience (35%), and purchasing behaviour (25%). Each component combines multiple data points: support experience includes NPS, time to close, escalations; purchasing behaviour includes product count, renewals, and opportunities.
Health scores are living metrics requiring current product usage reflection. Their value extends beyond customer management: unhappy customers indicate product problems, making product team involvement essential. Health scores serve as warning signs indicating where to spend time, enabling teams to ignore green customers while focusing on red ones.
Cross-selling and upselling opportunities emerge from strong retention strategies. "Land and expand" applies across business models: hook customers with specific value then expand relationships. Products can notice usage limits and prompt purchases, or encourage happy users towards advanced capabilities delivering increased value.
Creating customers for life requires products that attract and retain over the long haul. Leading indicators like health scores reveal true satisfaction levels. This data-driven insight opens paths for engaging and retaining customers through full product offerings. Continuous evolution ensures customers continue gaining value, requiring new approaches to product delivery.
Chapter 11: Product-led Design
Modern product design requires validating user experiences through high-fidelity prototypes before writing code. Teams need permission to work on ideation exercises like storyboarding and mind mapping, then flesh out ideas with prototypes showing how concepts flow together.
Today's prototypes reach higher fidelity with animations, micro-interactions, and hover states. Users can try entire mocked-up experiences, generating feedback early enough to save development time. The five-day "sprint" approach addresses critical business issues by taking ideas through design, prototyping, and testing to develop working prototypes in just one week.
Cross-functional collaboration is essential for innovative design. Diverse feedback considers corner cases and helps teams ship the right products the first time. Bring customers into discussions, include developers at every step, share plans with marketing and sales, get executive buy-in early. Critical insight can come from anywhere: when everyone aligns on vision from the start, better products ship faster.
Operationalising design at scale requires addressing design debt: the overabundance of non-reusable and inconsistent styles that slow growth. Design systems create single sources of truth, design languages everyone understands that integrate into designs, prototypes, and code. This reduces debt, accelerates processes, and builds bridges between teams.
Successful design systems consider three audiences: designers need operationalisation in existing tools and workflows; developers need design language accessibility through APIs; stakeholders need single sources of design truth accessible organisation-wide. Good systems separate audiences through access control, versioning, and data protection, maintaining design language integrity.
Today's most disruptive products come from teams considering customers at every process step. They understand customer problems, how others understand those problems, then collaborate on optimal solutions. When everyone embraces the why, great products follow. This design thinking extends into how products launch and drive adoption.
Chapter 12: Launching and Driving Adoption
Cloud-based software enables instant changes reaching users immediately. Faster release cycles mean more frequent feedback collection, ensuring products align with customer needs: the primary Agile goal.
Traditional waterfall approaches baked assumptions up front, making iteration difficult. By release time, customers had new requirements releases failed to cover. Modern approaches treat products and features as having lifecycles: coding, testing, deploying, limited release, launch, growth, and eventual sunsetting.
Controlled rollouts test products before general availability. Alpha implies super-early versions, beta lets people test and provide feedback. Products might stay in beta for years. Today's releases are rarely untested: product features begin as experiments rolled out to segments, progressively expanding as functionality improves.
Feature flags enable turning features on or off during releases, allowing deployment while restricting access to user subsets. Teams can test in production, safely roll out functionality, and take measured approaches monitoring impact on KPIs. However, too many flags create "flag debt": unsustainable, unmanageable code requiring eventual clean-up.
The death of software releases means products become fluid, rapidly evolving feature sets assembled uniquely per user. Product experimentation platforms randomly assign users to treatment and control groups, measuring whether features cause metric changes. Only valuable ideas survive.
Feature awareness and adoption determine product success. Every renewal depends on customers perceiving ongoing value from actively used features. Unused features lower perceived value and willingness to pay. Measuring adoption requires considering breadth (how widely adopted), time to adopt (how quickly users begin), and duration (how long usage continues).
Promoting launches requires relevance: tailoring announcements to appropriate segments, and clear desired actions. In-app announcements ensure messages reach users when most relevant. Improving adoption comes down to delivered value, requiring clear insight pairing metrics with direct feedback.
Goal setting and tracking require checking back on goals after shipping. Did you hit targets? Was the goal right? Document learnings and incorporate into future models. Teams are not done until they have intentionally decided whether to finish work based on validation. This discipline ensures products truly deliver intended value before moving forward.
Chapter 13: The Art of Letting Go
Removing features is one of product management's most powerful yet underappreciated acts. If something has outlived its usefulness, removing it is better than maintaining it. Old code taking space while creating defects eventually requires addressing code debt. Each additional capability requires maintenance and training while adding complexity.
People do not typically get compensated for removing features, yet keeping old features is expensive and time-consuming. Testing pain involves removing features to see user reactions: this marries analytics with intuition. If nobody complains, removal was safe.
Checking vision means considering whether features are part of the past or the future. When targeting enterprise customers, features used by small companies might be removal candidates. Engaging customers in conversation about what they would do without features helps understand pain better and develop replacement solutions.
Rewriting software is difficult because new versions compete against old features. "Parity" expectations create challenges when re-implementing years of institutional knowledge. Strategies include building separate standalone products like Basecamp 2 and 3, maintaining multiple versions while letting teams build desired products. Creating parallel products under throw-away brands like FreshBooks' BillSpring allows risk-taking without damaging existing brands.
The fallacy is building something new for everyone. Instead, build for small user subsets easy to convert, then expand to broader audiences over time. Using data to see what users actually do prevents guessing about feature importance. Less is more when it comes to products: ignoring code and features creates complexity affecting customer experience. Smart retirement strategies driven by data create better experiences.
Chapter 14: What Users Want
Gathering representative customer feedback requires moving beyond the loudest voices to actively recruit users who accurately represent different population segments. Highest-quality feedback comes from specific user sets: feature improvement input from active users, onboarding feedback from new users.
Traditional one-on-one interviews do not scale for modern product teams. New strategies include in-app surveys garnering higher response rates, survey tools enabling data analysis, NPS providing quick sentiment understanding, Customer Advisory Boards nurturing champion relationships, and spreadsheets allowing internal teams to share feedback.
Create single repositories for all qualitative feedback solves aggregation problems. These systems map feedback to product areas, enable closing loops with feedback providers, and allow meaningful aggregate analysis answering revenue impact questions.
Managing feature requests requires systematic prioritisation. Techniques include basic votes, weighted voting where users allocate budget across items, and pairwise voting comparing importance. Measuring by customer count, user count, revenue sum, or score sums reveals patterns. Centralised feedback systems make understanding common requests easier. Always close loops with feedback providers: let them know their voices were heard.
Maintaining product quality means addressing bugs effectively. Measuring bugs by feature pinpoints problematic areas. Tracking bugs reported versus fixed over time evaluates quality maintenance. Product performance requires setting acceptable standards and measuring against them regularly, as slow products fall from favour quickly even when valuable.
These feedback mechanisms inform the dynamic roadmapping that guides product evolution.
Chapter 15: Dynamic Roadmapping
Product roadmaps are powerful planning, communication, and alignment tools reflecting teams' future plans based on current priorities. They refine massive possibility universes into the few investments with greatest customer and business impact.
Gantt charts effectively visualise priorities, showing task dependencies and parallel work. Force-ranked lists maintain focus on the most important tasks sequentially. Roadmaps communicate product purpose to stakeholders and solicit feedback, giving direction to organisations.
Starting with vision and strategy ensures alignment with business objectives. Teams must identify product vision and principles (the why) before planning. Product goals translate strategy into executable plans: competitive differentiation, customer delight, technical improvements, satisfaction increase, lifetime value growth, churn reduction, geographic expansion, mobile adoption.
Effective prioritisation requires considering strategic alignment and customer behaviour. Understanding feature usage informs development resource investment, though underuse might indicate difficulty rather than lack of value. Adding targeted feedback determines the why behind behaviour.
Assigning specific metrics to roadmap items ensures value assessment. Business metrics like revenue represent higher-level outcomes; usage metrics indicate behaviour predicting outcomes. Each feature needs baseline KPIs set ahead, integrated within roadmaps to ensure measurement support is scoped.
Roadmaps provide strategic views complementing tactical backlogs. They communicate big-picture initiatives expanding markets, addressing competition, creating value. Incorporating goals and metrics illustrates the why behind priorities, making teams accountable. Without a clear why, avoid sharing roadmaps until priorities are discussed.
Roadmaps are never static: they are living documents regularly revisited and reprioritised based on new inputs. Setting expectations that roadmaps are not promises is crucial. Emotional attachment to roadmaps creates dangerous fixed mindsets. Customer willingness to pay for features provides valuable feedback justifying changes.
Publishing roadmaps publicly requires caution: development is not a perfect science and setting unmeetable expectations is dangerous. Different audiences need different detail levels. Having multiple roadmap versions for different audiences works better than single versions for all. Sharing roadmaps in presentations enables real-time feedback collection where the magic happens.
Chapter 16: Building Modern Product Teams
Product managers lead through influence rather than authority, inspiring others to follow without direct reports or control over resources. This requires establishing relationships based on mutual trust and respect that survive difficult times.
Product Operations (Product Ops) has emerged at the intersection of product, engineering, and customer success. It supports teams to tighten feedback loops, systematise development and launches, and scale product knowledge. Over half of product teams now have dedicated Product Ops functions, with larger companies more likely to have dedicated resources.
Product Ops performs four key functions.
- Optimisation of feedback involves collecting, structuring, and distributing customer feedback whether submitted directly or indirectly. This helps teams build the right products by preventing fragmented feedback.
- Alignment serves as connective tissue between teams, liaising with operational counterparts to enrich data and produce insights. Product Ops helps engineering understand the why behind building while shepherding customer stories to product teams.
- Feedback loops exchange data between departments and between products and customers. By refining data into insights, Product Ops enables smarter, faster decisions. This creates "product enablement": the data, stories, and guidance ensuring managers build the right solutions and prioritise critical improvements.
- Infrastructure and reporting responsibilities include selecting, integrating, maintaining, and operating product tech stacks. Product Ops compiles quarterly business reviews and board reporting, providing quantifiable product health perspectives through metrics like stickiness, adoption, retention, and NPS.
As customer journeys increasingly occur within products, companies elevate product leadership to senior positions. Product now has a seat at the table, requiring ops functions ensuring organisational alignment around products.
Conclusion: A Call to Action
The product-led movement blurs lines between product, engineering, marketing, sales, and customer success. Product responsibilities have expanded from shipping features to reimagining products as acquisition tools, retention vehicles, and strategic assets driving entire businesses.
Success requires starting incrementally with data and measurement, establishing measures and benchmarks tied to goals. Shift thinking to place products at the centre of customer experience through automation and self-service rather than human intervention. Organisations must align around product-led approaches with the right teams, measures, and customer-centric visions.