In Part I of our exploration of the down-in-the-weeds discussion pattern, we noted the value of understanding the pattern, and recognizing it quickly when it occurs. Even more valuable, in terms of group productivity, is the ability to avoid the weed patch altogether. That probably isn't achievable, but we can reduce the frequency of the pattern's occurrence. In this Part II, we offer two suggestions for preventing trips to the weed patch.
- Know your objectives
- Unless the parties to a conversation agree about the reason for the conversation, their respective contributions can pull the group in different directions. That's useful when the group isn't sure where it's going, though work on goal definition intentionally is probably more effective. When the parties haven't explicitly discussed the goals of the conversation, and reached agreement about those goals, irrelevant contributions are inevitable, and some of those will be down in the weeds.
- Beginning any complex discussion with an explicit statement of goals for that conversation is helpful for staying out of the weeds. Even better: give examples of what the weeds look like. For example, in a discussion of approaches for trimming requirements to achieve budget reduction for a project, a group might agree that inquiry into the merits of budget reduction would be a topic for another time, and that this conversation will focus on revising requirements to reduce costs.
- Define the scope of the discussion
- Knowing the objectives is one important step, but it leaves open the question of scope. One cause of trips down into the weeds is disagreement about the definition of relevant. Some contributions to conversations are relevant to the topic in a general sense, but they don't actually move the conversation in the direction of the agreed-upon objective.
- Agreeing on definitions of relevance might seem tangential to any given discussion, but Beginning any complex discussion
with an explicit statement of
goals for that conversation is
helpful for staying out of the weedsit's a tool that can be reused for many different conversations. A handy measure of relevance is this: How well does this contribution move us toward our objective? The group can then enumerate the properties of relevant contributions. Here are four possibilities: a contribution can clarify the objective, or argue in support of a specific possible path to the objective, or raise questions about a specific possible path to the objective, or enumerate properties of promising paths to the objective.
Avoiding the weed patch is usually advantageous — except when it isn't. Just as some desirable plants do sometimes grow among weeds, ideas that truly are treasures sometimes appear only when we take trips down into the weeds. That's why examining the detailed structures underlying the big issues is a useful thing to do. What is usually less useful is doing so when we're supposedly doing something else. First issue in this series 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? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:
- What Makes a Good Question?
- In group discussion or group problem solving, many of us focus on being the first one to provide the
answer. The right answer can be good; but often, the right question can be better.
- Wacky Words of Wisdom: V
- Adages, aphorisms, and "words of wisdom" are true often enough that we accept them as universal.
They aren't. Here's Part V of some widely held beliefs that mislead us at work.
- Heart with Mind
- We say people have "heart" when they continue to pursue a goal despite obstacles that would
discourage almost everyone. We say that people are stubborn when they continue to pursue a goal that
we regard as unachievable. What are our choices when achieving the goal is difficult?
- Anticipating Absence: Why
- Knowledge workers are scientists, engineers, physicians, attorneys, and any other professionals who
"think for a living." When they suddenly become unavailable because of the Coronavirus Pandemic,
substituting someone else to carry on for them can be problematic, because skills and experience are
not enough.
- Flexible Queue Management
- In meetings of 5-30 participants, managing the queue of contributors can be challenging. A strict first-in-first-out
order can cause confusion and waste time if important contributions are delayed. Some meetings need
more flexible queue management.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed