In environmental science, and elsewhere, the term problem displacement describes what happens when solving a given problem creates a different problem. For example, sewage sludge disposal by incineration solves the sewage sludge disposal problem, but one consequence is air pollution [Jänicke 1990]. The term problem displacement is possibly a misnomer, because displacement typically refers to moving from one place to another. In most cases of problem displacement, the created problem or problems usually replace the original problem. For this reason, in these circumstances, I prefer the term problem replacement.
Problem replacement can also apply to problem solutions in organizations. It can be useful as a management tool, because it can clarify organizational status by accounting more accurately for all the costs of solving a problem. As an example, consider technical debt.
Technical debt is the collection of technology artifacts, arising by any mechanism, which we would like to revise or replace for sound engineering reasons. In many cases, if not most, organizations incur new technical debt as a consequence of solving some other problem. In our terms, much technical debt is the result of problem replacement.
For concreteness, consider upgrading a Customer Relationship Management (CRM) system. Suppose that because of financial pressures, the company decides not to upgrade the hardware that supports the CRM software. And suppose further, as is common, that the latest version of the CRM software requires a hardware upgrade. Consequently, upgrading the CRM software is impossible, which means that CRM system users must maintain existing applications — and develop new ones — based on the (now outdated) CRM software. They must later repeat that work when the new system is installed. It therefore comprises technical debt.
The debt in this example is not due to shoddy workmanship or shortcuts in implementing CRM applications. Rather, it's the direct result of "solving" the company's financial problems by postponing a hardware upgrade. It's an example of problem replacement.
In most In most organizations, the costs of
retiring software technical debt are
usually charged to the Information
Technology (IT) function. That
practice can obscure the
actual source of the problem.organizations, the costs of retiring software technical debts of this kind are usually charged to the Information Technology (IT) function. In our example, the cost of IT is thus represented as higher than it actually would be without problem replacement. Likewise, the cost of financial management is correspondingly represented as lower than it would be without problem replacement. A more accurate accounting would allocate to the financial management function, rather than to IT, the costs of carrying and eventually retiring the technical debt.
Because problem replacement scenarios are common in organizations, they account for a significant fraction of technical debt. The overstatement of the costs of the IT function, and the corresponding understatement of the costs of other enterprise elements, make responsible management of the enterprise difficult.
Some replacement problems can be termed unintended consequences. Perhaps some technical debt is unintentional. But some solutions that entail problem replacement, especially those that burden political rivals, are most intentional indeed. We'll explore examples of that phenomenon next time. Next 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 welcomeWould you like to see your comments posted here? rbrennwvAHuToaetcKYHPner@ChacxOYhRWZlTLJwdoKKoCanyon.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.
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.
More articles on Problem Solving and Creativity:
- What Haven't I Told You?
- When a project team hits a speed bump, it often learns that it had all the information it needed to
avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering
this kind of knowledge more systematically.
- We Are All People
- When a team works to solve a problem, it is the people of that team who do the work. Remembering that
we're all people — and all different people — is an important key to success.
- What Makes a Good Question?
- In group discussion or group problem solving, many of us focus on being the first one to provide the
answer. The right answer can be good; but often, the right question can be better.
- Design Errors and Group Biases
- Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of
many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.
- Tackling Hard Problems: I
- Hard problems need not be big problems. Even when they're small, they can halt progress on any project.
Here's Part I of an approach to working on hard problems by breaking them down into smaller steps.
Forthcoming issues of Point Lookout
- Coming April 25: Narcissistic Behavior at Work: VI
- Narcissistic behavior at work distorts decisions, disrupts relationships, and generates toxic conflict. These consequences limit the ability of the organization to achieve its goals. In this part of our series we examine the effects of exploiting others for personal ends. Available here and by RSS on April 25.
- And on May 2: Narcissistic Behavior at Work: VII
- Narcissistic behavior at work prevents trusting relationships from developing. It also disrupts existing relationships, and generates toxic conflict. One class of behaviors that's especially threatening to relationships is disregard for the feelings of others. In this part of our series we examine the effects of that disregard. Available here and by RSS on May 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenRkKAaszoXnFngFDHner@ChacuPXDVoMlktSObCzToCanyon.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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.