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

Last updated: August 8, 2018

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 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 problems
cause 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. 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

[Brenner 2005]
See "Is It Blame or Is It Accountability?," Point Lookout for December 21, 2005, for more about blame and accountability. 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? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.comSend me your comments by email, or by Web form.

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:

A multi-function phoneDeniable Intimidation
Some people achieve or maintain power by intimidating others in deniable ways. Too often, when intimidators succeed, their success rests in part on our unwillingness to resist, or on our lack of skill. By understanding their tactics, and by preparing responses, we can deter intimidators.
A TSA Officer screening a passengerVirtual Termination with Real Respect
When we have to terminate someone who works at a remote site, sometimes there's a temptation to avoid travel — to use email, phone, fax, or something else. They're all bad ideas. Terminating people in person is not only a gesture of respect. It's good business.
A group of Emperor PenguinsWhat Do You Need?
When working issues jointly with others, especially with one other, we sometimes hear, "What do you need to make this work?" Your answers can doom your effort — or make it a smashing success.
An Africanized honeybee, also known as a killer beeRapid-Fire Attacks
Someone asks you a question. Within seconds of starting to reply, you're hit with another question, or a rejection of your reply. Abusively. The pattern repeats. And repeats again. And again. You're being attacked. What can you do?
Bowery men waiting for bread in a bread line in New York City in 1910Agenda Despots: II
Some meeting chairs crave complete or near-complete control of their meeting agendas. In this Part II of our exploration of their techniques, we emphasize methods for managing unwanted topic contributions from attendees.

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

Forthcoming issues of Point Lookout

An excavator loads spoil into rail cars in the Culebra Cut, Panama, 1904Coming October 23: Power Distance and Teams
One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.
John Frank Stevens, who conceived the design and method of construction of the Panama CanalAnd on October 30: Power Distance and Risk
Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

On 14The Race to the South Pole: Lessons in Leadership December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

The Power Affect: How We Express Our Personal Power

Many The
Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet 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.