Read a sample: 1. Define the Decision Before You Speak
The meeting invitation says, “Project update.” You have reviewed the work, collected notes from your team, and prepared a careful account of what has happened. Then, halfway through your explanation, a senior manager interrupts.
“What do you need from us?”
It is a reasonable question, but it can be surprisingly difficult to answer. You may know the project thoroughly and still be uncertain whether the group is expected to approve a change, choose between options, identify a risk, or simply hear that work is progressing. When the purpose of the meeting is unclear, preparation often becomes an exercise in collecting information rather than deciding what to say.
A high-stakes meeting does not have to involve a crisis or a room full of executives. It is any conversation in which the outcome matters enough that misunderstanding, delay, or an ill-informed choice would have consequences. A staffing discussion can be high stakes for the people doing the work. A routine review can become consequential if it determines whether a project moves forward.
Your first task is not to sound impressive. It is to understand what the meeting needs to accomplish and what you can contribute. That understanding gives you a reason to include some details, leave others available for questions, and ask for the next step plainly.
Imagine that you lead a team responsible for launching an internal service. Testing has revealed problems that need more attention. The original launch date is approaching, and you have been invited to give an update.
You could begin with the sequence of events:
> “We completed the first round of testing, then the team reviewed the feedback and met with operations. We found several issues, and we’ve been working through them. We also spoke to the training team about the rollout materials.”
None of that is necessarily irrelevant. The trouble is that listeners must work out why they are hearing it. They may not know whether the issues threaten the launch, whether you have a recommendation, or whether you need anything from them.
Now consider an opening that identifies the decision:
> “We need to decide whether to launch on the planned date or allow more time for testing. I recommend delaying the launch until the critical issues are resolved. Today I’m asking for approval to revise the schedule and confirm who needs to be involved.”
This version does not explain everything. It gives the room a useful frame for the conversation. Listeners can now understand why the testing results matter and what they are being asked to consider.
The decision is the choice that someone can make or advance because of the discussion. It might be whether to approve a proposal, select an approach, assign responsibility, accept a risk, or gather more information before proceeding. If no choice is available yet, the immediate decision may be narrower: agree on the question to investigate, identify who will decide, or set a time to return with options.
“Discuss the project” is a topic. “Choose whether to revise the launch schedule” is a decision. The distinction matters because a topic can expand indefinitely, while a decision gives the conversation a point of arrival.
Use a real meeting on your calendar, or work with the service-launch example. Take a few minutes to write short answers to the following prompts.
1. Name the topic. What does the invitation or agenda say the meeting is about?
2. Describe the choice. What could the group approve, reject, change, clarify, or investigate?
3. Identify your view. What do you think should happen next? If you do not yet have a recommendation, what needs to be learned before one is possible?
4. Make the request. What specifically do you want someone in the meeting to do?
5. Name the consequence of waiting. What becomes harder, riskier, or less clear if the issue remains unresolved?
For the hypothetical launch meeting, the answers might look like this:
- Topic: A project update on the internal service launch.
- Choice: Launch on the planned date or revise the schedule to address critical testing issues.
- View: Revise the schedule; the unresolved issues need attention before launch.
- Request: Ask the sponsor to approve a revised schedule, with the project lead to return with a proposed date after consulting the teams involved.
- Consequence of waiting: Teams may continue preparing for a date that could change, making coordination more difficult.
Notice that the request does not pretend the team already knows the right new launch date. It asks for the decision that can be made now and names the work needed next. A useful request can be specific without claiming that every detail is settled.
Now say your request aloud in one or two sentences. If it takes a long explanation before you can name what you want, return to the prompts. You may be combining several decisions, asking the wrong group, or describing a problem without identifying an action.
You might discover that your original plan was to “provide visibility.” Visibility can be valuable, but it is usually a means rather than the whole purpose. Ask yourself what people should do with the information. Perhaps they need to recognize an emerging risk, nominate someone to assess it, or know that no action is currently required. Each calls for a different opening.
A clear request still needs an appropriate recipient. The person who invited you may not…