Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 7, Issue 11;   March 14, 2007: Trying to Do It Right the First Time Isn't Always Best

Trying to Do It Right the First Time Isn't Always Best

by

You've probably heard the slogan, "Do it right the first time." It makes sense for some kinds of work, but not for all. For more and more of the work done in modern organizations, doing it right the first time — or even trying to — might be the wrong way to go.

Many workplaces are festooned with "slogan posters," and sometimes they do have a positive effect. But sometimes they're unhelpful — even destructive. One slogan that can be especially inappropriate in problem-solving organizations is "Do It Right the First Time." It has an equally inappropriate cousin: "If you don't have time to do it right, how will you get time to do it again?"

Gemini 7 as seen from Gemini 6

Gemini 7 as seen from Gemini 6 during the first-ever docking of two orbiting spacecraft. The Gemini Program was a preliminary to moon exploration, but none of the Gemini vehicles were capable of completing a trip there. The program's purpose was purely experimental. The pilot of Gemini 7, by the way, was James Lovell, who later commanded Apollo XIII, the mission that nearly failed due to an on-board explosion. Photo courtesy U.S. National Aeronautics and Space Administration.

These slogans might make some sense in the operational context, where tasks are very repeatable. But problem-solving tasks are different. Problem solving, which occurs most often in the project context, entails doing something new here, in our organization, if not the world.

Here are three advantages of organizational cultures that grant permission to experiment — to "do it wrong" the first time.

Accelerated progress
We often learn more by doing it wrong than by doing right. A series of well-designed experiments that focus on specific learning goals can usually advance the project faster than consistently trying to implement deliverable solutions.
Normalized risk taking
When we require that every effort produce deliverable results, we create a culture that's averse to taking the kind of risks that are often necessary to complete projects successfully.
Cost savings
When we can accept that a particular implementation isn't "final," and won't ever be, we can take steps to limit our investment in that implementation. We can work on answering only the question at hand.

Even if We often learn more
by doing it wrong
than by doing right
you decide that experimental approaches are sometimes justified, there are three traps awaiting many organizations.

Confusion between operations and projects
Leaders and managers accustomed to operationally oriented organizations often see exploratory failures as worthless indulgences, because they don't directly produce the desired result. Many with strictly operational experience must learn new ways when they manage problem-solving organizations.
Hidden problem-solving organizations
Problem solving organizations can be embedded within operationally oriented organizations. For instance, most IT organizations are responsible for information and computation operations. Managing them requires an operational orientation. But these same IT organizations also contain groups that develop new products and first-of-kind services. Managing these efforts requires a more experimental approach. And this is a problem for slogan posters, because everyone sees them, and some slogans aren't right for everybody.
Cultural inertia
Some organizations have a historically operational orientation, but now perform most of their work in the project context. In some cases, the old culture hasn't yet adapted to the new work.

Doing it right by first doing it wrong can give you personal advantages, too. A very small example: how much better would our work lives be if we gave ourselves permission to keep revising the email messages we write until we feel good about them? You can start today. Go to top Top  Next issue: Dismissive Gestures: I  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Would you like to see your comments posted here? rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.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 Personal, Team, and Organizational Effectiveness:

A hiker in the La Primavera calderaCommitment Makes It Easier
When you face obstacles, sometimes the path around or through them is difficult. Committing yourself to the path lets you focus all your energy on the path you've chosen.
A mismatchMessage Mismatches
Sometimes we misinterpret the messages we receive — what we see or hear. It's frustrating, and tempers can flare on both sides. But if we keep in mind two ideas, we can reduce the effects of message mismatches.
A captive white rhinoFour Popular Ways to Mismanage Layoffs: II
Staff reduction is needed when expenses overtake revenue. But when layoffs are misused, or used too late, they can harm the organization more than they help. Here's Part II of an exploration of four common patterns of mismanagement, and some suggestions for those managers and other employees who recognize the patterns in their own companies.
Heiltskuk Icefield, British ColumbiaFinding the Third Way
When a team is divided, and agreement seems out of reach, attempts to resolve the conflict usually focus on the differences between the contrasting positions. Focusing instead on their similarities can be a productive technique for reaching agreement.
A particularly complicated but well-ordered utility poleThe Utility Pole Anti-Pattern: II
Complex organizational processes can delay action. They can set people against one other and prevent organizations from achieving their objectives. In this Part II of our examination of these complexities, we look into what keeps processes complicated, and how to deal with them.

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

Forthcoming issues of Point Lookout

A form of off road driving also known as mud boggingComing November 30: Avoiding Speed Bumps: II
Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.
Tuckman's stages of group developmentAnd on December 7: Reaching Agreements in Technological Contexts
Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.

Coaching services

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