Here’s a more casual and concise version of the content, using markdown and retaining key ideas:
“Health metric” OKRs are a bit different from traditional OKRs, but they help maintain important aspects of a healthy organisation. They’re especially useful when your team is just starting with OKRs and moving from existing project-based work to focusing on outcomes.
Traditional OKR advice suggests advice suggests keeping “business as usual” (BAU) work out of your OKRs. The idea is that OKRs should focus on big, transformative goals, not the routine stuff that happens naturally.
Chris McChesney, the guy behind 4DX®, talks about Wildly Important Goals® that are “really important” but won’t happen unless you change things up significantly (video clip).
In Measure What Matters, Astro Teller, who leads Google X, says, “If you want your car to get fifty miles per gallon, fine. But if I tell you it has to run on a gallon of gas for five hundred miles, you have to start over.”
I used to fully agree with this. Focusing on game-changing outcomes forces you out of the daily grind and pushes you to set goals that feel almost impossible. I encouraged teams to use OKRs to shift from short-term projects to ongoing services that consistently deliver value.
But here’s the thing: when you’re trying to use OKRs to drive broader organisational change, you often start with a mix of projects and BAU work. Projects usually drive innovation, while BAU is the stable engine that keeps everything running.
For years, I worked with a cool design and UX company in London that made award-winning games. But behind the scenes, they also did a lot of work for large corporate clients — less exciting but steady and profitable. The games got all the attention, but the corporate work “kept the lights on.”
Telling a company like this to ignore BAU when setting OKRs is like telling a restaurant to ignore sourcing ingredients or washing dishes. No matter how creative you are in the kitchen, if you don’t have quality ingredients or basic hygiene, your business will fail fast.
I often suggest that organisations avoid adopting OKRs until they have a solid system for handling BAU work—one that’s almost “boring”—so they can focus their energy on innovation. The truth is, BAU work doesn’t just happen on its own; it takes real effort and attention.
If you completely leave BAU work out of OKRs, the people responsible for that work might feel like their contributions don’t matter. And while not everyone needs OKRs, having a way to include BAU in OKRs can make the transition smoother.
That’s where “health metric” OKRs come in.
Health metrics keep you grounded while you aim high.
Revenue, retention, customer returns, app error rates, feedback: you may not want to dramatically change any of these just now but they still matter. A lot.
For example, you might want to create products that people love, measured by metrics like weekly active users or monthly recurring revenue. But, at the same time, you’ll want to keep team morale high and retain existing customers.
While OKRs focus on the changes you want to see, health metrics focus on the numbers you want to keep steady: build times, customer satisfaction, repeat customer rates, team happiness, etc.
For example, a health metric OKR might be:
Measured by:
This isn’t a traditional OKR—it doesn’t aim for a big change—but it uses the OKR format to express a condition you want to maintain.
You could pair this with an ambitious OKR like:
Measured by:
This combo gives you an inspiring goal and clear guardrails to keep things on track as you reach for the stars. It helps everyone see how their work fits into the bigger picture and lets you use OKRs (or OKR-like goals) to cover your entire portfolio.
It’s not a long-term fix, though. Over time, you’ll want to rely less on OKRs for BAU work. But during the OKR adoption process, this approach can help ease the transition.