Objectives & Key Results (OKR)
Photo by Liam Desic on Unsplash
Align your business outcome objectives with upcoming deliverables and the backlog of work using OKRs.

Targetprocess’ OKR support is designed to connect your Enterprise OKRs with the experiments and enhancements you have identified or are implementing in product or solution development. Create your Objectives with related Key Results at multiple levels in your organisation and connect them to work items (like Epics or Features) and Scrum Sprint Goals or SAFe PI Objectives so you can easily see the activities or initiatives that are planned or in-progress to achieve the Key Results and ultimately accomplish your Objectives.

OKR Recap

Let’s do a quick recap on what OKRs are and how they can help your enterprise achieve Business Agility.

OKR (Objectives and Key Results) is a goal system. It is a simple tool to create alignment and engagement around measurable goals.

Creating alignment in the organization is one of the main OKR benefits. The goal is to ensure everyone is going in the same direction (focus), with clear priorities (clarity & transparency), in a constant rhythm (cadence).

As the name suggests, an OKR consists of two parts 1) the Objective and 2) a set of related Key Results.

In Targetprocess we support three levels of Objectives: Ultimate, Strategic and Tactical. The names of these levels can be renamed to suit your terminology. We advise to not cascade OKRs and to use the levels only for alignment over different time spans and scope.

Targetprocess Image

Support three levels of OKR with Targetprocess

When creating an OKR you can use the following sentence to help you create a good OKR: We strive to <Objective> as measured by <this set of Key Results>.

Objectives are memorable qualitative descriptions of what you want to achieve. Objectives should be short, inspirational and engaging. An Objective should motivate and challenge.


“If you have to stop to breathe while reading your Objective, it’s not a good objective” - Felipe Castro


Key Results are a set of metrics that measure your progress towards the Objective. For each Objective, you should have a set of 2 to 5 Key Results.


“If it does not have a number, it is not a Key Result” - Marissa Mayer

“Key Results must be results” - Christina Wodtke


First of all, we need an Objective. An example tactical objective might be: We strive to “Be recognized to have an awesome Customer Experience.” 

This sounds great, but how would you know if the experience is awesome? Remember, without measurements you don’t have a goal.

That is why we need Key Results. How can we measure if we are providing an awesome customer experience? Net Promoter Score and Repurchase Rate would be two good options. Do our customers feel so good about dealing with us that they would recommend us and buy again?

But measuring NPS and repeat purchases alone can send the wrong message. It might encourage us to make the customer happy at any cost. Therefore, we should include a countermeasure metric such as Customer Acquisition Cost. We want to make our customers happy while keeping the related costs under control.

The complete example would thus be:

Objective: We strive to “Be recognized to have an awesome Customer Experience.”

Key Results: as measured by:

  • Improve Net Promoter Score from X to Y.
  • Increase Repurchase Rate from X to Y.
  • Keep average Customer Acquisition cost under Y.

Having a set of Key Results including countermeasures to drive the right behaviour helps create a clear, and sustainable OKR.

So we have the Objective and the Key Result to measure our success, but how are we going to link it to the actual work that we are doing? This work (which should be seen as experiments or bets, see: “Hypothesis-Driven Development”) that we do in order to try and achieve our objective(s) should be made transparent. Without Targetprocess, you would need something like an Initiative or Activity description to keep record or track of them, but in Targetprocess we can use our regular Epics, Features and User Stories and Bugs for this. Thus we have Objectives, Key Results and related Work Items.

Targetprocess Image

Connect OKRs to Work Items

Combining Goal Systems

In Targetprocess we support different goal systems and they can exist next to each other. We have 1) OKRs (Strategic and Tactical OKRs) and 2) Scrum Sprint Goals and maybe SAFe PI Objectives. Instead of choosing one above the other we can connect them so they work together.

The OKR Goal system is to set aspirational business goals that we measure with Key Results. Good key results measure outcomes! An outcome is something that we can measure using an indicator but can’t change directly by doing something. We can, however, try to influence them by doing (small & safe) experiments.

“At Google and Bing, only about 10% to 20% of experiments generate positive results.” - Felipe Castro

The Scrum Sprint Goals and SAFe PI Objectives systems are there to set realistic goals to align teams (or team-of-teams) on delivering something together. Because they span only a short time period and are directly related to the work we do, they are usually output based. (We created and/or delivered something or we didn’t).

Going back to the OKR example of being recognized to have an awesome Customer Experience, we could imagine one team wants to improve performance and another team wants to optimize views for use on mobile devices, So they create “Views load in 2 seconds or less” & “Views are optimized for mobile device usage” as Team PI Objectives in order to focus on delivering this work, which might help achieve one or more of the Key Results of the OKR.

