Problem Displacement and Technical Debt

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 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

Footnotes

Your comments are welcome

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:

When All Your Options Are Bad

When you have several options, and all seem politically risky, what can you do? Here are two guidelines to finding your way to a good outcome.

Project Improvisation and Risk Management

When reality trips up our project plans, we improvise or we replan. When we do, we create new risks and render our old risk plans obsolete. Here are some suggestions for managing risks when we improvise.

Clueless on the Concept

When a team member seems not to understand something basic and important, setting him or her straight risks embarrassment and humiliation. It's even worse when the person attempting the "straightening" is wrong, too. How can we deal with people we believe are clueless on the concept?

Contributions, Open and Closed

We can classify contributions to discussions according to the likelihood that they stimulate new thought. The more open they are, the more they stimulate new thought. How can we encourage open contributions?

On Working Breaks in Meetings

When we convene a meeting to work a problem, we sometimes find that progress is stalled. Taking a break to allow a subgroup to work part of the problem can be key to finding simple, elegant solutions rapidly. Choosing the subgroup is only the first step.

See also Problem Solving and Creativity and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

Coming June 4: White-Collar Contractor Sabotage

Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.

And on June 11: More Things I've Learned Along the Way: VI

When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.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