Information Radiator: Your Team's Public Billboard

THE MENTAL MODEL: An information radiator is a large, highly visible display that passively broadcasts important project information to the entire team and stakeholders. Think of it as a public billboard for your team's health, making key metrics impossible to ignore because they are physically present in your workspace. The information should be simple enough to understand at a glance from across the room.

HOW IT WORKS: The core principle is "out of sight, out of mind." By placing critical information in a high-traffic area, the team maintains a constant, shared awareness of progress, blockers, and quality. These displays are typically large, using physical charts, whiteboards, or digital screens. They are updated frequently—often automatically—to reflect the current state of the project. The information is presented graphically and with minimal text to be absorbed quickly.

WHEN TO USE IT: Information radiators are powerful for co-located teams. Three common examples: first, a physical or digital Kanban board showing the flow of work; second, a large monitor displaying the continuous integration build status (e.g., green for pass, red for fail); and third, a prominent burndown chart tracking work remaining against time. They are excellent for promoting transparency and accountability.

WHEN NOT TO USE IT: They are less effective for fully remote teams unless a digital equivalent is made a central part of the team's virtual workspace. Avoid them for complex data that requires deep analysis; a radiator is for at-a-glance information, not detailed reports. If the information doesn't change often or isn't actionable, it will quickly become background noise and be ignored.

ONE CANONICAL EXAMPLE: A classic information radiator is the CI build monitor. A large TV screen is mounted in the team's area. When a developer commits code, the continuous integration server runs all tests. If all tests pass, the screen is green. If any test fails, the screen turns bright red, often with an accompanying sound. This immediately alerts the entire team that the build is "broken," and it becomes their highest priority to fix it. This simple, binary signal is unambiguous and drives immediate, collective action.