Category: agile
-
Using OKRs to Decide When to Kill Features
Understanding when a feature stops delivering user value is crucial to prioritising where your team works. OKRs can help you…
-
Validating key results is messy
Key results are also assumptions. Here’s how to ensure you’re testing your goals as well as your feature hypotheses.
-
How to recession-proof your company
An agile organization learns and acts fast on what it’s learning. The more agile an organization is the better chance…
-
OKR Anti-pattern: Creating OKRs to “fit” your backlog
We always have an existing backlog. If we create new goals, we have to rethink our work plan, not create…
-
OKR Leadership: OKRs are not task lists
If your teams’ OKRs are turning into lists of tasks to complete that’s a red flag that you’re asking the…
-
OKR Leadership: Stop telling people what to do
The biggest change a leader has to make if OKRs are to succeed is to stop telling their teams what…
-
OKR Leadership: A safe culture of learning
OKRs require the psychological safety for teams to be wrong and a culture that celebrates the learning they bring from…
-
OKR Leadership: Without Product Discovery Your Teams are Just Guessing
Setting up goals is the beginning of your OKR journey. The next step is understanding how you, as a leader,…
-
Horizontal IT is Why You Can’t Be Agile
It is no longer viable to design your organization around a centralised IT department. It’s not agile. It’s not customer…
-
How Do OKRs Work with Big Bang Releases
There are some products that have to be shipped as one big release. This article explains how to make big…