Curated learning

Learning paths

Follow a deliberate sequence through the wiki. Each path connects existing topics into a practical progression rather than another reading list.

01

Build product foundations

Move from a product idea to a coherent direction, roadmap, and set of operating principles.

For New product managers and cross-functional product teams
  1. practiceProduct Management

    The discipline of guiding a product toward sustained customer and business value through evidence, strategy, decisions, and coordinated learning.

    Read topic
  2. principleProduct Mindset

    A way of thinking that treats product work as an ongoing search for customer and business outcomes through collaboration, evidence, and adaptation.

    Read topic
  3. frameworkOutput, Outcome, and Impact

    A distinction between what a team produces, the change in user or system behavior, and the wider result that change contributes to.

    Read topic
  4. artifactProduct Vision

    A concise, durable description of the positive future a product seeks to create, for whom it matters, and why the direction is worthwhile.

    Read topic
  5. principleProduct Principles

    A small set of memorable decision rules that translate product strategy and learned values into guidance for recurring tradeoffs.

    Read topic
  6. artifactProduct Strategy

    A coherent set of choices about where and how a product will create distinctive customer value while advancing important business objectives.

    Read topic
  7. artifactValue Proposition

    A testable explanation of why a defined customer would choose an offering, based on relevant outcomes, pains relieved, and alternatives.

    Read topic
  8. practiceProduct Discovery

    The work of reducing uncertainty about which customer problems and product solutions are valuable, usable, feasible, and viable before scaling.

    Read topic
  9. principleProblem-Solution Fit

    Early evidence that a specific customer problem matters and that a proposed value proposition plausibly addresses it better than relevant alternatives.

    Read topic
  10. artifactProduct Goal

    A future state that gives a product team a shared objective and context for ordering work.

    Read topic
  11. artifactProduct Roadmap

    A strategic communication artifact that connects product direction and desired outcomes to a changing sequence of investments.

    Read topic
  12. principleProduct-Market Fit

    A condition in which a defined market repeatedly chooses, uses, and values a product strongly enough to support sustainable traction.

    Read topic
02

Turn research into evidence

Frame assumptions, learn from customers, validate solutions, and use experiments responsibly.

For Designers, researchers, and discovery teams
  1. methodAssumption Mapping

    A method for exposing beliefs behind a product idea and prioritizing the assumptions that are both critical and weakly supported.

    Read topic
  2. artifactResearch Question

    A focused statement of what a study needs to learn so the team can choose suitable evidence and make a defined decision.

    Read topic
  3. artifactUser Research Plan

    A document that connects a research decision to clear questions, participants, methods, logistics, ethics, and intended use of the evidence.

    Read topic
  4. practiceParticipant Recruitment

    The practice of finding, screening, inviting, and supporting people whose experience is relevant to a research question.

    Read topic
  5. artifactDiscussion Guide

    A flexible session script that translates research questions into a consistent flow of neutral topics, prompts, activities, and follow-ups.

    Read topic
  6. methodUser Interviews

    One-to-one conversations that uncover users’ goals, experiences, language, expectations, and reasoning around a product or problem.

    Read topic
  7. frameworkJobs to Be Done

    A lens for understanding the progress people seek in particular circumstances and why they choose, switch, or reject products and services.

    Read topic
  8. methodThematic Analysis

    A systematic method for coding qualitative data and developing patterns of shared meaning that answer a research question.

    Read topic
  9. methodUsability Testing

    Observing representative participants attempt realistic tasks to identify where an interface supports or obstructs successful use.

    Read topic
  10. methodA/B Testing

    A/B testing randomly assigns eligible units to variants and compares predefined outcomes to estimate the causal effect of a product change.

    Read topic
  11. practiceTriangulation

    The deliberate comparison of evidence from different methods, data sources, researchers, or theories to strengthen and complicate conclusions.

    Read topic
  12. principleValidated Learning

    Decision-relevant learning supported by credible evidence that tests a consequential assumption about customers, value, or viability.

    Read topic
