1. Build a basic OKR doc

Get started here with a simple doc to run your company's planning.

Now let’s get started with our OKR tutorial. In this first section, we will build a basic but very powerful OKR doc in Coda. At the end of this section, the doc will be ready for OKR use — especially if your team is familiar with OKR planning. The tutorial, we will help you supercharge your doc.

step 1.1⁠

, we will implement the options I recommended for most teams, for example, how to track status and progress. You can easily adjust the recommendation for your own team. To deviate from the tutorial’s OKR doc, you can take a look at my Planning Handbook Part I:

Define the planning output⁠

. That chapter contains many Coda examples, such as how to model a different hierarchy than what is shown in the tutorial. But if you are new to Coda, or new to OKRs, we recommend to follow the tutorial.

Before we dive in, a couple of things to note:

This tutorial assumes no prior knowledge of Coda.

We are building a classic OKR doc,

with high level objectives (in the sense of larger, longer-term company goals).

Example objective: Boost customer satisfaction

and under each objective, there are one or more key results. Those are the individual pieces of work you’ll work on to achieve your objectives. Key results in an OKR framework are typically written as measurable outcomes.

Example key result 1: Increase positive customer reviews by 20% in the next 3 months.

Example key result 2: Reduce customer complaint tickets by 30% in the next quarter.

⁠

1.1 Creating the basic OKR doc Every great doc starts with a great foundation.⁠

⁠

1.2 Adding org structure to the doc If you build your OKR doc for more than one team, you need to model team structure.⁠

⁠

1.3 Creating custom views of your OKRs Use one of Coda's most powerful features to give everyone their own view of the same shared data.⁠

⁠

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.