Dialogue — The Meeting
Alice's kitchen. Late. Bob turns up looking wrecked.
Bob: Seven meetings today. Seven. The one that broke me was the two o'clock. Fourteen people. Three of us needed to be there. The rest were cc'd on an email about "key stakeholders."
Alice: Any decisions?
Bob: Decisions get made in the corridor afterwards, between two people who already agree. You know this.
Alice: I know this.
Bob: I've had an architecture problem in my head all week. The kind that needs forty unbroken minutes. My calendar is fourteen coloured blocks with no gaps. I do my actual work before 7 AM and after 6 PM. Today I ate lunch in the eleven minutes between the two o'clock and the two-fifty.
Alice: When will you solve the architecture problem?
Bob: Tonight. About eleven. In a quiet house. Running on fumes.
Alice: (to the Agent) Bob is an engineer. His calendar has seven meetings a day, most of which he doesn't need to attend. His high-value work — design, architecture, problem-solving — gets pushed into early mornings and late evenings. The organisation measures presence and responsiveness. It doesn't measure thinking. What's happening here, and what should he do?
Agent: The organisation's coordination system has colonised the time it was supposed to coordinate.
Meetings optimise for alignment visibility — everyone feels informed, everyone was in the room. But this optimises a social variable at the expense of a cognitive one. The architecture problem requires sustained, unbroken attention. The calendar is systematically preventing the conditions that produce Bob's highest-value output.
Some questions:
- What happens if Bob declines the meetings he doesn't need? If the answer is "nothing operationally but it would look bad," then the system is optimising for appearance, not output.
- What's the architecture problem worth? If it's the most valuable thing he does this week, the seven meetings aren't free — each one costs an unsolved problem.
- Who else is doing their real work at 11 PM? If it's most of the team, this is a structural problem, not a scheduling problem.
Bob: "Who else is doing their real work at 11 PM." Jesus.
Alice: Everyone. The answer is everyone.
The architecture problem is solved at 11 PM, by a mind running on fumes. That time appears on no timesheet. The seven meetings do.