03

Ship with confidence

Connect requirements, engineering practices, release controls, and quality signals into a dependable delivery system.

For Product, design, and engineering teams
  1. artifactUser Story

    A concise statement of a desired outcome from a user’s perspective that acts as a prompt for collaborative requirements and delivery conversations.

    Read topic
  2. practiceAcceptance Criteria

    Specific, testable conditions that describe the behavior and outcomes a work item must satisfy to be accepted by product and delivery collaborators.

    Read topic
  3. methodStory Splitting

    A method for dividing a large user story into smaller, independently useful slices that preserve observable value and learning.

    Read topic
  4. practiceBacklog Refinement

    An ongoing collaborative activity that adds appropriate detail, order, and size to near-term backlog items as the team learns more about the work.

    Read topic
  5. artifactDefinition of Done

    A shared quality standard that defines when an increment is complete and usable.

    Read topic
  6. practiceContinuous Integration

    A development practice of integrating small code changes frequently and checking each integration with an automated build and test process.

    Read topic
  7. practiceCI/CD Pipeline

    An automated delivery workflow that builds, tests, packages, and promotes software changes through controlled stages toward production.

    Read topic
  8. practiceFeature Flags

    Runtime controls that change product behavior for selected contexts, allowing teams to separate code deployment from user-facing release decisions.

    Read topic
  9. practiceContinuous Delivery

    The capability to keep software in a releasable state so changes can be deployed safely, quickly, and sustainably whenever the organization chooses.

    Read topic
  10. practiceDesign QA

    Design QA is the structured review of an implemented product against approved design intent, system rules, content, responsive behavior, and accessibility requirements.

    Read topic
  11. metricDORA Metrics

    Five software-delivery performance measures used together to examine change throughput and instability for an application or service.

    Read topic
  12. practiceRetrospective

    A recurring team reflection that examines how work happened, identifies a meaningful improvement, and turns learning into a concrete experiment or action.

    Read topic
04

Measure product growth

Choose meaningful metrics and understand acquisition, activation, retention, and sustainable growth.

For Growth, analytics, and product teams
  1. practiceProduct Analytics

    Product analytics uses behavioral and operational data to understand how people experience a product and to inform improvement decisions.

    Read topic
  2. metricNorth Star Metric

    A North Star Metric is a durable product-level measure intended to represent recurring value delivered to customers.

    Read topic
  3. artifactInstrumentation Plan

    An instrumentation plan specifies the data a product must emit to answer priority questions, including event logic, properties, ownership, and validation.

    Read topic
  4. artifactEvent Taxonomy

    An event taxonomy is a governed naming and classification system for product events and properties, designed to keep behavioral data consistent.

    Read topic
  5. methodFunnel Analysis

    Funnel analysis measures how eligible users progress through a defined sequence of events and where they stop or diverge.

    Read topic
  6. metricActivation Rate

    Activation rate is the percentage of eligible new users or accounts that reach a defined early-value milestone within a specified time window.

    Read topic
  7. metricTime to Value

    The elapsed time from a defined starting point until a user first experiences a meaningful product benefit.

    Read topic
  8. methodCohort Analysis

    Cohort analysis compares groups that share a starting event or characteristic to reveal how behavior and outcomes change over time.

    Read topic
  9. metricRetention Rate

    Retention rate is the share of a defined starting cohort that remains active, subscribed, or otherwise retained at a later time.

    Read topic
  10. metricCustomer Churn

    Customer churn measures customers or accounts lost from an eligible base during a defined period, usually as a count or percentage.

    Read topic
  11. metricCustomer Acquisition Cost

    Customer acquisition cost measures the sales and marketing cost required to add a new paying customer within a defined scope and period.

    Read topic
  12. metricCustomer Lifetime Value

    Customer lifetime value estimates the economic value attributable to a customer relationship across its expected duration.

    Read topic
05

Design usable, accessible experiences

