Notion at Work: Achieve Your Goals

TL;DR

Model OKRs in Notion using master databases for Areas, Quarters, Objectives, and Key Results, then connect them with relations.

Briefing Cornell Notes

Briefing

OKRs in Notion are built as a connected system of master databases—areas, quarters, objectives, and key results—so progress updates automatically and teams can review outcomes with structured “lessons learned.” The core idea is to treat objectives and their measurable key results as data: relations link them to time periods and organizational categories, roll-ups compute progress percentages, and linked views present the right slice of information for dashboards, quarterly planning, and ongoing accountability.

The framework starts with a quick OKR refresher: objectives are qualitative, ambitious goals meant to land around a ~70% achievement rate, while key results are 2–5 measurable indicators that track progress toward each objective. Those key results become the measurable backbone of the system. Instead of manually updating status, the Notion setup calculates progress by dividing each key result’s current value by its target value, then rolls those percentages up to the objective level (average across related key results) and again to the quarter level (average across related objectives).

A central Notion “data page” holds the master databases. The build begins with an Areas database (renaming the title property to “area”), which acts as a high-level categorization layer for teams, departments, or clients. Next comes a Quarters database (renaming title to “quarter”), with a “timespan” date property and a “reflections” text field for recording what was learned. A formula-based “active” checkbox marks which quarter is currently in effect by checking whether today’s date falls within each quarter’s timespan; that hidden flag powers filtered views without cluttering the interface.

Objectives and key results are then modeled as separate databases. Objectives include a “reflections” text property. Key results include numeric “current value” and “target value” fields plus a formula “progress” percentage. Because Notion formulas can produce messy decimals, the system uses a rounding workaround (multiply by 100, round, then divide by 100) to keep percentages readable. Relations connect objectives to areas and quarters, and objectives to their key results. Roll-ups then compute objective progress (average of related key result progress) and quarter progress (average of related objective progress). An additional roll-up pulls the quarter’s “active” status into objectives so dashboards can show only what matters right now.

The second half of the system focuses on usability: templates and linked views. A “new quarter” template creates an inner quarter page with a linked database view of only the objectives belonging to that quarter, formatted as a gallery with progress shown per objective. Similarly, a “new objective” template creates an inner objective page with a linked database view of only that objective’s key results, using a list/table layout that makes updating “current value” straightforward. Finally, a gateway-style home view (and optional area/quarter views) filters objectives to the active quarter and active area, using the roll-up-driven logic.

To close the loop, reflections are treated as first-class fields. The system recommends a dedicated reflection page that aggregates quarterly and objective records in editable tables, where teams document why targets were missed or achieved—so future OKRs can be shaped by what actually happened. The result is an OKR workflow that’s measurable, time-aware, and reviewable, with automation doing the status math and templates doing the presentation work.

Cornell Notes

The OKR system in Notion is designed around master databases and automated calculations. Objectives link to Areas and Quarters, while each objective links to multiple Key Results. A formula computes key result progress as current value divided by target value (rounded for readability), then roll-ups average key result progress into objective progress and objective progress into quarter progress. A formula-driven “active” checkbox in the Quarters database marks the current quarter based on today’s date, enabling filtered dashboards that always show the right slice of work. Templates (“new quarter” and “new objective”) create inner pages with linked, automatically filtered views, and “reflections” fields capture lessons learned to improve future OKRs.

How does the system turn qualitative objectives into something trackable without manual status updates?

Each objective is paired with measurable key results. Key results store numeric “current value” and “target value,” and a formula calculates “progress” as current ÷ target. Relations connect key results to their objective, and a roll-up averages the related key result progress to produce an objective-level progress percentage. That objective progress then rolls up again to the quarter level by averaging the progress of objectives tied to the quarter.

What role does the Quarters database play beyond just labeling time periods?

Quarters is the time engine. It includes a “timespan” date property and a formula-based “active” checkbox that checks whether today’s date falls within each quarter’s timespan. That “active” flag can be hidden but still used for filtering. The setup also adds a “reflections” text property so lessons learned can be recorded per quarter, and a “time span” roll-up is used to support chronological sorting in views.

Why does the build separate Areas, Objectives, Key Results, and Quarters into different databases?

Separation makes relations and roll-ups reliable. Areas provides a high-level category layer (teams, departments, or clients). Objectives represent the qualitative goal and store objective-level “reflections.” Key Results hold the measurable metrics and progress formula. Quarters provides the time context. With this structure, Notion can automatically compute progress and generate filtered linked views (e.g., “active quarter objectives” or “objectives for a specific quarter”) without duplicating data.

How are progress percentages kept readable in Notion formulas?

The raw progress calculation can produce long decimals. The system uses a rounding workaround: multiply the computed ratio by 100, apply round, then divide by 100. This yields clean percentage values for both key results and roll-up outputs, which also makes progress bars and card displays easier to interpret.

How do templates make the system scalable when new quarters or objectives are created?

A “new quarter” template creates an inner quarter page containing a linked database view of objectives filtered to only those related to that specific quarter template instance. It also formats the view as a gallery and adjusts card preview settings for a cleaner layout. A “new objective” template similarly creates an inner objective page with a linked view of key results filtered to only those tied to that objective. This means new records automatically get the correct sub-pages and filtered lists without rebuilding views each time.

How does the system ensure learning carries forward after OKRs end?

Both quarters and objectives include “reflections” text properties. The recommended workflow is to maintain a reflection page that aggregates quarter and objective records in table views, so teams can document why targets were missed or what drove success. Those notes then inform how future objectives and key results are set, aligning planning with real outcomes.

Review Questions

If key result progress is computed as current ÷ target, what roll-up method is used to derive objective progress, and why does that choice matter?
Where does the “active” checkbox come from, and how does it drive filtered dashboards across the workspace?
What is the purpose of using templates for “new quarter” and “new objective,” and what specific linked views do they generate?

Key Points

1
Model OKRs in Notion using master databases for Areas, Quarters, Objectives, and Key Results, then connect them with relations.
2
Compute key result progress with a formula (current value divided by target value) and round to keep percentages readable.
3
Use roll-ups to average key result progress into objective progress, and average objective progress into quarter progress.
4
Create a formula-driven “active” quarter flag based on today’s date within each quarter’s timespan to power always-current filtered views.
5
Use templates (“new quarter” and “new objective”) to generate inner pages with linked, automatically filtered views for objectives and key results.
6
Store “reflections” at both the quarter and objective levels, and aggregate them in a reflection page to capture lessons learned for future OKRs.

Highlights

Progress becomes automatic: key result percentages roll up into objective progress and then into quarter progress via relations and roll-ups.

A hidden “active” checkbox in the Quarters database marks the current quarter using a date-range formula, enabling dashboards that stay current.

Templates eliminate repetitive setup by generating quarter and objective pages with linked databases filtered to the correct records.

Reflections are treated as structured fields (quarter and objective), turning OKR reviews into reusable organizational learning. 

Topics

Mentioned

William Nutt
OKRs

Notion at Work: Achieve Your Goals - OKRs in Notion