The whole library.
One useful idea at a time.
Browse every guide to product building, branding and marketing, or explore a topic to find your next step.
Page 3 of 10
Explore topicsHow to run a product growth review that ends in decisions
Run product growth reviews around user outcomes, evidence quality, active hypotheses, and named next steps so the meeting produces decisions instead of metric commentary.
How to measure product engagement without rewarding busywork
Measure product engagement through meaningful progress and task quality, separating useful participation from repeated clicks, unnecessary visits, and avoidable work.
How to write a product scope a delivery team can build
Write a buildable product scope with a bounded user outcome, explicit workflow rules, edge cases, acceptance evidence, and a clear list of decisions still open.
How to choose MVP boundaries without breaking the core workflow
Choose MVP boundaries around a complete user outcome, distinguish necessary support from optional breadth, and preserve recovery paths while reducing delivery scope.
How to model product data around real workflow states
Model product data through entities, ownership, workflow states, and change history so the system preserves meaning when users revise, transfer, or remove information.
How to define API contracts before integrating product features
Define API contracts around product meaning, permissions, error behavior, and change expectations so client and service teams can build a coherent workflow together.
How to choose a product quality strategy by risk
Choose product quality checks from the consequences of failure, covering core workflows, access, data integrity, accessibility, and recovery with proportionate evidence.
How to prepare a product release readiness checklist
Prepare a release readiness checklist that connects deployed behavior, data changes, permissions, recovery, and operational ownership to the user outcome being released.
How to design product integrations for failure and recovery
Design integrations around ownership, data meaning, partial failure, retry behavior, and visible recovery so an external dependency does not make the workflow ambiguous.
How to define product reliability around critical user actions
Define product reliability through critical user actions, meaningful failure states, dependency behavior, and recovery expectations that operators can actually verify.
How to prepare a technical handoff that preserves product decisions
Prepare a technical handoff with workflow rules, architecture boundaries, operational ownership, verification evidence, and open decisions for the next team.
How to design product permissions from actions and ownership
Design product permissions through actions, resource ownership, role context, and explicit denial behavior so access rules stay coherent as the product grows.