How to Prepare for Meetings: Why Asking for Less Gets You More
You spent three hours crafting the perfect pre-read. Ten pages of context, three attached spreadsheets, color-coded sections. You sent it 48 hours in advance with a polite "Please review before our meeting."
The meeting starts. Blank stares. "Sorry, I didn't get a chance to look at it."
Sound familiar?
Here's what nobody tells you: the problem isn't that people don't care. It's that you asked for too much.
The Excel Workbook Incident
A product manager once sent multiple Excel workbooks as meeting prep. No context. No guidance. Just massive spreadsheets with the instruction to "look through and understand."
Zero people opened them.
When confronted, the response was predictable: "I worked really hard on this! Others should take this much care for their own job."
Here's the brutal math that makes this impossible: If five people each create a 10-page report, and everyone reads everyone else's reports before a 30-minute meeting, you've just created a multi-hour prep burden for a half-hour conversation. The prep time now exceeds the meeting time by 5-10x.1
No wonder nobody does it.
Why Over-Preparation Backfires
The irony is that over-preparing and not preparing stem from the same root cause. The moment anyone perceives that prep will take too long, that their time would be better spent elsewhere, you've lost them.
Research on cognitive load and decision fatigue from behavioral psychology explains why. When faced with a cognitively demanding task (like reading dense documentation), our brains perform a quick cost-benefit analysis.2 A 10-page pre-read triggers an immediate "this will take 30+ minutes" calculation.3 That's enough to trigger avoidance.
The request goes into the mental "I'll do this later" pile. Later never comes.
Meanwhile, the over-preparer (let's call her Alex) grows increasingly frustrated. She's doing the work. Why isn't everyone else? She starts to question why she bothers when the culture seems to reward the least prepared person in the room.
The Shift in Practice
A team was struggling with their weekly sync. People showed up cold. Updates were meandering. Meetings ran long.
One week, the lead tried something different. Instead of sending the usual agenda with attached documents, they sent one simple request to each team member: "Please share one sentence about your current task status before the meeting."
That's it. One sentence. Thirty seconds of effort.
Everyone responded.
The meeting transformed. People arrived already aware of what was happening across the team. Talking points that overlapped were combined. Connected work streams were identified before the meeting even started. The conversation flowed naturally. They finished 15 minutes early with all points discussed.
Same team. Same work. Different approach.
A marketing director at a B2B software company had a similar revelation. She'd been sending a 47-slide quarterly roadmap deck for stakeholder review meetings. Attendance hovered around 30%, and those who did show up clearly hadn't looked at the slides.
She changed tactics. Instead of the deck, she sent three questions:
- What's your biggest concern about Q3 priorities?
- Which initiative would you cut if we had to choose?
- What are we missing?
Stakeholder participation jumped to 85%. The meeting itself became a real discussion instead of her presenting to blank faces. People came with opinions already formed, ready to engage.
The pattern holds across contexts. An engineering team lead stopped sending detailed sprint planning documents and started asking each developer: "What's blocking you this week?" Response rate went from sporadic to consistent. A sales team replaced their weekly report template with a single question: "What deal needs help?" Suddenly, everyone contributed.
Why This Works
The shift from overwrought prep to effective prep isn't about dumbing things down. It's about precision.
Here's the formula:
Before: "Please prep for the meeting" or "Review the attached documents"
After: "How is [specific thing] coming along?"
The difference is scope. "Prep for the meeting" is daunting because there's always so much going on in any given person's job. It's open-ended. Broad. Paralyzing.
"How is the API integration coming along?" is specific. Actionable. Answerable in one sentence.
The real ask was never to prepare a report. It was to answer a focused question. When you make the request specific and unique to each person, they're much more likely to respond.
A 30-second prompt has almost no friction. You can answer it between meetings, while waiting for code to compile, during a coffee break. It doesn't require context switching or deep focus.
A 10-page document requires dedicated time, mental energy, and the right environment. Those three things rarely align before a meeting.
What This Means for Meeting Culture
The meeting prep paradox reveals something deeper about organizational culture: we've confused thoroughness with effectiveness.
We think more context equals better decisions. More documentation equals better preparation. More detail equals more engagement.
The opposite is true.
More often creates overwhelm. Overwhelm creates avoidance. Avoidance creates the exact problem we were trying to solve: people showing up unprepared.
This isn't about lowering standards. It's about respecting the social contract of meetings. When you accept a meeting, you're committing to show up prepared. But preparation needs to be possible within the constraints of reality.
Asking someone to spend two hours prepping for a 30-minute meeting breaks that contract from the other direction.
How to Make the Shift
If you're an over-preparer frustrated that nobody reads your materials, or a meeting facilitator trying to get better participation, here's how to change your approach:
1. Start with one question (not three)
The temptation is to ask multiple questions to cover all bases. Resist it. One focused question per person is more powerful than three generic ones. A product team lead learned this when she stopped sending a five-question survey before roadmap reviews and started asking each stakeholder one tailored question. "What's your team's capacity constraint for Q3?" got better responses than a generic questionnaire ever did.
2. Make it personal and specific
Generic "please review" requests get ignored. "How is the customer onboarding redesign progressing?" gets answered. The difference is that the second version shows you know what that person is working on and care about their specific contribution. It's harder to ignore something clearly meant for you.
3. Time-box your ask
If responding takes more than 60 seconds, you've asked for too much. Test this yourself. Before sending prep requests, time yourself responding to them. If it takes you more than a minute (and you have more context than anyone else), it will take others longer. Adjust accordingly.
4. Share context, don't demand it
Your detailed documentation isn't wasted. It's reference material. Instead of "Review this 10-page document before the meeting," try "Here's background context if you want it (no need to read before we meet). My main question for you is: [specific question]?" People appreciate having resources available without feeling obligated to consume them all upfront.
5. Make it skimmable
When you do need to share information, format it for speed. Bullet points beat paragraphs. Bolded key points beat walls of text. A three-item list beats a detailed narrative. An operations manager cut her weekly update from two pages of prose to five bullet points with bolded numbers. Reading time dropped from 10 minutes to 90 seconds. Engagement went up.
6. Make non-response visible
When prep is quick and specific, there's no excuse not to do it. Visibility creates accountability without confrontation.4 If everyone can see that four people submitted their one-sentence update and two people didn't, social pressure does the work for you. No nagging required.
7. Celebrate completion
When people do prep (even briefly), acknowledge it. "Thanks for the heads up on the API delay, really helpful to know before we dive in." Positive reinforcement works. People repeat behaviors that get recognized.5
The Bottom Line
The meeting prep paradox isn't really a paradox at all. It's human nature.
When you ask for everything, you get nothing. When you ask for something specific and achievable, you get what you need.
Your three-hour pre-read isn't demonstrating thoroughness. It's demonstrating a misunderstanding of how people actually work.
The most effective meeting prep isn't the most comprehensive. It's the most focused.
So next time you're tempted to attach five documents and write a detailed agenda, stop. Ask yourself: what's the one thing I need each person to think about before we meet?
Then ask for exactly that. One sentence. Thirty seconds.
You'll be surprised how much more you get when you ask for less.
