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:

Is the Question "How?" or "Whether?"

In group decision-making, tension sometimes develops between those who favor commitment to the opportunity at hand, and those who repeatedly ask, "If we do that, how will we do it?" Why does this happen?

The Tyranny of Singular Nouns

When groups try to reach decisions, and the issue in question has a name that suggests a unitary concept, such as "policy," they sometimes collectively assume that they're required to find a one-size-fits-all solution. This assumption leads to poor decisions when one-size-fits-all isn't actually required.

Ten Approaches to Managing Project Risks: III

Project risk management strategies are numerous, but these ten strategies are among the most common. Here are the last three of the ten strategies in this little catalog.

Virtual Brainstorming: II

When virtual teams must brainstorm, they try to do so virtually. But brainstorming isn't just another meeting. There's a real risk that virtual brainstorms might produce inadequate results. Here's Part II of some suggestions for reducing the risk.

Problem Displacement and Technical Debt

The term problem displacement describes situations in which solving one problem creates another. It sometimes leads to incurring technical debt. How? What can we do about it?

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

Forthcoming issues of Point Lookout

Coming July 18: High Falutin' Goofy Talk: III

Workplace speech and writing sometimes strays into the land of pretentious but overused business phrases, which I like to call high falutin' goofy talk. We use these phrases with perhaps less thought than they deserve, because they can be trite or can evoke indecorous images. Here's Part III of a collection of phrases and images to avoid. Available here and by RSS on July 18.

And on July 25: Exploiting Functional Fixedness: II

A cognitive bias called functional fixedness causes difficulty in recognizing new uses for familiar things. It also makes for difficulty in recognizing devious uses of everyday behaviors. Here's Part II of a catalog of deviousness based on functional fixedness. Available here and by RSS on July 25.

Coaching services

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

Public seminars

The Race to the South Pole: The Power of Agile Development

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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's a date for this program:

• Ohio National Insurance, 1 Financial Way, Blue Ash, OH: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. 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.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.