Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 22, Issue 7;   February 23, 2022:

Disproof of Concept

by

Proof-of-concept studies of system designs usually try to devise solution options and discover the system's operating constraints. But limitations can become clear too late. A different approach — disproof of concept — can be a useful alternative.
RMS Titanic departing Southampton on April 10, 1912

RMS Titanic departing Southampton on April 10, 1912. Widely acclaimed as "practically unsinkable," she sank in the early hours of April 15, on her first crossing of the Atlantic. Even the word practically couldn't sufficiently protect the prognosticators from risk. Photo by F.G.O. Stuart (1843-1923), courtesy Wikipedia.

A common pattern in problem solving and product development is known as proof of concept (POC). In a proof-of-concept exercise, we charter a team and give them access to what we believe to be a package of resources sufficient for building a demonstration of the concept we're trying to study. It seems like a reasonable approach. Proof of concept limits risk by limiting the scale of the trial. Then, so the theory goes, if the trial works we can scale up with a great degree of confidence. If the trial doesn't work, we make adjustments and try again. But for problems that require much scaling up proof-of-concept is an unsafe choice. The approach we really need is disproof of concept.

Bias in the proof-of-concept concept

The goal The name "proof of concept" is
actually part of the problem.
It communicates and reinforces
the bias of the investigation.
of proof-of-concept exercises is to find a way to make the big idea work. That's why we call them proof-of-concept exercises. To achieve that goal, the team makes a string of decisions and assumptions designed to help it reach the goal. The problem with this approach is that it encourages a bias. That bias arises from three factors: the name of the POC approach, a conflict of interest, and the politics of POC teams.

The name "proof of concept"
The name "proof of concept" is actually part of the problem. The name communicates and reinforces the bias of the investigation. In essence, the team isn't investigating the properties of the concept or any preliminary implementation of the concept. Rather, the name communicates the fact that the team is responsible for proving the validity of the concept. Instead of searching for adjustments that strengthen the concept, the team focuses on finding ways — any ways at all — to demonstrate that the concept works.
An inherent conflict of interest
The conflict of interest arises from the conflict between the overall goal — make the idea work — and another goal, often unspoken: find the weaknesses, misconceptions, and shortcomings in the concept under study. Indeed, some of these POC teams take as their charter the necessity of proving that the concept works. For them, failure is not an option. For them, the concept must work because they believe that failure to prove the concept would raise questions about their personal capabilities and, in some cases, their loyalty to the organization.
The politics of POC teams
To be a member of a POC team is to recognize the politics of failure. The framing of the team's mission is to prove the concept. Team success is defined as proving the concept. Team failure is failing to prove the concept. One result of this framing of the team's mission is the tendency of some POC teams to search for the set of special cases and circumstances in which they can prove the concept. Finding those circumstances enables them to declare that they achieved the goal, subject to constraints. Example: A POC team studying the plans for the Titanic might have found that the Titanic was a fine, safe, ocean liner provided it doesn't run into icebergs — or anything else unexpected. The problem with this kind of conclusion is that it isn't a proof of concept; it's a proof of concept with some very important contingencies. But politically savvy POC teams find it difficult to choose any other course.

Disproof of concept

A significant risk of the POC approach is that the POC team might expend resources — and more important, calendar time — discovering conditions and devising adjustments that make the concept workable. In one unfortunate scenario, the POC team does find conditions and adjustments that make the concept workable, but the conditions and/or adjustments aren't acceptable in anticipated field conditions. That is, the concept works in the POC environment, but it isn't feasible at full scale. For teams that want to avoid producing this outcome too late in the investigation to be helpful, a very useful alternative is an approach based on disproof of concept (DOC).

In the disproof-of-concept approach, the DOC team aims to find the "fatal flaws" in the concept as quickly as possible. It's actually a variant of the "fail faster" approach to innovation. The DOC approach recognizes that calendar time is the most precious of all resources. By uncovering fatal flaws early, the DOC approach affords designers and strategists early warning of the need for adjustments. And with early warning they have greater freedom and a wider array of options for making adjustments. Go to top Top  Next issue: Logical Presentation Can Be Ineffective  Next Issue

How to Spot a Troubled Project Before the Trouble StartsProjects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

Your comments are welcome

Would you like to see your comments posted here? rbrenEQuetChPjwYBDxmgner@ChacxXTxBssoFmfDfMugoCanyon.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:

A waterfall and spray cliff in the mountains of VirginiaThe Shower Effect: Sudden Insights
Ever have a brilliant insight, a forehead-slapping moment? You think, "Now I get it!" or "Why didn't I think of this before?" What causes these moments? How can we make them happen sooner?
A Lockheed L-1011 Tristar aircraft like the one flown by Eastern Airlines flight 401Problem Not-Solving
Group problem solving is a common purpose of meetings. Although much group problem solving is constructive, some patterns are useless or worse. Here are some of the more popular ways to engage in problem not-solving.
A 1934 Packard Eight LimousineSome Risks of Short-Term Fixes
When we encounter a problem at work, we must choose between short-term fixes (also known as workarounds) and long-term solutions. Often we choose workarounds without appreciating the risks we're accepting — until too late.
A rainbowNewtonian Blind Alleys: II
Some of our decisions don't turn out well. The nature of our errors does vary, but a common class of errors is due to applying concepts from physics originated by Isaac Newton. One of these is the concept of spectrum.
Out-of-service gas pumps during the Colonial Pipeline shutdownThe Expectation-Disruption Connection
In technology-dependent organizations, we usually invest in infrastructure as a means of providing new capability. But mitigating the risk of disruption is a more powerful justification for infrastructure investment, if we understand the Expectation-Disruption Connection.

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

Forthcoming issues of Point Lookout

Bottom: Aerial view of the Forth Bridge, Edinburgh, Scotland. Top: Inside the Forth Rail Bridge, from a ScotRail 158 on August 22, 1999.Coming June 1: Mental Accounting and Technical Debt
In many organizations, technical debt has resisted efforts to control it. We've made important technical advances, but full control might require applying some results of the behavioral economics community, including a concept they call mental accounting. Available here and by RSS on June 1.
A goose and goslingsAnd on June 8: Flexible Queue Management
In meetings of 5-30 participants, managing the queue of contributors can be challenging. A strict first-in-first-out order can cause confusion and waste of time if important contributions are delayed. Some meetings need more flexible queue management. Available here and by RSS on June 8.

Coaching services

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