Observation:
Ask the engineer where the project is, and the answer is in terms of components: what builds, what passes tests, what is still uncertain.
Ask the project manager, and the answer is in terms of milestones: what is on track, what slipped, what changed scope.
Ask the manager, and the answer is in terms of commitments: what was promised, what is at risk, what is green, yellow, or red.
Ask the sponsor, and the answer is in terms of outcomes: what was delivered, what was paid for, what the project demonstrates about the decision to fund it.
Ask the client, and the answer is in terms of experience: what they can use today, what they were told to expect, what is still missing.
Each answer is defensible from its role’s perspective. Each answer is internally consistent. Collectively, they do not compose a single map (FN-0009).
Implication:
“Status” is not a shared object. It is a set of views that never fully overlap, each shaped by the vocabulary of the role that produced it.
Alignment is not achieved by informing stakeholders. It is achieved by reconstructing a composite view across the roles, and this reconstruction is itself a deliverable that rarely has an owner.
Projects fail less often because stakeholders disagree about where the project is, and more often because no one notices they are reading different maps.
Part of the Field Notes series documenting operational patterns observed in real-world platform architectures.