PMP Practice: Support diversity and inclusion

Effective servant leadership in hybrid environments requires adapting to individual team member needs rather than applying a one-size-fits-all approach. Different team members have different levels of experience, confidence, and preferences for autonomy versus structure. A skilled project manager recognizes these differences and flexes their leadership style accordingly—providing clear direction and task breakdown for those who benefit from it, while empowering others with the autonomy they need to thrive. This situational leadership approach honors both the agile principle of self-organizing teams and the reality that not all team members are at the same point in their development journey. Since velocity is stable and the tension is about leadership style rather than performance, adapting the approach to individual needs directly addresses the root cause without disrupting team composition or imposing unnecessary process overhead.

**Why not A:** Forcing a uniform leadership style ignores individual differences in how team members work best. Some people genuinely perform better with more structure while others excel with autonomy. Standardization would likely frustrate half the team regardless of which style is chosen, and fails to demonstrate the situational awareness and adaptability that effective leadership requires.

**Why not C:** Removing team members who have different working preferences is premature and damaging. The team's velocity is stable, indicating no performance problem. Transferring people disrupts both teams and treats natural variation in work preferences as a defect rather than an opportunity for adaptive leadership. This also signals to the team that the project manager cannot handle diversity in working styles.

**Why not D:** While mentoring can be valuable, it does not address the immediate leadership issue. The developers who want more direction are not necessarily less experienced—they may simply work better with more structure. Creating a formal program adds process overhead and implies that preferring structure is something to be 'fixed' rather than accommodated. The core issue is Aïcha's leadership approach, not peer-to-peer development needs.