As updating the views for mobile devices might be an incremental job, the team might deliver this Team PI Objective in several increments using several Sprint Goals like “Optimize views for display in mobile Safari (iPhone)” and “Optimize views for display in mobile Chrome (Android devices)” etc...

Therefore the entities of these goal systems are connected in Targetprocess as follows:

Targetprocess Image

Connect OKRs to Work Items and Scrum Iteration Goals & SAFe PI Objectives

Key Features of Targetprocess’ OKR Solution

OKR Hierarchy Levels

Our OKR solution allows you to create OKRs at several levels in your organization like Ultimate, Strategic or Tactical or you can rename them to something like Mission, Company and Team. This allows you to easily see how OKRs of different levels and spanning different periods are linked together and are a stepping stone on the way to success!

Have full transparency on OKR Hierarchy using a list view
See your Objectives with their Key Results in one view

Linking Objectives to Work Items

Maximize OKR transparency by linking your OKRs to the related activities or initiatives represented as work items (like Epics or Features). This helps with both the top-down and bottom-up views. It helps development teams focus on the intended outcomes and understand how they are measured while giving stakeholders insights into the related upcoming solution enhancements or additions.

Easily see the related Work Items to any Objective
Easily link Work Items to any Objective via the detailed view

Report on OKR Status and Progress Overview

Use Targetprocess’ reporting and dashboarding functionalities to create clear overviews on the status and progress of your Objectives and Key Results. You don’t need a license or logged-in user for those who need to see the dashboards.

Publish and show the progress on your objectives on a shared website for anyone to see
See the progress of your teams OKRs by Key Result easily using a RAG-B color system

OKRs Combined with SAFe PI Objectives and Scrum Sprint Goals

OKR is a goal setting system targeting improved business outcomes. In Scrum and SAFe there are other more output oriented goal systems like Sprint Goals and PI Objectives. In Targetprocess you can optionally link them together to maximize transparency and get the benefits of both.

Targetprocess Image

Have a transparent view on Iteration Goals with parent PI objective and parent OKR

Or contact
a sales representative

Get a live
product demo

Let one of our product specialists create your account
and shape Targetprocess for your company needs.


See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.

Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.

For Transparency above the Team Level 

Azure DevOps
Azure DevOps
Add Targetprocess on top of the team level tool: get visibility on Product and Portfolio level.
Atlassian Jira Software
Atlassian Jira Software
Ensure free data flow from Jira to Targetprocess for greater visibility for all team members.

For Continuous Integration and Continuous Delivery 

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
Automatically link branches and merge requests to Targetprocess entities.
Automatically associate branches and pull requests with Targetprocess entities.
Link code revisions with any Targetprocess entity.
Automatically associate branches and pull requests with Targetprocess entities.
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.

For Product Management, ITSM, Sales and Marketing to Stay on the Same Page 

Centralize unstructured communication on Miro’s online whiteboard inside Targetprocess.
Microsoft Project Server
Microsoft Project Server
Provide visibility into high-level goals and details about implementation for all teams.
Synchronize customer service, sales, the PM office, and development teams.
Allow all team members to collaborate on shared artifacts from customer service tickets.
Collaborate on shared work items, consolidate reporting across the entire organization.

Experts and clients say More Reviews & Case Studies

  • Targetprocess is recognized as a Leader in Gartner’s 2020 Magic Quadrant for Enterprise Agile Planning Tools and included in the related Critical Capabilities for Enterprise Agile Planning Tools

    April 2020, “Magic Quadrant for Enterprise Agile Planning Tools”

    *Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
  • We have been using Targetprocess for more than three years by now and still been surprised when our teams find news ways and work areas to use it…
    It is really so flexible that we can nearly model and effectively use in each workflow we need. New departments request me from time to time to show them “that tool you have with nice cards ☺

    Jorge Rivero Sanchez
    Innovation Director
  • I love how adaptable and flexible Targetprocess is. It meets the various needs of so many different departments within our organization. We manage all of our IT, creative and legal workflow through Targetprocess. It’s helped create a centralized location for our cross-department needs – as well as providing a history of our work.

    Katie MacCabe
    Assistant Director
  • I used Targetprocess at some very large multi-team multi-program clients and had a consistently good experience.
    I’ve got a lot of experience of Jira, Rally, PivotalTracker, Trello, Mingle and open source agile lifecycle management tools. I like Targetprocess better – it covers a lot more ground, the information architecture is really consistent, it’s solid as a rock and fast too. Best of breed.

    Peter Merel
    CTO and Agile Coach