The agenda was aspirational
You sent the agenda four days out.
Three items. Tight. Time-boxed. One page attached to the calendar invite so everyone could come prepared.
They confirmed attendance. Nobody pushed back. You walked in with a deck for each point and ten minutes to spare.
By 11:15, you were still on item one.
The Situation
The meeting didn't collapse. Something else happened.
A question opened up a conversation none of you had planned. Someone stepped out and came back with a colleague who turned out to be exactly the right person to have in the room. The conversation went somewhere genuinely useful. Just not to items two and three in the agenda.
You left with a full page of notes and a quiet knot in your stomach about everything you hadn't covered.
Your counterpart left the room glowing. You both attended the same meeting.
The Friction
In Slot logic, an agenda is a contract. It states what the meeting is for, lets people prepare, and creates a shared record. Getting through it is how you know the meeting worked. When it runs over on item one, the reading is: we lost control. Something went wrong.
In Flow logic, an agenda is a general direction. What matters is whether the conversation was useful, whether the people in the room produced something together. Whether item three got ticked off is almost beside the point. When the meeting ran over on item one, the reading was: we got somewhere real. That was a good meeting.
They're running completely different definitions of what a meeting is for.
