Advanced OKR and KPI tracking in Notion

A Notion-based OKR system can turn project planning into measurable outcomes by linking goals (OKRs) to KPIs and then tracking KPI results over time—complete with an automatically calculated “current value” and capped progress percentage. The payoff is practical: teams can see whether work is actually moving key metrics, not just whether tasks are being completed.

The workflow starts by adding an “OKR” property to every project using a select field that maps initiatives to time windows (e.g., “2023 Q1,” “2023 Q2,” etc.). Once projects carry an OKR quarter label, custom views can filter and display what’s “in progress” for each quarter, making it clear what the organization is prioritizing across the year. For example, content creation projects can be assigned to a specific quarter initiative, while other projects like a book-writing effort can be placed into a different quarter. This creates a simple but powerful way to group work by when it’s meant to land.

Next comes KPI tracking. Each project gets a set of KPIs—metrics like YouTube views, click-through rate, or monetized revenue for a video project, and waitlist signups or purchases for a book project. To keep the system flexible, KPIs live in a dedicated database. Each KPI record relates back to a single project and stores three core fields: a KPI name, a starting value (“from”), and a target value (“to”), with units (e.g., views, %, pounds) used to clarify what the numbers mean. Projects then display their KPIs via a linked view (and can be arranged as boards or other layouts).

The system becomes truly “OKR-like” when it adds KPI results over time. A second database records performance snapshots: each entry includes a date, a numeric value, and a relation back to the KPI being measured. KPI records then roll up those historical results to compute a “current value.” Because rollups can return multiple values, the setup uses a formula trick to extract the latest entry (the last value in the comma-separated list) so the project always shows the most recent performance.

Finally, a progress formula converts the current value into a percentage between the starting and target values. The calculation subtracts the starting value from the current value, divides by the target range (target minus start), multiplies by 100, and then caps the result so it stays between 0% and 100% even if performance dips or overshoots. That capped progress is what powers clean visualizations and makes the system honest.

At the project level, KPIs appear as “cards” (e.g., in a gallery view) showing current value, start, target, and progress. When progress stalls—say click-through rate isn’t improving—the workflow ties the measurement back to action: identify the tasks needed to move the KPI (like changing a video title or thumbnail), then plan those tasks into the existing task system. The result is a feedback loop where iteration is driven by metrics, not guesswork.