Information Radiator

What is an Information Radiator?

An information radiator is a large, prominently placed display, such as a task board, burndown chart or build monitor, that shows a team's current status to anyone passing by. Alistair Cockburn coined the term in 2001.

Updated November 2026 · 3 min read


An information radiator is a large, highly visible display that shows a team's current status, such as work in progress, build health or progress toward a goal, in a place where anyone walking by can read it at a glance. The point is that information comes to people without anyone having to ask for it, open a tool or attend a meeting.

The term was coined by Alistair Cockburn in Agile Software Development (2001), and the idea overlaps with the "big visible charts" that Kent Beck described in Extreme Programming Explained (1999). It also echoes visual management in lean manufacturing, where status boards and andon lights make problems on the shop floor obvious. Today many radiators are wall-mounted screens or shared dashboards rather than paper, but the principle is the same.

Common types of information radiators

RadiatorWhat it showsQuestion it answers
Task or Kanban boardWork items by statusWhat is everyone working on, and what is stuck?
Burndown chartRemaining work over the sprintAre we on track to finish?
Build or deployment statusWhether the main branch is passingIs it safe to merge and release?
Service health dashboardError rates, latency, uptimeAre users affected right now?
Goal or OKR trackerProgress against a quarterly targetAre we moving the metric that matters?
Team agreementsWorking norms, definition of doneHow have we agreed to work?

What makes a good information radiator

  • Readable from a distance. Large text and simple visuals; a passer-by should get the message in a few seconds.
  • Current. Updated automatically or as part of daily work. A stale radiator is worse than none because it misleads.
  • Focused. Shows a few things that drive action, not every available metric.
  • Honest. Makes bad news as visible as good news, so problems get attention early.
  • Owned by the team. The team chooses what to show and changes it as its questions change.

The opposite is sometimes called an information refrigerator: data that exists but is locked inside a tool or report that people must go looking for.

How to set up an information radiator

  1. Start with a question. Decide what the team or its stakeholders most need to know without asking.
  2. Choose the display. A physical board for colocated teams, a wall screen for an office, or a pinned shared dashboard for distributed teams.
  3. Automate the data. Pull status from the work tracker, CI system or monitoring tools so it stays fresh.
  4. Put it where people look. Next to the team area, in the standup space or at the top of the team channel.
  5. Review it regularly. In retrospectives, ask whether the radiator still changes behavior. Remove what nobody uses.

Information radiator example

Consider a hypothetical engineering team whose main branch often stays broken for hours because nobody notices failed builds in the CI tool. Over one month, broken builds took an average of 4 hours to fix. The team mounts a screen in its area showing the main-branch status in large green or red text, along with the name of the last person to merge. Over the next month, the average time to fix a broken build drops to 45 minutes, and the team adds a second panel showing its sprint burndown, which it now reviews during the daily standup.

Common pitfalls

  • Dashboard overload. A screen with 30 charts is ignored. Fewer, bigger signals work better.
  • Manual updates that lapse. If someone must remember to update it, it will drift out of date.
  • Using it to monitor individuals. Radiators that rank or expose individual performance make people game the numbers.
  • Showing only vanity metrics. Numbers that only ever go up do not prompt decisions.

Information radiators are a practical form of transparency in Kanban and Scrum teams. They overlap with dashboards and agile metrics, with the difference that a radiator is placed to be seen without being sought out.

Frequently asked questions

What are examples of information radiators?

Common information radiators include Kanban or task boards, burndown charts, build and deployment status screens, service health dashboards, goal or OKR trackers and posted team agreements. Each answers one question at a glance, such as whether the team is on track or whether it is safe to release. They can be physical boards or wall-mounted screens.

What is the difference between an information radiator and a dashboard?

An information radiator is placed to be seen without anyone looking for it, such as a screen in the team area or a board by the standup space. A dashboard usually lives inside a tool that people must open. Data hidden away like that is sometimes called an information refrigerator. See dashboard.

How do you keep an information radiator useful?

Keep an information radiator useful by automating its data so it never goes stale, limiting it to a few large signals and making bad news as visible as good news. Let the team decide what it shows and review it in retrospectives, removing anything nobody acts on. Avoid ranking individuals, which pushes people to game the numbers.