This blog is for discussions of leading & managing groups and teams. I will be entertaining questions from readers, and also discussing my own experiences and insights.
March 13, 2024
March 4, 2024
Designing Success: Key Strategies for Launching a Virtual Team
April 5, 2023
Want more creativity from your team? Do brainstorming right!
Creativity, and the innovation that stems from it, are increasingly valuable for all organizations these days. Some folks even go so far as to say that creativity & innovation are “the engine of growth”. But how do we help our teams actually become more creative? There is lots of advice out there, such as “encouraging a growth mindset”, building greater trust within the team, and reducing meetings to block out time for creativity. These are all helpful ideas, and I’m not disparaging any of them. But another, simpler, strategy is to go back to a technique most of us are familiar with and have used in the past (or so we think): brainstorming.
Brainstorming as a tool and technique goes back to the 1940’s and the work of Alex Osborne, an advertising executive. Osborne formalized the technique in his 1953 book Applied Imagination. In this work, he described the brainstorming technique and laid out the 4 rules for effective brainstorming. Now normally, when I tell people that there are “rules” for brainstorming, they are quite surprised. After all, brainstorming is supposed to be about creativity, new ideas, and even breaking down the rules, right? But following the rules helps to ensure an effective brainstorming process.
The four rules of brainstorming were set out in Osborne’s 1953 book and are relatively simple.
1) The more ideas, the better. This is an easy principle of brainstorming to accept. The basic idea here is that the more ideas we have to work with, the greater chance we have of finding an idea that meets all of our criteria in the end. So we sit down and get as many ideas out as possible.
2) The crazier the idea, the better. This is also an easy principle of brainstorming for folks to accept. Indeed, this is what we often are looking for when we set down to “brainstorm”, is for someone to toss out that really crazy, off-the-wall, creative idea that will lead to the next iPhone, Tesla, 3-D printer, or similar. As more ideas come out on the table, we increase our chance of getting these truly innovative ideas. But we also need to explicitly give people permission to come up truly outlandish ideas, as opposed to censoring their ideas to fit into the constraints that we have (or believe we have).
3) “Piggy-backing”, or building on someone else’s idea is welcome. As we listen to someone else’s idea, we often have thoughts about how we could add a little twist to it. This may not count as a “new idea” from an intellectual property perspective, or as we think about “who to give credit to”. But from a brainstorming perspective this is encouraged because these slight variants give rise to other ideas as people continue to build on and react to what others have said. In my experience, some teams are perfectly okay with this rule. Other teams have a harder time with it, often when team members feel competitive pressure to come up with the “most” creative idea as individuals, or that they are being evaluated or judged based upon the creativity of the ideas that they come up with individually. If this is happening in your team, you need to do some work moving people from a sense of individual performance to team-based performance.
4) Deferring judgement on any idea until all the ideas are on the table. This is the rule that most groups tend to have the most difficulty with. Whether the judgement is a simple “oh, that would be too expensive”, or even a positive “hey, that’s a great idea!”. Once anyone within the team evaluates an idea, all the team members start to evaluate their ideas before they share them. This then leads to fewer ideas overall, and fewer truly innovative ideas. Numerous research studies have found that evaluation apprehension (the fear of having our ideas criticized by others) leads to a significant decrease in both the quantity and quality of ideas that come forward in a brainstorming session.
So what does this mean for you as a leader? First, understand that as a team leader you have some responsibilities in terms of how the brainstorming session is designed. For example, how large and how diverse a group do you want in the brainstorming session? What background information do you want people to be familiar with beforehand? Are you able to bring in an outsider to help facilitate the session or will you do it yourself?
Second, make sure that your team members are familiar with, and truly understand, the 4 rules. An effective brainstorming session is more than simply bringing people together and hoping for spontaneous creativity. Make sure to tell them that they won’t be judged by what they say, and that any idea (even those that might seem impractical or even infeasible) are welcome. Talk to them about the role of the facilitator, and that person will be doing during the process.
Finally, follow up on that by your behavior in the brainstorming session. Demonstrate the rules of brainstorming by piggy-backing off others ideas and putting truly crazy ideas out there. If you or your team is relatively new to true brainstorming, consider having a “warm-up round” first where you work on an unrelated problem, to practice the behaviors of putting ideas out there as quickly and with as little filtering as possible.
Finally, remember that while brainstorming can be an excellent tool, there are plenty of variants out there as well that may be more appropriate for you to use in your situation. For example, if you have a large group and you think people will be talking over each other, or putting ideas out faster than they can be captured, you might consider the “nominal group technique”. If you want to use the brainstorming process to have team members realize the connections between their ideas and viewpoints (for example, if members believe there is conflict or tension within the team), consider using team mind mapping. If you want the brainstorming process to help your team get more comfortable with both coming up with and critiquing ideas and plans, consider the “sub-team” approach – break your team into 2 or more smaller sub-teams. Give the sub-teams time to come up with a certain number of ideas, then have each sub-team present what they think is their best idea for discussion, feedback, and improvement in the larger team session.
Ultimately, the idea generation technique you use will depend on your specific goals and the problems or constraints you have to work with. But a common key across all of these techniques is forcing people to suspend judgement for a period of time to let ideas come out. The more you can do as a team leader to cultivate that sort of intellectual openness and psychological safety in your team, the more creative and innovative thinking you will start to see from your team members.
March 31, 2023
Questions to ask when your team is having trouble
A recent article in Harvard Business Review titled "6 Questions to Ask Yourself When You're Frustrated with Your Team" provides some excellent advice about how you might change your own behavior as a team leader. But like so many articles on managing people (either as teams or as individuals), it focuses almost entirely on managing interpersonal interactions and not nearly enough on the importance of creating a context that sets people up for success.
A former mentor of mine, Harvard University psychologist Richard Hackman, once opened a keynote speech by saying that managers shouldn't try to motivate people to change. Instead, he said, managers should focus on putting in place conditions that made positive outcomes more likely, and negative outcomes less likely. He described what he meant by this in his book Leading Teams: Setting the Stage for Great Performances, in which he described what he found through his research on teams in a variety of different industries and settings, from airline crews to intelligence teams to symphony orchestras. Through his research, Hackman identified several critical conditions that supported successful teams across all these very different contexts. In this blog post, I will focus on the first three, which Hackman termed "The Essentials".
- Having a Real Team. Real teams have well-defined, stable membership. The team and its members have the authority to conduct their work and make critical decisions without always needing "permission" from someone at a higher level. Finally, real teams conduct their work in an interdependent manner - meaning they do much of their work together, as opposed to coming together in periodic meetings to share updates. So as you look at an underperforming team, ask yourself questions like - do they have a core, stable membership that gives them the consistency needed to learn over time? Do they have the authority they need to complete the task without constantly waiting for external approval? If this appears to be the problem, consider helping the team stabilize its membership. This is often done by reducing the size of the team.
- Having a Compelling Direction. Team members are motivated by having a shared task that is clear, challenging, and consequential. They have been charged with completing specific goals, but have not been told to use specific means to reach those goals. As you look at the team, ask yourself if there is a clear, shared endpoint at all the team members are working towards? Will the challenge of reaching that goal require the team members to work with and learn from each other? Does the team have the authority to manage their own work in terms of how they meet the goal? If this is an issue, help the team by providing clarity around the end goal, and explaining the importance of the project to the organization.
- Having the Right People. A major reason that teams work well is that they bring together a diverse group of people in terms of backgrounds, perspectives, and skill sets. But to do that, team members need to have (and trust that all other team members have) certain base levels of skill and competence in their own specialties. When teams don't have the right people, it sometimes is because one or more individuals don't have the knowledge, skill, and ability you thought they had. However, just as often it is because there are too many team members who are just too similar in terms of the skills they bring to the table, their training and the way they solve problems, or the perspectives that they bring. Take a close look at how people were selected for this team, who was chosen, and why? Was it truly based on their knowledge, skill, and ability? Or have some individuals become the "go-to" people for your team?
January 21, 2023
3 Steps to Improve Your Team Debriefs
After Action Reviews (AARs) were institutionalized as a practice in the 1970’s by the US military to formalize learning from experience and improve team and unit performance. Their use contributed to significant performance increases, causing this innovation to be rapidly adapted outside the armed forces. But is your organization using them correctly?
The AAR was developed as a more participatory alternative to a supervisor driven performance critique. The idea being that by having the critique be driven by team members, rather than a supervisor, a more complete picture of events and interactions can be developed and shared. This shared understanding, in turn, leads to the opportunity to make changes in plans, routines, resources, and interactions, leading to improved performance. The good news is that AAR’s have been shown to improve performance by up to 25%.
But what if your team reviews could be helping you even more? Recent research by Angus Fletcher of the Ohio State University, Preston Cline from the University of Pennsylvania, and Matthew Hoffman of the FBI, conducted in partnership with the US Army Special Forces and described in this article from Harvard Business Review, shows a path forward.
The core strategy they identify is to create greater accountability within the team by developing a clear, shared understanding of what happened. To do this, they advocate 3 steps.
1) Focus on people, not process. Addressing an abstract, impersonal process may feel “safe”, especially early in a team’s life. But that impersonal safety also leads to a lack of passion. Instead, they suggest you personalize the impacts of what happened, and what change could achieve. Do this by focusing on team members, customers, and other stakeholders. Bring their experience and perspectives into the review to highlight the importance of improvement.
2) Focus more on what happened rather than what could be done. Traditionally, AAR participants spend roughly 25% of the review discussing initial expectations and the instance/performance itself, and 75% of the review focused on the performance gap and what to change. Fletcher, Cline, & Hoffman suggest flipping that ratio to spend much more time ensuring that everyone has a clear, shared sense of what actually happened and that everyone shares their perspective – especially those with divergent points of view. Doing this increases available information, decreases defensiveness, and reduces what psychologists refer as Shared Information Bias. This allow problem areas to be defined with greater clarity and develops a shared focus for creative problem solving later on.
3) Get clarity and triangulation. Whether someone is claiming credit for a positive outcome, or assigning blame for a negative one, make sure they are clear about how/why “behavior A” led to “outcome B”. What other factors might have influenced the outcome? What other outcomes did this behavior cause? Do others who saw or were present for this behavior agree with this logic?
Adding these features to your team debriefs may feel uncomfortable at first, but over time will lead to a greater focus on change and accountability for you and your team.
January 13, 2014
Problem people, problematic environments
November 13, 2013
The functions (and liabilities) of hazing
October 18, 2013
Sports teams and other work teams
How to Build Team Trust When Everything Feels Uncertain
Inspired by HBR’s “How Leaders Can Build Stakeholder Trust in Uncertain Times” Uncertainty is no longer a temporary condition—it’s the new n...
-
Maximizing Team Effectiveness: The 60/30/10 Rule Explored Leaders and managers in are constantly seeking effective strategies for team dev...
-
Inspired by HBR’s “How Leaders Can Build Stakeholder Trust in Uncertain Times” Uncertainty is no longer a temporary condition—it’s the new n...
-
Is Your Hybrid Team Still Engaged? Warning Signs and What to Do About Them Hybrid work has moved from novelty to normal, reshaping how tea...