What to Communicate When Introducing OKRs

You can have the right Objectives, a clean process and a good tool, and still watch OKRs fail because of how they were announced. People hear "new goal framework" and translate it to "more reporting" or "a new way to be measured". The way you communicate in the first weeks sets that story. This is the third and final guide in our getting started series. The first covered your first two weeks and the second covered how to organize OKRs internally. This one is about what to say.

Start With Why, Not With the Framework

Nobody cares about OKRs. People care about the problem OKRs are meant to solve. Maybe priorities keep changing. Maybe teams work hard but pull in different directions. Maybe nobody knows what leadership actually wants this quarter. Name that problem first, in plain words. Then introduce OKRs as the way you are going to address it. John Kotter's classic Harvard Business Review article, Leading Change: Why Transformation Efforts Fail, puts under-communicating the vision near the top of the list of reasons change efforts stall. The why has to come from you, and it has to come first.

Say What Changes, and What Does Not

Be concrete about what people will experience. "We will pick one Objective per team each quarter. Each Key Result has one owner. We meet for fifteen minutes every week to look at the numbers." That is a change people can picture. Then say what does not change: their role, their manager, their day-to-day tools. Uncertainty about what is not changing causes more anxiety than the change itself.

Also say what you are not doing. You are not adding a new layer of reporting. You are not replacing existing plans overnight. You are starting with one team and learning. Framing the first cycle as a pilot lowers the stakes and makes it easier for people to point out what is not working.

Be Clear About Performance Reviews

This is the question everyone has and few will ask out loud: will my OKR results affect my review, my bonus, my job? Answer it before it is asked. The standard advice, and the one we recommend, is that OKRs are a tool for focus and learning, not a performance rating. Ambitious targets only work when missing them is safe. If you tie OKR scores to pay, people will set targets they know they can hit, and you lose the whole point. If your organization does want a link to performance, say exactly what it is. A vague answer is worse than an honest one you disagree with.

Set Expectations About Transparency

OKRs work best when everyone can see everyone's goals, including leadership's. Tell people that up front, because it is a real change for many organizations. Explain why: shared visibility is what lets teams align themselves without extra meetings. Also explain what visibility means in practice. A red Key Result is information, not an accusation. The first time someone reports an honest red and gets thanked for it instead of grilled, the message lands. The first time someone gets punished for it, it is over. Our post on the transparency paradox goes deeper on this.

A Kickoff Message You Can Adapt

Keep the kickoff message short and send it from the most senior person involved. It should cover five things, in this order. First, the problem: "We have too many priorities and not enough clarity on which ones matter most." Second, the decision: "Starting this quarter, the leadership team will set one Objective with three Key Results, and we will share them with everyone." Third, what it means for the reader: "You will be able to see these goals in Easy OKR. Over the next months we will invite more teams to set their own." Fourth, the routine: "We meet every Monday for fifteen minutes to look at progress." Fifth, the guardrail: "This is not a performance review. We expect to miss some targets and to learn from that." Then invite questions and name the person to ask.

Send it in the channel your organization actually reads. Follow up in person or on a call within a week. One message is never enough. Kotter's rule of thumb is that leaders under-communicate by a factor of ten. Plan to repeat the core message in every check-in and every review for the first cycle.

Involve People Before You Announce

The best communication is a conversation that happened before the announcement. If the team whose OKRs you are announcing helped write them, the message becomes "here is what we decided together" rather than "here is what you are now measured on". Research reported by SHRM on collaborative goal setting finds that goals employees help shape earn stronger commitment than goals handed down. Book the planning session first, then write the announcement.

What to Say at the First Check-in

The first check-in sets the tone for every one after it. Open by repeating the purpose in one sentence: "We are here to see where the numbers stand and what is in the way, not to explain ourselves." Model the behavior you want. If your own Key Result is behind, say so plainly and say what you will try next. Thank the first person who flags a blocker. Close on time. A check-in that runs long teaches people that it is a status meeting in disguise.

What to Say at the First Review

At the end of the first cycle, resist the urge to declare victory or failure. Report the results honestly, then spend most of the time on what you learned: about the Objective, about how you measured it, and about the process. Announce the two or three changes you will make next cycle. Then say clearly whether and how you will expand OKRs to more teams. People are watching to see if this was a one-off. Telling them what happens next is how you show it was not.

Repeat Yourself

The message that OKRs are about focus, learning and shared direction has to be said many more times than feels natural. Say it in the kickoff. Say it in the check-ins. Say it when someone reports a red. Say it when you welcome a new employee who was not there for the kickoff. As John Doerr writes in Measure What Matters, OKRs are a communication system as much as a goal system. Treat them that way from the first message, and the framework has a chance to become part of how your organization works rather than another initiative that quietly faded.

References

• Leading Change: Why Transformation Efforts Fail — Harvard Business Review
• Managers Can Add Collaboration to Goal-Setting for Stronger Teams — SHRM
• John Doerr, Measure What Matters (Portfolio, 2018)