OKRs: Gtmhub vs Spreadsheets

When people start using OKRs, they invariably turn to something simple, which often means Google Sheets or an Excel template.


They assume that an OKRs platform can only help once they master OKRs. It's a common misunderstanding, given the point of good OKR software is to help you along the whole journey.


The reality is that organizations use OKRs and Gtmhub to align and focus on what's important. To achieve that, Gtmhub helps organizations successfully adopt and scale the use of OKRs throughout the enterprise.


There are countless ways Gtmhub beats a generic tool like a spreadsheet, but I'll focus on what I think are the ten most important ones.
 

#1 Visual alignment

Problem: One of the key reasons why anyone adopts OKRs is to drive alignment across the organization. 


The goal is to make sure that everyone in the company understands what needs to be achieved in the big picture context, i.e., how it all comes together. 


The problem with a spreadsheet is that all you get is hundreds or thousands of rows, making it impossible to understand how aligned you are.

Gtmhub Solution: We understand that bringing about alignment is a key use case of OKRs. To that end, we provide multiple ways of visualizing the alignment between objectives. 

Furthermore, you can see how your quarterly (tactical) objectives align with your annual (strategic) objectives. 

Navigating OKRs, isolating specific teams, initiatives, owners, or attainments is also possible – to quickly find what can be improved.
 

The Gtmhub alignment view

#2 Focus vs information overload

Problem: Aside from alignment, the second most important benefit of OKRs is bringing about focus. During the quarter or year, we all get distracted by countless tasks, meetings, and initiatives – this is where OKRs keep us focused on what's really important. 

The problem with spreadsheets, especially in larger organizations, is that it's hard to keep focus when OKRs appear as hundreds, if not thousands, in extreme cases, tens of thousands of rows.

Gtmhub solution: To solve the information overload, Gtmhub provides functionality called The Hub. While there are situations when you need to see other OKRs and how they align, most of the time, you only need relevant OKRs in front of you.

Relevant OKRs are your OKRs, OKRs of your team, OKRs where you own the key result (number) or where you are expected to complete a task.

The Hub: Only the relevant OKRs

#3 Automation

Problem: OKRs, like most other processes, die from neglect. 

There is no value in having OKRs if you don't keep track of the progress; correct the course where necessary; divert resources and in general, manage your organization based on the attainment of the targets.

What happens to most of OKRs in spreadsheets (and elsewhere) is that they are set at the beginning of the quarter and then updated at the end of the quarter, when for all intents and purposes it's too late.

Gtmhub Solution: The vast majority of data being tracked for OKRs is already available in the organization. In Salesforce, Jira, Google Analytics, Spreadsheets (!), databases, and whatnot. 

To remove the mind-numbing need to copy & paste this data on a weekly basis, Gtmhub connects to 150+ business systems and automatically updates progress in real-time. 

If your KR is to increase the number of leads – we can get this data from Salesforce (or Hubspot, Base, etc., etc.). 

If you are trying to reduce the first response to a ticket, we can get this from Zendesk. 

If you are… well, you get the picture.

Automating OKRs through built-in data sources

#4 Reporting & Analytics

Problem: If a tree falls in a forest and no one is around to hear it, does it make a sound?

If you are running your OKRs in a spreadsheet, it will cause you a lot of anxiety. At any given moment, do you know how well are you doing as an organization? As a team? What OKRs are at risk? Which teams don't have OKRs? Is progress being made?

Spending a ton of time to adopt OKRs only to be no better off in understanding what's going on is as frustrating as it is futile.

Gtmhub Solution: Seeing the high-level picture, both on the OKR attainment and also on the OKR process, is crucial to quickly identify areas of improvement. 

In addition to seeing the key figures, you can slice and dice those by initiatives and teams; so you can compare perhaps how well is the marketing team doing vs the sales team. Once you identify the problems, you can then drill down into details and take action.

A high-level overview of OKRs

#5 Process design

Problem: The best and worst thing about spreadsheets is that they are free form. You can do anything you please in a spreadsheet; the same applies to the thousands of your colleagues.

OKRs are fundamentally a process – the way you and your teammates will achieve goals. Agreeing on how this process should look and then enforcing it in a spreadsheet is akin to herding cats. 

