Holding Back
February 24, 2015
I wrote last week in this space about the positive place for disagreement in organizations; and I held back on pushing the topic a bit further.
Sometimes an organization leader has to hold back. Sometimes the leader needs to recognize that the organization has more disagreement than it can handle and that taking on another topic for which much disagreement is likely would be like drinking from a fire hose.
In Leadership on the Line (HBS, 2002), authors Ronald Heifetz and Marty Linsky write that “leadership requires disturbing people – but at a rate they can absorb.”
Heifetz and Linsky describe the need to “orchestrate the conflict” in four steps:
- “Create a holding environment” – a safe place to interact.
- “Control the temperature” – turn the heat up to get people’s attention, and turn it down for them to cool off or to catch up.
- “Set the pace” – not too fast that we leave too many people behind; not too slow that we lose the vision and momentum.
- “Show the future” – remind people of the “orienting value” – that is, the positive reason to go through all the negative rancor.
Oyster Stew
November 13, 2015
Jonathan Swift, an 18th Century writer I was introduced to as an English major in college, grabbed my attention and loyalty with the statement, “He was a bold man who first ate an oyster.”
I’ve hated oysters for their look, their texture and their taste; and also because, as a child, oyster stew was the Christmas Eve fare that stood between me and the time when we could begin opening presents under the Christmas tree.
But I have loved Swift’s metaphor.
Imagine the courage – or the desperation – of the first person to eat an oyster … or any other ugly, slimy critter ... raw!
But it is often this person, bold or desperate enough, who looks past appearances to tackle something of such unpleasant prospects, who actually makes the discovery or connects the dots or makes the breakthrough necessary for real progress.
What are the most unappetizing issues before us? Transfers? Football scheduling? Specialization? What unappealing solutions might we be avoiding because they look so awful? Are we bold enough to take a bite out of them?