Coaching High-Performing Teams

or "How I found my way back to Software Development"

Tim Bickerton / @timbickerton

My story

How can you add value if you're not an engineer?

Provide an atmosphere of trust, learning, empowerment

• "What" vs. "how"
• Safe space
• Meet commitments

Get out of their way

• Reduce bureaucratic overhead

Provide shelter

• "First line of defense" against distractions
• Channel communications
• Caution: alienation

Know when (not) to insert

• Resist "nexus" mentality
• Tactical problem-solving vs. prioritization
• Servant leadership
• Suggestion: prioritize resolution need

Promote a respectful work environment

• Encourage constructively delivered feedback
• Encourage constructive challenging of status quo
• Example: OK to disagree, but provide a new suggestion

"Embed" (co-locate)

• 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...

• You can still add value by not writing a line of code
• You've been there
• You know how this works
• Use these "gifts" to coach high-performance

Thank You