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? 🙂

Categories:

Tags:

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

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