OKR Reporting and Dashboards: Making Progress Visible

Why OKR reporting is more than status updates

Many organizations confuse OKR reporting with status updates: "KR1 is at 65%, KR2 is at 40%." That is not reporting -- those are numbers without context.

Good OKR reporting answers three questions:

1. Where do we stand? (Current progress of all OKRs) 2. Are we on track? (Trend and forecast) 3. What do we need to do? (Action items and decisions)

The difference between reporting and mere tracking is context. A number alone says nothing. A Key Result at 40% can be excellent (if we're only in week 3 of 13) or alarming (if we're in week 11).

OKR dashboards should therefore always show the temporal context: where should we be vs. where are we? Are we above or below the expected trend?

According to a Gartner study (2025), 67% of companies working with OKRs do not use a dedicated reporting tool. They rely on spreadsheets, presentations, or verbal updates. The result: inconsistent data, outdated information, and decisions based on gut feeling rather than facts.

"A dashboard that only shows numbers is a spreadsheet with a pretty interface. A good dashboard tells a story -- and guides toward action."

Dashboard design: The 5 principles of effective OKR dashboards

A good OKR dashboard follows clear design principles. Here are the five most important:

Principle 1: Glanceable

The dashboard must answer the most important question within 10 seconds: "Are we on track?" Use traffic light colors (green/yellow/red), progress bars, and clear trend arrows.

Principle 2: Drill-down capable

The first glance gives the overview. When needed, you must be able to go deeper: from the company level to team OKRs, from team OKRs to individual Key Results, from Key Results to the underlying data.

Principle 3: Context over numbers

Show not just the current value, but also: - The starting value (baseline) - The target value - The expected value at the current point in time - The trend (rising, stagnating, falling)

Principle 4: Action-oriented

Every dashboard element should lead to an action. A red KR is not decoration -- it is a call to action. Connect conspicuous metrics with next steps.

Principle 5: Regularly updated

A dashboard that is only updated monthly is useless for weekly decisions. Aim for real-time data or at least weekly updates.

In Northly, dashboards are automatically updated in real time. Every check-in update flows immediately into the visualization -- without manual maintenance.

"The perfect dashboard is invisible. It delivers the right information at the right time to the right person -- without anyone having to ask."

Key metrics: What belongs on an OKR dashboard?

Not all metrics belong on an OKR dashboard. Too much data confuses more than it helps. Here is a curated selection of the most important OKR metrics:

Progress metrics:

• OKR completion rate: Percentage of OKRs that are on-track (traffic light status)
• Average Key Result progress: Weighted average of all KR progress
• Confidence level: How confident are the teams that they'll achieve their quarterly goals?
• Trend line: How is progress developing across the weeks of the quarter?

Health metrics:

• Check-in completion rate: What percentage of teams conduct regular check-ins?
• Stale OKRs: OKRs that haven't been updated in 2+ weeks
• Alignment coverage: What percentage of team OKRs are linked to company OKRs?

Quality metrics:

• OKR quality score: Average quality rating by the AI Coach
• Ambition level: Distribution of OKR scores (a score average of 1.0 suggests sandbagging)
• Number of OKRs per team: Does it fall within the recommended range of 2-3 Objectives?

The "one-number summary":

For executive leadership, it can be helpful to have a single number that describes the overall health of the OKR program. Northly calculates an OKR Health Score (0-100) that combines progress, engagement, and quality.

Also read our check-in guide for details on the metrics collected during check-ins.

Automatic vs. manual: When automation pays off

One of the most important decisions in OKR reporting: which data is collected automatically, which manually?

Collect automatically:

• Quantitative Key Results with data source connections (e.g., revenue from CRM, traffic from analytics, tickets from the support tool)
• Check-in completion rates (from the OKR tool)
• OKR quality scores (from the AI Coach)
• Alignment overviews (from the Strategy Map)

Collect manually:

