The category has converged on the heatmap. Green, amber, red, organized by team or objective. Executive view. Quarterly read-out. Slide-ready.

It is, almost without exception, useless.

What a heatmap actually tells you

That something is off. That's it. A red cell means "this KR is behind." It doesn't tell you:

• Which work item was supposed to move it.
• Whether anyone is actively working on it this week.
• Whether the right person owns it.
• What to start, stop, reassign, or kill.

You can stare at a beautifully designed red square for fifteen minutes and learn nothing actionable. The heatmap is a temperature reading. The reason the patient has a temperature lives one layer down — in the actual work.

Why vendors keep building them anyway

Because heatmaps demo well. They look like clarity. They photograph nicely for a sales deck. And they let an executive feel they have visibility without anyone having to do the hard work of connecting the goal to the work meant to move it.

A red heatmap is the start of a question. Most tools end there.

What "the doctor" looks like

It looks like a system that, when a KR is at risk, can immediately show you:

• The work currently tagged as moving this KR, and its state.
• The owner of the KR and the owners of each work item.
• The work that was meant to move it but stalled, stopped, or got silently re-prioritized.
• The work elsewhere in the company that could be reassigned to move it instead.

That isn't a dashboard. That's an operating layer. It's the thing a Chief of Staff currently rebuilds by hand every Sunday night because no tool does it for them.

The Vindaris position

A heatmap is a fine summary. It is not a strategy execution system. If your tool stops at color-coding, you don't have execution software. You have a thermometer with a nice login page.