In group problem solving, we generate new ideas, we assess or judge them, and we experiment to see how well they work. Since experimenting is usually costly and time-consuming, we use our judgment to select the most promising ideas for experimentation. But the judging process makes mistakes. Here are two insights that can help prevent rejecting good ideas or accepting bad ones.
- The right to judge is inalienable
- After idea generation, and the newborn ideas are subjected to judging and evaluation, two traps await. First, we sometimes confuse judging ideas with judging the people who generated them. Honest attempts to critique ideas can seem like personal criticism, and criticism intended to be personal can be disguised as honest attempts to critique the ideas.
- Second, during judging, judges and their comments might in turn be judged. This secondary judging degrades the judging process. In some cases, generators might demand that judges themselves address the issues they identify: "Show us how to fix it," or "If you're so smart, show me a better way." Such demands that judges "earn" the right to judge are violations of the (usually implicit) contract between the judges and the larger group. They freeze the judging process and they might even inhibit contributions by other judges.
- When we act as judges of new ideas, we must take care to judge the ideas — not their generators — in good faith. When we provide comments on newborn ideas, we must also suggest underlying principles that can guide the generators during the next cycle. When we ask people to judge new ideas, we can accept or reject their comments, but we must trust that those comments are provided in good faith, unless there is clear proof to the contrary.
- Judging can uncover misunderstandings
- Generators have their Judging newborn ideas is one
of the earliest points at which
differences in understanding
the problem become clearown understandings of the problem to be solved; judges have theirs. Judging newborn ideas is one of the earliest points at which differences in these understandings become clear.
- In processing judges' comments, difficulties can arise if the group mistakenly assumes that there is only one understanding of the problem. The ensuing debate about the relevance of a critique can in fact be irrelevant itself, if what's needed is consensus about the problem definition, rather than consensus about the judges' comments.
- Shared group understanding of the problem definition is one of the first things to check when processing judges' critiques. For any reasonably complex problem, all of the members' understandings will likely require multiple revisions. Success depends on the group converging on a single understanding of the problem, and judges' critiques provide an important means of exposing divergences.
As you begin judging these ideas, keep in mind that your understanding of how groups solve problems is yours; others have theirs.
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenkbOjHFKxpTsbyVkFner@ChacZXClCYisbrHAzdPToCanyon.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 Problem Solving and Creativity:
- What Haven't I Told You?
- When a project team hits a speed bump, it often learns that it had all the information it needed to
avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering
this kind of knowledge more systematically.
- Unintended Consequences
- Sometimes, when we solve problems, the solutions create new problems that can be worse than the problems
we solve. Why does this happen? How can we limit this effect?
- Forward Backtracking
- The nastiest part about solving complex problems isn't their complexity. It's the feeling of being overwhelmed
when we realize we haven't a clue about how to get from where we are to where we need to be. Here's
one way to get a clue.
- How to Foresee the Foreseeable: Preferences
- When people collaborate on complex projects, the most desirable work tends to go to those with highest
status. When people work alone, they tend to spend more time on the parts of the effort they enjoy.
In both cases, preferences rule. Preferences can lead us astray.
- Problem Displacement and Technical Debt
- The term problem displacement describes situations in which solving one problem creates another.
It sometimes leads to incurring technical debt. How? What can we do about it?
Forthcoming issues of Point Lookout
- Coming July 5: Tackling Hard Problems: II
- In this Part II of our look at solving hard problems, we continue developing properties of the solution, and look at how we get from the beginning to the end. Available here and by RSS on July 5.
- And on July 12: Performance Issues for Non-Supervisors
- If, in part of your job, you're a non-supervisory leader, such as a team lead or a project manager, you face special challenges when dealing with performance issues. Here are some guidelines for non-supervisors. Available here and by RSS on July 12.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenSvHoltQDjRQGjlsRner@ChacZCdGfVHrByTulYAZoCanyon.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:
- 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. Here are some upcoming dates for this program:
- Creating High Performance Virtual Teams
- Many people 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:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 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:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.