Improving Focus and Alignment by Organizing around OKRs and managing OKR Flow

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Today, I wanted to share two quick observations about OKRs.

Too many teams working on each strategic OKR

OKRs Matrix vs Organizing around OKRs

I encounter many organizations that use OKRs. Too many of them have this crazy matrix where the high-level OKRs – those that aim to achieve the organization’s strategy – map to too many teams/functions in the organization. This creates a need to cascade the OKRs, create sub-OKRs, or other techniques which eventually create a larger and larger distance between the OKRs at the team level and the strategic OKRs. While this at least creates transparency of who’s involved in executing each aspect of the strategy, we can and should do better.

One key thing that unlocks agility and value is to “Organize around Value”. Scrum talks about each team having ONE Product Goal they focus on. SAFe has a specific principle of “Organizing around value”.

If you’re using OKRs One question to ask yourself is what is the relationship between OKRs and teams/teams of teams? If most OKRs require a multitude of teams across the organization/portfolio to achieve them, this will require a lot of coordination.

Try reorganizing into a value stream network/topology/team structure that aligns with your OKRs – where each team/team of teams can focus, and where there is clearer accountability around which team/group owns a specific high-level OKR.

Yes, you can find OKR and Agile management tools that will let you deal with complex networks of cascading OKRs, but Simplicity FTW…

Too many OKRs

Another symptom I’m seeing way too often is too many OKRs. Some of that is related to the OKR matrix I mentioned above. Some of it is just plain old push vs pull and classic wishful thinking at all levels. What could we do about that? Do we have a proven approach that can help? mmm…

Maybe we should visualize the FLOW of OKRs through the funnel of considering them, prioritizing/refining, committing to them, working on them, reviewing, achieving…
How about LIMITING and REDUCING the amount of OKRs in progress across the organization at any point in time – the alignment that OKRs promise relies on focus rather than trying to boil the ocean
Next, let’s manage the flow of OKRs proactively. Maybe even use some metrics like OKR cycle time, throughput, WIP, and aging.
Let’s inspect the flow from time to time. We might learn a few things. Maybe we should adopt the definition of how these OKRs flow and how we’re managing them.

How many of you ARE leveraging Kanban/Flow practices to improve how your organization uses OKRs to align strategy and execution?

PS do you see how similar this would be to a portfolio Kanban? Could it be the next generation of portfolio Kanbans? 🙂

Subscribe for Email Updates:

Categories:

Tags:

Agile Techniques
Scaled Agile Framework
Elastic Leadership
ALM Tools
Sprint Planning
Video
Sprint Iteration
Lean Agile Leadership
Principles of Lean-Agile Leadership
AI Artificial Intelligence
Agile Basics
Agile Israel Events
Lean Budgeting
Limiting Work in Progress
Continuous Planning
Kanban Basics
Kaizen Workshop
Agile Project
Agile Israel
Risk Management on Agile Projects
Advanced Roadmaps
DevOps
Releases Using Lean
Perfection Game
Lean Agile
QA
ARTs
ROI
Enterprise DevOps
Kanban
Nexus vs SAFe
Keith Sawyer
System Team
ART Success
Self-organization
predictability
Presentation
Built-In Quality
System Integration Environments
Agile Product Development
Planning
Large Scale Scrum
Professional Scrum Product Owner
GanttBan
LAB
Agile Outsourcing
Effective Agile Retrospectives
SAFe
Scrum.org
Agile Community
Scrum Primer
Accelerate Value Delivery At Scale
POPM
Pomodoro Technique
Amdocs
BDD
Certification
Agile Exercises
SAFe Release Planning
Games and Exercises
Product Ownership
Agile Development
Business Agility
EOS®
Continuous Improvement
Process Improvement
Systems Thinking
RTE
Scrum Guide
Reading List
Agile Marketing
NIT
Engineering Practices
Entrepreneurial Operating System®
Jira admin
Introduction to Test Driven Development
Agile Delivery
A Kanban System for Software Engineering
Nexus Integration Team
Operational Value Stream
Lean Agile Basics
Agile and DevOps Journey
Lean and Agile Principles and Practices
Agile Risk Management
Kanban Kickstart Example
Quality Assurance
AI
Lean and Agile Techniques
Lean Agile Management
Scrum With Kanban
Scrum Values
Lean-Agile Budgeting
Development Value Streams
Lean-Agile Software Development
Lean Startup
Agility
Managing Risk on Agile Projects
lean agile change management
Continuous Integration
Professional Scrum with Kanban
Artificial Intelligence
Managing Projects
transformation
Applying Agile Methodology
Agile for Embedded Systems
Agile Release Planning
Implementing SAFe
Agile Release Management
Agile in the Enterprise
Spotify
The Kanban Method
Atlaassian
Agile Assembly Architecture
Acceptance Test-Driven Development
Introduction to ATDD
Covid19
Agile Games and Exercises
Continuous Delivery
Kaizen
Slides
Jira Plans
Agile Testing Practices
ATDD
Frameworks
speed @ scale
Daily Scrum
Agile Program
Scrum Master
Change Management
AgileSparks
Webinar
Code
Jira Cloud
ATDD vs. BDD
Agile India
Nexus and SAFe
speed at scale
User stories
Agile Contracts Best Practices
An Appreciative Retrospective
The Agile Coach
Legacy Code
What Is Kanban
SA
Hybrid Work
Scrum Master Role
Tools
Coaching Agile Teams
Risk-aware Product Development
Agile Games
Certified SAFe
SAFe DevOps
LeSS
System Archetypes
SPC
Professional Scrum Master
Rovo
Sprint Retrospectives
Agile Project Management
Achieve Business Agility
Kanban Game
Software Development Estimation
Continuous Deployment
Iterative Incremental Development
WIP
Tips
Nexus
PI Objectives
Scrum and XP
Lean Risk Management
Portfolio for Jira
ScrumMaster Tales
LPM
Atlassian
Kanban 101
IT Operations
PI Planning
Story Slicing
chatgpt
Test Driven Development
Agile
RSA
Software Development
Retrospectives
Program Increment
Risk Management in Kanban
Manage Budget Creation
Legacy Enterprise
agileisrael
Scrum
Agile Product Ownership
Jira
Lean Agile Organization
Nexus and Kanban
Rapid RTC
Confluence
Value Streams
Release Train Engineer
Implementation of Lean and Agile
RTE Role
Product Management
Agile Mindset
Team Flow
TDD
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart