Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 39;   September 29, 2010: Management Debt: I

Management Debt: I

by

Management debt, like technical debt, arises when we choose paths — usually the lowest-cost paths — that lead to recurring costs that are typically higher than alternatives. Why do we take on management debt? How can we pay it down?
Soldiers of IX Engineering Command, U.S. Army Air Force, putting down a Pierced Steel Planking (PSP) Runway at an Advanced Landing Ground under construction somewhere in France following the Normandy Landings of World War II

Soldiers of IX Engineering Command, U.S. Army Air Force, putting down a Pierced Steel Planking (PSP) Runway at an Advanced Landing Ground (ALG) under construction somewhere in France following the Normandy Landings of World War II. ALGs were the temporary airfields used by aircraft engaged in air support of Allied forces. One of the most serious challenges faced by the engineers was simply keeping up with the speed of the advance. This imbalance of capability between combat and engineering units can be viewed as one consequence of management debt. It is possible that a heavier investment in engineering capability, relative to combat capability, was required. Naturally, precise projection of the relative requirements was difficult prior to the event. In peacetime activities suitable precision is more easily achievable. Photo from "The Air Force Engineer", Army Air Forces Engineer Command, MTO.

The concept of technical debt has been useful to decision makers in the software engineering community, where it's used to evaluate relative costs of design choices. Choosing a low-cost approach that creates problems in the future is analogous to taking on a debt that incurs interest charges until it's repaid. Strangely, this metaphor isn't as popular in general management circles, where it may be even more useful as the concept of management debt.

Management debt arises as a consequence of making choices that might be very attractive in the near term, but which create recurring costs in the long term.

For instance, consider the problem of updating a mainframe-based IT operation. Although a less mainframe-intensive operation might be more effective, more nimble, and more compatible with today's labor market, the near-term cost of conversion can be staggering, due to the cost of replacing the capabilities of the custom software that has accumulated over the years. Continuing with the mainframe avoids those near-term costs, but it incurs ongoing costs in the form of inflexibility, high overhead, and inability to exploit modern technologies. These latter costs can be viewed as the interest on management debt resulting from a decision to defer payment of the "current bill" — namely, the cost of converting the mainframe operation.

Here are two essential insights about management debt for decision makers and those who support them.

It's not the debt that matters, it's the interest
Since actual financial debt is usually undesirable, we sometimes regard "management debt" as undesirable in an absolute sense. Not so.
Management debt isn't the problem. The problem is the "interest" — the long-term, recurring costs that result from the debt. When resources are allocated to paying the interest on management debt, the organization sometimes misses opportunities because of insufficient resources.
When deciding Management Debt is the
consequence of decisions
that favor low-cost
approaches carrying
long-term, recurring
costs
how to pay down management debt, emphasize those components that generate the highest recurring costs. Use the savings to pay down remaining debt.
Doing nothing usually seems best
There's a natural reluctance to commit large chunks of available resources to any effort, especially when that effort is unglamorous, or doesn't produce immediate revenue. We look longingly at alternatives that are more appealing, either because they do produce revenue, or because they generate good feelings or praise.
And when we do look longingly at alternatives, we tend not to focus on the long-term costs of failing to pay down management debt. Not recognizing these costs might be an example of the cognitive bias known as the Availability Heuristic. It's difficult to imagine the long-term costs of a decision, and it can even be difficult to accept the closely reasoned arguments of experts who are able to imagine those consequences. See ":wrapquotes" for more.

In Part II, we'll take a slightly more quantitative approach to management debt.  Management Debt: II Next issue in this series  Go to top Top  Next issue: Management Debt: II  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Update March 26, 2018

Although this article and the next have held up well over the years, my work in technical debt has provided several insights that relate to management debt.

Like technical debt, management debt can be incurred unintentionally
Like technical decisions, management decisions sometimes have unintended consequences. For example, as the result of an acquisition, integrating the assets of the IT operation of an acquired business into the combined business might be more difficult than anticipated. The ongoing efforts to integrate the two sets of assets can be viewed as the interest charges on management debt incurred as a result of the acquisition.
Interest charges on management debt can arise from external causes
Again using an acquisition as an illustration, consider the case in which part of the acquired business — call it Site Beta — is located apart from the rest of the combined enterprise. Management decides not to relocate everyone from Site Beta, to save costs. But there are costs associated with maintaining this separation, too, and they can be regarded as the metaphorical interest charges on the management debt incurred by not relocating Site Beta. These charges aren't due to external causes.
But now suppose that the products produced at Site Beta become wildly successful, because the new owners of Beta's principal competitor have decided to exit the market. As a result of the increased business, travel between Site Beta and the rest of the enterprise increases. This results in lost time, delays, and increased costs, which all contribute to the metaphorical interest charges associated with maintaining Site Beta as a separate operation. These additional costs are traceable to the unanticipated success of Beta's products, rather than to management's decision not to consolidate Site Beta with the rest of the enterprise.
Some management debt masquerades as technical debt
In the acquisition example above, describing the consequences of an acquisition, most would regard the IT asset integration difficulty as an instance of technical debt. My own view is that it is a technical manifestation of a management debt incurred in the course of the acquisition. The ongoing metaphorical interest charges ought to be charged to the acquisition, rather than to IT operations.

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 Personal, Team, and Organizational Effectiveness:

The blaming bossWhen Your Boss Attacks Your Self-Esteem
Your boss's comments about your work can make your day — or break it. When you experience a comment as negative or hurtful, you might become angry, defensive, withdrawn, or even shut down. When that happens, you're not at your best. What can you do if your boss seems intent on making every day a misery?
Address fileSnapshots of Squirming Subjects
Today we use data as a management tool. We store, recall, and process data about our operations to help us manage resources and processes. But this kind of management data is often scattered, out of date, or just plain incorrect, and taking a snapshot doesn't work. There is a better way.
A toasterSome Costs of COTS
As a way of managing risk, we sometimes steer our organizations towards commercial off-the-shelf (COTS) components, methodologies, designs, and processes. But to gain a competitive edge, we need creative differentiation.
Bill Moyers speaking at an event in Phoenix, ArizonaAsking Clarifying Questions
In a job interview, the interviewer asks you a question. You're unsure how to answer. You can blunder ahead, or you can ask a clarifying question. What is a clarifying question, and when is it helpful to ask one?
Virginia SatirCongruent Decision Making: I
Decision makers who rely on incomplete or biased information are more likely to make faulty decisions. Congruent decision making can limit the incidence of bad decisions.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness 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.