Start from the user or business problem you want to change, define the metrics that show progress, and use initiatives to capture the experiments or roadmap work supporting the result.
01Set your baseline. Check where you are today, then choose targets that stretch your team.
02Agree on ownership. Give each key result a clear owner and a source of data.
03Check in every week. Review the numbers, share confidence, and decide what needs attention.
KNOW WHAT TO MEASUREThe numbers behind your goals.
Choose a small set of KPIs to watch alongside your OKRs.
Explore related KPIs 
Product OKR questions
What should product OKRs measure?
Product OKRs should measure changes in user behavior, such as activation rate, feature adoption, retention, and time-to-value, rather than shipping milestones. A launch is an initiative; the behavior change it causes is the key result.
How do product OKRs relate to the roadmap?
OKRs define the outcomes the roadmap should produce, and roadmap items become the initiatives under each key result. This keeps the team free to swap features in and out during the quarter as long as the outcome is still moving.