Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 51;   December 21, 2016: Problem Displacement and Technical Debt

Problem Displacement and Technical Debt

by

The term problem displacement describes situations in which solving one problem creates another. It sometimes leads to incurring technical debt. How? What can we do about it?
A diagrammatic representation of the Deer Island Waste Water Treatment Plant in Boston Harbor

A diagrammatic representation of the operation of the Deer Island Waste Water Treatment Plant in Boston Harbor. Ending years of noncompliance with federal water treatment regulations by Massachusetts, the Massachusetts Water Resources Authority began partial operation of the plant in 1995. It became fully operational in 2000. View a larger image

Addressing the problem of sewage treatment necessarily requires confronting the question of what to do with the various products it produces, while avoiding generating new problems. This diagram, and the explanation that accompanies it at the MWRA Web site, shows how the plant design solves the sewage problem while it avoids creating new problems. For example, the methane generated in the sewage digesters is collected and used in Deer Island?s on-site power plant to create steam that supplies hot water and heat for the facility. This process is one of many other renewable energy processes the plant employs.

Image courtesy Massachusetts Water Resources Authority.

In A diagrammatic representation of the Deer Island Waste Water Treatment Plant in Boston Harborenvironmental 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.  Problem Displacement by Intention Next issue in this series  Go to top Top  Next issue: Problem Displacement by Intention  Next Issue

303 Secrets of Workplace PoliticsIs 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

Comprehensive list of all citations from all editions of Point Lookout
[Jänicke 1990]
Martin Jänicke. State Failure: The Impotence of Politics in Industrial Society. University Park, Pennsylvania: Pennsylvania State University Press, 1990. p.47. Order from Amazon.com. Back

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

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

PizzaCritical Thinking and Midnight Pizza
When we notice patterns or coincidences, we draw conclusions about things we can't or didn't directly observe. Sometimes the conclusions are right, and sometimes not. When they're not, organizations, careers, and people can suffer. To be right more often, we must master critical thinking.
A team raises a wall of a new home sponsored by the U.S. Department of Housing and Urban DevelopmentOrganizing a Barn Raising
Once you find a task that you can tackle as a "barn raising," your work is just beginning. Planning and organizing the work is in many ways the hard part.
The Messerschmitt Me 262, which was the first jet fighter to fly in combatHow to Foresee the Foreseeable: Preferences
When people collaborate on complex projects, the most desirable work tends to go to those with highest status. When people work alone, they tend to spend more time on the parts of the effort they enjoy. In both cases, preferences rule. Preferences can lead us astray.
Dunes in Death Valley, CaliforniaHill 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."
A switch in the tracks of a city tramwayThe Reactive Rescheduling Cycle
When the current schedule is no longer viable, we reschedule. But rescheduling is unlike devising a schedule before work has begun. People know that we're "behind" and taking time to reschedule only makes things worse. Political pressure doesn't help.

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

Forthcoming issues of Point Lookout

A white water rafting team completes its courseComing 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.
Tuckman's stages of group developmentAnd 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:

Reprinting this article

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

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.