English for Technical Leadership: How Engineering Managers Communicate
Learn the English vocabulary and phrases engineering managers use for roadmaps, OKRs, 1:1s, performance reviews, and escalation conversations.
Moving from individual contributor to engineering manager means your communication style must shift. You no longer just describe technical work — you set direction, align people, and navigate organisational complexity. This guide covers the English vocabulary and phrases that effective technical leaders use every day.
Strategic Vocabulary
Technical leaders frequently discuss direction, resourcing, and organisational goals. These terms appear in planning documents, all-hands presentations, and executive updates.
| Term | Meaning |
|---|---|
| Headcount | The number of people in a team or available to hire |
| Technical vision | A long-term description of where the engineering organisation is heading |
| Roadmap | A plan showing what will be built and when |
| OKR | Objectives and Key Results — a goal-setting framework |
| Engineering strategy | A document explaining how engineering decisions support business goals |
| Capacity planning | Estimating team bandwidth for future work |
OKR Language in Practice
OKRs have a specific structure. The Objective is qualitative and inspiring; the Key Results are measurable.
- Objective: “Build a world-class developer platform.”
- Key Result: “Reduce deployment time from 45 minutes to under 10 minutes by Q3.”
When writing Key Results, use verbs like increase, reduce, achieve, launch, and maintain followed by a measurable target.
Escalation Language
Escalation means raising an issue to someone with more authority or a broader view. The language matters — poor escalation can sound like complaining rather than problem-solving.
Effective escalation pattern:
- State the issue clearly and factually.
- Explain the impact.
- State what you have already tried.
- Ask for a specific decision or resource.
Phrases:
- “I want to bring this to your attention because it’s blocking progress on the Q2 roadmap.”
- “We’ve explored two options internally and haven’t been able to resolve this without cross-team alignment.”
- “I’m not asking you to make this decision for us, but we need clarity on the priority before we can proceed.”
1:1 Vocabulary
One-to-one meetings are the primary tool for building relationships and unblocking individuals. Useful vocabulary:
| Term | Meaning |
|---|---|
| Growth areas | Skills or behaviours an engineer is developing |
| Blockers | Things preventing someone from making progress |
| Career pathing | Discussing the steps toward an engineer’s next role or promotion |
| Alignment | Ensuring two people or teams share the same understanding or goals |
| Psychological safety | An environment where people feel safe to speak up and take risks |
Useful 1:1 questions:
- “What’s the most frustrating thing about your work right now?”
- “Is there anything I can do to better support you?”
- “How are you feeling about your growth in the last quarter?”
Performance Review Language
Performance reviews require precise language. Avoid vague praise or vague criticism — be specific and behavioural.
| Weak | Strong |
|---|---|
| ”She’s a great engineer." | "She consistently delivers high-quality code that requires minimal rework in code review." |
| "He struggles with communication." | "He would benefit from writing more detailed context in pull request descriptions." |
| "She needs to step up." | "She is ready to take ownership of the full delivery of a feature, from design through deployment.” |
Example Sentences
- “Our engineering strategy for this half is focused on reducing operational toil so that engineers can spend more time on product work.”
- “During the last 1:1, we discussed a growth area around technical communication — specifically, writing clearer RFCs.”
- “I’m escalating this dependency to the platform team because it’s on the critical path for our Q3 launch.”
- “Headcount for the new data platform team has been approved — we’ll be hiring two senior engineers and one staff engineer.”
- “The OKR for this quarter is to improve deployment frequency from twice a week to daily, as measured in our DORA dashboard.”
A Note on Tone
Technical leaders in English-speaking environments are expected to be direct but not blunt, confident but not arrogant. Phrases like “I’d suggest…” or “One way to think about this is…” signal confidence while leaving room for dialogue. Practise using hedged but clear language, especially in writing.