As we saw last time, solving problems sometimes creates new problems. This phenomenon is called problem displacement (PD), though as I mentioned, the newly created problem or problems can be very different from the original problem. When that happens, problem replacement (PR) is probably a more accurate term. Although both PD and PR are often unintentional, they can also be most intentional indeed.
Below are some examples of intentional PD or PR in the organizational setting. In these fictitious examples, the Iris project needs (but doesn't have) a team member with knowledge of the (fictitious) HSL programming environment. The Hibiscus project does have HSL experts and often works with HSL. The Carnation project generally competes with Iris for staff and other resources. The Daffodil project depends on Carnation. Summary: Carnation Competes with Iris, Hibiscus has HSL experts, Daffodil Depends on Carnation, and Iris is Independent, but lacks HSL expertise.
- PD for damage control
- Suppose that Carnation's team member, Houdini, has truly magical HSL skills. If Iris is higher priority than Carnation, the sponsors and project managers of Carnation and Iris might agree to temporarily assign Houdini to Iris instead of Carnation. Overall it isn't a good solution, but it is the least bad.
- Iris no longer has an HSL skill shortage; now Carnation does. Staff reassignments like this are examples of intentional problem displacement.
- PR as a problem-solving approach
- In some cases of staff reassignment, the "donor" project can accommodate the temporary reassignment, with minimal sacrifice, because both the donor and receptor project managers can cleverly rearrange their schedules.
- Instead of solving the receptor's problem alone, donor and receptor solve their shared staff problem together. Replacing the original problem with a new problem makes a painless solution possible.
- PD as a problem-solving approach
- In an example of problem displacement, Iris transfers the HSL work to the Hibiscus project, which is heavily involved with HSL. Hibiscus is willing to take on the work (and budget) because it fits so well with what they're already doing. This eliminates the need to reassign Houdini.
- Some problems are actually in the wrong "place" when we first notice them. We can solve them using problem displacement.
- PD or PR as a political weapon
- Suppose that Iris's Problem displacement that threatens
the health and success of the
enterprise is not uncommonsponsor, Irv, regards Carnation's sponsor, Cheryl, as a rival. In what many would consider a breach of ethics, Irv tries to get Houdini reassigned from Carnation to Iris, not only because he needs Houdini's HSL expertise, but also because the reassignment will threaten his rival Cheryl's success. - This would be intentional, nefarious problem displacement. It threatens the health and success of the enterprise, and it is not uncommon. In a more sophisticated version, Irv's real target is Dan, who leads Daffodil, which depends on Carnation. By disrupting Carnation, Irv disrupts Daffodil.
By now I hope it's clear that so-called "unintended consequences" are not always unintended. When next you hear of unintended consequences, think carefully. First issue in this series Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Your comments are welcome
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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 Problem Solving and Creativity:
- Project Improvisation Fundamentals
- Project plans are useful — to a point. Every plan I've ever seen eventually has problems when
it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's
Part I of a set of tips for mastering project improvisation.
- Hill Climbing and Its Limitations
- Finding a better solution by making small adjustments to your current solution is usually a good idea.
The key word is "usually."
- Rationalizing Creativity at Work: I
- Much of the work of modern organizations requires creative thinking. But financial and schedule pressures
can cause us to adopt processes that unexpectedly and paradoxically suppress creativity, thereby increasing
costs and stretching schedules. What are the properties of effective approaches?
- Why Meetings Go Down Rabbit Holes
- When a meeting goes "down the rabbit hole," it has swerved from the planned topic to detail-purgatory,
problem-solving hell, irrelevance, or worse. All participants, not only the Chair, contribute to the
problem. Why does this happen?
- Contrary Indicators of Psychological Safety: I
- To take the risks that learning and practicing new ways require, we all need a sense that trial-and-error
approaches are safe. Organizations seeking to improve processes would do well to begin by assessing
their level of psychological safety.
See also Problem Solving and Creativity and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed