Presenting and Speaking Up in Meetings and Interviews

Many capable people stay quiet in meetings because they wait for the perfect thing to say, and then the moment passes. Speaking up well is less about being a natural talker and more about having a simple structure and a few habits you can rely on when your heart is beating faster than usual.

Why speaking up matters and what makes it hard

In meetings and interviews, people judge your thinking by how you express it. If you know the answer but ramble, or know something useful but never say it, the people around you cannot tell. That matters for visibility on the job, and in interviews it can be the difference between a clear answer and a confusing one.

It is hard because of fear of being wrong, fear of sounding junior, and not having a structure ready. You can change the third one quickly. The first two get easier with practice.

A structure you can use anywhere: point, evidence, point

Point-evidence-point (sometimes called PEP) is simple. First, state your main point in one sentence. Second, give one or two pieces of evidence or an example. Third, repeat the point, ideally with the action or conclusion. The opening point tells listeners where you are going; the closing point tells them you are done.

Point:    "I think we should delay the release to Monday."
Evidence: "Two of the five payment tests are still failing, and the fix needs a
          code review that won't happen before tonight."
Point:    "So I'd suggest Monday, and I can post a test status update by noon
          tomorrow."

Point:    "I'm a good fit because I learn quickly and I finish what I start."
Evidence: "In my final-year project I had never used React; within three weeks I
          built the dashboard and our team presented it at the college expo."
Point:    "So I'd bring that same quick learning to this role."

For experience questions, use the same idea with the STAR method. For the very first question, see how to answer "tell me about yourself".

Pausing, pace and the first sentence

• Pause before you answer. Two or three seconds to think looks thoughtful, not weak. You can say "Let me think for a moment."
• Slow down. Nervous speakers speed up. Aim for slightly slower than feels natural, and finish sentences instead of trailing off.
• Pause after important points. Silence lets the point land, and gives you a second to breathe.
• Rehearse only the first sentence of any answer or talk. Once you start well, the rest follows more easily.
• Cut filler by replacing it with a pause. Trying to eliminate every "um" is not worth the energy; a silent pause usually sounds better than a filler word.

Handling nerves honestly

Nerves do not completely go away, and no technique removes them entirely. Many experienced speakers still feel them. What helps is making them manageable. Preparation reduces how much there is to be afraid of. Practising out loud, standing up and with a timer, is much more useful than reading your notes silently.

Slow breathing (a longer exhale than inhale) calms many people before they speak, though it works better for some than others. Some people find it useful to think of nerves as energy rather than danger, but the evidence for such reframing is mixed, so treat it as something to try, not a guarantee. It is fine to say "I'm a bit nervous" if you want to; most listeners are supportive, and they usually notice less than you think.

Answering questions you do not know

Bluffing is the worst option, because experienced interviewers and colleagues usually notice, and it damages trust. A better pattern is: say what you do know, say honestly what you do not know, and say how you would find out.

Interview:
"I haven't used Kafka directly. I've used RabbitMQ for message queues in my
internship, so I understand the basic idea of producers and consumers. If I had
to learn Kafka, I'd start with the official docs and build a small example."

Meeting:
"I don't have that number with me. I'll check and send it to you by 3 pm."

When the question is unclear:
"Just to make sure I answer the right question: do you mean the cost for this
year or the long-term cost?"

Common mistakes

• Starting with an apology. "This might be a silly question..." weakens what follows. Just ask it.
• Burying the point in a long explanation. Say the point first.
• Reading from slides or notes word for word.
• Speaking too fast to finish quickly.
• Never speaking because you are waiting for a perfect idea. A clear, small contribution is better than a perfect one that you never say.
• Ignoring the room. Check whether people look lost, and ask "Does that make sense so far?"

How this shows up in interviews and on the job

Interviews are basically structured speaking practice. Most candidates are nervous, and interviewers expect it; they are more interested in whether you can organise your thoughts and handle a question you did not prepare for. Read common interview mistakes to avoid for habits to watch out for.

On the job, speaking up is how your work becomes visible: giving a short status in standup, raising a risk early, or asking a clarifying question. These small contributions add up faster than one big presentation.

How to practise

Record yourself on your phone answering one question with point-evidence-point, then listen back. Check three things: did you state the point first, did you use a concrete example, and did you finish clearly? Repeat with a different question each day for a week, and in real meetings, set a goal of one contribution per meeting.