The sequence is so common it has a rhythm. Week three: all green. Week six: all green, one yellow that turns green again after the owner "syncs with the team". Week ten: still green. Week thirteen: the KPI lands at 71% of target, and the leadership meeting devotes forty minutes to the question nobody can answer, which is how a goal that was green for twelve straight weeks managed to miss by that much.
The reflex is to blame honesty. Someone must have known. Usually that is wrong, and it matters that it is wrong, because the fixes that follow from "people hid the truth" (more check-ins, harder questions, status meetings with more executives in the room) do not work. The dashboard was not hiding what people knew. It was faithfully aggregating information that could not contain the answer.
What a status field actually measures
A status field measures the owner's belief, at the moment of reporting, filtered through what the owner can see. Each of those three clauses removes information.
Belief: owners report intention as much as state. "Green" often means "I have a plan for this", which is a statement about the plan, not the trajectory.
At the moment of reporting: status is sampled weekly at best. Whatever happened between samples, a dependency reprioritised, a key engineer redirected, a decision deferred, arrives only at the next sample, if the owner noticed it at all.
What the owner can see: this is the big one. A revenue KPI might depend on work in four teams. Its owner runs one of them. The other three report their own goals to their own managers, and the cross-links are exactly where the execution risk accumulates. Nobody in the chain is lying. Everybody is reporting a true local picture, and the global picture that emerges from stacking them is false.
Roll-ups make it worse
Most goal tools respond to this by aggregating: the KPI is at 64% because its child projects average 64%. The percentage inherits every weakness of the statuses beneath it, then adds one of its own. It has no time dimension. Sixty-four percent with ten weeks left and a steady rate is a healthy goal. Sixty-four percent after the easy wins, with the rate falling, is a miss that has not been announced yet. The single number cannot distinguish them, and the roll-up paints both the same colour. A pace-to-plan calculation distinguishes them in one line of arithmetic, which is precisely why it is uncomfortable and rarely automated into the dashboard.
The work knew
Here is the part worth sitting with. In nearly every green-then-missed post-mortem, the evidence was available months earlier, just not in the status system. It was in the work.
The tasks under the goal stopped closing in week four. The Slack channel that had been active around the launch went quiet in week five. The platform team's board showed their capacity moving to an incident backlog in week six. Two teams that both reported green were, visibly, building toward different definitions of done. Any one of these, read directly, contradicts the dashboard. All of them together are the miss, in progress, fully documented in systems the company was already paying for.
Status data and work data are different substances. Status is what people say about the work. Work data is what the work is doing. When they disagree, the work is right, and the entire green-dashboard failure mode is a decision, usually unexamined, to run the company on the first substance and treat the second as operational detail.
Reading the work instead
Reversing that decision has two requirements.
First, the connection has to exist. Goals and KPIs on one side, projects, tasks and conversations on the other, explicitly mapped, so that "what work is under this goal" has an answer a system can traverse. This is the unglamorous foundation, and it is why serious strategy execution programs spend their first effort on mapping rather than on reporting templates.
Second, someone or something has to read it continuously. The signals are not subtle: work gone quiet, effort flowing to unrelated projects, run-rate below required rate, teams diverging. What they are is numerous, spread across tools, and tedious. A Chief of Staff can assemble the picture for a big review, twice a quarter, at real cost. A system can hold it current all the time.
This is what Vindaris is for. You map strategy, goals and KPIs down to every project and task, connect the tools where the work lives, and the Work Graph reads what the work is actually doing, with task-level context down to the Slack thread. When effort and resources drift from a goal, when connected work goes quiet, when a KPI stops pacing to plan, the alert reaches the owner with the reason attached, in week four. Not in the post-mortem.
The quarter you get back
A CEO who moves from status-colour reporting to work-based detection does not get better dashboards. She gets earlier weeks. The miss that used to announce itself in week thirteen announces itself in week five, while moving people, cutting scope, or renegotiating the dependency are still live options. The dashboard can even stay green, as long as green now means something: not "the owners are optimistic", but "the work underneath is actually moving at the rate the targets require".
The number does not miss because people lie. It misses because the truth was stored in a place nobody was required to look. Move the looking, and the green starts to mean something again.