Stop Using Meetings to Discover Information You Could Have Read

Stop Using Meetings to Discover Information You Could Have Read

How pre-work, async input, and AI turn 90-minute updates into 30-minute decisions

This is Part 3 of a three-part series on decision-centric meeting culture. If you're starting here, Article 1 -- "Your Calendar Is Broken Because Your Decisions Are" -- is where the argument begins, and Article 2 -- "If You Don't Have a Decision Role, You Don't Need a Seat" -- builds directly on it. It's worth reading all three in order.

In Article 1, we talked about designing decisions before meetings. In Article 2, we drew a hard line: no decision role, no seat.

Now let's name a third uncomfortable truth that sits underneath both of those:

If people are learning the basics for the first time inside the meeting, the meeting is already failing.

Someone had to say it.

The Group Reading Session Problem

Most "status" or "update" meetings follow a predictable and quietly painful pattern. Someone shares their screen or pulls up a deck. People see the content for the first time. Basic clarifying questions start rolling in. Half the meeting gets spent narrating slide content that everyone could have read in five minutes. By the time the actual trade-offs and decisions need attention, there's no time left -- so someone says, "Let's find time to reconnect on this."

And you book another meeting.

That's not collaboration. That's a group reading session that accidentally scheduled itself as a decision forum.

Meetings Are for Synthesis and Decisions, Not Discovery

There are three distinct types of cognitive work that get crammed into a typical meeting, and understanding the difference between them changes everything.

Discovery is absorbing new information and getting context. It's a solo activity -- people do it at different speeds, in different ways, at different times of day. Some people read fast; some need quiet; some prefer to listen to a summary. Forcing everyone to discover information at the same moment, in the same room, at the pace of whoever is narrating is one of the most expensive and least effective things a team can do together.

Sense-making is where things get interesting. It's connecting dots, seeing patterns, debating trade-offs, and surfacing the tensions that aren't obvious from the data alone. This is where synchronous time genuinely earns its place.

Decision and commitment is choosing a path and agreeing who will do what next. This is the moment that justifies the meeting's existence -- and it almost always gets squeezed out by the time discovery runs over.

When discovery gets crammed into meeting time, you waste the slowest and most expensive channel available (group synchronous time) on the cheapest kind of work (reading and listening). You crowd out the actual collaboration you said you wanted. And you end up needing "another meeting" just to make the decision you ran out of time for.

Connect Decision Roles to Pre-Work

Here's where RACI, DACI, and RAPID stop being just about who sits in the room and start shaping what happens before anyone shows up.

For any important decision, the roles map directly to pre-work responsibilities:

The Recommend / Driver / Responsible person drafts a short decision brief before the meeting. It doesn't have to be long -- one to two pages covers it. It needs three things: the context (what's happening and why it matters), the options (two or three real choices with honest pros and cons), and the recommendation (what they believe is best and why they believe it). This gets shared in advance, not handed out when people walk in.

The Input / Contributors / Consulted people review the brief and add their perspectives asynchronously -- comments in the doc, flagged risks, alternative views, missing data. They do this before the meeting, not during it.

The Decide / Approve / Accountable person actually reads the brief. They come into the meeting with a leaning -- not a blank slate, not performed neutrality, but a genuine provisional view based on the pre-work. That's what makes the meeting useful.

Now the meeting has a different and much more valuable job: surface the real disagreements, clarify the key uncertainties, and make the call. Not: read slides out loud and hope something resolves.

AI as Your Meeting Front-End

This is where I'd encourage you to think differently about AI tools -- not as a way to summarize a bad meeting after the fact, but as infrastructure that makes the pre-work dramatically easier to do in the first place.

Drafting the brief. The Driver feeds raw notes, prior documents, and relevant data into an AI tool to generate a tight first draft of the decision brief. They refine it, sanity-check it, and make it sound human. What used to take two hours of staring at a blank doc takes twenty minutes of editing a solid starting point.

Summarizing long attachments. Ask AI to produce concise summaries of detailed reports, user research, or lengthy slide decks so that stakeholders can quickly absorb the essential context without reading a 40-page document the night before.

Highlighting contention points. Once Input contributors have commented on the decision doc, ask AI to scan those comments and surface: where people disagree, questions that remain unanswered, and risks that have been raised by multiple voices. That list becomes the agenda.

Generating the agenda itself. Build the meeting agenda around those contention points rather than around the slide structure. Something like: "Five minutes recapping the recommendation, twenty minutes on these two specific disagreements, five minutes confirming the decision and next steps." That's a thirty-minute meeting that actually produces something.

The meeting is now built on top of already-shared information, not used as the first place anyone encounters it. That's a completely different kind of conversation.

Try This: One Decision, One Brief, One Short Meeting

Pick a real decision coming up in the next one to two weeks that currently has a 60 to 90-minute meeting attached to it.

Ask the person in the Driver / Recommend / Responsible role to do the following:

Draft a one to two-page decision brief with three sections: the question being answered, the options under consideration, and the recommended option with the reasoning behind it. AI can help with the first draft if it saves time -- just make sure the final version is accurate and human.

Share the brief at least 48 hours before the meeting. Ask the Input and Contributors to comment directly in the document. Ask the Decider to note in the doc where they're currently leaning.

In the meeting itself: spend three to five minutes recapping the recommendation, then use the remaining time on the biggest points of disagreement, any risks that could change the decision, and confirming the final call and next steps. Cap the meeting at thirty minutes. Hold the line on that.

Afterward, ask the attendees three questions: Did this feel like a better use of time? What made it easier or harder? What would you tweak next time? Those answers are your roadmap for the next one.

Designing for Decisions, Not Time Slots

When you put all three articles together, a coherent picture of what's actually possible emerges.

Clear decision roles (Article 1) mean the right people are in the conversation from the start. Role-based attendance (Article 2) means the meeting is the right size. Pre-work, async input, and AI (this article) mean the meeting starts at a different altitude than it used to -- higher, sharper, and with less distance to cover before the real work begins.

The result is meetings that are smaller and sharper, focused on actual collaboration, and respectful of the time and cognitive energy of everyone involved.

If you landed here first, start with Article 1 -- "Your Calendar Is Broken Because Your Decisions Are" -- and follow the thread in order. The three articles build on each other, and the full picture is worth having.

From here, the deeper dive is the obvious next step: turning these ideas into team norms, giving managers scripts and practical templates, and measuring whether things are actually improving. That's where the companion guide goes -- for people who want to move from "interesting ideas" to "this is how our team works now."

Pick one meeting this week and try the brief. Just one. See what it changes about the conversation.