September 7, 2026 · 8 min read
TL;DR: Boards, dashboards and information radiators are keyed 10 times and wrong 20 times across the bank. The keyed ten all answer the same complaint: people cannot see the state of the work. The twenty distractors offer visibility for a problem that is about something else, and the exam lists that something else in the stem: missing content, poor quality, a need for interaction, a stakeholder's false belief.
Visual management is a real agile practice with a real place in the exam. The bank offers it as the wrong answer twice as often as the right one, and the discriminator is not whether a board would be nice to have. It is whether the stem describes a visibility problem.
When the scenario says, in some form, that people cannot see what is going on.
Stakeholders on an agile delivery complain they cannot tell who is working on what or how far anything has got. Keyed, as a pair, is putting the work on a kanban board and holding a daily stand-up that walks it. Both complaints are about visibility, and a board plus a daily walk makes assignments and progress visible without adding any reporting.
A business representative asks how many defects turned up in the latest testing round, and the project manager does not have the number memorised. Keyed is walking them to the team area where the information radiator displays it. Promising to email the figure later delays an answer that is already on display. Sending them to the scrum master puts a person in front of information that is meant to be transparent.
A functional manager running a waterfall project wants agile tools that expose problems before they happen. Keyed is putting the product backlog, the kanban board and the velocity chart on display in a co-located team area. Writing a change into the project management plan documents an intention but exposes nothing.
A hybrid project's agile and predictive teams have drifted out of alignment. Keyed, as a pair, is a common kanban board that tracks both teams' deliverables and a single set of milestones and dependencies. A team burned by executives who used velocity to push them faster is offered flow-based scheduling with a kanban board, and it keys. And when a project manager takes over an agile project with a great deal of information to reach a wide stakeholder group, the communication approach that fits the delivery method is frequent, transparent communication built around an information radiator, not written status reports on a schedule.
One keyed item is worth reading twice. An ESG dashboard reports a project's completion percentage under the heading of a group-wide commitment, and operations staff have started describing the commitment itself as forty per cent met. The keyed answer changes the dashboard so the project reports categories verified out of eleven, shown separately from the group commitment. Adding a note beneath the percentage loses, because the headline is what gets quoted. The dashboard is keyed here because the dashboard is what is doing the misleading.
When the stem names a problem that visibility does not touch: missing content, poor quality, a need for interaction, or a stakeholder's false belief.
The problem is content. An operations director says the updates lack specifics on adoption rates and user feedback. Standing up an interactive dashboard is offered and loses to tailoring the updates to include those metrics. The explanation is exact: the dashboard changes the channel and leaves the content problem intact if adoption metrics are not among the measures it exposes, and it shifts the work of finding the answer onto a director who has just said they are not getting it.
The problem is quality. Product quality has been poor for several sprints. Displaying the kanban board in the war room for transparency is offered and loses to test-driven development, which attacks defects at the point where they are created.
The problem is interaction. A supplier's team works from its own site and the project manager cannot attend its daily stand-up. A shared electronic kanban board is offered and loses to a scrum of scrums, because a board shares information without the interaction the question asks for. A government department requires a remote team's workstations and board to be visible at all times. Monitors displaying information radiators lose to fishbowl windows left open all day, because monitors serve the room they stand in.
The problem is a belief. A client-services director is quoting halved turnaround times from demonstrations that only ever showed the content an AI tool handles well. Publishing quality scores by content type on the delivery team's dashboard is offered and loses to drawing each demonstration from the live job mix, because the dashboard reports to the delivery team rather than to the person quoting the times.
Common trap: using a board to say something a board should never say. When every impediment traces to one department head who has already been asked and refuses, publishing an information radiator that ranks stakeholders by how actively they support the project is offered. It loses, and the explanation calls it what it is: publicly ranking stakeholders humiliates a colleague the project still depends on. Radiators show the state of the work. The bank never keys one that shows the state of a person.
Each tool answers one question at one horizon, and the bank's distractors offer a tool at the wrong horizon.
| Tool | What it answers | Where the bank offers it wrongly |
|---|---|---|
| Kanban board | The state of today's work, where it is blocked | As a forecast of whether the release will finish on time |
| Iteration burndown | Work remaining in this iteration | As a big-picture view for a sponsor |
| Feature burn-up, cumulative flow diagram | Release-level done versus remaining | Rarely; these are the keyed sponsor tools |
| Information radiator | Current data anyone can read without asking | As a fix for version confusion, which needs the PMIS |
| Dashboard | Figures on demand for the people who want them | As a fix for missing content or a stakeholder's false belief |
The forecast row is the one that catches candidates. A sponsor midway through an agile project asks whether it will finish on time. Looking over the kanban board and current work in progress is offered and loses to reviewing velocity, the product burndown and other KPIs. The board shows the state of today and says nothing about how many iterations remain. When a sponsor wants the big picture of implemented versus outstanding, the keyed pair is the cumulative flow diagram and the feature burn-up, and the kanban board is one of the two distractors.
And the tool is never the point. A business representative is put off by a whiteboard and sticky notes on a high-profile technology project. Promising a software-based board to avoid the embarrassment loses. The keyed answer explains that the team is applying visual management, and the explanation notes that an electronic board is only as current as the last person who remembered to update it. Every one of these thirty options is explained in the bank rather than just marked right or wrong, and that is what turns a list of tools into a decision rule.
When is an information radiator the keyed answer on the PMP exam? When the problem is visibility: stakeholders cannot tell who is working on what, a business representative asks for a figure that is already on display, two teams are drifting out of step, or a manager wants problems exposed before they bite. The board makes current information ambient.
When is a dashboard the wrong answer? When the complaint is about content rather than access. A director who says the updates lack adoption metrics needs the metrics added to what is sent; a dashboard changes the channel and leaves the missing content missing, while shifting the work of finding the answer onto the person who asked.
Is a whiteboard with sticky notes acceptable on a high-profile technology project? Yes. The bank keys explaining that the team is applying visual management. Low-tech, high-touch tools are a deliberate choice: the board is always current, anyone can read it without logging in, and changing it costs seconds.
Can a kanban board tell a sponsor whether the release will finish on time? No. It shows the state of today's work. A forecast needs a rate and a remaining quantity, which is velocity and the product burndown, or throughput on a flow-based team.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Kanban as a System: WIP Limits, Pull, and Finding the Real Bottleneck and Status Reporting on the PMP Exam: What the Report Is For, and Who It Is For. Communication tasks are mapped on the People domain study page.
When is an information radiator the keyed answer on the PMP exam?
When the problem is visibility: stakeholders cannot tell who is working on what, a business representative asks for a figure that is already on display, two teams are drifting out of step, or a manager wants problems exposed before they bite. The board makes current information ambient.
When is a dashboard the wrong answer?
When the complaint is about content rather than access. A director who says the updates lack adoption metrics needs the metrics added to what is sent; a dashboard changes the channel and leaves the missing content missing, while shifting the work of finding the answer onto the person who asked.
Is a whiteboard with sticky notes acceptable on a high-profile technology project?
Yes. The bank keys explaining that the team is applying visual management. Low-tech, high-touch tools are a deliberate choice: the board is always current, anyone can read it without logging in, and changing it costs seconds.