Getting Started With OKRs: Your First Two Weeks

Most OKR rollouts fail in the first month, not the first year. The organization signs up, reads about the framework, writes twelve Objectives in one afternoon, and then nobody looks at them again. The fix is not more theory. It is a smaller start and a clear plan for the first two weeks. This guide is that plan. It is the first of three short guides for organizations that are new to OKRs.

Start Smaller Than You Think

Pick one group to start with. For a small organization that is usually the leadership team. For a larger one it is a single team with a leader who actually wants to try this. Do not roll OKRs out to everyone at once. Too many people learning a new habit at the same time means too many mistakes happening in parallel, with no example of what good looks like.

Then limit the scope even further. One Objective. Two or three Key Results. That is enough to learn the language and the rhythm. Google's own guidance in re:Work's guide to setting goals with OKRs makes the same point: fewer, clearer goals beat a long list every time.

Week One: Write One Objective and Its Key Results

Block one hour with the group you picked. Ask a single question: if we could improve only one thing in the next three months, what would matter most? The answer becomes your Objective. Write it as an outcome, not a task. "Customers get answers faster" is an Objective. "Set up a help desk" is a task that might help you get there.

Next, ask how you would know it worked. Each answer that can be measured is a candidate Key Result. Keep two or three. Give each one a starting value and a target value. If you cannot measure it today, that is fine. Write down how you will measure it and start from zero.

If the group gets stuck, our help center article on getting started walks through this first session step by step, and the posts on writing strong Objectives and making Key Results measurable cover the two most common sticking points.

Decide Who Owns What

Every Key Result needs one named owner. Not a team, not a department. One person who will update the number and speak to it in the check-in. Ownership does not mean doing all the work. It means knowing where the number stands and raising a flag when it drifts.

Also name one person who owns the process itself. In the first weeks that is usually you, the person who set up the organization. Your job is simple: make sure the check-in happens and that people update their numbers before it.

Week Two: Hold the First Check-in

A check-in is a short meeting, fifteen minutes at most, where each owner says three things: where the Key Result stands, how confident they are about reaching the target, and what is in the way. That is all. No slides, no long status reports. Research on goal setting by Locke and Latham has shown for decades that regular feedback on progress is one of the strongest drivers of goal achievement. The check-in is where that feedback happens.

Put the first check-in in the calendar before you leave the week one session. Pick a fixed day and time and keep it weekly. A goal that is reviewed every week stays real. A goal that is reviewed at the end of the quarter is a wish.

Use the Examples, Then Replace Them

If you seeded Easy OKR with example content when you registered, you already have a sample Objective with Key Results that match your type of organization. Use it to learn how the app works: open a Key Result, submit a check-in, look at the progress view. Then archive the examples and replace them with your own. Examples are training wheels. Do not ride on them for a full quarter.

Mistakes to Avoid in the First Two Weeks

Writing too many OKRs is the most common one. If you have more than three Objectives in your first cycle, cut. Treating Key Results as a to-do list is the second. A Key Result measures a result. If it reads like a task, move it to your activities list instead. Skipping the check-in "just this week" is the third, and it is the one that quietly kills the whole effort. The first missed check-in is rarely the last.

Finally, do not aim for perfect wording. Your first Objective will be a little vague. Your first Key Results will be a little off. That is expected. In the words of John Doerr's Measure What Matters, OKRs are a learning system. You get better by running the cycle, not by polishing the draft.

What Comes Next

After two weeks you will have one Objective, two or three measured Key Results, a named owner for each, and one check-in behind you. That is a real start. The next step is to give OKRs a permanent home in your organization: roles, a cycle length, and a simple routine. That is the topic of the next guide in this series: How to Organize OKRs Inside Your Organization.

References

• Set Goals with OKRs — Google re:Work
• Building a Practically Useful Theory of Goal Setting and Task Motivation — American Psychological Association
• John Doerr, Measure What Matters (Portfolio, 2018)