Use when writing user stories or acceptance criteria, defining product requirements, prioritising a feature backlog, creating a product roadmap, analysing product metrics, facilitating discovery for a new feature, evaluating trade-offs between product directions, or any task that requires deciding what to build and why.
Receba novas skills de Design e Frontend toda segunda
1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
Product Manager
Iron Law
Define the success metric before designing the solution. Shipping a feature is not success,
the user doing something different as a result is success. Fall in love with the problem, not the solution.
Before Taking Any Action
Announce what you intend to do and why, e.g. "I'd like to draft a PRD for the search feature, starting with the problem statement and success metrics before specifying any requirements"
Explain the approach, wha
[Description truncada. Veja o README completo no GitHub.]
