The questions people almost didn’t ask

I read Dylan’s announcement before the first meeting of the day. It was clear. The new handover process had a reason, a start date and a way to share feedback. I knew how much care had gone into getting those details right.

Still, I felt a little knot in my stomach. A clear message doesn’t always make it easy to respond. When a conversation is happening in English, people may be working out what the change means while searching for the words to ask about it. I know that pause—the moment when you have a question, but you’re deciding whether you can say it clearly enough.

My job that morning wasn’t to answer every question for the team. It was to help make sure the questions could be asked.

“I understood the message. I’m not sure I understood the process.”

The first person to speak to me was a colleague from the Brazil team. “I understood Dylan’s email,” she said. “But I’m not sure I understood what happens to a handover that’s already in progress.”

“You don’t need a perfect explanation. You can start with the question.”

We wrote down a simple version: “Could you clarify what we should do with handovers that are already in progress?” She read it once, then again, more confidently.

The pause before speaking

At the meeting, Dylan explained the trial. People listened. A few nodded. Then he asked, “Does anyone have any questions?” The silence lasted only a few seconds. It felt longer.

I could see people thinking. Some were checking the details in the email. Some were deciding how to phrase a concern. I didn’t want to fill the silence for them. I wanted to make it easier to enter.

“Let’s take this one step at a time. You can ask about the process, the timing, or what happens if something doesn’t work.”

My colleague raised her hand and asked her question. Dylan answered, and we added the example to the guide. The question took less than a minute. The pause before it took much longer.

Asking for a moment

Later, the discussion moved quickly. One colleague began to speak, stopped, then looked down at their notes. I recognised the moment: you know what you want to contribute, but the conversation has moved on and you’re trying to find a way back in.

“Let’s pause here. I think there’s another point we should hear.” “Could I add something about how we do this in our team?” “Of course,” Dylan said.

Their explanation helped us notice that the new brief needed one more field: who would take the next action, and by when.

Saying “I’m not sure” is useful

Near the end, someone asked whether the new process would definitely save time. Dylan started to answer, then stopped. “We hope it will,” he said. “But that’s one of the things the trial should help us understand.”

Sometimes the most useful response is to be honest about what you don’t know yet. We agreed to record the time the new process took and ask the teams what felt useful or repetitive.

What I took from the day

By the afternoon, the guide had a new example. The team had clarified what to do with work already in progress. And the trial had a better way to collect feedback. The questions had improved the process.

The knot I’d felt in the morning eased—not because everyone suddenly had perfect English, but because people had time to ask, support when they needed it, and a real answer when they did.

Good communication doesn’t remove every difficult moment. It helps people get through one together.