Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 8, Issue 10;   March 5, 2008: What, Why, and How

What, Why, and How

by

Last updated: August 8, 2018

When solving problems, groups frequently get stuck in circular debate. Positions harden even before the issue is clear. Here's a framework for exploration that can sharpen thinking and focus the group.

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.

2nd. Lt. Henry Martyn Robert, U.S. Army (center)

2nd. Lt. Henry Martyn Robert, U.S. Army (center), directs the construction of gun emplacements at San Juan Island in what is now Washington State in mid-August 1859, during the "Pig War" between the U.S. and Britain. Robert is the Robert of "Robert's Rules," which he published in 1876. Robert's Rules is one example of a framework for a group process. Many other frameworks exist, undoubtedly the most numerous of which are defined as cultural norms. Robert's Rules is an example of an intentionally invented framework.

Other examples of invented frameworks for group processes are Alex Faickney Osborn's brainstorming, Virginia Satir's Temperature Reading, and my own What Haven't I Told You?. Examination of group process frameworks in actual use reveals that simplicity is essential for everyday use. For example, Robert's Rules as commonly practiced consist of only about a dozen of the rules in the current edition, which contains more than 100. Photo of an uncredited art work courtesy U.S. National Park Service.

"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.

What
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.
Why
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
"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.

What
The "What" Simplicity is essential
for everyday use of
structured group processes
of 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
"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
"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. Go to top Top  Next issue: Responding to Threats: III  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? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 Effective Meetings:

An air traffic controller using a display system at an Air Route Traffic Control CenterRemote Facilitation in Synchronous Contexts: I
Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting chair — will discover quickly that remote facilitation presents special problems. Here's a little catalog of those problems, and some suggestions for addressing them.
A dense Lodgepole Pine stand in Yellowstone National Park in the United StatesAgenda Despots: I
Many of us abhor meetings. Words like boring, silly, and waste come to mind. But for some meeting chairs, meetings aren't boring at all, because they fear losing control of the agenda. To maintain control, they use the techniques of the Agenda Despots.
Word salad with font dressingVirtual Meetings: Indicators of Inattention
If you've ever led a virtual meeting, you're probably familiar with the feeling that some attendees are doing something else. Here are some indicators of inattention.
Five almondsWorkplace Memes
Some patterns of workplace society reduce organizational effectiveness in ways that often escape our notice. Here are five examples.
A VoiceStation 500 speakerphone by PolycomInterrupting Others in Meetings Safely: II
When we feel the need to interrupt someone who's speaking in a meeting, to offer a view or information, we would do well to consider (and mitigate) the risk of giving offense. Here are some techniques for interrupting the speaker in situations not addressed by the meeting's formal process.

See also Effective Meetings, Effective Communication at Work and Problem Solving and Creativity for more related articles.

Forthcoming issues of Point Lookout

An excavator loads spoil into rail cars in the Culebra Cut, Panama, 1904Coming October 23: Power Distance and Teams
One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.
John Frank Stevens, who conceived the design and method of construction of the Panama CanalAnd on October 30: Power Distance and Risk
Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

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

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

The Race to the South Pole: Lessons in Leadership

On 14The Race to the South Pole: Lessons in Leadership 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. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

The Power Affect: How We Express Our Personal Power

Many The
Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet 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.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
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.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.