Managing High-Performing Teams
Who Could Benefit from This Talk?
- Managers of high-performing teams
- Managers trying to elevate team performance
- High performers seeking improved relationships
What Makes a High-Performing Team?
- Number of commits?
- Number of pull requests?
- Number of code additions/deletions (++/--)?
- Number of passing tests?
Lead Differently
- Redefine your traditional value-add
- There is a role for you!
But how?
Provide an atmosphere of trust, learning, empowerment
- "What" vs. "how"
- Safe space
- Meet commitments
Get out of their way
- Reduce bureaucratic overhead
- Suggestion: standups vs. written status reports
Provide shelter from distraction
- "First line of defense"
- Channel communications through you
- Caution: alienation
Know when (not) to insert
- Resist "nexus" mentality
- Tactical problem-solving vs. prioritization
- Servant leadership
- Suggestion: prioritize resolution need
Co-locate ("embed")
- Respect for creative process
- Observe working norms
- Reduce “ivory tower” misconceptions
- Promote "just-in-time" communication
Address under-performers
- Live/die as a team...to a point
- Mitigate drain and resentment
- Replace under-performers
Listen
- Communication occurs, but differently
- "Active listening"
- Parrot back to confirm understanding
- Have others parrot back
And remember...
- Leadership is needed
- Actively combat role ambiguity
- Challenge: lead differently!
- Your "gift"
Thank You
GitHub: tbickerton
Twitter: @timbickerton