Lesson Objective
Learn to incorporate data into stable work routines using operational dashboards, periodic reviews, and simple governance and learning mechanisms.

By the end of this lesson, the participant will be able to:

  • distinguish between a dashboard as a query panel and a dashboard as a routine tool
  • understand how to organize daily, weekly, or cohort-based reviews
  • recognize the value of decision logs, review rituals, and data ownership
  • understand how visualization design can reinforce a Data Driven culture

From useful dashboard to dashboard integrated into the routine

In Block 2, the focus was on designing more useful dashboards for each profile. At this level, the additional step is that these dashboards are no longer just well-designed tools, but tools integrated into regular work routines.

A panel has little value if no one consults it at the right time, if it is not connected to a conversation, or if it does not lead to decisions.

Review rituals

  • daily review of operational signals
  • weekly review by section or product
  • monthly review of cohorts, retention, or churn
  • tracking of ongoing experiments or activations

The important thing is that data becomes part of a recognizable work cadence, rather than remaining an occasional resource.

Decision logs and accumulated learning

Another valuable practice is documenting decisions, hypotheses, and results. A decision log doesn’t have to be complex. It can simply be a way to document:

  • what was observed
  • what was decided
  • why the decision was made
  • what result it had
  • what was learned

This allows the organization to accumulate learning and avoid relying solely on informal memory.

Data ownership and responsibility

As data becomes more central, it is also important to better define:

  • who owns a metric
  • who validates a definition
  • who updates a taxonomy
  • who reviews a dashboard or alert

Without this minimum responsibility, even good tools can quickly degrade.

Visualization as a support for coordination

At this level, visualization no longer just serves to communicate results. It also helps coordinate teams, set priorities, and sustain regular conversations between different roles.

A good dashboard or monitoring panel helps the newsroom, audience, product, and business teams speak a more shared language.

Try it yourself

Your newsroom has three well-designed, accurate, daily-updated dashboards. The problem: nobody looks at them consistently. The last recorded team review was six weeks ago.

You’ve been asked to fix this — not by rebuilding the dashboards, but by changing how the organisation uses them.

The three dashboards are:

  • Daily operations: Top content by traffic, real-time active users, traffic by sourcex
  • Weekly audience: New vs. returning users, section performance, newsletter results, churn signals
  • Monthly business: Subscriber growth, ARPU, cohort retention, conversion funnel

Consider:

  1. Design a minimum review routine: who reviews each dashboard, how often, and in what format? (Be specific — a weekly standup, a Friday Slack digest, a monthly meeting. What works for each one?)
  2. Pick one dashboard. Write a simple decision log entry after a fictional review. (What was observed · What was decided · Why.)
  3. The monthly dashboard has been showing rising churn for three consecutive months. Nobody acted because there was no defined owner. Who in a typical newsroom should own that signal — and what does “owning it” mean in practice?
  4. What is the real difference between a team that has dashboards and a team that uses them? How would you know which one your newsroom currently is?

Data that isn’t reviewed doesn’t exist. A ritual turns a dashboard into a decision.

Lesson Conslusion
At this stage, being Data Driven means embedding data into routines, roles, and shared practices. Dashboards gain value when they support regular decisions, coordination, and continuous learning across the organization.