insights you can use |
|
|
"Poor management can increase software costs more rapidly than any other factor." (Barry Boehm) Behind Closed Doors: Secrets of Great Management (Pragmatic Programmers) Archives Dec 2008 Nov 2008 Oct 2008 Dec 2007 Nov 2007 May 2007 April 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 April 2006 March 2006 February 2006 January 2006 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 Contents (c) 2003-2008 Esther Derby I also publish an occasional newsletter for people who manage in software organizations. If you'd like to receive the newsletter, drop me an email. It's on paper, so please include surface coordinates - name and full address.
Syndicate this site (XML)
|
Wednesday, November 03, 2004
Don't sell that child to the gypsies: remaining calm in the face of Sophie's Rule
A while back I posted a little riff on the question "Why?". We want to know why, but asking "Why?" isn't always the best way to find out. I offer alternative ways to ask the question. Reader Shannon Mann recently sent this response: The person asking is almost always wanting to know something else, and 'Why?' is their verbalisation of their confusion. When confronted by 'Why?', reflecting some part of the question back to the asker will often open doors to communication (and eliminate the internal strife of having someone question your credibility). Shannon describes how he responds when his child asks "Why?": ...the first asking of why, I give an answer, the second asking of why, I ask, 'Why do you think this is this way?' (or some such). Almost every time, the child already has a formed opinion and has little trouble explaining. I love this! I can imagine the conversation playing out with a my 3-year-old niece. I think it might be a bit dicey, though, if it's your boss asking "Why?" This is the conversation running through my head: Manager: Why is the release late? You: Why do you think the release is late? errr. I'm not sure the boss would take that very well. How about this: Manager: Why is the release late? You: I've thought about that a lot; what causes do you see from your point of view? (Sigh. I've done it again. I've restated a Why question as a What question.) And I do think this could lead to an interesting dialogue. Thanks for writing Shannon. (Sophie's Rule refers to Brian Marick's advice for learning about what customers do -- and why.) | |