Tuesday, October 16, 2012

Listening to Your Team


Sometimes for a retrospective, I'll have a team play the ball point game. I do this because it let's be see the team dynamics as a whole in only 20 minutes. Is someone dominating the rest of the team? Is this a team afraid to take risks? Is this a team that innovates? Is this a team that has trust, is close and works well together, or are they a group of individuals who begin to blame and finger-point when the pressure is on?

Recently I had a picture of a team that was unique to me, but perhaps common to others. It was a team that I would give an A+ to for effort and energy. They were trying as hard as the possibly could, and that was part of the problem. They were so intense, so focussed, trying so hard that they weren't listening and giving weight to everybody's ideas. Instead, in the craziness and loud voices, it seemed they found themselves guided (or more appropriately, driven) by the energy and passion of a few.

After several iterations, and even my sharing with them the performance I've seen from the vast majority of other teams, they were beginning their next iteration with exactly the same approach as before, yet committing to significantly more work. "What changes have you made since last sprint?" I asked. "We are going to be more focussed!" they said emphatically. I wish you could have seen the situation - these guys had been giving more effort and energy than a playoff team, yet were saying the missing key to success was focus? Essentially, they were saying they were going to try harder, but make no other changed and more than double their productivity.

In the quiet moment while I had their attention, I asked if anyone on the team had any ideas that hadn't been tried yet. Immediately, one then two then three people shared great ideas that would enable the team to hit their goal. Now, these people sharing their ideas were not the loud, gregarious, driving leaders. They were more likely introverts. Just like the ones that statistically make up the majority of your technical team.

Often, I'll lead retrospectives by having everyone write down their thoughts one what's going well, not-so-well, and any ideas. This ensures that I hear the voice of even the quietest (or newest or youngest) team member. Our agile teams do not succeed based on the old, traditional approach of a project manager in charge who, often, is expected to make all decision (and therefore often the only person trying to solve all problems). Agile teams rely on collective intelligence. The same way that Google has come up with great products such as AdWords and Maps, or the way that Barrick Mining found fresh approaches to find where to mine based on contest submissions from around the world (as described in Mavericks at Work). 

No one of us is as smart as all of us, so make sure that you're creating space to hear all voices and great insights of your team.

1 comment:

Mike tyson said...
This comment has been removed by a blog administrator.