agile3
Practices & Events

Information Radiators

Big, visible displays of a team's key information that anyone passing by can read at a glance.

2 min read · Practitioner

In 30 seconds

  • Information that radiates to anyone nearby, without asking.
  • Examples: task boards, burndown charts, build status screens.
  • Keep them few, current and easy to read.

The idea

Alistair Cockburn coined the term. Instead of hiding information in tools only some people open, display it where everyone sees it daily. These displays are also called big visible charts.

Common examples

What makes a good one

  • Readable from a distance or at a glance
  • Always current, ideally updated automatically
  • Shows what the team actually uses to decide

Remote teams use a shared dashboard pinned in their main channel.

Myth vs reality

Myth · More charts means more transparency.
Reality · Too many radiators become wallpaper.
Myth · Radiators are for managers.
Reality · They're mainly for the team.
Myth · Digital tools make them unnecessary.
Reality · Tools hide information unless someone looks.

FAQ

What's an information refrigerator?

Information stored where you must go looking for it, the opposite of a radiator.

How many radiators should a team have?

A handful at most.

Who maintains them?

The team, preferably with automation.