Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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