A project changes direction, and an engineer is reassigned from planned work. The team needs more than the new assignment: it needs to understand the priority, the effect on its road map, and how concerns can be raised. Transparency means sharing relevant information and explaining decisions to the people affected by them. It helps a team work with change rather than guess at what is happening. section 3.2.6 section 3.2.3
Transparency is not the same as disclosing everything. An engineering manager must keep people informed while protecting sensitive information. Explain goals, expectations, project obstacles, and changes to work; use discretion with individual performance details, feedback sources, and confidential personnel information. Psychological safety matters too: people need to be able to ask questions and offer feedback without fear of reprisal. section 3.2.3 section 4.2.1
Make transparency a regular practice:
- Share the mission, goals, expectations, milestones, and obstacles clearly and consistently. When priorities change, explain the decision and its reasoning, then take responsibility for the outcome. section 3.2.3 section 3.2.6
- Make room for questions and feedback through one-on-ones, team meetings, retrospectives, or anonymous surveys. Listen before assuming that everyone understands or agrees. section 3.2.3 section 9.2.5
- Give people insight into how decisions are made. Seek relevant team input, document agreements, and share the resulting plan with those who must act on it. section 9.3.1 section 11.4.2
- In performance conversations, make goals and expectations clear and deliver feedback privately. Discuss development without exposing the source of someone else’s feedback. section 4.2.1 section 4.3.3
- During a departure or layoff, communicate promptly about workload, knowledge transfer, and next steps. Acknowledge concerns while respecting confidentiality and legal constraints. section 8.3.1 section 4.5.3
When a teammate leaves
A key departure can leave colleagues worried about their jobs and burdened by unfinished work. Silence may intensify that uncertainty. A manager can explain the departure process, identify knowledge-transfer and task-reprioritization steps, and describe the hiring plan where appropriate—without sharing private details about the person who left. section 8.3.1 section 4.5.3
When teams revise a plan
Two teams agree to change priorities, allocate people differently, and adjust delivery dates. They record the decisions in a shared project tracker and email both teams the revised plan. The agreement becomes visible to the people responsible for carrying it out. section 11.4.2
A useful check before communicating is: Who is affected, what do they need to know to do their work, what reasoning will help them understand the decision, and what must remain private? Return with updates as circumstances change. Transparency builds trust through relevant, honest communication—not through indiscriminate disclosure. section 3.2.3 section 9.3.1