Turn an understanding of people and content into clear, inclusive interfaces that work across contexts and abilities.

For Product designers, UX practitioners, and frontend teams
  1. principleUsability

    Usability is the extent to which specified users can achieve specified goals effectively, efficiently, and satisfactorily in a defined context of use.

    Read topic
  2. termMental Model

    A person’s internal explanation of how a system works and what will happen when they act.

    Read topic
  3. practiceInformation Architecture

    Information architecture organizes and connects content so people can understand what exists, where to find it, and what to do next.

    Read topic
  4. practiceNavigation Design

    Navigation design creates visible, predictable paths that help users understand their location, available destinations, and next steps.

    Read topic
  5. practiceInteraction Design

    Interaction design shapes how people act with a product over time, connecting goals, controls, feedback, system state, and recovery into a coherent experience.

    Read topic
  6. principleVisual Hierarchy

    Visual hierarchy uses position, scale, spacing, contrast, grouping, and sequence to reveal importance and guide attention through an interface.

    Read topic
  7. practiceResponsive Design

    Responsive design uses fluid layout, flexible media, and conditional rules so one interface adapts continuously across viewport sizes and capabilities.

    Read topic
  8. practiceInclusive Design

    Inclusive design is a process that recognizes exclusion, learns from human diversity, and creates adaptable solutions with affected people.

    Read topic
  9. principleAccessibility

    Digital accessibility means designing and developing products so people with disabilities can perceive, understand, navigate, interact, and contribute.

    Read topic
  10. frameworkWCAG

    WCAG is the W3C’s testable international standard for making web content more accessible to people with disabilities.

    Read topic
  11. frameworkDesign System

    A design system is a maintained set of principles, guidance, reusable assets, and coded components for producing coherent product experiences.

    Read topic
  12. methodUsability Testing

    Observing representative participants attempt realistic tasks to identify where an interface supports or obstructs successful use.

    Read topic
06

Take a product to market

Choose a market, shape a differentiated offer, set its commercial model, and coordinate launch and adoption.

For Product managers, founders, marketers, and commercial teams
  1. methodMarket Segmentation

    Market segmentation divides a broad market into meaningful groups whose shared needs, circumstances, or behavior support distinct product and go-to-market choices.

    Read topic
  2. termTarget Market

    A target market is the customer group a company deliberately chooses to serve with a coordinated product, positioning, channel, and commercial strategy.

    Read topic
  3. artifactIdeal Customer Profile

    An ideal customer profile describes the account or customer type most likely to gain strong value from an offering and support a healthy business relationship.

    Read topic
  4. methodMarket Sizing

    Market sizing estimates the number or value of potential customers and transactions within explicit boundaries, assumptions, units, and time periods.

    Read topic
  5. methodCompetitive Analysis

    Competitive analysis examines how customers solve a problem, how alternatives create value, and where a product can make a defensible strategic choice.

    Read topic
  6. artifactValue Proposition

    A testable explanation of why a defined customer would choose an offering, based on relevant outcomes, pains relieved, and alternatives.

    Read topic
  7. practiceProduct Positioning

    Product positioning defines the market context, audience, distinctive value, and credible reason a customer should choose a product over alternatives.

    Read topic
  8. practicePricing Strategy

    Pricing strategy defines how a business sets and evolves prices, packaging, metrics, and terms to support customer value and business goals.

    Read topic
  9. frameworkGo-to-Market Strategy

    A coordinated plan for reaching a defined market, communicating value, delivering the product, and creating a repeatable path to adoption and revenue.

    Read topic
  10. practiceProduct Marketing

    A cross-functional practice that builds market understanding, positioning, messaging, launch readiness, and adoption for a product and its audiences.

    Read topic
  11. practiceProduct Launch

    The coordinated introduction of a product or major change to a target market, supported by readiness checks, communication, delivery, and learning.

    Read topic
  12. practiceCustomer Success

    A proactive practice for helping customers achieve intended outcomes with a product while sustaining a healthy, mutually valuable relationship.

    Read topic
