An engineering manager may leave a meeting convinced that a task is clear, while the person taking it on has a different understanding of the goal. Communication is more than delivering a message: it means exchanging information, listening to the response, and checking that people share an interpretation. It matters in spoken conversations and writing, with technical and nontechnical audiences alike. section 5.4.1 section 15.3.4
Choose the approach that fits the conversation:
- Tailor the message. Decide what the audience needs to know, then make the point clear and relevant rather than getting lost in technical detail. Tact matters too: a comment about someone’s pace can damage morale even when the underlying concern is valid. section 2.5.12 section 15.3.4
- Make dialogue two-way. When discussing performance, listen to both perspectives, describe past actions, recognize good work, and agree on goals or improvements. Adapt feedback to the individual instead of assuming one style works for everyone. section 4.2.5
- Confirm delegated work. Explain why you chose the person, the desired outcome, available support, priority, milestones, and how you will coordinate. Invite questions and ask the person to explain the task back; that can reveal a mismatch early. section 5.4.1
- Leave a record when alignment must last. Discuss expectations early, document agreements, and revisit them through check-ins. For work spanning teams or long periods, meeting notes and a follow-up message give everyone something to consult. section 11.3.2
- Keep channels open for concerns. One-on-ones, team meetings, retrospectives, and surveys can surface morale problems, burnout risks, or conflicting cross-functional priorities. Hearing a concern is a start; work with people on the response. section 3.2.2 section 9.2.5
Aligning a project before work begins
A manager needs the team to understand the road map and product leadership to confirm the sizing. They bring both sides together, take detailed minutes, and share a follow-up email. The meeting lets people clarify expectations; the notes help them retain the agreement. section 11.3.2
Working through a disagreement
A cross-functional partner and an engineering team disagree about the scope of an operational-readiness document. They state their concerns and constraints, listen to each other, and agree on a shorter version containing essential metrics and mitigation plans. Open dialogue makes room for compromise without losing the shared launch objective. section 9.3.2
Communication improves with practice. Try regular writing and opportunities to speak, but also review a recent conversation: Did the other person have room to question your assumptions? What would you clarify, document, or ask next time? section 2.5.12 section 9.4
