Many of the Gtmhub users are developers. Often, when just starting out with OKRs, teams wonder how OKRs work with agile.

Here is the way we think about it:

  • Objective : What we want to achieve?

  • Key results : How are we going to measure success?

  • Tasks : What are we going to do about it?

Task is not a key result

Fixing a bug or implementing a feature should never be a goal in itself: therefore “Implementing feature X” is not a good objective nor is it a good key result.

Ultimately, we always start with an objective – albeit it is sometimes implicit. Next, we want to come up with several key results that will allow us to measure our progress. Finally, we start defining tasks that will help us achieve our objective.

To illustrate this point, let us examine a real-world example.

  • Objective (what we want to achieve) : Increase user engagement

  • Key results (how are we going to measure success) :

    • Average user logs in 6 times a week

    • Average user writes 2 comments a month

    • Average user likes 1 item a month

  • Tasks (what are we going to do about it) :

    • Send a weekly summary email to every user

    • Implement push notifications when someone comments on user’s item

    • Implement push notifications when someone likes user’s item

    • Send a “check-in” email when user does not log in for 7 days

To enable this natural flow, we have released a native JIRA plugin and revamped our objectives UX.

Work with OKRs directly from JIRA

No one likes switching contexts. To that end, we have released a native JIRA plugin which allows you to associate epics , stories , tasks , and bugs to any of Gtmhub OKRs from within JIRA.

Work with OKRs directly from JIRA

Work with OKRs directly from JIRA

All of the JIRA items are automatically synced to Gtmhub, so your colleagues – including those less technically inclined – can see all the effort taking place for any given objective.

Gtmhub rethinks OKRs

When done right – OKRs are incredibly powerful.

The problem, however, is that getting OKRs right is not exactly simple; especially when there are dozens or even hundreds of people involved. This is one of the strengths of Gtmhub – especially when compared to spreadsheets: we remove the “OKRs bureaucracy” out of your way, so you can focus on achieving objectives.

The new objective screens in Gtmhub follow this simple paradigm:

  • Objective

  • Key results

  • Effort

Objective > Key Results > Effort paradigm

Install JIRA plugin for free

We are now making JIRA plugin publicly available, free of charge, to all Gtmhub users.

Here is a short document detailing how to connect JIRA and Gtmhub .

Did this answer your question?