Transparency makes project information, decisions, progress, risks, and limitations visible and understandable to the people who need them. It supports trust, accountability, realistic expectations, and timely problem-solving. section 8.4.3 section 9.2.1
Practice transparency through deliberate communication:
- Schedule regular meetings, send updates, and use collaboration platforms to keep concerns and progress visible. section 8.4.3
- Report completed milestones, upcoming tasks, roadblocks, risks, and the steps being taken to address them. section 8.4.3
- Explain limitations calmly and propose alternatives instead of dismissing requests or promising unrealistic outcomes. section 8.4.3
- Give direct, constructive feedback, including unpleasant news, rather than using white lies to avoid conflict. section 9.2.1
- Provide context and feedback loops, using clear language that works across cultural and language differences. section 7.3.3
A transparent deployment
Automated deployment messages left a team confused because they lacked project-specific context. A lead developer instead explained when each step would begin, what to expect, and which tasks people needed to perform. The deployment became faster and produced fewer errors. section 7.3.3
Transparency in mentoring
A mentor who praised code but silently changed it withheld useful criticism and limited the mentee’s growth. Comments in code reviews would have made the reasoning visible and turned the changes into a learning opportunity. section 9.2.1
