On Assigning Responsibility for Creating Trouble

When we discover an issue within our organizations, two intertwined imperatives demand attention: "How did this happen?" and "What do we do about it?" As we address the former question, almost inevitably we begin to assign responsibility for creating the problem. Even if we succeed in avoiding blamefests [Brenner 2005], we can still make gross errors. To understand how many traps await us on the path to Truth, consider the example of technical debt.

Technical debt is any technological element that contributes, through its existence or its absence, to lower productivity or to a higher probability of defects in engineering efforts, or which depresses enterprise agility somehow. When we recognize it, we usually want to revise or replace some technological artifacts — or create what's missing — for sound engineering reasons. Technical debts can be found associated with enterprise assets of all kinds.

The causes of growth in technical debt are numerous, including — among many others — insufficient resources, schedule pressure, existing technical debt, changes in strategic direction, changes in law or regulations, and the risks associated with creating first-of-kind solutions to difficult problems. In most engineering activity, new technical debt is inevitable.

When technologists — engineers, their managers, or others in technical roles — try to alert the rest of the organization to the problems associated with accumulating technical debt, they often meet resistance from nontechnologists. Technologists usually respond to this resistance by explaining technical debt and its consequences, and sometimes they do receive the resources, time, and cooperation they need to start retiring the accumulated technical debt, and to avoid adding more debt to the burden the enterprise already carries.

But explaining rarely works, for reasons beyond mere misunderstanding the issue. One fundamental problem is the term technical debt. Nontechnologists must be forgiven for believing that since technical debt is inherently technical, it follows that its causes are also technical; that technologists are solely responsible for creating technical debt, and nontechnologists play no role. That is, of course, false.

A second Language, stereotypes, and
assumptions can conspire
to confuse us about the
causes of problemscause of misconceptions about the causes of technical debt lies in the assumptions we make about what diligent work looks like. Many nontechnologists have roles in General Management, Sales, Marketing, or Business Development. They're working hard when they're in contact with each other or with people external to the enterprise. They're traveling, conversing by telephone, or hosting meetings. By contrast, technologists are working hard when they're at their (real or virtual) desks, or attending (real or virtual) meetings on premises. They do attend meetings off premises, but they do so at much lower rates than do nontechnologists.

When nontechnologists assess the technologists' work ethic, they tend to use the same standards and assumptions they apply to themselves. They under-estimate the technologists' activity level because outwardly, technologists appear more often to be what nontechnologists would regard as "idle" — sitting at their desks. [Schein 2004]

And so language, stereotypes, and assumptions conspire to lead some to believe that technologists are solely responsible for technical debt. Proceeding from that conclusion, finding a resolution of the problem will be difficult indeed. Language, stereotypes, and assumptions can be traps.  Top    Next Issue

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

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 Conflict Management:

What Insubordinate Nonsubordinates Want: II

When you're responsible for an organizational function, and someone not reporting to you won't recognize your authority, or doesn't comply with policies you rightfully established, you have a hard time carrying out your responsibilities. Why does this happen?

Impasses in Group Decision Making: II

When groups can't reach agreement on all aspects of an issue, the tactics of some members can actually exacerbate disagreement. Here's Part II of an exploration of impasses, emphasizing two of the more toxic tactics.

Toxic Conflict in Virtual Teams: Minimizing Authority

Toxic conflict in virtual teams is especially difficult to address, because we bring to it assumptions about causes and remedies that we've acquired in our experience in co-located teams. In this Part II of our exploration we examine how minimizing authority tends to convert ordinary creative conflict into a toxic form.

Attributes of Joint Leadership Teams

The leadership of most teams, business units, or enterprises consists of a single individual. Others have joint leadership teams. What kinds of joint leadership teams are there, and what factors can affect their success?

Toxic Disrupters: Responses

Some people tend to disrupt meetings. Their motives vary, but their techniques are predictable. If we've identified someone as using these techniques we have available a set of effective actions that can guide him or her toward a more productive role.

See also Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Coming August 13: Leaving High-Touch Jobs: How

High-touch jobs require that we work closely with colleagues, teammates, clients, or suppliers. Because choosing to leave such a job affects all these people, and the person departing, we would do well find a path that respects all involved. Here are some suggestions. Available here and by RSS on August 13.

And on August 20: Earned Value and Goodhart's Law

Earned Value Management, widely used approach to project management, is most useful in contexts in which estimators are familiar with the Tasks, the Technologies, and the Teams. But even then, it is vulnerable to the tactics of those who game the metrics. Available here and by RSS on August 20.

Coaching services

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