Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 11, Issue 34;   August 24, 2011: New Ideas: Experimentation

New Ideas: Experimentation

by

In collaborative problem solving, teams sometimes perform experiments to help choose a solution. These experiments sometimes lead to trouble. What are the troubles and how can we avoid them?
Stainless steel cutlery

Stainless steel cutlery. Stainless steel is a relatively recent invention, discovered by Harry Brearley at the Brown Firth Laboratories in 1913. With trouble brewing in Europe, arms manufacturers had a strong interest in developing metals that were more wear-resistant for use in gun barrels. Brearley was investigating chromium iron alloys when he discovered one formulation that was especially corrosion-resistant. Cutlery of the day was made of silver (we still call it silverware), or more often, plated steel, but corrosion of the steel, and tarnishing of the silver, were ongoing problems. Brearley's "rustless steel" was immediately successful. Though his employers had little interest in becoming cutlery manufacturers, the success of the product motivated them to claim ownership of the patent. A legal wrangle ensued, and Brearley resigned.

The outcome might have been much more beneficial for all concerned, including society at large, if Brown Firth had had a more sophisticated process for capturing knowledge generated as a byproduct of its problem solution experiments.

The formulation of stainless steel that eventually became a standard, and which is still in use today, was developed by Brearely's successor. Read more at Wikipedia. Photo by Hannes Grobe.

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  Go to top Top  Next issue: Is the Question "How?" or "Whether?"  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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? rbrenFTHSFcOaNMizzpDaner@ChacjwfjgqYmwqNObakkoCanyon.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.

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:

Something from Abraham, from Mark and from HennyAbraham, 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?
A cup of coffeeHelp for Asking for Help
When we ask for help, from peers or from those with organizational power, we have some choices. How we go about it can determine whether we get the help we need, in time for the help to help.
A hummingbird feeding on the nectar of a flowerAnnoyance to Asset
Unsolicited contributions to the work of one element of a large organization, by people from another, are often annoying to the recipients. Sometimes the contributors then feel rebuffed, insulted, or frustrated. Toxic conflict can follow. We probably can't halt the flow of contributions, but we can convert it from a liability to a valuable asset.
Wilson's Bird-of-paradiseNew Ideas: Judging
When groups work together to solve problems, they eventually evaluate the ideas they generate. They sometimes reject perfectly good ideas, while accepting some really boneheaded ones. How can we judge new ideas more effectively?
Platypus swimmingSolving the Problem of Solving Problems
Problem solving is sometimes difficult when our biases interfere with generating candidate solutions, or with evaluating candidates we already have. Here are some suggestions for dealing with these biases.

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

Forthcoming issues of Point Lookout

A vizsla in a pose called the play bowComing April 26: Why Dogs Make the Best Teammates
Dogs make great teammates. It's in their constitutions. We can learn a lot from dogs about being good teammates. Available here and by RSS on April 26.
A business meetingAnd on May 3: Start the Meeting with a Check-In
Check-ins give meeting attendees a chance to express satisfaction or surface concerns about how things are going. They're a valuable aid to groups that want to stay on course, or get back on course when needed. Available here and by RSS on May 3.

Coaching services

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

Reprinting this article

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

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople 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 an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.