For example, how many objectives should a person own? What's considered good attainment? Will you use numbers or color-coding? How often should check-ins be made? The list goes on and on.

Gtmhub solution: At Gtmhub, we understood early on that to successfully run OKRs at scale, establishing and enforcing rules is necessary. Because rules differ from organization to organization, so we ensure clients can make their own custom rules. But make no mistake - rules have to exist – otherwise, everyone is wasting their time.

Here are just some of the numerous settings that you can define in Gtmhub:

  • how long is your planning period (quarter? 6 weeks?)
  • when is the deadline to check-in progress?
  • what are the grading scales (numbers, colors, emojis?)
  • what kind of notifications should users receive?

Defining the OKRs check-in cadence in Gtmhub

#6 Permissions

Problem: While it is true that OKRs are about transparency, there are cases when either for legal or compliance reasons, it's necessary to limit access to some OKRs. For example, the CFO objectives in a publicly-traded company, or the need for privacy when dealing with an individual's personal objective.

This is basically impossible to do in a spreadsheet - aside from having multiple files. But that creates more problems than it solves.

Gtmhub solution: Gtmhub organizes OKRs in planning sessions; time-bound collections of OKRs. Planning sessions can be protected by permissions granted either to individual users or groups of users. In addition, Gtmhub has a concept of a "private OKR", which will be seen only by the manager of the OKR owner.

Defining access level permissions for an individual user

#7 Progress tracking

Problem: When you update your key results in the spreadsheet, the only thing everyone sees is a number. There will be no trend, no context, no plan.

Knowing how a key result was trending over time and the infliction points is crucial for the learning process.

Gtmhub solution: At Gtmhub, we record every single change to a key result with a comment on what happened. This gives everyone insight into what were the key actions which resulted in progress.

Key result progress over time 

 

 

#8 Security

Problem: OKRs contain some of the most important data any organization will have, including targets and progress data on everything a company wants to achieve. 

Storing such data in a file that goes back and forth in email, slack, or Dropbox without any idea who is accessing it, who is changing it… well, is risky at best, and may actually be illegal (GDPR, personal information, insider information…).

Gtmhub Solution: Unlike with a file that is downloaded, access to Gtmhub can be revoked (through Gtmhub or SSO solution). Furthermore, Gtmhub employs three layers of firewalls, full end-to-end encryption at rest and in transit, geographical isolation, indefinite backups, full access logs…

#9 Collaboration

Problem: Alignment comes from people working together, giving different perspectives, and jointly pushing towards the desired outcome. To do this effectively, one needs a way to communicate and keep track of past conversations. While this is possible in a spreadsheet, we've all come to hate paragraphs of text within a cell.

Gtmhub Solution: We provide a way for people to communicate right within the context of an OKR. One can use mentions to involve more colleagues, and all of this always follows an OKR.

#10 Bonus: Approval Workflow

Approval Workflow is a bonus use case, as it is still not available – but we will release it in Q2 2019.

Problem: At the beginning of the planning period, when OKRs are being set, people need to sync on what's important and the appropriate targets. Doing this in a spreadsheet is organizational mayhem.

Larger organizations will have multiple offices, often in different time zones. Getting the entire organization to plan synchronously in a week or two is basically impossible. The end result of this is usually one of the two: a) complete chaos and anarchy or b) everyone is six weeks late with their OKRs.

Gtmhub Solution: In Q2 we will release an Approval Workflow for defining OKRs. This feature aims to streamline the communication and negotiation of OKRs between various stakeholders. By making the entire process asynchronous, we expect to allow even the largest organizations to finalize their OKRs within one week.

Final words

Running OKRs in a spreadsheet is signaling to your organization that OKRs are not that important. Your sales team is using Salesforce, your engineering team is using Jira, your finance team is using Xero, your HR team is using Workday… by using a DIY, IKEA-like solution for OKRs you are sabotaging the process from the get-go.

Even if your team somehow buys in, you are making it unnecessarily complex for them. Instead of working on achieving objectives, people will be spending significant time figuring out just how to do a common task within that spreadsheet.

In the end – spreadsheets will create so much friction that your organization will fail at OKRs.

Achieving results is what it's what's all about. Right?

Image source: rawpixel.com