Engineering Manager English: 1:1s, Performance, and Team Communication

Introduction

Becoming an engineering manager requires not just technical knowledge but also a new set of English vocabulary for conversations that do not happen in code. One-on-one meetings, performance reviews, career development discussions, and team health assessments all have their own language. For non-native English speakers, the shift from engineering vocabulary to management vocabulary can be challenging. This guide covers the most important terms and phrases that engineering managers use every day.

One-on-One Meetings (1:1s)

A 1:1 (pronounced “one on one”) is a regular, private meeting between a manager and a direct report — usually 30 to 60 minutes, weekly or bi-weekly. The vocabulary:

• direct report — someone who reports directly to you; “I have five direct reports”
• standing agenda — recurring topics that appear in every 1:1; “our standing agenda covers current work, blockers, and career development”
• blockers — obstacles preventing progress; “what blockers can I help you remove?”
• “What’s on your mind?” — a classic 1:1 opener that invites the direct report to set the agenda
• “How are you doing, really?” — asking about wellbeing, not just work status
• “What would make next week better than this week?” — a forward-looking question to identify improvements
• action items — specific tasks agreed upon in the meeting; “I will follow up with the design team — that’s my action item from today’s 1:1”

In 1:1s, the phrase “this is a safe space” is sometimes used to signal that the direct report can speak candidly without the conversation being used against them. Good managers create psychological safety for honest conversations.

Performance Reviews and Ratings

Performance review vocabulary is important for both managers and engineers:

• performance review (also performance appraisal) — a formal assessment of an employee’s work, usually annual or bi-annual
• meets expectations — standard performance; “this rating means you are delivering what is expected at your level”
• exceeds expectations — above-average performance; “this rating means you are consistently going beyond your scope”
• growth areas — aspects where the person should improve; “I want to be honest — collaboration is a growth area for you this half”
• calibration — a meeting where managers align on ratings across the team; “we calibrate ratings to ensure consistency across the organisation”
• feedback — input on someone’s performance; “I have some feedback for you about your communication in the last sprint review”
• constructive feedback — feedback that identifies issues and suggests improvements, phrased helpfully

The word “calibration” is important in larger organisations. In calibration meetings, managers compare their ratings and discuss individual cases to prevent inconsistency. An engineer rated “exceeds” in one team should be comparable to one rated “exceeds” in another.

Career Development Vocabulary

• career ladder — a document defining the expectations and competencies for each engineering level; “our career ladder has six levels from junior engineer to distinguished engineer”
• level up — get promoted to the next level; “what does she need to do to level up to senior engineer?”
• growth plan — a written plan for reaching the next career level; “we co-created a growth plan with specific milestones for the next six months”
• stretch goal — a challenging goal beyond the current scope, designed to build new skills; “leading the migration project is a stretch goal that will help him level up”
• sponsor — someone who advocates for your career internally, beyond just a mentor; “I am actively sponsoring her for the staff engineer track”

The distinction between mentor and sponsor is important in English: a mentor gives advice; a sponsor actively advocates for opportunities and advancement on your behalf.

Team Health and Engagement

Managers monitor team health with specific vocabulary:

• morale — the general mood and confidence of the team; “morale has dipped since the layoffs — I need to address it in our team meeting”
• engagement — how invested team members feel in their work; “engagement scores in the last survey dropped 10 points”
• psychological safety — the belief that you can speak up, disagree, or make mistakes without punishment; “low psychological safety leads to people hiding problems rather than surfacing them”
• attrition — team members leaving; “we have high attrition in the infrastructure team — I need to investigate the root cause”
• retention — keeping team members; “retention is my top priority this quarter”
• recognition — acknowledging good work; “public recognition in team meetings improves morale significantly”

Key Vocabulary

Term	Definition
1:1	A regular private meeting between a manager and a direct report
direct report	An employee who reports directly to you
calibration	A meeting where managers align on performance ratings across teams
career ladder	A document defining competencies and expectations at each engineering level
growth plan	A written plan for reaching the next career level with specific milestones
stretch goal	A challenging objective designed to build new skills
sponsor	Someone who actively advocates for your career advancement
psychological safety	The belief that you can speak up without negative consequences
morale	The general mood and confidence of the team
attrition	The rate at which team members leave the organisation

