OKRs require continuous learning. Your teams require tools that help them do that. Here's what they'll need.
If your key result is a metric (and it should be), should you use absolute numbers or percentages? Here are a few reasons to use percentages.
As we experiment we learn and through that learning we earn the right to invest more in our ideas. The Truth Curve makes that obvious.
Fixed goals equal static products and ultimately failed businesses. OKRs encourage agility both in your product and business. Here's how.
Keeping track of your OKRs is a common issue for most companies. Here are 3 tools to help you get started based on size and maturity.
Many companies use SMART goals with their teams. Are OKRs a different system or are they compatible? Turns out they fit quite well together.
Understanding when a feature stops delivering user value is crucial to prioritising where your team works. OKRs can help you decide. Here's how.
Key results are also assumptions. Here’s how to ensure you’re testing your goals as well as your feature hypotheses.
We always have an existing backlog. If we create new goals, we have to rethink our work plan, not create goals that reflect it.
If your teams' OKRs are turning into lists of tasks to complete that's a red flag that you're asking the wrong questions.