Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 19, Issue 16;   April 17, 2019: Gratuitous Complexity as a Type III Error

Gratuitous Complexity as a Type III Error

by

Some of the technological assets we build — whether hardware, software, or procedures — are gratuitously complex. That's an error, but an error of a special kind: it can be the correct solution to the wrong problem.
Prototypes of President Trump's "border wall."

Prototypes of President Trump's "border wall." Photo by Mani Albrecht, U.S. Customs and Border Protection Office of Public Affairs, Visual Communications Division.

As I've noted in an earlier edition, statisticians identified Type I and Type II errors about 70 years ago. Briefly, a Type I error is a false positive and a Type II error is a false negative. The concept of Type III errors is a generalization of these first two. The approach I favor is that of Raiffa [Raiffa 1968], who identified Type III errors as those errors in which one solves the wrong problem correctly. So, for example, building walls and fences to stop the flow into Nation A of refugees fleeing the violence of drug cartels in Nation B is a Type III error, because the problem isn't the flow of refugees into Nation A; rather, the problem is the violence of drug cartels in Nation B.

Gratuitous complexity in the design of technological products or technological infrastructure can also be a Type III error. By gratuitous I mean unwarranted by the application, or lacking justification in terms of the needs of those who use the asset. That is, a gratuitously complex system is one that could be replaced by a simpler design that would meet all present or near-term needs of stakeholders.

What makes gratuitous complexity a Type III error is that it doesn't usually arise by accident. That is, engineers and designers don't run around dreaming up complex designs because they couldn't think of how to meet the need more simply. While it's true that achieving elegant simplicity does require significant and intentional effort, there is a wide gap between elegant simplicity and gratuitous complexity. When a gratuitously complex system is proposed as a solution, something more than failure to achieve elegance is afoot. It's possible — even likely — that the proposed design is intended to solve problems other than the stated system requirements. Below is a little catalog of the problems gratuitous complexity might be intended to solve.

Boredom
People do get People do get bored from time to
time, especially when the work
they do seems repetitive and dated
bored from time to time, especially when the work they do seems repetitive and dated. To make things more interesting, engineers might redefine the problem they're solving in such a way that a more complex solution is required. From the perspective of the engineers, gratuitous complexity is solving the boredom problem, not the user's problem.
Political advantage
One can gain political advantage by becoming one of the few people who can deal with the complexity of the system under construction. But that works only if the system complexity crosses a threshold that's high enough. Gratuitous complexity can be the solution to political weakness.
Inability to shape strategy
Some technologists might have argued for a shift in organizational strategy, but failed to persuade decision makers to adopt it. By creating systems that meet the needs of the strategy they advocate, they can reduce the resources required to adopt the rejected strategy, which can make a future adoption decision more attractive. The engineer or designer is thus using gratuitous complexity to solve the problem of inadequate influence on organizational strategy.
Learning and practice
Some technologists use their task assignments to meet personal learning and practice objectives. To accomplish this, they must sometimes add complexity to what they construct to meet their personal needs, rather than the needs of the asset's stakeholders. Their work then demonstrates their grasp of current technology trends. If this mechanism occurs with significant frequency, it's possible that the employer's objectives are outdated, and this phenomenon could be interpreted as a warning to the employer.

If previous efforts, possibly involving different sets of assets, also included gratuitous complexity, the value of those efforts might be enhanced if the current effort exploits the gratuitous complexity of the past efforts. Eventually, the entire asset suite might be converted in this way. This phenomenon is among the more difficult to detect, because it seems to be confirmation of the wisdom of past design decisions. Although that might make sense technologically, it's a wasteful investment unless the organization intends to move in the direction those assets support. Go to top Top  Next issue: Big, Complicated Problems  Next Issue

303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Raiffa 1968]
Howard Raiffa. Decision Analysis: Introductory Lectures on Choices Under Uncertainty. New York: Mcgraw-Hill College, 1968. 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 Workplace Politics:

Ralph Waldo Emerson in 1846, in a charcoal portrait by artist Eastman JohnsonA Critique of Criticism: II
To make things better, we criticize, but we often miss the mark. We inflict pain without meaning to, and some of that pain comes back to us. How can we get better outcomes, while reducing the risks of inflicting pain?
A Hug-Free Zone posterUnwanted Hugs from Strangers
Some of us have roles at work that expose us to unwanted hugs from people we don't know. After a while, this experience can be far worse than merely annoying. How can we deal with unwanted hugs from strangers?
Small cage with canary used in testing for carbon monoxide after the Hollinger Mine fire on February 10, 1928On Being the Canary
Nobody else seems to be concerned about what's going on. You are. Should you raise the issue? What are the risks? What are the risks of not raising the issue?
A sea otter and pupPower, Authority, and Influence: A Systems View
Power, Authority, and Influence are often understood as personal attributes. To fully grasp how they function in organizations, we must adopt a systems view.
A horserace, which is a useful metaphor for the abuser's view of a conversationExploitation and Conversational Narcissism at Work: I
Exploitation of others is one of four themes of conversational narcissism. Knowing how to recognize the patterns of conversational narcissism is a fundamental skill needed for controlling it. Here are five examples that emphasize exploitation of others.

See also Workplace Politics 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.