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 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-2006 Esther Derby I also publish a quarterly 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)
Links |
Friday, June 30, 2006
The cost of anger
On his consulting blog, Jerry Weinberg says: "Anger, for a consultant, is a costly luxury, and I am by nature somewhat of a cheapskate. By eliminating there-then-them anger, I cut my angry outbursts in half. By noticing my pattern of anger escalation, I dampen nine-tenths of the remaining half to the point where it doesn't interfere with my consulting practice. That leaves only about 5 per cent of the angry episodes I used to have, just one in twenty. Although this seems a dramatic improvement in frequency, it doesn't result in an equally dramatic improvement in the cost of my angry outbursts." Anger is equally costly for managers: Managers who blow up when they hear bad news stop hearing information about problems until those problems can no longer hide. By that time, many avenues for action aren't viable any more, and the manager is left with few choices and poor options. Managers who display anger at the people who report to them -- belittling them in public or private -- lose trust, dampen creativity, and lower productivity. Managers who rail against other departments, units, or managers crush collaboration and joint problem-solving. Here's Jerry's explanation of there-then-them anger: "...sometimes I find myself growing angry at my clients, only to realize that I'm responding to something similar the client said or did at another time or place. Or perhaps I'm responding to something similar my mother used to say to me when I was five years old. Clearly, I'm going to have to bring my mind into the present context if I'm to be effective." This is more common than you might imagine. One colleague, Todd, realized that part of his difficult with a peer was that when the peer was upset, her facial expression mirrored the expression Todd's father wore when he was angry (and about to smack Todd). The there-then-them trigger doesn't have to be a person, it can be a situation. When someone (maybe you, maybe someone else) is in a there-then-them dynamic, the task is to bring that person into the present. One way to do that is to differentiate the past from the present by consciously noticing what's different about the person / situation in the present and the person / situation in the past. Sometimes it's the physical details (Todd's dad didn't wear glasses, and his peer does. His peer is female, not male. His peer doesn't have parental authority...etc). If you notice that you have angry outbursts, try journaling to see patterns in triggers or explore similarities with past interactions and events. The point isn't to eliminate emotion, but to not be hijacked by it, so that you can choose how to respond. | Sunday, June 25, 2006
Website 3.0
I just rollled out version 3.0 of my website. I've changed the look a bit, added search and updated the list of articles. I removed some out-dated material. And I've made the site easier to maintain. Which, in theory, means I'll update it more often. In the next few weeks, I'll update the articles-by-topic index and add more articles (I added Entrust to Another, a blog post grown up to be an article). There are over 25 articles on the site now, I've lots more to add. | Monday, June 19, 2006
A Compensation Story
| Monday, June 05, 2006
Making Good Teams Great
I didn't make a single post in May. That's because I was working on Agile Retrospectives: Making Good Teams Great, which I co-authored with Diana Larsen. It's due out in July from the Pragmatic Bookshelf. Yippee! | getting ready to coach I recently talked to a person who billed himself as a coach. Here's how he expained what he does: "I explain the obvious to the stupid." Oh, my. It isn't very helpful to dismiss the people as stupid. They may not know as much, or have as much experience. But no matter how hard this guy tries to hid it, his contempt will leak through. So inspired by that conversation, I wrote a little article on perparing for coaching. It's on the Scrum Alliance site. | |