As we've seen, collaborative problem solving does have risks — new ideas might be crushed prematurely, judges might be intimidated, and more. Risks continue when we move to experimentation or prototyping. Let's now examine how to avoid some of the troubles that can arise during experimentation.
- Design experiments to facilitate learning
- Most experimental efforts are designed merely to determine whether an idea "can work," but that isn't enough. We need to know not only whether the idea can work, but also what its weaknesses are, how severe they are, and how we can address them.
- Regard each experiment as an exploration of the solution and how it interacts with a hostile environment. Try to determine the consequences of its misbehavior, and the cost of eliminating that misbehavior.
- Capture learning from experiments
- Experiments — especially well-designed experiments — create knowledge. Since experiments cost time and resources, we must be prepared to capture all the knowledge they create. We sometimes adjust experiments on the fly in response to what we're learning. Although these adjustments can be helpful if the adjusted experiment is still well designed, that isn't always the case. Sometimes the result of adjusting experiments on the fly is a muddled mess from which we can learn little, if anything at all.
- When conducting experiments to test newborn ideas, provide a means of capturing and storing generated ideas in such a way that they don't interfere with the ongoing experiment. When the new learning does demand immediate adjustment of the current experiments, take care to adjust them in ways that can still produce useful experimental results. That care takes time and effort, which means schedule and budget.
- Protect experiments from transition to production
- One of the most common tales of tragedy is that of the prototype that got sold to a customer. The interference of production with experimentation creates two classes of problems. First, because the prototype was intended as an experiment, it often has attributes and structures that make it unreliable and expensive to maintain or enhance. Second, if the pattern of interference of production with experimentation has occurred before, the experimenters learned long ago that they must take steps to make the prototypes more durable than ordinary experiments would have to be.
- The resultOne of the most common
tales of tragedy is that of
the prototype that got
sold to a customer is that experimentation is more expensive than it needs to be, and maintaining or enhancing fielded products that are former prototypes is more expensive than it needs to be. In short, the result is neither a good prototype nor a good product.
- When conducting experiments to test newborn ideas, conduct experiments. Insulate the experiments from any pressure to convert them into products. Your experiments will be cheaper, and when the time comes to actually build a product, it will be built right.
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 welcomeWould you like to see your comments posted here? rbrenhokKMGMRcqhOPSIkner@ChacJaqvQXKEUDvXHhFJoCanyon.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.
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.
More articles on Problem Solving and Creativity:
- Should I Keep Bailing or Start Plugging the Leaks?
- When we're flooded with problems, and the rowboat is taking on water, we tend to bail with buckets,
rather than take time out to plug the leaks. Here are some tips for dealing with floods of problems.
- The Solving Lamp Is Lit
- We waste a lot of time finding solutions before we understand the problem. And sometimes, we start solving
before everyone is even aware of the problem. Here's how to prevent premature solution.
- Teamwork Myths: Conflict
- For many teams, conflict is uncomfortable or threatening. It's so unpleasant so often that many believe
that all conflict is bad — that it must be avoided, stifled, or at least managed. This is a myth.
Conflict, in its constructive forms, is essential to high performance.
- 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?
- How to Foresee the Foreseeable: Recognize Haste
- When trouble arises after we commit to a course of action, we sometimes feel that the trouble was foreseeable.
One technique for foreseeing the foreseeable depends on recognizing haste in the decision-making process.
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenUOkjCybOdzfKSMXpner@ChacpBUoBoSYMcGwBWVvoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- 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.