New Ideas: Experimentation

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.

If one of these ideas for experiments is itself a new idea for your organization, try adopting it — but experiment first. First in this series   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 Problem Solving and Creativity:

Abraham, Mark, and Henny

Our plans, products, and processes are often awkward, bulky, and complex. They lack a certain spiritual quality that some might call elegance. Yet we all recognize elegance when we see it. Why do we make things so complicated?

Figuring Out What to Do First

Whether we belong to a small project team or to an executive team, we have limited resources and seemingly unlimited problems to deal with. How do we decide which problems are important? How do we decide where to focus our attention first?

Breaking the Rules

Many outstanding advances are due to those who broke rules to get things done. And some of those who break rules get fired or disciplined. When is rule breaking a useful tactic?

What Makes a Good Question?

In group discussion or group problem solving, many of us focus on being the first one to provide the answer. The right answer can be good; but often, the right question can be better.

Remote Hires: Inquiry

When knowledge workers join organizations as remote hires, they must learn what's expected of them and how it fits with what everyone else is doing. This can be difficult when everyone is remote. A systematic knowledge-based inquiry procedure can help.

See also Problem Solving and Creativity and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Coming October 5: Downscoping Under Pressure: I

When projects overrun their budgets and/or schedules, we sometimes "downscope" to save time and money. The tactic can succeed — and fail. Three common anti-patterns involve politics, the sunk cost effect, and cognitive biases that distort estimates. Available here and by RSS on October 5.

And on October 12: Downscoping Under Pressure: II

We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope. Available here and by RSS on October 12.

Coaching services

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