Idea Flow
Models
Idea Flow
  • Welcome!
    • Why Models?
    • Why Principles?
  • Agility & Transformations
    • Intro to Agile
      • What Does Agile Mean?
      • What Is An Agile Mindset?
    • Intro to Transformation
      • Why Transform?
      • How Is The Transformation Done?
      • Who Transforms?
      • Which Areas or Functions Transform?
      • How Long Does A Transformation Take?
  • Agile Transformation (Idea Model)
    • Intro to IDEA
      • Leadership-Strip (Tanzaku)
      • Managing The Change
      • Metrics
      • Coaching Plan
        • Coaching Assessment
    • Initial Exposure
      • Training & Coaching
      • Assessment
    • Develop Basics
      • Training & Coaching
      • Assessment
    • Evolve & Reflect
      • Training & Coaching
      • Assessment
    • Accelerate & Kaizen
      • Training & Coaching
      • Assessment
  • Delivery Approach (Flow Model)
    • Intro to Flow
      • Flow of Work
      • Dev Sec Ops
    • Conceptualise
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Commence
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Construct
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Confirm
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Complete
      • Process
      • Outputs
    • Check
      • Process
  • Scrum, Kanban & Other Agile Frameworks
    • Double-Loop Scrum
    • Kanban
  • 3D Work-Breakdown
    • Intro to Work Breakdown
    • Direction
    • Discovery
    • Delivery
    • Flow & 3D Work-Breakdown
  • Roles & Responsibilities
    • Overview
      • Trust Circles
      • Enterprise View
    • Core Team Roles
      • Scrum Master / Iteration Manager
      • Product Owner
      • Developer
      • Tester
      • Business Analyst
      • Infrastructure
    • Extended Team Roles
      • Product Manager
      • Test Lead
      • Tech Lead
      • Subject Matter Expert (SME)
      • UX/UI Designer
      • Infrastructure Lead
      • Project Manager
      • Solution Architect
      • Delivery Manager
      • Change Analyst
    • Trusted Advisor Roles
      • Project Sponsor
      • Stakeholders
  • Topics
    • Prioritisation
    • Estimation
      • Estimation Overview
      • Epic Estimation
      • Initiative Estimation
    • Planning
      • Sprint / Iteration Planning
      • Release Planning
      • Quarterly Planning
      • Problem Statement
    • Ceremonies
      • Showcase
      • Scrum of Scrums
      • Stand-up
      • Retrospective
      • Elicitation
      • Elaboration
      • Acceptance Criteria (AC)
    • Artefacts
      • Tech Spike
      • Definition of Done
      • Social Contract
      • Personas
      • Lean Canvas
      • User Stories
    • Toolkit
      • Success Sliders
      • ICaRuS Scoring
      • Accountability Cards
    • Quality
      • Test Strategy
      • Test Plan
      • Quality Attribute Definitions
      • Test Type Definitions
      • Regression Test Suite Definitions
      • Defect Definitions
      • Defect Severity
      • Defect Priority
      • Agile Testing Quadrants
      • Risk-Based Testing
    • Templates
      • 3rd Party Handover Template
      • Audit Logs
    • Data
      • Information Management
    • Kanban
  • Agile Testing (4Aces Model)
    • Intro to Agile Testing
      • Test Principles
        • Test Automation Principles
      • Test Artefacts
      • Test Triangle
      • Agile Testing Quadrant
    • Arrange
    • Act
    • Assert
    • Annihilate
  • INCIDENT MANAGEMENT (TRACeR MODEL)
    • Intro to TRACeR
      • What is Incident Management
      • Incident Management Workflow
    • Triage
    • Review
    • Action
    • Check
    • Resolve
  • Change Management (3C Change Model)
    • Intro to 3C Change
      • What is Change?
      • What is Change Management?
      • 7Rs of Change Management
      • Model States
      • Implementation
    • Capture
      • Priority
      • Experience
      • Impact
      • Change Types
    • Consider
      • Risk
    • Conduct
      • Plan
        • Change Activities Matrix
      • Perform
        • Rollback or Roll-forward
      • Prove
        • Change Result/Status
  • Faciliation
    • Intro to Faciliation
      • Agile Facilitation
      • Planning and Running a Workshop
    • Meetings
      • Meeting Prep
    • Workshops
      • Quarterly Planning Workshop
      • Integrated Culture Workshop
    • Games
      • Dice Game
      • Battleships
      • Kanban Pizza Game
    • Icebreakers
      • Check Your Personal Thinking Style
  • Agile Coaching (A6 Model)
    • Intro to Coaching
    • Agree
    • Address
    • Assess
    • Align
    • Assign
    • Account
  • Agile Leadership
    • Intro to Agile Leadership
  • Strategy
    • What is Strategy?
    • What is Vision?
    • What is a Mission?
    • What are Values and Drivers?
    • Intent-based Outcomes
    • MunroMaps
  • OKRA
    • OKRS + ACTIONS = OKRA
      • Implementation
      • Cycle Cadence
    • Objectives
      • OKRs
    • Key Results
    • Actions
  • Agile Software Architecture (C4 Model)
    • Intro to Architecture
      • Role of the Architect
      • SOLID Principles
      • DRY Principle
      • Single Source of Truth (SSOT)
    • Context
      • Examples
    • Container
      • Examples
    • Component
      • Examples
    • Code
      • Examples
    • Patterns
      • Back-end for Front-end (BFF)
      • Event-Driven Microservices
  • Portfolio Management (PMO Practice Model)
    • Intro to Portfolio Management
      • Practices & Flow
      • Objectives
      • Types
      • Maturity Assessment
      • Setting Up
        • Charter
    • Demand Practice
    • Risk Practice
    • Performance Practice
      • Cost of Delay (CoD)
      • Metrics
    • Report Practice
    • Delivery Practice
    • Asset Practice
    • Change Practice
  • RAFT
    • RAFT Framework
  • Tools
    • Jira
      • Best Practice
      • Printing Physical Cards
    • Confluence
      • Best Practice
      • Example Confluence Layout
    • Power BI
      • Power Query M
    • Miro
      • Best Practice
  • FAQs
    • Frequently Asked Questions
    • Glossary of Terms
  • Thanks & Contributors
    • Thanks
    • License
