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

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?"

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 rightyou 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.  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 Personal, Team, and Organizational Effectiveness:

Taming the Time Card

Filling out time cards may seem maddeningly trivial, but the data they collect can be critically important to project managers. Why is it so important? And what does an effective, yet minimally intrusive time reporting system look like?

Games for Meetings: I

We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part I of a little catalog of some of our favorites, and what we can do about them.

The Limits of Status Reports: II

We aren't completely free to specify the content or frequency of status reports from the people who write them. There are limits on both. Here's Part II of an exploration of those limits.

Planning Disappointments

When we plan projects, we make estimates of total costs and expected delivery dates. Often these estimates are so wrong — in the wrong direction — that we might as well be planning disappointments. Why is this?

Notes to Self

Many of us jot important reminders to ourselves on sticky notes, used envelopes, scraps of paper, and whatnot. Often we misplace these notes, or later find them too late to serve their purposes. Here's a low-tech alternative that works better for some.

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

Forthcoming issues of Point Lookout

Coming March 29: Time Slot Recycling: The Risks

When we can't begin a meeting because some people haven't arrived, we sometimes cancel the meeting and hold a different one, with the people who are in attendance. It might seem like a good way to avoid wasting time, but there are risks. Available here and by RSS on March 29.

And on April 5: The Fallacy of Division

Errors of reasoning are pervasive in everyday thought in most organizations. One of the more common errors is called the Fallacy of Division, in which we assume that attributes of a class apply to all members of that class. It leads to ridiculous results. Available here and by RSS on April 5.

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:

• 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