Most problems facing modern organizations are too complicated for solo solvers. We address them as groups, and sometimes groups encounter difficulties. Group problem solving is something most of us learned by doing — few have trained for it, and those who did have learned different methods. Today's shrunken training budgets provide little aid, and we have little time for training anyway.
"What, Why, and How" is a simple structure that can help. When we use it to explore the problem and its candidate solutions, it guides the discussion and helps avoid those frustrating loop-de-loops. Here's how to apply it (possibly iteratively) to clarify the problem.
- Work together to write a clear statement of the facts of the problem. No excuses or explanations — just facts. Example: We were scheduled to finish by December 30, and now that appears impossible.
- The answer to "Why?" is our best understanding of the causes of the "What." It describes the mechanism that brought about the "What." It might identify several independent or interacting elements. Example: Since we underestimated the linkages between our project and other efforts, we had to compete for the time of some key people, and that introduced unanticipated delays.
- "How" explains what keeps the problem in place. It explains the source of the problem's longevity, and how it persists despite our having recognized it. Example: Our project is now so late that even though we're getting the time we asked for from those key people, we need more than that to catch up, and they can't provide it because they have other commitments.
And here's how to apply What-Why-How to a candidate solution.
- The "What" Simplicity is essential
for everyday use of
structured group processesof a proposed solution is a concise statement describing it. No words about implementation, cost, or schedule — just the vision. Example: We'll work out a new schedule that allows us more time, and we'll also hire three contractors to accelerate our pace.
- "Why" summarizes our motivation for adopting this solution, including the advantages of this solution without reference to any other solutions. Example: Even if we apply additional resources, we can't make the December date, but we do believe that some specialized extra help will improve performance.
- "How" provides a high-level description of the strategy and tactics we intend to deploy to implement the solution. Example: Todd will work with the internal customer to determine a new date, while Beth begins a search for contractors who can meet our needs. They'll coordinate to ensure that the date we get fits the availability of the contractors.
If your team faces an issue that has resisted resolution, try the What-Why-How approach. If you don't have an issue right now, but they often do arise, use this issue: We often encounter issues that lead to endless loop-de-loop debates that resist resolution. 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 welcomeWould you like to see your comments posted here? rbrenbzEIoWjnJifcgCvQner@ChacbxnPNGIHxxwuMNRpoCanyon.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 Effective Meetings:
- When Meetings Boil Over
- At any time, without warning, you can find yourself in a meeting that boils over. Sometimes tempers
rise, then voices rise, and then people yell and scream. What can a team do when meetings threaten to
boil over — and when they do?
- 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.
- How to Ruin Meetings
- Much has been written about how to conduct meetings effectively. Here are some reliable techniques for
doing something else altogether.
- When the Chair Is a Bully: I
- Most meetings have Chairs or "leads." Although the expression that the Chair "owns"
the meeting is usually innocent shorthand, some Chairs actually believe that they own the meeting. This
view is almost entirely destructive. What are the consequences of this attitude, and what can we do about it?
- Rationalizing Creativity at Work: I
- Much of the work of modern organizations requires creative thinking. But financial and schedule pressures
can cause us to adopt processes that unexpectedly and paradoxically suppress creativity, thereby increasing
costs and stretching schedules. What are the properties of effective approaches?
Forthcoming issues of Point Lookout
- Coming February 27: Brainstorming and Speedstorming: II
- Recent research into the effectiveness of brainstorming has raised some questions. Motivated to examine alternatives, I ran into speedstorming. Here's Part II of an exploration of the properties of speedstorming. Available here and by RSS on February 27.
- And on March 6: A Pain Scale for Meetings
- Most meetings could be shorter, less frequent, and more productive than they are. Part of the problem is that we don't realize how much we do to get in our own way. If we track the incidents of dysfunctional activity, we can use the data to spot trends and take corrective action. Available here and by RSS on March 6.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendmtoXWCGCIxMpVQDner@ChacNMbWAqwmdvMAwYOooCanyon.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
- 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.