Powered by GitBook
On this page
  • OKRs at a Glance
  • Objectives
  • Key Results
  • Initiatives
  • Monitoring & Grading
  • Committed Goal (Must hit 100%)
  • Stretch Goal (70% to 100% is Success)
  • BHAG (Some progress is Success)
  • Reporting
  • Progress and Difficulty
  • Confidence
  • Trends & Averaging

Was this helpful?

  1. OKRA
  2. Objectives

OKRs

Last updated 7 months ago

Was this helpful?

OKRs at a Glance

  • Objectives are ambitious and may feel somewhat uncomfortable

  • Key results are measurable and should be easy to grade with a number (Google uses a scale of 0 – 1.0) (100%? increments of 10 or 1 or 0.1? Why not 0-10)

  • OKRs are public so that everyone in the organization can see what others are working on

  • The “sweet spot” for an OKR grade is 60% – 70%; if someone consistently fully attains their objectives, their OKRs aren’t ambitious enough, and they need to think bigger

  • Low grades should be viewed as data to help refine the next OKRs

  • OKRs are not synonymous with employee evaluations

  • OKRs are not a shared to-do list

```notebook-python
#@title OKRs
## !pip install diagrams &> /dev/null 
from diagrams import Cluster, Diagram
from diagrams.programming.flowchart import Document

with Diagram("OKRs", show=False) as diagram:

    with Cluster("Company"):
      company_obj = Document("Objective") 
      company_kr = Document("Key Result")
      company_group = [ company_obj, company_kr ]

      company_obj >> company_kr

    with Cluster("Division"):
      div_obj = Document("Objective") 
      div_kr = Document("Key Result")
      div_group = [ div_obj, div_kr ]

      div_obj >> div_kr

    with Cluster("Team"):
      obj = Document("Objective") 
      kr = Document("Key Result")      
      tm_group = [ obj, kr ]

    init = Document("Initiative")

    company_obj >> div_obj >> obj

    obj >> kr >> init

diagram
```

Objectives

An Objective describes an outcome you’d like to achieve in the future. An Objective sets the direction — think of it like a destination on a map.

An Objective answers the question: “Where do I want to go?”

To ensure they’re inspirational and can be understood by everyone, they shouldn’t be technical and shouldn’t contain a metric.

Objectives should be:

  • Ambitious - More than just "business as usual" or incremental change, an objective describes an aspirational yet attainable transformation, growth, and improvement that significantly improves the current situation.

    • For example, introduce disruptive innovations, establish differences between the company and competitors, or be recognized as an industry leader in a category.

  • Meaningful - A top priority that advances the company's strategy and greater mission; provides direction to departments, teams, and individuals about where we are going and how we are getting there.

  • Inspirational - By providing an aspirational yet meaningful target, empower teams to reprioritize work to focus on what makes the most progress against an objective; to accomplish this, the objective should also be easy to remember.

  • Align Teams & Individuals - Need to be broad enough to be relevant to at least more than one department, team, or individual one level down, but also specific enough that the objective can be measurable by up to three key results; if associated Key Results are satisfied, Objective should be achieved.

    • For example, a product-related OKR at the CEO level, such as increasing users by 100%, would have the Product leader as responsible. Still, every other function would also need to contribute to achieving that KR.

  • Clear, Responsible Party - While aspirational objectives will often require collaboration and teamwork, they should have one responsible person to ensure the completion of the objective.

  • Focused - A person or team should have no more than 3 Objectives in order to focus on only the highest priority items; this also provides clarity on what we will not do in order to remain focused.

  • Transparent - Allow individuals, teams, and departments to see how their work contributes to the overall goals of the company. By sharing OKRs, individuals, teams, and departments are able to spell out their priorities and avoid having others disrupt focus with non-priority items.

