Once upon a time, an engineering consulting company hit a speed bump. Revenue was falling so fast that staff attrition couldn't keep up with the contraction. So management leapt into action, declaring a salary freeze.
But there was a carrot — if the company met its revenue target, everyone would get a bonus. In consulting, revenue equates roughly to billable hours, so the engineers did their best to help Marketing find business. Trouble was, there wasn't enough business.
With less than a month to go before the CEO's annual state-of-the-company address, Management announced a buy-out for people close to retirement. After his address, in Q&A, a bright engineer asked him, "Since so many are taking the buy-out, we won't have enough billable hours left to meet the bonus target. Does this mean there's no bonus?"
Jacques, the CEO, was blind-sided, but he was no dummy. He knew that if he said yes, he could expect an exodus of his best engineers. So he replied, "I'll have to get back to you on that." Back in the calm of his office, Jacques and his team worked out the right answer: "We'll lower the bonus target proportionately."
So they issued a memo, and everyone relaxed some. But Jacques had been embarrassed at a time when he needed to show strong leadership. He probably wasn't ready for that question because it involved an intersection of two unrelated policies. Since there are so many policies in any company of even moderate size, the number of such intersections is large, and it's difficult to anticipate which intersections cause problems.
The executive team goofed, as most do now and then. Yet, even though we test our products thoroughly, we rarely test organizational changes before we "roll them out." It's a high-risk practice, because we end up testing our change plans using the company itself. To limit that risk, we must discover defects in change efforts before we execute them, and one approach that works well is the simulation.
Even though we test
our products thoroughly,
we rarely test organizational
changes before we
"roll them out"Simulations — sometimes called "games" — parallel reality. They're especially valuable when the event being simulated is high-risk. That's why the military runs war games, and why US presidential candidates run mock debates.
Simulations do require planning to ensure that they're faithful to reality, and you do need a skilled facilitator. But you can use simulations to test almost any organizational effort — process designs, project plans, test plans, reorganizations, mergers and acquisitions, marriage proposals — anything. Simulations can be off-site and small-scale, and you can use stand-ins for the actual players if security is an issue.
Next time you have that queasy feeling about your plans, look before you leap — simulate. Top Next Issue
Is your organization embroiled in Change? Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt? Read 101 Tips for Managing Change to learn how to survive, how to plan and how to execute change efforts to inspire real, passionate support. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Organizational Change:
- When Fear Takes Hold
- Leading an organization through a rough patch, we sometimes devise solutions that are elegant, but counterintuitive
or difficult to explain. Even when they would almost certainly work, a simpler fix might be more effective.
- Good Change, Bad Change: II
- When we distinguish good change from bad, we often get it wrong: we favor things that would harm us,
and shun things that would help. When we do get it wrong, we're sometimes misled by social factors.
- When Change Is Hard: I
- Sometimes changing organizations goes smoothly. More often, it doesn't. Whatever methodology we use
— and there are many methodologies available — difficulties can arise. When change is hard,
what's happening? What makes change hard?
- Obstacles to Finding the Reasons Why
- When we investigate what went wrong, we sometimes encounter obstacles. Interviewing witnesses and participants
doesn't always uncover the reasons why. What are these obstacles?
- The Expectation-Disruption Connection
- In technology-dependent organizations, we usually invest in infrastructure as a means of providing new
capability. But mitigating the risk of disruption is a more powerful justification for infrastructure
investment, if we understand the Expectation-Disruption Connection.
See also Organizational Change and Organizational Change for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More