It's early afternoon on a glassy tropical ocean in 1798. You're a "jack tar" — an ordinary seaman on an English sailing vessel. You're on the watch, with little to do, because the sails are already set and the ship is nearly becalmed under a hot equatorial sun. Along with most of the rest of the watch, you're splicing sheets in the merciful shade of the mainsail.

Tenacious under full sail. Photo courtesy Jubilee Sailing Trust, which "promotes the integration of able-bodied and physically disabled people through tall ship sailing adventures."
Every minute or so, one of you looks over his shoulder at the smoking lamp. It's still out, but you expect the mate to order it lit at any moment. When that happens, you can light your pipe.
Lighting the smoking lamp told sailors they could smoke. Smoking was generally dangerous on the deck of an eighteenth century vessel, because just about everything on board was flammable, and the tar they used to caulk seams was everywhere. Even an ember from a pipe could set it alight. Smoking was permitted only when the wind was light and favorable.
In problem-solving organizations, we don't worry much about fire, but the tendency to jump into "solution mode" prematurely is just as dangerous, because most problems have multiple interacting causes.
For instance, if a solution addresses one of the causes, and it fails, we might think that our solution didn't work, when actually it was necessary, but not sufficient. And some causes are active only when other causes are inactive. The bad behavior we observe when our trial solution is in effect might actually be due to a different failure mechanism.
Even when we're just exploring a problem, we're easily deflected into solving it, which makes it difficult to focus on understanding rather than solving. One technique that helps is to use a "solving lamp," analogous to the sailor's smoking lamp.
Get a Lava Lamp, or a flashlight that you can stand on end. Bring it to any meeting that you think might be vulnerable to falling into solution mode prematurely. Explain that during the parts of the meeting when the solving lamp is lit, we're looking for solutions, and when the solving lamp is out, we're doing something else.
The tendency to jump into
"solution mode" prematurely
is dangerous because
most problems have
multiple interacting causesHere are some of the advantages of solving only when the solving lamp is lit:
- It's easier to solve problems that you actually understand
- Some people will find it easier to wait until everyone understands the problem better
- Those who prefer exploring the problem before solving it are on a more equal footing with those who prefer moving to solution earlier
- Solutions are more likely to encompass the right combination of interacting causes
If you're an organizational leader considering how to equip all conference rooms with solving lamps, but you don't know where to find the budget for it, then you have a problem. The solving lamp is lit. 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? rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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:
Discussion Distractions: II
- Meetings are less productive than they might be, if we could learn to recognize and prevent the most
common distractions. Here is Part II of a small catalog of distractions frequently seen in meetings.
Communication Refactoring in Organizations
- Inadequate communication between units of large organizations is one factor that maintains the dysfunction
of "silo" structures in large organizations, limiting their ability to act coherently. Communication
refactoring can help large organizations to see themselves as wholes.
Still More Things I've Learned Along the Way
- When I have an important insight, or when I'm taught a lesson, I write it down. Here's another batch
from my personal collection.
Paid-Time-Off Risks
- Associated with the trend to a single pool of paid time off from separate categories for vacation, sick
time, and personal days are what might be called paid-time-off risks. If your team must meet customer
expectations or a schedule of deliverables, managing paid-time-off risks can be important.
Internal Audits Without Pain
- If adhering to established procedures is part of your job, you probably experience occasional audits.
You can manage the pain of the experience by regarding audit preparation as part of the job. Because
it is. Here are some tips for navigating audits.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming May 14: Working with the Overconfident
- A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.
And on May 21: Mismanaging Project Managers
- Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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
rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
