Speak English at work with confidence

Usually it isn’t your English. With your team you share context, so short answers work. With senior people you have to give the context yourself, in fewer words, and that is a separate skill. We prepare the three moments where it shows most: answering a question in a meeting, a quick update in the corridor and a one-to-one. You leave each session with a few lines you can use that week.

It usually means people outside your team don’t know what you did or why it mattered. Visibility comes from a few habits you can repeat: one clear update a week that leads with the impact, one good question in larger meetings, and a short list of wins for your one-to-ones. We build those habits around your real work, then practice the conversations where they happen.

Often, yes. At senior levels people are judged on how they explain decisions, handle disagreement and represent the team, not only on the work itself. We start by agreeing what your manager wants to see, then practice those situations until they feel normal. I can’t promise a promotion; that depends on your company. What we can change is how your work comes across.

Match the setting. In the kitchen or a lift, a general question wants one friendly sentence and a question back: “Good, thanks. Busy but in a good way. How about you?” A real question about your project gets one positive line and an offer to talk properly: “Could I put 15 minutes in your calendar?” Save the problems for the one-to-one. We role-play both, including invitations you didn’t expect.

Two things: train your ear, and have a calm way to ask. For the first, we use short real clips in the accents you hear most (British, Indian, Australian and others) and focus on the words you miss. For the second, you learn to ask for the exact part you missed and confirm it in one sentence. Most people find that asking quickly feels far less awkward than guessing.

Say the point first, then one reason, then stop and let them ask. For example: “Yes, we can ship on Friday. The only risk is the payment test, and I’ll know by Thursday.” Long answers and restarted sentences usually come from looking for the perfect version while you speak. A good-enough sentence said once sounds more confident than a perfect one said twice. In sessions I interrupt the way a busy manager would, so you get used to giving the short version first.

Give yourself a few seconds on purpose: “Good question. Let me think about that for a second.” Then check what they mean if it’s unclear, answer the part you can, and promise the rest: “I don’t have the exact number with me. I’ll send it today.” We practice with rapid questions after your own presentations and updates, so the pause becomes a habit instead of a panic.

Lead with what they need to know, not with what you did. A simple order works: where we are, what it means, what’s next, and anything you need from them. “We’re on track for Friday. The login change is done; testing finishes Wednesday. Nothing needed from you this week.” We record your update at the start of the program and again later, so you can hear the difference.

A client of mine, an operations lead in New York, heard this from her boss every week. Where she worked before, being direct was normal; in a US company it came across as harsh. She already knew how to soften a request. She lost it when she was busy. We use a simple pattern: a soft opening, a clear time, and an offer to help. Instead of “Can you please finish this?”, try “It would be great to have this finished today at 3pm. If you need any help, let me know.” Then we role-play it under pressure, with you as the manager and me as a difficult colleague, until the softer version comes out first.

Early, and with a plan. Say what happened, what it means, two options and your recommendation, then what you need: “The release will slip by a week because of a payment bug. We can ship Friday without the new screen, or wait a week. I’d wait, because the bug affects real payments.” We practice it with your own projects, including the follow-up question everyone dreads: “Why didn’t we know earlier?”

Natural English at work is mostly shorter sentences, common phrasal verbs and the set phrases colleagues use every day. I’m a native speaker from New York, and each session adds phrases from your own situations to a personal phrase bank, with a note on where each one fits and where it would sound odd. Most clients start using native phrases naturally after six to nine months.

Often, yes, because the coaching is communication training: presenting, meetings, explaining decisions and working with senior stakeholders, practiced in English. I can write a short program outline for your manager or HR describing the goals and outcomes, invoice the company directly, and send progress notes at the midpoint and end with your agreement. Check your company’s policy; the final decision is theirs.

Know your first 30 seconds by heart, then speak to one idea per slide instead of reading it. Slow down on the problem and the result, and use a pause instead of “um”. We work on a real presentation of yours: you present it once as usual, we fix the structure and delivery, and you record it again so you can compare.

Remote work makes it harder to jump in, so you need a few reliable ways in: a short question early in the call, “Can I add something here?”, and a written follow-up after meetings that sums up your point. We practice getting into fast conversations, holding the floor when someone talks over you, and the informal chat at the start of calls that builds relationships.

Prepare the questions, not just the slides. Most client questions fall into a few types: why the numbers moved, what happens next, and why it costs what it costs. We list the hardest ones, I play a demanding client, and you practice short answers with ready lines: “That’s a fair question. Here’s how we see it.” and, when you need time, “Let me confirm the figure and come back to you by end of day.”

Prepare small talk the way you prepare a meeting. Pick five safe topics (the trip, food, the city, the work week, family) and two easy questions for each, and you’ll rarely be stuck. We practice the moments that happen on every trip: arriving, the coffee break, dinner, and saying goodbye in a way that keeps the relationship going. Many people find small talk over dinner harder than the technical sessions, and that’s normal.

Make it a question about the outcome, not a judgment of the spec: “Just to make sure I understand: the current request sends a phone number, but the new endpoint has no field for it. How should we handle that?” Name the gap, say what you observed, and ask how it should work. We practice with vague instructions on purpose, so asking for the missing detail becomes routine.