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:

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