Accessibility
Building products that work for users with disabilities through inclusive design and standards.
DevelopEvery concept from the Product Lifecycle, as a searchable index.
This is the flat view. Concepts across seven lifecycle stages, alphabetically sorted. Use the search box to find a concept by name, or filter by stage to narrow the list. If you want the narrative view - stages, flow, journey - see the Product Lifecycle page.
54 of 54 concepts
Building products that work for users with disabilities through inclusive design and standards.
DevelopIterative delivery frameworks that structure how teams plan, ship, and adapt.
DevelopSurfacing the unverified beliefs underneath a plan and testing the riskiest ones first.
PlanReleasing to a controlled group before general launch to catch real-world issues early.
QualifyDeciding which bugs block launch, which can wait, and how to communicate the call.
QualifyExtracting durable lessons from a product or feature that didn't survive.
RetireTurning scattered user input into patterns that drive product decisions.
DeliverTelling users a product is being retired in a way that preserves trust.
RetireBuilding an evolving post-launch roadmap that responds to real usage data.
DeliverOrchestrating product, engineering, design, marketing, sales, and support to land a launch.
LaunchDefining the milestones, dependencies, and readiness checks that precede launch.
PlanTelling users about a new feature in a way that drives adoption.
LaunchBuilding a realistic snapshot of a user segment to focus product decisions.
ConceiveMoving user data and workflows safely when retiring a product or feature.
RetireChoosing the metrics that will tell you whether the product is working.
PlanTransferring design assets to engineering in a way that preserves intent.
DevelopWorking with engineering and design as partners, not as resources.
DevelopDeciding whether a struggling product should change direction, be killed, or be maintained.
RetireReleasing new features to controlled cohorts before exposing them to all users.
LaunchChoosing what to build next from a longer list of candidates.
PlanWatching the metrics that tell you whether a launch is going well in real time.
LaunchTurning product instincts into testable hypotheses and validating them with users.
ConceiveFinding where users abandon a flow and diagnosing why.
DeliverDetecting the signals - usage, cost, strategy - that justify deprecation.
RetireSetting up the analytics that will let you measure what matters after launch.
DevelopPreparing internal teams to support and sell a new product.
LaunchUnderstanding why users hire a product - and why they fire it.
Conceive Read the reference page →Balancing the velocity of shipping against the long-term cost of shortcuts.
DevelopMapping the landscape a product will compete in before committing to a direction.
ConceiveTracking whether users actually use the product over time.
DeliverDefining the smallest version of a product that delivers real value and tests a real hypothesis.
PlanRevisiting whether the metric you chose still captures what matters.
DeliverIntroducing a new feature to existing users without disrupting their workflow.
LaunchEstimating how big the addressable opportunity is before committing resources.
ConceiveMapping the opportunity space before you pick a solution; testing assumptions before you commit.
Conceive Read the reference page →Running structured experiments to learn what improves the product.
DeliverStructuring the call on whether the product is ready to ship.
QualifyFalling in love with the problem before falling in love with the solution.
ConceiveA short, shared, solution-free definition of what you're solving - and how you'll know it's fixed.
Conceive Read the reference page →Mapping what gets built when, and what gets traded off in service of it.
PlanConnecting product decisions to a coherent longer-term vision.
ConceiveStructuring quality assurance so it catches issues before they reach users.
DevelopVerifying that new releases don't break existing functionality, with rollback paths if they do.
QualifyHolding the line on what's in and what's out as a project unfolds.
DevelopDefining the outcomes a product is trying to achieve in a given time period.
PlanGetting the people who matter on side before execution begins.
PlanSpotting where work is stuck and clearing the path forward.
DevelopWatching real users attempt to use a product to find where it breaks down.
QualifyVerifying with real users that the product meets the original requirements.
QualifyTalking to real users to understand needs that data alone can't reveal.
ConceiveWriting requirements that engineering and design can act on without ambiguity.
DevelopArticulating why a user would choose this product over the alternatives.
ConceiveProducing a product requirements document that aligns teams and reduces rework.
DevelopSetting objectives and key results that focus a team on outcomes that matter.
PlanThe framework pages above are being written one at a time. Each is a short reference page on how I think about that concept - not a textbook definition. New pages are added regularly.