You have ten minutes before a meeting starts. The invitation is familiar, but the purpose is not. There are three attachments, a long message thread, and no time to read everything. The usual response is to skim randomly, open too many files, and enter the meeting with fragments of context but no clear idea what you need to contribute.
Ten minutes is not enough for comprehensive preparation, but it is enough to become useful. The key is to prepare for the meeting’s likely output rather than trying to absorb every piece of background. In a short preparation window, your job is to identify the purpose, the decision or action at stake, your role, the few facts that matter, and the question you cannot afford to leave unanswered.
Minute 1: Identify what the meeting must produce
Start with the calendar invitation, not the attachments. Read the title, description, attendee list and any agenda. Ask one question: what should be different when this meeting ends?
The answer might be a decision, approval, plan, status alignment, problem diagnosis or assignment of next steps. If the invitation only names a topic, translate it into a likely outcome. “Website launch” is a topic. “Decide whether the website can launch Friday” is an outcome. “Q4 budget” is a topic. “Agree which requests fit within the Q4 budget” is an outcome.
If the request itself is vague, use the same outcome-first logic described in How to Clarify a Vague Work Request Before You Start. You do not need perfect certainty. You need a working hypothesis about why everyone is spending time together.
Minutes 2-3: Work out why you are in the room
Next, look at the attendee list and determine your expected role. Are you there to provide information, recommend an option, approve something, challenge assumptions, execute the next step, or simply stay informed?
This matters because different roles require different preparation. A decision-maker needs the options and consequences. A subject-matter expert needs the relevant facts and risks. A project owner needs current status, blockers and dependencies. A contributor may only need to understand the decision and the action that could land with them.
Do not prepare as though you own every part of the meeting. Ten-minute preparation becomes possible when you narrow the scope to the contribution only you are likely to make.
Minutes 4-5: Find the source of truth
Now open the most authoritative current document. Avoid reading the entire email chain chronologically. Look for the latest brief, project tracker, proposal, decision memo or status document. If several versions exist, check dates and identify the one people are actually using.
Scan for four things: current state, deadline, unresolved issue and owner. Those four facts usually explain most of the operational context. If the meeting concerns a project with external dependencies, also check what is waiting on someone else. A simple waiting-for list is useful precisely because it makes these dependencies visible without forcing you to reconstruct them from messages.
Resist the urge to open every link. Each new tab creates another branch of context to understand. Follow a link only when it answers a question directly connected to the meeting outcome.
Minutes 6-7: Write a three-line briefing for yourself
Stop reading and write three lines in your notes:
- Current: What is true now?
- Decision: What needs to be decided, confirmed or resolved?
- My input: What fact, recommendation, question or commitment am I likely to contribute?
For example: “Current: vendor delivery moved from Tuesday to Thursday. Decision: whether Friday launch remains realistic. My input: testing requires one full business day after delivery, so Friday leaves no recovery margin.”
This tiny briefing is more useful than a page of copied notes because it turns background into meeting-ready judgment. It also exposes gaps. If you cannot write the “Current” line, you need a status fact. If you cannot write the “Decision” line, the meeting may not have a clear objective. If you cannot write “My input,” you may be attending mainly for awareness.
Minute 8: Identify one question that changes the outcome
Choose one question you need answered. Do not make a long list of everything you do not know. Prioritize the uncertainty that could change the decision, your commitment, or the next step.
Useful questions sound like: “Is Friday a contractual deadline or an internal target?” “Which customer segment is included in this first release?” “Who has final approval if Finance and Sales disagree?” or “Are we choosing an option today or only narrowing the alternatives?”
A good question reduces ambiguity for the group, not just for you. It should connect missing information to a consequence. That makes it easier for others to answer and keeps the meeting focused on work rather than background explanation.
Minute 9: Decide your position before the discussion starts
If the meeting may require your recommendation, form a provisional position now. It can change when new information appears, but arriving with a view is better than outsourcing all thinking to the meeting.
Use a simple structure: “Based on what I know, I recommend X because Y. I would change that recommendation if Z is true.” This separates your current judgment from the assumption underneath it.
For a decision meeting, this is especially important. A meeting should not become the first moment everyone starts thinking about the choice. The principles behind a decision-focused meeting are the same as those used in a strong proposal: make the problem, options, trade-offs and ask visible enough that people can exercise judgment rather than search for context.
Minute 10: Prepare to capture the outcome
Use the final minute to create a blank closing structure in your notes: Decision, Actions, Owners, Deadlines, Open Question. You are preparing for the end of the meeting before it begins.
This prevents a common failure: people spend thirty minutes discussing an issue, then rush into the next call without recording what changed. The structure in How to Write a Meeting Recap That Actually Gets Action works because it separates decisions from discussion and turns next steps into complete commitments.
You do not need to volunteer as the formal note-taker. The structure is for your own clarity. If an action is assigned to you, confirm the deliverable and date before leaving. If a decision affects your work, record it in language specific enough that you can act without replaying the conversation later.
What to skip when you only have ten minutes
Short preparation works only if you deliberately ignore low-value activity. Do not read every old message, polish notes nobody else will see, research peripheral questions, or create a detailed chronology of how the issue developed. Do not spend six minutes formatting a document and four minutes understanding the meeting.
Also avoid turning preparation into anxiety-driven checking. Opening every attachment can feel responsible while actually reducing comprehension. Your goal is not to prove that you consumed all available information. Your goal is to enter with enough context to help produce the right outcome.
When ten minutes is not enough
Some meetings genuinely require deeper preparation. A contract negotiation, disciplinary conversation, financial approval, executive presentation or technical review may depend on evidence that cannot be responsibly compressed into a quick scan.
Recognize that distinction early. If the decision carries substantial cost, legal exposure, safety implications or irreversible consequences, ten minutes should be used to identify what preparation is missing, not to pretend you are ready. State the gap and request the time or information required for a sound decision.
For ordinary knowledge-work meetings, however, the ten-minute method is often enough to move from “I know there is a meeting” to “I know what this meeting needs from me.” That is a meaningful difference.
Use the same structure after the meeting
Good preparation and good follow-through are mirror images. Before the meeting, identify the expected outcome, current state and your contribution. After the meeting, record the actual decision, actions, owners and deadlines.
If the meeting produces work that depends on other people, move those dependencies into your tracking system. If it changes priorities, update your plan instead of relying on memory. The approach in What to Do When Work Priorities Keep Changing is useful when a meeting suddenly displaces work you had already committed to.
A reusable ten-minute meeting preparation checklist
When the calendar reminder appears and you realize you are underprepared, use this sequence: define the outcome; identify your role; find the current source of truth; write Current, Decision and My Input; choose one high-value question; form a provisional position; and prepare to capture decisions and actions.
The method is intentionally small. It does not replace proper preparation when the stakes demand it. It gives you a disciplined fallback for the far more common situation where the meeting is approaching, your day has been busy, and you need to become useful quickly.
Ten minutes cannot give you complete context. It can give you the right context. Focus on what the meeting must produce, what only you need to contribute, and what must be clear when everyone leaves. That is usually the preparation that matters most.