Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 21, Issue 23;   June 9, 2021:

Self-Imposed Constraints

by

When we solve problems, the problem definition and associated constraints determine the possible solutions. Sometimes, though, solving the problem is unnecessarily difficult because we accepted self-imposed constraints as real. How can we avoid that?
A meeting at a whiteboard

A meeting at a whiteboard. Exchanging views about a problem sometimes requires nonverbal methods.

When we're solving problems, we sometimes unintentionally impose constraints that make solving easy problems difficult and solving difficult problems impossible. Relaxing these constraints is rare because we so rarely recognize that the constraints are self-imposed. Sometimes we incorrectly regard these constraints as part of the original problem, and therefore not subject to alteration.

After changing these self-imposed constraints, problem solutions often become easier to find. Because the challenge is to recognize self-imposed constraints, it's helpful to have a handy checklist of the common forms they take. With checklist in hand we can inspect the problem definition and the associated solution constraints. When we find a constraint that's on this list, we can recognize it as a candidate for alteration or removal.

Here's a list of these patterns of self-imposed constraints. Maybe you can add more.

We can't revise the problem definition because it's complete and correct
In many cases the person or persons (the "problem-posers") who constructed the problem definition don't belong to the group charged with solving the problem (the "problem-solvers"). In these situations there's a tendency for the problem-solvers to accept the problem definition without questioning it. Sometimes this happens, in part, because the problem-posers outrank the problem-solvers politically, and the problem-solvers don't feel authorized to question the problem definition.
But until careful study begins, we can't be certain that the problem as posed actually has a solution. Or a solution might exist, but it isn't consistent with pertinent laws or regulations. Some problems have no solutions. Verify that what the problem-posers want is actually legal, that it conforms to the laws of Physics and Economics, and that it makes logical sense. You don't want to be engaged in a search for the cheapest way to turn marshmallows into gold.
That way isn't the best way
Suppose the problem-solvers have found an approach that seems to be workable. The approach has provided a path around all known obstacles. But someone has expressed a general feeling that there's a better way. This pattern can appear when solving problems of any scale, from World Hunger to the order of the items in a meeting agenda.
The odd We sometimes unintentionally impose
constraints that make easy problems
difficult and difficult problems impossible
thing is that for most problems, the group's charter has no language that commands, "Find the best solution." But we search for the best solution anyway. That can be wasteful, because good enough often is good enough. Complex problems rarely have a "best" solution. See "Problem Defining and Problem Solving," Point Lookout for August 3, 2005, for more.
We can't afford (or have no time for) experimentation
Some problems have solutions that become evident only after we try a series of candidate solutions, either in real life or in simulation. But trials — even simulated trials — require resources. When those who control those resources refuse to provide them, finding acceptable solutions can be more difficult. That's life. But when we decide not to request the resources necessary for trial solutions, or when we don't even think of experimenting with trial solutions, or when we fail to make clear the full costs of parsimony, we're imposing an unnecessary constraint on our own problem-solving process.
Try some experiments as a way of exploring possibilities. Start by making simplifying assumptions that might not be justifiable in the real problem. Be careful. Experiments have a way of morphing into prototypes that then become the solutions. This happens, in part, because people want to recover the costs of the experiments. Before constructing the real solution, terminate all experiments. Start the real solution from a clean sheet.
The solution to this problem will be much (cleaner, cheaper, …) if we do X first
When the problem at hand (I'll call it P) is to enhance or build upon existing assets, a common pattern involves attending to those assets (the X referred to above) before solving P. While doing so might be wise if the problem solution is already in hand, it's a dubious strategy if the solution to P is understood only in broad outlines. Actually solving P frequently produces new information that can alter views about exactly what X entails.
Undertaking X first is risky, because it defers P. There's a high bar to meet whenever we defer one problem to address another. That pattern can repeat recursively: as we defer P to handle X, we then find a third problem Y that causes us to propose deferring X until we deal with Y, and so on. If tackling X before solving P really is a good idea, then it's worth doing on its own merits. Consider putting X in the queue as backlog to be cleared after the work on P is completed. In other words, take on some technical debt (X) until the more immediate issue (P) is cleared. P might need some rework later, and that is a consideration, but do consider it.
Failed attempts are failed attempts; move on
When we try a candidate solution, and discover an insurmountable obstacle that renders it a failure, we can rule out that candidate. But there is usually value in understanding the details of the failure. Moving on without capturing that knowledge can be an expensive mistake. For example, a clear understanding of one failed candidate solution can be useful for adjusting other candidate solutions before studying them.
Design your solution attempts so that you can harvest value even from failure. If they succeed, fine. But if they fail, they should fail in ways that expand your knowledge and understanding of the problem. This means that you need to gather enough data along the way so that even if an approach fails, it helps you formulate new approaches, or suggests ways to modify other failed approaches.
Pictures don't lie: diagrams are complete and unbiased
Solving some problems entails constructing and interpreting graphic representations of concepts and relationships. When these representations are displayed on screens, paper, or whiteboards, they are inherently two-dimensional. That's fine for many situations, but if higher dimensionality is needed, these graphical representations can only be approximations, and approximations can be misleading. Sizes and placement of representations of elements of the problem can convey biases that affect how we understand the problem and how we formulate solutions.
The biases that arise from the inherent limitations of two-dimensional diagrams are outside our awareness. That's one reason why intentionally removing the biases can be so difficult. One approach that helps in some cases is redrawing the graphical representations in different ways, perhaps by different people. Scramble the diagrams. New insights might result.
Wait! There's more!
The problem-solvers found a solution to what the problem-posers asked for. But as they were implementing it, they realized something they could add (call it X) with what seemed to be just a bit more work. And that additional capability would surprise and delight everyone. The problem-posers weren't actually asking for X, but the problem-solvers were certain that they would be pleased.
If the additional work really is just a "bit," then of course, just do it. But that case is rare indeed. Almost always, the additional work is a budget buster.
Solving the more general case
The problem-solvers found a solution to what the problem-posers asked for. But as they were implementing it, they realized that their solution (call it X) was just a special case of a large class of problems for which they believe they have the general solution (call it X'). They believed that X' wasn't much more work than X, and that having X' in hand would surprise and delight everyone. The problem-posers weren't actually asking for X', but the problem-solvers were certain that they would be pleased.
This is another example of the actual implementation turning out to be far more work than it first seemed. Almost always, this is another budget buster.

Over time, solving many problems, you'll occasionally have "a-hah" moments when you suddenly realize how to solve the problem at hand. When that happens, ask yourself, "What was I assuming that prevented me from seeing this until now?" If you find an answer to that question, and it turns out to be a self-imposed constraint of a kind not included in this list, add it to your own list. And send me a note. I'd like to expand my collection. Go to top Top  Next issue: Organizational Roots of Toxic Conflict  Next Issue

101 Tips for Effective MeetingsDo you spend your days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenXEiRBfuFHUtjHrqUner@ChacpYPvvSVhUNIOeXHKoCanyon.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 Problem Solving and Creativity:

Helping each otherWhen We Need a Little Help
Sometimes we get in over our heads — too much work, work we don't understand, or even complex politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?
Captain Robert F. Scott and most of his team returning from the South PoleProject Improvisation and Risk Management
When reality trips up our project plans, we improvise or we replan. When we do, we create new risks and render our old risk plans obsolete. Here are some suggestions for managing risks when we improvise.
Stainless steel cutleryNew Ideas: Experimentation
In collaborative problem solving, teams sometimes perform experiments to help choose a solution. These experiments sometimes lead to trouble. What are the troubles and how can we avoid them?
Eugene F. Kranz, flight director, at his console on May 30, 1965, in the Control Room in the Mission Control Center at HoustonDesign Errors and Group Biases
Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.
An onion, sliced and dicedThe Rhyme-as-Reason Effect
When we speak or write, the phrases we use have both form and meaning. Although we usually think of form and meaning as distinct, humans tend to assess as more meaningful and valid those phrases that are more beautifully formed. The rhyme-as-reason effect causes us to confuse the validity of a phrase with its aesthetics.

See also Problem Solving and Creativity and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

Handling Q&A after a presentation, a situation in which formulaic utterances occur with elevated frequencyComing September 22: Formulaic Utterances: I
With all due respect is an example of a category of linguistic forms known as formulaic utterances. They differ across languages and cultures, but I speculate that their functions are near universal. In the workplace, using them can be constructive — or not. Available here and by RSS on September 22.
A collection of identical boltsAnd on September 29: Formulaic Utterances: II
Formulaic utterances are things we say that follow a pre-formed template. They're familiar to all, and have standard uses. "For example" is an example. In the workplace, some of them can be useful for establishing or maintaining dominance and credibility. Available here and by RSS on September 29.

Coaching services

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

Public seminars

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.

Bullet Points: Mastery or Madness?

DecisBullet Point Madnession 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.

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.