Practice Tips

1. Write 1:1 questions in English before each meeting. Prepare 3-4 questions that go beyond status updates: “What is challenging you most right now?”, “Is there anything I can do to make your work easier?”, “How are you feeling about your career direction?”

2. Practise giving feedback using the SBI model. SBI stands for Situation, Behaviour, Impact: “In yesterday’s sprint review (situation), you interrupted the product manager twice (behaviour), which made it difficult for her to finish her point and created tension in the room (impact).”

3. Learn the phrase “growth area” instead of “weakness.” “Growth area” is more constructive and focuses on development rather than deficiency. Using it signals that you see people as capable of change.

4. Use “calibration” correctly. When discussing ratings, say “we will calibrate next week” rather than “we will decide ratings.” Calibration implies a collaborative, consistent process — not an arbitrary decision.

Conclusion

Engineering management vocabulary — 1:1s, direct reports, calibration, career ladder, psychological safety, morale — describes a distinct set of professional conversations. Mastering these terms in English helps you conduct better meetings, give clearer feedback, and build stronger teams. For non-native speakers making the transition from engineering to management, learning this vocabulary is as important as learning the management practices themselves.

Engineering Manager English: 1:1s, Performance, and Team Communication – Continued

Let’s delve deeper into crafting effective conversations as an engineering manager. While technical expertise is crucial, the ability to communicate clearly and empathetically is what truly unlocks a team’s potential. This section focuses on refining your language around key areas like 1:1 meetings, performance feedback, and overall team health – particularly for those navigating English as a second language. Remember, it’s not about perfection; it’s about genuine connection and conveying your intentions effectively. We will explore phrasing that fosters open dialogue and constructive action.

Navigating the Nuances of 1:1s

One of the trickiest aspects is structuring a productive 1:1. Instead of simply asking “How are you?” (which can feel transactional), try framing it with questions that invite deeper reflection. Instead of “Did you complete your tasks?” – consider, “Let’s talk about what you worked on this week and any challenges you faced.” Notice the shift in focus; we’re moving from a simple status update to an opportunity for discussion. Using phrases like “What’s on your mind today?” or “I wanted to check in and see how things are going for you” (emphasizing ‘you’) demonstrates genuine interest. Avoid overly formal language when possible – a relaxed tone can encourage vulnerability.

Giving Constructive Feedback - The ‘SBI’ Model

Giving feedback, especially difficult feedback, requires careful phrasing. The SBI model – Situation, Behavior, Impact – provides a structured approach that minimizes ambiguity and defensiveness. “During the sprint planning meeting (Situation), you suggested a different approach to data validation (Behavior) which, while innovative, ultimately led to some integration issues later on (Impact). Let’s discuss how we can ensure similar situations are addressed proactively in future.” This allows for a focused discussion without immediately landing on blame. Another helpful phrase is “I observed…” instead of “You did…”

Building Team Health Vocabulary

Beyond individual conversations, understanding team dynamics is vital. Words like “synergy,” “collaboration,” and “psychological safety” are frequently used – but their meanings can be subtle. ‘Psychological safety’ isn’t just about being nice; it’s about creating an environment where people feel comfortable taking risks, admitting mistakes, and voicing dissenting opinions without fear of negative consequences. Phrases like “Let’s ensure everyone feels heard” or “How can we foster a more collaborative environment?” demonstrate awareness of this critical element.

# Example CLI Command (Git - Demonstrating Branching & Merging)
git checkout feature/new-ui -b new-ui
git add .
git commit -m "Added initial UI components for the new design"
git push origin new-ui

Key Takeaway: Focus on clarity, empathy, and structured communication. Practice using phrases that invite dialogue rather than dictating instructions. Remember, your goal is to empower your team members to thrive – clear language is a powerful tool in achieving this.