Blog


Bad Meetings Are Boring and Ineffective

Every day, when my husband returns from work, I ask him “How was your day?”  Most of the time, he shrugs, and says something like, “Urrggghhh – so many meetings – I didn’t get ANY work done.” I’ve no idea what he does, but his LinkedIn profile tells me he “attends meetings and adds value.”

But meetings ARE work. They are an important part of the collaborative process, and one that the Scrum framework recognizes and formalized.

According to MeetingKing, 11 million meetings occur in the US every business day, and waste $37 billion in lost time each year. Maybe you are in a boring meeting right now, reading this.

Patrick Lencioni’s fable, “Death by Meeting,” hits the nail on the head:

“Bad meetings, and what they indicate and provoke in an organization, generate real human suffering in the form of anger, lethargy, and cynicism. We typically complain we have too many meetings, but the real issue is that the meetings normally aren't very effective.”

That doesn’t sound very agile, does it?

Lencioni cites the problem as twofold. Meetings generally lack:

Drama or conflict Contextual structure

Frustration is inevitable when “little is decided as participants have a hard time figuring out whether they are supposed to be debating, voting, brainstorming, weighing in or just listening.”

Why Are We So Bad at Meetings?

We are failing our Scrum Masters. They are our anointed servant leaders, coaches, and facilitators. How inspiring! However, we rarely tell them HOW to fulfill those roles. There is a general overemphasis on process and technology, and an under-emphasis on leadership skills.

I have a recurring daydream, where I decline every single meeting on my calendar. Eventually, if I’m really needed, I’ll be contacted again. Bliss! I’ve learned that this isn’t the most emotionally intelligent way of dealing with meeting overload.

David Grady’s humorous take on organically seeding good meeting etiquette is a great primer, especially when you have no idea what the meeting is about:

You don’t HAVE to accept every meeting you are invited to – use the “tentative button.” Talk to the organizer, and let them know you are excited to support their work. Ask what their goal is and how you can help. If you do this often and respectfully enough, maybe people will become more thoughtful about putting meetings together.

The Difference Between In-Person and Virtual Meetings

While I was attending an advanced agile scaling class a few years ago, the instructor stated, “at scale, Scrum won’t work if you have distributed teams – they must be co-located.” Always one that likes to debate, I sent out a “thought balloon” to see how it would be shot down. I was curious.

“Do you think that 16 years after the Agile Manifesto and its principles were written, technology has changed enough to update the idea that ‘the most efficient and effective method of conveying information to and within a development team is face-to-face conversation?’”

“NO!” was the emphatic response, followed by a couple of slick and funny YouTube videos highlighting the problems with conference, or worse, VIDEO conference calls.

I had to admit I agreed with him. Today’s modern communication software does not replace face-to-face conversation, but the reality is that the majority of teams are moving to this type of dispersed work. 

Whatever the latest technology du jour is, it will not replace the fact that you can learn how to facilitate better.

So what can we do to make the meetings suck less?

Have a Plan

I have great respect for the Grove Facilitation Model, which provides a robust, world-class way to lead a meeting.  It helps to provide the context for the following questions that every participant of a meeting needs to know:

Why am I here? Who are you people? What are we doing? How should I behave? When can I leave?

In my agile coaching practice, a common weak point I see is the retrospective being omitted. People don’t have time to do these meetings, and therefore they mistake the lack of effectiveness for false efficiency. This points to all kinds of juicy and dysfunctional problems, but meetings don’t HAVE to be a chore.

Make Your Virtual Meetings Shine

After training with The Grove on successful virtual meeting facilitation, I’d love to share their six main points to consider when planning a meeting. Make a template and fill it in so you have a proper plan you can add to your agendas. Scrum Masters, discuss it with your team to use as part of your working agreements.

Prepare Assign roles (such as tech support, scribe, timekeeper or facilitator). Don’t make the team lead a facilitator. Use a visual focal point for each agenda point. Humans are a visual species – this is how we remember and engage with things. Include a team portrait and graphic facilitation. Practice transitions. Determine how you will reach your outcome. How will time be used, who owns each topic, when do you make decisions, how will you make and document a decision? Make it engaging. I like to channel Sharon Bowman’s The 6 Trumps™ for any occasion. The person doing the most talking is doing the most learning, and if anything is longer than about 10 minutes, then you have lost your audience engagement. Design things well to maximize audience participation and use simple tools. Clarify Communication Channels Confirm meeting arrangements ahead of time. Audio is the most important element to get right. Include working norms. For example, always use a headset – no speakerphones permitted. How will you share working documents? Which ones does your company support? Which ones support the type of work you want to do? KISS (keep it simple, stupid)! Go Slow to Go Fast Expect a slow start. Include an icebreaker to allow people to get settled. It also serves as a subtle way to do a tech check and ensure that everyone can hear. Display the agenda often, especially at the beginning, transitions and the end. Virtual meetings often omit an agenda altogether. Create space right away for people to have their voices heard and get connected to content. Ask people to reframe the purpose of the meeting -- include a “2 breath” rule to allow for bottom-lining of context. Ensure Participation is Balanced Engage everyone by name, especially in blended meetings. Make space for quiet participants. Be sure to throw the quiet people a line. Structure an inclusive process (maybe write thoughts down first, then share). Keep Calm and Carry On Keep participants accountable to the agenda. Expect things to fall apart. Always have a lower-tech back up plan (phone or chat). Actually Follow Up Form crystal-clear agreements on next steps. Communicate with people after the meeting. Make the notes visual and ban the bullet point. It’s a snore fest. My list here is ironic. Document! List action items, owners and due dates, and add things to the backlog.

