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 non-technologists. 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. Non-technologists 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 non-technologists 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 non-technologists 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 non-technologists.

When non-technologists 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 non-technologists 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.

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:

Recalcitrant Collaborators

Much of the work we do happens outside the context of a team. We collaborate with people in other departments, other divisions, and other companies. When these collaborators are reluctant, resistive, or recalcitrant, what can we do?

Workplace Bullying and Workplace Conflict: II

Of the tools we use to address toxic conflict, many are ineffective for ending bullying. Here's a review of some of the tools that don't work well and why.

So You Want the Bullying to End: II

If you're the target of a workplace bully, ending the bullying can be an elusive goal. Here are some guidelines for tactics to bring it to a close.

Compulsive Talkers at Work: Peers I

Our exploration of approaches for dealing with compulsive talkers now continues, with Part I of a set of suggestions for what to do when a peer interferes with your work by talking compulsively.

Compulsive Talkers at Work: Peers II

Our exploration of approaches for dealing with compulsive talkers now concludes, with Part II of a set of suggestions for what to do when peers who talk compulsively interfere with your work.

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

Forthcoming issues of Point Lookout

Coming April 21: Choice-Supportive Bias

Choice-supportive bias is a cognitive bias that causes us to evaluate our past choices as more fitting than they actually were. The erroneous judgments it produces can be especially costly to organizations interested in improving decision processes. Available here and by RSS on April 21.

And on April 28: The Self-Explanation Effect

In the learning context, self-explanation is the act of explaining to oneself what one is learning. Self-explanation has been shown to increase the rate of acquiring mastery. The mystery is why we don't structure knowledge work to exploit this phenomenon. Available here and by RSS on April 28.

Coaching services

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

Public seminars

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.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.
   
• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.
   

Bullet Points: Mastery or Madness?

Decision-makers in modern organizations commonly demand briefings in the form of bullet points or a series of series of bullet points. But this form of presentation has limited value for complex decisions. We need something more. We actually need to think. Briefers who combine the bullet-point format with a variety of persuasion techniques can mislead decision-makers, guiding them into making poor decisions. Read more about this program.

• A recording of a program presented June 24, 2020, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.
   
• A recording of a program presented June 24, 2020, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.