Point Lookout An email newsletter from Chaco Canyon Consulting
Point Lookout, a free weekly email newsletter from Chaco Canyon Consulting
March 5, 2008 Volume 8, Issue 10
 
Recommend this issue to a friend
Join the Friends of Point Lookout
HTML to link to this article…
Archive: By Topic    By Date
Links to Related Articles
Sign Up for A Tip A Day!
Create a perpetual bookmark to the current issue Bookmark and Share
Tweet this! | Follow @RickBrenner Random Article

What, Why, and How

by Rick Brenner

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
Simplicity is essential
for everyday use of
structured group processes
"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" 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: Part III  Next Issue
Bookmark and Share


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? Send 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:
Hot and ColdTake Regular Temperature Readings
Team interactions are unimaginably complex. To avoid misunderstandings, offenses, omissions, and mistaken suppositions, teams need open communications. But no one has a full picture of everything that's happening. The Temperature Reading is a tool for surfacing hidden and invisible information, puzzles, appreciations, frustrations, and feelings.

Detour SignHow We Avoid Making Decisions
When an important item remains on our To-Do list for a long time, it's possible that we've found ways to avoid facing it. Some of the ways we do this are so clever that we may be unaware of them. Here's a collection of techniques we use to avoid engaging difficult problems.

A late rabbitGames for Meetings: Part III
We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part III of a little catalog of some of our favorites, and what we could do about them.

A plopPlopping
When we offer a contribution to a discussion, and everyone ignores it and moves on, we sometimes feel that our contribution has "plopped." We feel devalued. Rarely is this interpretation correct. What is going on?

two different chairsTake Any Seat: Part I
When you attend a meeting, how do you choose your seat? Whether you chair or not, where you sit helps to determine your effectiveness and your stature during the meeting. Here are some tips for choosing your seat strategically.

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

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact me for details at rbrenner@ChacoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the e-book!

Past issues of Point Lookout are available in five e-books:
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

Person-to-Person Communication for Project Managers
When Person-to-Person Communicationswe talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here are some upcoming dates for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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 an upcoming date for this program:

Human-Centered Risk Management
Most Human-Centered Risk Managementof us can assess technological risks, but risks related to human behavior tend to resist our best efforts. This session provides a framework for evaluating risks related to the behavior of individuals, teams, organizations and people generally. Human-centered risk differs from technological or market risk, because objective evaluation requires acknowledging personal and organizational limitations and failures. Since some of those limitations and failures might apply to the people assessing the risks, or to their superiors, there's a tendency to deny them or to explain them away. Our approach examines capability, organization, context, risk mitigation, and workplace politics. It has tools for guiding the assessment and management of human-centered risk, and we show how to extend these tools to suit your situation. You'll learn how to identify sources of risk in human behavior; recognize systemic and individual barriers to acknowledging risk; assess the effects of organizational turbulence; determine the risk associated with inappropriate internal risk transfer; estimate the effects of team dysfunction, toxic conflict and turnover; and measure the impact of workplace politics. 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Project Management in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help project managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:

The Politics of Meetings for People Who Hate Politics
ThereThe Politics of Meetings for People Who Hate Politics's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:

101 Tips for Targets of Workplace BulliesAre you being targeted by a workplace bully? Do you know what to do to end the bullying? Read 101 Tips for Targets of Workplace Bullies to learn powerful methods for dealing with workplace bullies. Check it out!
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?
My free weekly email newsletter gives concrete tips and suggestions for dealing with the challenging but everyday situations we all face.
A Tip A DayA Tip a Day arrives by email, or by Yahoo! Widget, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
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 away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
SSL