07

Lead healthy product teams

Create the conditions, decision boundaries, communication habits, and operating rhythm that help cross-functional teams succeed.

For Product leaders, design leaders, engineering managers, and team leads
  1. frameworkCross-Functional Team

    A team combining the skills needed to discover, deliver, operate, and improve a shared product outcome.

    Read topic
  2. artifactTeam Charter

    A jointly created document that clarifies a team’s purpose, boundaries, membership, decision rights, commitments, and measures of success.

    Read topic
  3. artifactWorking Agreements

    Explicit, team-created norms for everyday collaboration, including communication, meetings, focus time, decisions, handoffs, and conflict.

    Read topic
  4. principlePsychological Safety

    A shared belief that people can raise questions, admit mistakes, offer ideas, and challenge assumptions without interpersonal punishment.

    Read topic
  5. principleDecision Rights

    An explicit allocation of who may decide, who contributes, and how unresolved product choices are escalated.

    Read topic
  6. practiceDelegation

    The deliberate transfer of responsibility and appropriate decision authority while the delegating leader retains overall accountability.

    Read topic
  7. artifactStakeholder Map

    A stakeholder map identifies people and groups who affect or are affected by a decision, then makes relationships, power, interests, and engagement visible.

    Read topic
  8. practiceStakeholder Management

    A deliberate practice for understanding, involving, and communicating with people who influence a product or are affected by its outcomes.

    Read topic
  9. practiceFeedback Culture

    An environment where people routinely exchange specific, useful observations and act on them across roles, levels, and moments of work.

    Read topic
  10. practiceOperating Cadence

    A deliberate rhythm of recurring decisions, reviews, planning, and information sharing that helps an organization operate predictably.

    Read topic
  11. practiceProduct Operations

    The discipline of improving the systems, data, tools, and routines that help product teams make decisions and operate effectively at scale.

    Read topic
  12. practiceProduct Leadership

    The practice of setting product context, developing people and teams, shaping organizational conditions, and holding a product portfolio accountable for outcomes.

    Read topic
08

Build technical fluency

Understand the system boundaries, delivery practices, operational signals, and risks behind modern digital products.

For Product managers, designers, and technical collaborators
  1. termFrontend and Backend

    A division between the user-facing software that presents and collects information and the server-side software that applies shared rules and manages protected resources.

    Read topic
  2. frameworkClient and Server

    An interaction model in which a client initiates requests for capabilities or resources that a server provides across a defined boundary.

    Read topic
  3. frameworkRequest and Response

    An interaction model in which a client sends a message asking for an operation and a server returns a message describing the outcome.

    Read topic
  4. termHTTP

    The application-level request-response protocol that defines shared semantics for transferring representations and operating web systems.

    Read topic
  5. termApplication Programming Interface (API)

    A defined interface through which software components request capabilities or exchange data without depending on each other's internal implementation.

    Read topic
  6. termEndpoint

    A specific addressable interface location where a client can interact with a software service using defined operations and messages.

    Read topic
  7. termDatabase

    An organized store of persistent data managed so software can create, retrieve, update, protect, and recover information.

    Read topic
  8. frameworkCloud Computing

    A model for obtaining configurable computing resources over a network on demand with measured, elastic capacity.

    Read topic
  9. practiceCI/CD Pipeline

    An automated delivery workflow that builds, tests, packages, and promotes software changes through controlled stages toward production.

    Read topic
  10. principleObservability

    Observability is the ability to understand a system’s internal state and behavior from the telemetry and context it exposes.

    Read topic
  11. metricService-Level Objective

    A service-level objective sets a target value for a service-level indicator over a defined period, expressing the intended reliability level.

    Read topic
  12. methodThreat Modeling

    A structured method for identifying valuable assets, trust boundaries, plausible threats, and proportionate security responses before and during system change.

    Read topic

Start typing to search titles, definitions, categories, and frameworks.