Avoid Having to Reframe Failure

Asked about his repeated failure to devise an electric light, Thomas Edison supposedly said something like this: "I have not failed 10,000 times. I have not failed once. I have succeeded in proving that those 10,000 ways will not work." There are disputes about the exact phrasing he used, but the gist of his message is clear: there is some value in failure.

Although his claim is valid, Edison certainly didn't set out to find those 10,000 ways that don't work. That's why his comment is somewhat humorous.

It's an example of reframing — the process of altering how we view concepts, situations, conditions, or events, usually by changing how we view the importance of contextual elements. In the example above, Edison emphasizes the often-ignored value of knowing which candidate solutions don't work.

Although reframing is helpful when we fail, succeeding is even better. Here are three tips for avoiding the need to reframe failure.

Design the approach to yield value independent of outcome

Although all efforts have (or should have) primary objectives, we can sometimes design our efforts so that failure to achieve the primary objective inherently contributes to a different success. For example, if Approach A fails, but Approach B can use much of the knowledge or infrastructure generated by having attempted A, then the failure of A leaves us in good position for B.

Intentionally interlocking solution approaches in this manner might require attempting a less-favored approach first, but the risk management benefits of inverted order can be attractive enough to make inversion sensible.

Define multiple objectives

Defining multiple objectives from the outset creates multiple opportunities for success, even if some objectives are more important than others. For example, in a proposal effort, winning the contract is the obvious primary objective. But making the cut to the final short list might also be an achievement, if we're employing process improvements and simultaneously studying their effects on proposal efforts.

Having multiple Although reframing is
helpful when we fail,
succeeding is
even betterobjectives generates value even if the primary objective isn't realized. Articulating them in advance makes reframing an undesirable primary outcome less necessary, because success in achieving the secondary objectives is so evident.

Shorten the goal horizon

Primary objectives that are achievable only after large-scale investments of resources and time tend to be less certain, because predicting outcomes of complex activities over long time scales is difficult. And with elevated levels of uncertainty come decreased probabilities of success.

By setting objectives that are achievable on shorter time scales, adjustments for unforeseen events, based on what we learn along the way, become more achievable. The learning then becomes part of the outcome, which is a success in itself. And we can apply that learning to the next set of shorter-range objectives.

All three of these tactics make available options that teams might not otherwise notice. What options have so far escaped your notice?  Top    Next Issue

Are 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!

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.

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 Project Management:

Seeing Through the Fog

When projects founder, we're often shocked — we thought everything was moving along smoothly. Sometimes, with the benefit of hindsight, we can see that we had — or could have had — enough information to determine that trouble was ahead. Somehow it was obscured by fog. How can we get better at seeing through the fog?

Nine Project Management Fallacies: III

Some of what we "know" about managing projects just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.

Managing Risk Revision

Prudent risk management begins by accepting the possibility that unpleasant events might actually happen. But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch resources by revising or denying risks. Here's a tactic for managing risk revision.

Long-Loop Conversations: Asking Questions

In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple question can take a day or more. And when the response finally arrives, it's often just another question. Here are some suggestions for framing questions that are clear enough to get answers quickly.

How We Waste Time: II

We're all pretty good at wasting time. We're also fairly certain we know when we're doing it. But we're much better at it than we know. Here's Part II of a little catalog of time wasters, emphasizing those that are outside — or mostly outside — our awareness.

See also Project Management and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Disjoint Awareness: Bias

Some cognitive biases can cause people in collaborations to have inaccurate understandings of what each other is doing. Confirmation bias and self-serving bias are two examples of cognitive biases that can contribute to disjoint awareness in some situations. Available here and by RSS on January 22.

And on January 29: Higher-Velocity Problem Definition

Typical approaches to shortening time-to-market for new products usually involve accelerating problem solving. Accelerating problem definition can also help. 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 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:

• 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 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 people 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.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.