• Qualitative Key Results (e.g., "Gathered feedback from 10 customers")
• Confidence levels (personal assessment by team members)
• Context information (Why is a KR behind plan? What are the next steps?)
• Retrospective learnings (qualitative insights)

The automation strategy:

Start with manual check-ins and automate gradually:

Phase 1 (Quarter 1-2): All updates manual. Teams learn the process. Phase 2 (Quarter 3-4): Quantitative KRs are connected to data sources. Manual updates only for qualitative KRs. Phase 3 (Quarter 5+): Full automation where possible. Reports are generated automatically and sent via email.

"Automation is not an end in itself. It pays off when it eliminates manual work without losing the human context."

Northly supports both approaches: manual check-ins for getting started and automated data connections for advanced teams. The real-time analytics combine automatic and manual data into a unified picture.

Executive dashboard vs. team dashboard: Different audiences, different views

Not everyone needs the same dashboard. A CEO has different questions than a team lead. Design your dashboards for specific audiences:

Executive dashboard (C-level / leadership):

Focus: Overview and strategic decisions

Contents: - Company OKR progress at a glance (traffic light status) - OKR Health Score (overall program health) - Top 3 risks (KRs with lowest confidence level) - Cross-team alignment overview - Quarterly trend compared to prior quarters

Update frequency: Weekly, automatic

Team dashboard (team leads / teams):

Focus: Operational progress and blockers

Contents: - All team OKRs with current progress - Check-in history and trends - Blockers and open action items - Alignment with company OKRs - KR details with start, target, and current values

Update frequency: After each check-in (ideally weekly)

Cross-team dashboard (OKR master / agile coaches):

Focus: Program health and adoption

Contents: - Check-in completion rates across all teams - OKR quality distribution - Stale OKR overview - Alignment gaps - Adoption trends

Update frequency: Weekly

In Northly, you can configure separate dashboard views for each audience. The Strategy Map additionally provides a visual alignment overview that is particularly valuable for executive reporting.

"A dashboard for everyone is a dashboard for no one. Each audience needs the information relevant to their decisions."

Reporting rhythm: When and how often to report

The right reporting rhythm depends on the audience and the purpose. Here is a proven cadence:

Weekly: Check-in updates

• Each team updates their Key Results
• Automatic report to team lead and stakeholders
• Format: Short and concise (number + trend + optional comment)

Monthly: Progress report

• Aggregated report across all teams
• For executive leadership and department heads
• Including trends, risks, and action recommendations
• Format: 1-2 page executive summary + dashboard link

Quarterly: Review report

• Comprehensive end-of-quarter report
• Goal achievement, learnings, and recommendations for next quarter
• Format: Presentation in the company review + written report

Automatic alerts:

In addition to regular reporting, set up automatic alerts:

• Stale OKR alert: Notification when an OKR hasn't been updated in 2+ weeks
• Low confidence alert: Notification when a team sets their confidence level to "low"
• Milestone alert: Notification when a Key Result reaches an important milestone

Northly automates this reporting rhythm: weekly digests via email, monthly progress reports, and real-time alerts for critical changes.

Also read our article on AI-powered OKR planning, which explains how automation improves the entire OKR lifecycle.

Conclusion: Reporting as a culture tool

OKR reporting is more than an administrative process. It is a culture tool that promotes transparency, trust, and data-driven decisions.

The key insights:

• Good reporting answers three questions: Where do we stand? Are we on track? What do we need to do?
• Dashboard design follows principles: clarity, drill-down capability, context, action orientation, freshness
• Different audiences need different dashboards
• Automation saves time, but human context remains indispensable
• The reporting rhythm should encompass weekly check-ins, monthly reports, and quarterly reviews

"The best OKR reporting goes unnoticed. It delivers the right information at the right time -- and thereby enables better decisions."

With Northly, you get all reporting capabilities in one place: real-time dashboards, automatic reports, configurable views for different audiences, and the AI Coach that not only helps with OKR creation but also improves reporting quality.

Also read our OKR methodology guide to understand the broader context, and learn how OKRs for remote teams benefit especially from good reporting.