Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 17, Issue 52;   December 27, 2017: On Assigning Responsibility for Creating Trouble

On Assigning Responsibility for Creating Trouble

by

When we assign responsibility for troubles that bedevil us, we often make mistakes. We can be misled by language, stereotypes, and the assumptions we make about others.
An engineer attending a meeting with 14 other engineers

An engineer attending a meeting with 14 other engineers. You can't see them, because they're at least 4,000 miles away in four locations.

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 problems
cause 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. Go to top Top  Next issue: Polychronic Meetings  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!

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Brenner 2005]
Richard Brenner. "Is It Blame or Is It Accountability?," Point Lookout blog, December 21, 2005. Available here. Back
[Schein 2004]
Edgar H. Schein, Organizational Culture and Leadership, Fifth Edition. San Francisco: Jossey-Bass, 2004, p. 33. Order from Amazon.com. Back

Your comments are welcome

Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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 Conflict Management:

Gen. Patton and Gen. Weyland photographed at Nancy, FranceWhat Insubordinate Nonsubordinates Want: III
When you're responsible for an organizational function, and someone not reporting to you doesn't comply with policies you rightfully established, trouble looms. What role do supervisors play?
A New England stone wallHow to Misunderstand Somebody Else
Misunderstandings are commonplace at work, as in most of the rest of Life. At work, they might be even more commonplace, because at work it sometimes seems that people are actually trying to misunderstand. Here's a handy guide for those who want to get better at misunderstanding others.
A field of corn severely stunted by droughtToxic Conflict in Virtual Teams: Virtuality
In virtual teams, toxic conflict sometimes seems to erupt spontaneously. People who function effectively in co-located teams can find themselves repeatedly embroiled in conflicts that seem to lack specific causes. What triggers toxic conflict in virtual teams?
A pariah dogPariah Professions: I
In some organizations entire professions are held in low regard. Their members become pariahs to some people in the rest of the organization. When these conditions prevail, organizational performance suffers.
President Obama meets with Congressional leadersEthical Debate at Work: II
Outcomes of debates at work sometimes favor one party, not only at the expense of the other or others, but also at the expense of the organization. Here's Part II of a set of guidelines for steering debates toward wise outcomes.

See also Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Photo of Jack Webb as Sergeant Joe Friday from the television series DragnetComing September 3: Contributions in Team Meetings: Advocating
An agenda in the form of an ordered list of topics might not provide an appropriate framework for a given meeting. For example, if A depends on B, and B depends on A, we must find a way to discuss A and B together in some orderly fashion. Here are some alternatives to linear, ordered agendas. Available here and by RSS on September 3.
A Venn Diagram of three setsAnd on September 10: Contributions in Team Meetings: Scoping
Some meetings focus on solving specific problems. We call them "working sessions." More often, we delegate problem solving to task teams, while meetings wrestle with the difficult task of identifying or "scoping" problems rather than solving them. Scoping discussions can be perilous. Available here and by RSS on September 10.

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:

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 Bluesky, 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.