Categorising the Objective will begin to shape the objective (See Monitoring & Grading). For example, Committed Goals do not need to be inspirational or ambitious; however, most of the other attributes are applicable.

Key Results

A Key Result is a measurable outcome required to achieve the Objective. They help you measure progress toward the Objective — like a signpost that shows how close you are to your destination.

Key Results answer the question: “How do I know if I’m getting there?”

Key Results encourage you to be ambitious yet realistic. And they must contain a start and target value.

A KR differs from a KPI as it can be measured in a number of ways; for example, “assess and document” can be with polls, NPS surveys, direct feedback, etc. If there is a simple, quantifiable measure of the KR, then it can also be a KPI.

Key Results should be:

  • Incremental - A Key Result should focus on a number of incremental or steps on the way to an outcome instead of just the outcome.

  • Aspirational - Ambitious but realistic stretch goals; if it feels uncomfortable, it's a good KR.

  • Linked - Be aligned to an Objective and be relevant to teams one level down; this alignment also allows KRs to roll down to become objectives one level down easily.

    • KRs should not be too specific that the KR needs to be rolled more than one level down.

  • Clear, Responsible Party - one single person or team responsible for Key Result.

  • Influenceable - the Key Result owner (department, team, or individual) should be able to impact Key Result through the owner's actions.

    • Example: an individual KR to change company-wide net retention is too broad; there are too many other conflating factors for an individual to determine impact. However, net retention could be appropriate KR for an entire department.

  • Time Bound - has a due date usually within the quarter.

  • Measurable - As Key Results provide the milestones for how we’ll complete the objective, KR should be either a qualitative (i.e. completed Y/N or a number of steps of the project completed) or quantitative (increased a metric by x) measure that can prove we accomplished the Key Result. Quantifying Key Results is strongly preferred.

  • Mutually Exclusive - Measure one component of progress for an objective without overlapping with progress represented by other Key Results. Progress for one Key Result shouldn’t count towards another Key Result.

    • Example: A Key Result for a number of transactions and a Key Result for the average dollar amount of transactions are an example of mutually exclusive Key Results: one KR measures volume while the other Key Result measures the quality of volume. On the other hand, a Key Result for a total number of transactions and a Key Result for a number of transactions from North America is an example of an overlap: progress gets ‘double-counted’ for both Key Results.

  • Collectively Exhaustive - Key Results should fully account for what’s required to achieve an objective. If all Key Results are achieved, then, by default, the Objective must also be achieved.

  • Few Words and Ubiquitous Language -

Initiatives

Initiatives are all the projects and tasks that will help you achieve a Key Result. They set the overall direction and describe how you’ll reach your destination.

Initiatives answer the question: “What will I do to get there?”

These are the actions. They need an owner (responsible). The accountable owner is the owner of the KR.

Monitoring & Grading

Each KR should be categorised in order to measure it against the best scale. Once the scale has been decided, then the starting point must be defined.

Committed Goal (Must hit 100%)

The business-as-usual target is one that you’d expect to hit 100%. Anything other than 100% would be considered a failure. Given what we went through earlier about goals being hard, these are the exception, not the rule.

Binary goal. Either it is done, or it is not.

Stretch Goal (70% to 100% is Success)

Part of the OKR planning process is to agree on what a hard stretch target would be.

Hard goals are sometimes called stretch or committed goals as well. Achieving 100% of the target would be amazing, and 70% would be good.

The engine room of OKR is conversation and debate around what your Objective should be, what you should measure, and what ‘good’ and ‘amazing’ would look like.

BHAG (Some progress is Success)

It’s been shown that what is considered ‘visionary’ companies often also set highly aspirational, Big Hairy Audacious Goals (BHAG). They are set to inspire greatness, new ways of doing things, new approaches to problems and genuine innovation. You need to choose when and where to set them, obviously, but their value is clear. Calibrating the success of a BHAG is harder, but 30% to 100% for many would be seen as a great result.

Reporting

When reporting on OKRs during the quarter, there are a couple of elements to take note of:

Progress and Difficulty

Together the % progress and the level of difficulty show how the goal is progressing. This is a key part of the reporting - a conversation!

Confidence

Where progress looks backwards, confidence levels look forwards and benefit from what you know about the execution of the goal and the likelihood of making good progress going forward.

Trends & Averaging

Averaging an OKR looks like this:

Key result #1: 0.5 Key result #2: 0.7 Key result #3: 0.3

Objective: 1.5 ÷ 3 = 0.5