As a project risk manager one of your risks is that a member of the team does not know something that they need to know in order to get a task done.
Some people ask for help when they are stuck or unsure. Some don’t. People who do not ask for help when they should are an added risk to your project.
I’d be interested to hear what others do about this. I think pairing is a great way to surface this risk.
When I interview someone for a role I keep asking questions until the candidate says “I do not know” or “I’d have to ask someone else” or some such variant. If they cannot admit they do not know something, they are a very real potential risk to the project. When they know more about a subject than I do, I will get someone else who is an expert to probe their knowledge. The area where you are most at risk is in their area of greatest competence as it is here that they are least likely to ask for help.
June 24th, 2011 at 4:33 pm
Completely agree. I’ve even caught myself doing this a few times.
I call some of this playing “intellectual chicken”.
The trick is having people around who are willing to promote the sharing of what they don’t know. Even to the point of having one of your team act as a stooge. You could set up a deliberate game where the team take it in turns to ask “stupid” questions to ensure everyone makes a point of doing so – either on a per-day rotation or everyone in a single session.
Funnily enough I wrote up my thoughts on this recently 🙂
There was also a great article in Computing magazine a few years ago called “the strange truth about developers” that really hit this on the head for me – Unfortunately I’ve not yet found a copy of it online.
September 1st, 2011 at 8:47 am
@Captain Crom: I’ve got a PDF version of the ‘Strange Truth…’ article, and if anyone is interested, feel free to connect with me on LinkedIn – http://uk.linkedin.com/in/coachkidd