Poorly facilitated meetings are still poor meetings, irrespective of location. Virtual meetings just amplify facilitation problems. Facilitation as a skill is not often purposely honed--it’s something that most people “just do.” The evidence overwhelmingly tells us that it is not usually done well.

Now I know my husband does work by attending meetings and adding value, even though he feels like he attends every one of those 11 million meetings a day.

Bad meetings are boring and ineffective. But, if done well, they can be a time-saver.

Have you had positive or negative experiences with virtual meetings? Do you have any tips for improving their efficacy? Let me know in the comments below!

Find more information about different facilitation models here:

Grove Facilitation Model and OARRS

Agile Coaching Institute POWER

 

The Beekeeper’s Guide to Agility

You know what is amazing about bees? They form an amazing, efficient system, with tight communication, working towards a common goal. Sound familiar?

Now, a bee’s team is roughly 50,000 members strong – each having a specific role that is shared by the super-system. They are truly T-shaped workers, able to do whatever is needed for the survival of the hive.

But bees have a bad rap.

What does this have to do with agility? I’m asking you to challenge your perceptions and seek out a different point of view, both about bees and about problem solving. We cannot blindly follow a process or dogma and expect it to work in any situation.

That dreaded bee swarm that lands in your backyard and terrorizes your family isn’t just a nuisance, it’s a sign that the hive is doing fantastically! That super-organism is doing so well, in fact, that they have a need to reproduce and form a couple of colonies apart from the original one. This means more pollination of your food, and more honey.

The bees have nothing to protect (no home, nursery or honey stores), so they are fairly docile. They’ve gorged themselves on honey in preparation for their search for a new home to such an extent that they physically can’t bend their butts over to sting you. Ironically, this is one of the safest times to be around thousands of stinging insects.

Human brains are flawed, and constantly give us false information. This causes us to live in an echo chamber, delight in our confirmation bias and blissfully ignore alternate points of view.

I can guarantee that if you identify a problem in your team, business unit or organization, it is likely that viable solutions are not where you immediately expect them to be. If you take the time to uncover your blind spots, you will strengthen your problem-solving skills and challenge others to do the same.

Check out the principles of Integral Agile Theory below for more information. You’ll uncover your comfort zone (how you tend to approach problem-solving) as well as your blind spot (what you are ignoring in that problem-solving).

“We Should Do What They Do!”

One of the most common failures in agile transformations is that they ignore internal culture and how it will change the solution. You cannot do what Spotify or Salesforce* does and expect it to work for you, your team or your company. Process dogma does not transfer verbatim to other instances.

*Insert the cool transformation story du jour.

Why is this challenging at work?

“Touchy-feely” (or “woo-woo”) discussions are uncomfortable in a business setting. This is the blind spot in most transformation efforts. Process changes and improvements (or “do-do”) is the echo chamber of a lot of misinformed solutions, such as requesting more training or implementing another organization’s process framework.

Simply put, if you ignore the human system’s agility (culture) and focus solely on the business agility (hierarchy and processes), you risk dooming your long-term system journey.

Impediments Are Not Generic

If we jump to a conclusion when we are told of an impediment because “the process” tells us to do so, we risk ignoring the uniqueness of our own environment.

I worked in one organization where managers were routinely given the Scrum Master role. This horrified new employees who were familiar with the “standard” role definitions of Scrum.

On deeper reflection, the culture of that company had defined the role of engineering manager as being a true servant leader, with advanced empathy and a goal to coach their teams toward self-management and continuous improvement. These are obviously some of the key responsibilities of a Scrum Master. 

Thus, what initially appears as an impediment is then clearly reframed.  When managers don’t hold these expected cultural traits, that is the true impediment, not the blanket belief that managers should never be Scrum Masters. Such a belief ignores company culture and shared values.

Why Do I Care About This So Much?

I care about this so much because it’s giving agile a bad name. Lazy implementations of the wrong process tarnishes the entire craft with an ugly hue.

I challenge you to embrace your blind spots and look at things differently.

Come say hi at Agile2017 where I’ll be talking about this in more detail. Until then, feel free to share your thoughts about Integral Agile Theory in the comments section below.