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 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 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
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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:
Changing the Subject: II
- Sometimes, in conversation, we must change the subject, but we also do it to dominate, manipulate, or
assert power. Subject changing — and controlling its use — can be important political skills.
Coping with Layoff Survival
- Your company has just done another round of layoffs, and you survived yet again. This time was the most
difficult, because your best pal was laid off, and you're even more fearful for your own job security.
How can you cope with survival?
How to Reject Expert Opinion: I
- When groups of decision makers confront complex problems, they sometimes choose not to consult experts
or to reject their advice. How do groups come to make these choices?
Paradoxical Policies: II
- Because projects are inherently unique, constructing general organizational policies affecting projects
is difficult. The urge to treat projects as if they were operations compounds the difficulty. Here's
a collection of policies for projects that would be funny if they weren't real.
Disjoint Awareness: Systematics
- Organizations use some policies and processes that can cause people in collaborations to have inaccurate
understandings of what each other is doing. Performance management, politics, and resource allocation
processes can all contribute to disjoint awareness.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming September 3: Contributions in Team Meetings: Advocating
- An agenda in the form of an ordered list of topics might not provide an appropriate framework for a given meeting. For example, if A depends on B, and B depends on A, we must find a way to discuss A and B together in some orderly fashion. Here are some alternatives to linear, ordered agendas. Available here and by RSS on September 3.
And on September 10: Contributions in Team Meetings: Scoping
- Some meetings focus on solving specific problems. We call them "working sessions." More often, we delegate problem solving to task teams, while meetings wrestle with the difficult task of identifying or "scoping" problems rather than solving them. Scoping discussions can be perilous. Available here and by RSS on September 10.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
