profile

Scaling w/ Agility

Improving Strategic Traction Through an OKR Kanban System

Published 5 months ago • 1 min read

What gets measured gets managed. But setting OKRs isn't enough. The flow and traction of OKRs need to be managed as well - otherwise, you'll find yourself in the OKR swamp.
​
Using an OKR Kanban can help you both see the swamp and improve the flow and traction of OKRs.

Here's an example -

Here are some of my favorite patterns for managing OKR flow using Kanban:

  • Use One OKR Kanban board. It's okay and preferable to see OKRs from multiple departments/teams/groups on the same board. It reinforces the transparency and alignment as well as interesting conversations about misalignment.
  • Use an OKR workflow for considering/exploring possible objectives/bets, planning/committing, actual experimentation/execution towards outcomes, and reflection/adaptation. This will help reinforce a product-oriented mindset - for both product and business OKRs!
  • Consider a workflow that helps you identify struggling OKRs to focus on - e.g., a Red/Yellow/Green - and make sure to start Red and expect OKRs to "Earn" their movement to Yellow/Green based on actual evidence. (This is a poor man's Work Item Aging approach)
  • Limit the number of OKRs in progress and consideration - Focus drives traction.
  • Visualize who's involved in which OKR, as well as the level of coupling/integration.
  • Decide whether to visualize KRs independently - this can provide interesting insights but can also hurt transparency if there's too much information.
  • If your board is too busy - that says something!
  • Use your OKRs Kanban when checking your OKRs and considering any new OKRs or other significant work. It can help facilitate healthy conversations.

How are YOU managing your OKRs? Do you have any favorite patterns for seeing and improving OKR flow?

​Read Improving Strategic Traction Through an OKR Kanban System On Your Browser​

Yours,

Yuval

Looking for ways to improve flow and traction on your company's strategic initiatives?

The Organizational Traction Trail Map is a practical, no-fluff email course designed to help leaders of scale-up and midsized organizations break free from scattered priorities and bring organizational flow, focus, and clarity.

Scaling w/ Agility

A newsletter for leaders on how to think through scaling challenges and develop/grow organizations using product and agility principles and practices.

Are You Struggling to Scale Your Organization ? Need agility but dubious of process BS/dogma? I share reflective, pragmatic, principled takes on how to approach scaling your organization leveraging the essence (rather than theater) of product operating models, agile practices and frameworks, and business operating systems such as EOS and OKRs.

Read more from Scaling w/ Agility

Context is King You’ve probably encountered this term in the context of AI. You won’t get far with AI, even with amazing prompting techniques, if AI doesn’t have the right context. Many people focus on the Data aspect of context – what’s in our CRM, in our collaboration tools, in our ERP, in any of our vertical systems. Another interesting aspect is the intent – what are we trying to achieve? What is our strategy? What problems are we focused on? Who are the players? Some of that information...

3 days ago • 1 min read

Hey Reader, Before you fix teams, fix the system they operate in. Most organizations focus their improvement efforts at the team, program, or product level while maintaining the same organizational operating system—how they make decisions, fund work, and measure success. These teams might be using the latest and greatest processes (Agile, Product Model, Lean Startup, take your pick) but they still need to manage countless dependencies. The funding and GTM processes are still following classic...

10 days ago • 1 min read

When Vered and I got married, my father-in-law gave me a very nice watch as a wedding gift. I didn’t wear a watch that often at the time. I wore the watch, but it didn’t transform me. It provided the service of telling the time, but even back in 2004, we had phones that had clocks. And I was and am pretty punctual so didn’t need that transformation. (And when you’re in Engineering/IT leadership, nobody cares about the watch you wear… at least in Israel… ) Don’t tell Eli, but that watch spent...

17 days ago • 1 min read