Gratuitous Complexity as a Type III Error

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 datedbored 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.  Top    Next Issue

Is 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

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 Workplace Politics:

The High Cost of Low Trust: I

We usually think of Trust as one of those soft qualities that we would all like our organizational cultures to have. Yet, truly paying attention to Trust at work is rare, in part, because we don't fully appreciate what distrust really costs. Here are some of the ways we pay for low trust.

The Risky Role of Hands-On Project Manager

The hands-on project manager manages the project and performs some of the work, too. There are lots of excellent hands-on project managers, but the job is inherently risky, and it's loaded with potential conflicts of interest.

Management Debt: I

Management debt, like technical debt, arises when we choose paths — usually the lowest-cost paths — that lead to recurring costs that are typically higher than alternatives. Why do we take on management debt? How can we pay it down?

Durable Agreements

People at work often make agreements in which they commit to cooperate — to share resources, to assist each other, or not to harm each other. Some agreements work. Some don't. What makes agreements durable?

Surviving Incompetence: II

When your organization undertakes a misguided effort that will certainly fail, you have options. One is to head for the exit. To search for a new position in such circumstances requires some care. Example: an internal transfer might not really be an exit.

See also Workplace Politics and Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

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