What does it mean that meeting design as cognitive architecture?

Meetings are the primary site where teams think together. A poorly designed meeting wastes collective cognitive capacity. A well-designed meeting is a cognitive tool that produces thinking no individual could achieve alone.

Example: A data platform team held a weekly one-hour architecture review. The format had been the same for two years: the presenter shared their screen, walked through a design document for thirty minutes, then opened the floor for questions. Attendance was mandatory for all eight engineers. In practice, three engineers dominated the discussion. Two others checked Slack during the presentation. The remaining three asked occasional clarifying questions but rarely influenced the outcome. The tech lead, Noor, recorded one meeting and analyzed it. Of sixty minutes, thirty-two were the presenter talking, fourteen were questions from the same two senior engineers, eight were logistics and context-setting, and six were genuine multi-party discussion. The meeting consumed eight engineer-hours per week and produced six minutes of collective thinking. Noor redesigned the meeting. She shared the design document twenty-four hours in advance with three specific questions for reviewers to address. The meeting opened with five minutes of silent reading and written comments on the document. Then each person had two minutes to voice their most important concern. Only after every voice was heard did open discussion begin — limited to twenty minutes. The meeting shrank from sixty to forty minutes, attendance dropped from mandatory-eight to relevant-five, and the quality of feedback increased dramatically — because the architecture was designed for the team's cognitive process rather than the presenter's communication preference.

Try this: Audit one recurring team meeting using these five metrics. (1) Preparation ratio — what percentage of attendees read pre-work before the meeting? (2) Voice distribution — how many unique people speak substantively? (3) Decision clarity — does the meeting end with clearly stated decisions and owners? (4) Cognitive mode match — does the meeting format match its purpose (generative vs. evaluative vs. informational)? (5) Necessity — would the outcome change if this meeting were replaced by an asynchronous document? Score each metric 1-5. For any metric scoring below 3, redesign that aspect of the meeting. Test the redesign for two cycles and re-audit.