A 1:1 is not a status update. It is the primary vehicle for building trust, surfacing blockers, understanding motivation, and developing the person in front of you. Done well, it is the highest-leverage 30 minutes in a manager's week.

The performance review is a formal moment in a continuous process. Its purpose is to reflect on a period, recognise impact, and agree on direction - not to deliver verdicts. When it is run well, both parties leave with clarity and energy.

A Personal Development Plan is a living document that connects where someone is now to where they want to go, with concrete actions and manager support. Most PDPs fail because they are activity lists, not outcome maps.

A Performance Improvement Plan is a formal process for addressing sustained underperformance. It should be the last step before formal action, not the first. When used correctly, it provides clear expectations, genuine support, and a fair opportunity to recover. When used incorrectly, it is a managed exit with extra steps.

A career conversation is a dedicated, unhurried conversation about where someone wants to go and what it will take to get there. It is distinct from a 1:1, a performance review, and a development plan review. Most engineers never have one. Most managers never initiate one.

A talent review is a structured conversation about the development needs, retention risks, and growth potential of every person in the team. When run well it surfaces things that 1:1s miss and creates a shared picture of the team's capability and future.

A calibration session is where managers compare their assessments of people at the same level to ensure consistent standards are being applied. It is the mechanism that prevents the same word meaning different things to different managers.

A resignation is often a surprise. It does not have to be. When handled well, the departure process protects relationships, surfaces learning, and leaves the door open. When handled badly, it poisons the team and damages your reputation.

Onboarding is not admin. It is the process of turning a new hire into a contributing, connected, confident team member. Most onboarding fails because it front-loads information and under-invests in belonging, context, and early wins.

A hiring loop is the structured sequence of interviews that assesses a candidate against defined criteria. When it is well designed, every interviewer knows what they are assessing, evidence is captured consistently, and the debrief produces a clear, defensible decision.

Engineering managers are often given budget responsibility without budget training. Understanding how to read a budget, track spend, forecast accurately, and make trade-off decisions is a core management capability - not a finance team problem.

FinOps is the practice of bringing financial accountability to cloud spending. For engineering managers, it means understanding where your cloud costs come from, which teams and services drive them, and how to create a culture of cost-conscious engineering without slowing delivery.

Team conflict is inevitable. How a manager responds to it determines whether it becomes a learning moment or a festering problem. The instinct to smooth things over quickly is usually wrong - most conflict needs to be named, understood, and worked through, not suppressed.

Team restructures are common and often necessary. They fail not because of the design but because of the communication, the timing, and the failure to understand what people actually need to hear. A restructure done well can energise a team. Done badly, it triggers a wave of resignations.

A role profile defines what a role exists to achieve, what the person in it is accountable for, and what capability is expected at each level. It is the foundation of fair hiring, clear performance conversations, and consistent development. Most organisations do not have them. The ones that do have a significant advantage.