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. Here's an example - Here are some of my favorite patterns for managing OKR flow using Kanban:
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. |
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.
Reader Jonathan asked for some more color on the OKR swamp... Remember the Fire Swamp from Princess Bride? (If you don't, RUN to watch the movie. And consider this spoiler alert - and snooze this email until you're back) Navigating your OKRs often feels like the Fire Swamp. There are so many OKRs that they are all stuck - like the standing, dark, moist water in the Fire Swamp. The exercise of creating them involves wordsmithing agony that reminds you of a Battle of Wits with a sicilian......
Hi there. I thought I'd share what is going on behind the scenes ... January started with a flurry of deep work with clients and I'm still trying to figure out how to weave writing on a consistent schedule into these periods. In the future I might use these opportunities to share some classics/reruns. In addition, I've been focused on developing an email course. It's about how to improve organizational traction and outcomes using familiar agility principles and techniques. I've been working...
Most organizations wait way too long to adopt some portfolio-level agility practices. They’ve been told, “You can’t scale what’s broken,” so they wait until they nail agile at the team and product group level. What if fixing what’s broken REQUIRES focusing on the upstream operating models shaping the work and context of these teams? Back in 2012 or so, I met an SVP responsible for a 1000-person delivery organization that was working in a traditional waterfall. Critical Chain optimized...