Outcome-Oriented Thinking
Shipping a feature is not an outcome. Outputs are what your team produces. Outcomes are what changes for the user as a result. A product org can have a 95% delivery rate on its roadmap and a 0% outcome rate on its strategy.
This skill is the product-strategy lens on outcomes — specifically: North Star selection, outcome hypotheses, and the output/outcome/impact chain applied to product bets. For generic OKR authoring (team-level objectives and key results), use `out
[Description truncada. Veja o README completo no GitHub.]