Execution Fog: The Translation That Broke

She walks out of Monday’s planning meeting. The plan is clear. Everyone has read it. Three top priorities for the week. Ownership assigned. Calendar blocked.

By Friday, the team has shipped — and none of it matches what was planned.

None of the work is wrong. None of the people are wrong. None of the ownership shifted in any meeting she was in. The dashboard reports a productive week. The hours show up. The deliverables exist.

But the Monday plan and the Friday work are not the same thing. The gap is small in any single piece. Across all three priorities, the gap is the week.

She traces what happened. One priority hit a vendor delay nobody surfaced because everyone assumed someone else would. One priority got reshuffled because a customer call surfaced something that felt more urgent. One priority got executed against the team’s version of what it meant, not the version she meant — and nobody asked which version was the version.

She notices the senior person who started planning her week privately, somewhere in the spring, without bringing the full picture to the Monday meeting.

She notices that the team treats the official plan as a suggestion and the real plan as the thing that emerges by Wednesday.

She notices that she has stopped trusting that what she heard agreed to in the room is what will be in the work.

She notices that the gap is not in the meeting. The gap is in the translation between the meeting and the calendar.

She has not named it yet.

She has begun to notice that the plan and the work no longer recognize each other.