Article written for The Articulate Method website.
To answer an unexpected question in a meeting, pause, check that you understand it, and decide what you can say accurately. Lead with your answer, add a useful reason or condition, then give the other person room to respond.
Perhaps you’ve been listening quietly when someone turns to you: “What do you think?” You have a view, but the first sentence won’t come. Or you start talking and realise halfway through that you’re answering a different question.
You don’t need a polished speech. You need a starting point. The seven fictional examples below show how to find one, including when you don’t know the answer. There’s also a short lesson from our channel and a three-minute exercise to try before your next meeting.
Choose the right response
Before you worry about how to phrase your answer, ask yourself: “Do I understand the question, and do I know enough to answer it?”
| What is happening? | Your next move | A possible opening |
|---|---|---|
| The question is clear and you have the information. | Answer directly. | “My recommendation is…” |
| You are unsure what the person means. | Clarify the scope. | “Are you asking about the cost or the delivery time?” |
| You know only part of the answer. | Explain that part and name the limit. | “I can confirm the current status. The final date still needs checking.” |
| An accurate answer requires verification. | Say what you will check and arrange a follow-up. | “I’ll check the approved figures and send an update by tomorrow morning.” |
Only offer a follow-up time you can keep. If checking depends on someone else, say when you’ll update the group, even if you won’t have the final answer by then.
If you simply need thinking time, say:
“Let me think that through for a moment.”
Then pause. You don’t have to fill the space with an explanation of why you need to think.
Build a short, useful answer
For a straightforward question, try:
Answer → supporting reason → finish.
For example:
“I’d start with a smaller trial. It would let us test the instructions before involving the whole team.”
You can stop there. The recommendation and its reason are clear, and the group can ask for more detail.
If your answer depends on something, say so:
“Friday is possible if testing finishes on Thursday. Until then, I would treat it as a provisional date.”
iSpeak’s guidance on unexpected questions offers similar advice: clarify what you’re being asked and follow up honestly when you don’t have the answer.
Treat the structure as a starting point. Some questions need one sentence. Others need enough detail for the group to make a decision.
Seven worked meeting examples
Read the answers aloud. Use the wording that feels natural to you, and change the details to match what you actually know and can promise.
1. You are asked for a recommendation
Context: The team is choosing a format for customer training.
Question: “Which option would you recommend?”
Response that creates confusion: “There are benefits to both, and we discussed several things last week, so it depends on quite a few factors.”
Clearer response: “I’d recommend two shorter sessions. That would give participants time to try the process and bring questions to the second session.”
The group hears your choice straight away and can discuss the reason behind it.
Likely follow-up: “Would that increase the cost?”
“It might. I’d need to compare the trainer’s pricing before recommending that we book it.”
You can recommend a format while being honest that the price still needs checking.
2. You are asked whether a deadline is achievable
Context: A launch still depends on testing.
Question: “Can we launch on Friday?”
Response that creates confusion: “Yes, probably. We should be fine.”
Clearer response: “Friday is possible if testing finishes on Thursday with no critical issues. I’ll confirm the test status tomorrow afternoon.”
“Possible if” matters here. It tells your colleague what needs to happen before Friday becomes a firm date.
Likely follow-up: “Can we announce Friday today?”
“I wouldn’t confirm it publicly until testing is complete. We can prepare the announcement while keeping the date provisional.”
Even when someone wants a quick yes or no, keep the condition that makes your answer accurate.
3. You are asked to choose between priorities
Context: You are preparing a client proposal and updating an internal guide.
Question: “Which should we finish first?”
Response that creates confusion: “They’re both important, and I’ve already done a lot on the guide.”
Clearer response: “I’d finish the client proposal first because the client needs it tomorrow. Is anyone waiting on the guide before then?”
You’ve named a priority, explained why, and checked whether you’ve missed something that could change the order.
Likely follow-up: “What happens to the guide?”
“I’ll look at the remaining work and come back with a revised date once we’ve agreed the priority.”
That gives you time to check the workload before promising a new deadline.
4. You are asked to explain an unexpected result
Context: Fewer people registered for an event than the team expected.
Question: “Why were registrations lower?”
Response that creates confusion: “People probably weren’t interested in the topic.”
Clearer response: “I don’t know yet. I’d check how many people received the invitation, visited the page and completed registration. That should help us see where to look next.”
Lower registrations are something you can observe. Lack of interest is only one possible explanation, so it needs checking.
Likely follow-up: “What would you check first?”
“I’d start with whether the invitations reached the intended audience. That gives us a starting point for the review.”
You still have something useful to contribute: a sensible place to start looking.
5. You are asked for a figure you cannot verify
Context: A colleague asks about the approved project budget.
Question: “What is the exact amount?”
Response that creates confusion: “About twenty thousand, I think—maybe a bit more.”
Clearer response: “I don’t have the approved amount in front of me. I’ll check the budget record and send the exact figure after the meeting.”
An approximate number can quickly become the number everyone uses. Checking the record is worth the delay.
Likely follow-up: “Can you give us a rough estimate now?”
“I don’t remember it well enough to give you a reliable estimate. Can we leave that decision open until I’ve checked?”
If you do have a reasonable basis for an estimate, explain it and label the figure as approximate. Otherwise, leave the number out.
6. You receive a broad or unclear question
Context: A manager has reviewed your draft proposal.
Question: “Can we make this better?”
Response that creates confusion: “Yes, I’ll change the introduction and add more detail.”
Clearer response: “Which improvement matters most here: a clearer recommendation, stronger evidence, or a shorter document?”
This question helps you find out what the manager needs before you spend time changing the draft.
Likely follow-up: “The recommendation needs to be clearer.”
“Then I’ll put the proposed decision at the start and explain the two reasons supporting it.”
Now you both know what the revision will address.
7. The question has several parts
Context: A colleague asks about a pilot.
Question: “Who would take part, how long would it run, and what would we measure?”
Response that creates confusion: “We’d measure how well it works, and the team could probably help.”
Clearer response: “I’ll take those in order. I’d start with the support team and try it for two weeks. We’d check whether people can complete the process using the new instructions.”
Following the order of the question makes it easier to remember all three parts. It also helps your colleague follow the answer.
Likely follow-up: “Why two weeks?”
“That’s a starting suggestion. We’d need to check whether the team will use the process often enough in those two weeks.”
Write down the parts if that helps. You can also ask which part the group wants to address first.
Watch the three-step answer lesson
Watch Caught Off Guard? The 3-Step Answer Framework from our official @TheArticulateMethod channel.
The companion lesson summarises a simple approach: pause, give a headline answer, add a supporting reason, then stop.
Try this after watching: Answer “What would you improve first in our current process?” Give one recommendation and one reason. Then check whether more detail is actually needed.
Try this after watching: Answer “What would you improve first in our current process?” Give one recommendation and one reason. Then check whether more detail is actually needed.
Use the examples and practice cards here to put that approach into your own words.
Practise in three minutes
Choose a project you know well, or make up a simple situation such as planning a team event. You can record yourself if you’d find it useful.
- 0:00–0:30 — Prepare. Write down three facts about the situation and one thing you do not know.
- 0:30–1:15 — Answer. Pick a question card at random. Choose whether to answer, clarify or check information, then respond aloud.
- 1:15–1:45 — Review. Which sentence answered the question? Did you say anything you weren’t sure about? If you recorded the answer, listen once with those two questions in mind.
- 1:45–2:30 — Try another card. Practise a different response type. You may need a clarification question rather than an explanation.
- 2:30–3:00 — Choose one adjustment. For example: state the recommendation earlier, name the condition, or give a realistic follow-up.
These timings simply keep the exercise short. In a real meeting, take the time the question needs.
Six reusable question cards
Print or copy these prompts, shuffle them, and use one at a time.
| Card | Question |
|---|---|
| 1 — Recommend | “Which option would you choose, and why?” |
| 2 — Check timing | “Can we finish by the proposed date?” |
| 3 — Prioritise | “What should we do first if we cannot complete everything?” |
| 4 — Explain | “What do we know about why this result changed?” |
| 5 — Verify | “What is the exact figure, and where can we confirm it?” |
| 6 — Clarify | “How could we make this better?” |
Open the printable practice cards — a ready-to-print version of these cards with the review checklist.
Ask a partner to choose a card and add a follow-up. Practising alone? Try “Why that option?” or “What would change your answer?”
Review your answer
Use Yes / Not yet / Not applicable:
- Did I answer the actual question or clarify it?
- Could the listener identify my main point?
- Did I include a useful reason or necessary condition?
- Did I separate confirmed information from uncertainty?
- If I promised a follow-up, was it specific and realistic?
- Did I finish without repeating the same explanation?
Pick one thing to change on your next attempt. An occasional hesitation doesn’t make an otherwise useful answer a failure.
Common mistakes
Starting too far back. If someone asks which option you recommend, give the recommendation before explaining last week’s discussion.
Sounding more certain than you are. “I’ll check that” is more useful than a confident answer the group later has to correct.
Cutting out an important detail to stay brief. Keep any condition that changes the meaning of your answer, such as a deadline depending on approval.
Hearing criticism before you’ve understood the question. If the request feels vague or challenging, ask what the person wants to know before defending your work.
Promising an answer too soon. Allow time to check the information, especially when you need another person’s help.
Official companion lesson · 9 min 18 s
How to Answer Without Rambling Under Pressure | Day 16
When a question catches you off guard, PREP gives you a short route through the answer: point, reason, example, point. Watch the Day 16 lesson, then try it on one of the question cards above.
Frequently asked questions
Is it acceptable to ask for thinking time?
Yes. Try “Let me think about that for a moment.” Then decide whether you can answer now, need to clarify something, or need to check a fact.
What if I do not know the answer?
Say so plainly: “I don’t have that information yet.” Add what you can confirm or explain how you’ll find out. If someone else owns the information, name the person or team to ask.
What if the question contains an assumption I disagree with?
Clarify it before answering: “Before I answer, can we check whether that deadline has been agreed?” Then address the question using the confirmed information.
How long should my answer be?
Give enough information for the person to understand your answer and any important limits. Then pause. If they’re ready to move on, you don’t need to keep explaining.
Can I use notes?
Yes. Short prompts can help you track facts, conditions and multi-part questions. Keep exact figures written down when accuracy matters.
For prepared contributions, read How to Give a Clear 30-Second Meeting Update. For further practice, find the Interview Answer Framework in The Articulate Method resources and adapt it to your next meeting question.
Put this skill into daily practice
One short lesson a day for 30 days — clarity, fluency, confidence, connection, and influence. The Articulate Challenge gives you a structured path to apply what you just read, with real speaking tasks you can complete at your own pace.
