Lucid Meetings Blog

This blog is full of advice for running a great meeting. Of course, teams don't run just one meeting. Teams run lots and lots of meetings.

Now, if you have oodles of spare time, you can design each and every one of your team's meetings from scratch using the advice you'll find here. No one has those oodles, however, which is why—despite the ready availability of all this super practical how-to goodness–lots of folks just make stuff up.

Other teams find a better way. They design their meetings up front, then codify these designs into a Meeting Operating System that makes it easy for them to run those meetings over and over again.

It doesn't matter what kind of team you work on or what you're trying to do - if you can't get that team to all agree and do their part, you fail.

Teamwork is the practice of agreeing on a shared goal and then dividing the work required to achieve that goal amongst the team members. To get that agreement and coordinate all that doing, you've got to communicate.

We're coming up on our 10th anniversary here at Lucid, and over all those years, we've done our fair share of failing. One of our more painful failures came about through a failure to effectively communicate.

A Meeting Flow Model is a form of process documentation that highlights the main meetings used to achieve a business result. In the previous article, I introduced the Meeting Flow Model (MFM) concept and described some of the benefits enjoyed by teams that use a defined MFM. Meeting Flow Models are super sweet.

You and your team can get these benefits too, but only after you start using an MFM and then work to refine it for your unique needs.

How do you get a useful Meeting Flow Model for your team?

By doing some Meeting Flow Modeling.

Meeting Flow Modeling is a multi-step process that takes teams several days–and often longer–to complete. In our Quickstart program, we walk teams through this process over the course of several weeks. I'm sharing this in case you think the process below looks a little complicated at first glance. Please keep in mind that this isn't something you're going to knock out in an afternoon.

For every significant goal your company needs to achieve, your team meets. In most companies, these meetings get very little forethought. They're just part of what happens as you do the work.

In other companies, teams plan out the meetings they'll use to achieve their goals. They design each meeting, just like they design the forms they use for capturing data and the reports they'll use to measure progress.

This meeting design work is a critical but often neglected aspect of successful business process design.

Here at Lucid, we call the design of a series of meetings related to a specific business process Meeting Flow Modeling. If you've ever heard me talk about the three parts of an effective Meeting Operating System, you may recognize this term.

Meeting Flow Model

A Meeting Flow Model is a form of process documentation that highlights the main meetings used to achieve a business result.

Many teams lack a clear process for making decisions. Others create decision-making processes that are plenty clear, but take forever. Most employ a confused mix, running some decisions through an agonizing gauntlet of analysis but leaving others up to the leader-of-the-day's whims.

These teams waste money and time. They also undermine the group's confidence and trust.

Who wants to work on a team where nothing gets done, because no one ever makes a decision without first checking and re-analyzing 97,000 times? Not me. Not you, I'm guessing.

None of us wants to work with a leader who makes arbitrary decisions based on secret criteria, either. While executive mandate sounds powerful, in reality it means that the leader couldn't get anyone else to back that decision with them, so they chose to bully it into being instead.

What works? And if your team doesn't have great decision making habits, how do you get started?

Introducing Michael Zipursky
The Lucid Meetings team is delighted to welcome our newest contributor, Michael Zipursky. Our CEO met Michael when she was interviewed for his Consulting Success podcast. After the interview, Michael shared how implementing the simple meeting process described below helped the consultants he works with reduce drama and retain happy clients.

It's a perfect example of how powerful it can be when you have a consistent structure for your meetings, and how you don't have to over-complicate things to get great results.

In this post, Michael share the 3-step framework that's helped hundreds of consultants build trust with clients.
— Team Lucid

Do you feel nervous before meeting with your consulting clients? If so, chances are you aren’t well-prepared.

With proper preparation and a specific agenda, your meetings will be productive and stress-free. Not only will this make your life easier, but your clients will appreciate it as well. 

In this article, I’ll explain a simple 3-part framework you can use for your client meetings. This framework works especially well if you’re working with clients on an ongoing basis. 

After reading, you’ll know how to run the perfect consulting meeting — and how to leverage meetings into more consulting work.

Before & After Using The Meeting Agenda: Jane’s Story

Jane never felt quite comfortable during meetings with her client.

Sure, she was delivering on the project just fine — but these meetings with the client were a sticking point.  She wasn’t sure what the purpose of the meeting was. She went into them hoping for the best. 

Without a clear structure to the meeting, it was hard for her client to see progress. They even started to doubt her value. 

She could feel the business slipping away.  

Introducing Douglas Ferguson
The Lucid Meetings team is delighted to welcome our newest contributor, Douglas Ferguson. Douglas Ferguson is the president of Voltage Control, an Austin-based agency that specializes in Innovation Transformation.

We were introduced to Douglas through our network as the go-to facilitator to bring in when you want to run a Design Sprint.

What's a Design Sprint? In this post, Douglas tells us all about it.
— Team Lucid

We often know what we should do or what we want to do to make our product and services better. But, we don’t. Instead, what we have to do and what’s on fire at-the-moment usually takes precedence. So, when we want to make big shifts, it’s all about carving out time and focus. Design Sprints give you both.

Let me give you an example from one of my favorite Design Sprints: on-demand meal delivery company Favor asked me to facilitate a Design Sprint last year. They wanted to focus on how to improve the earnings of their “Runners" (the people who deliver the meals) by 10% while also cutting the number of Runners who found the job frustrating by half.

Tackling this problem with design had been on their mind, but they just hadn’t gotten to it. By dedicating time for a Design Sprint, they were able to kickstart important improvements.

"We started with all these ideas about what our users wanted and needed in the next version of our app. The design sprint made us rapidly validate these assumptions instead of getting months down the road and realizing we were designing things our users didn’t want or need. In one week, we were able to build a solid foundation for our redesign from real user feedback."

-Meg Nidever, UX Designer, Favor Delivery

Even better, the Sprint experience led to a renewed dedication to prototyping and user testing for the Favor team.

What is a Design Sprint?

A Design Sprint is like an all-inclusive retreat for your next great business idea. This timeboxed, self-contained process allows teams the opportunity to consider an existing problem or a new idea, gather insights on potential or current users, prototype ideas, and validate them all within about five days.

I often find inspiration for better meetings from gatherings outside the business world. I'm curious: what is it that makes someone who grimaces through every meeting pony up good money to gather with other people after work? Why do so many people raise their hands claiming to hate meetings when I speak at meetings they had to pay to attend? 

People don't hate meetings. They hate pointless wastes of their time. So what does success look like?

Successful gatherings of all types share several common characteristics. The JoCo cruise is one such successful gathering.

Billed as a "nerdy summer camp at sea," the JoCo cruise is an affinity cruise for lovers of sci-fi, fantasy, board games, and all things deliciously nerdy. More importantly, as John Schwartz writes in the New York Times, the JoCo cruise regularly creates a "floating community of friends."

One of the most important reasons for holding a meeting is to make decisions.

Yet too often, the decision-making process degenerates into a battle between competing points of view. Participants become polarized, entrenched in their positions and paralyzed by their disagreements. Unable to resolve the conflict, the group often makes a decision that everyone says they can live with, but that no one really supports. Or worse, no decision gets made at all, and the group misses the opportunity to take positive collective action.

The Anna Karenina phenomenon builds on the first line of Tolstoy’s novel, which states:

“Happy families are all alike; every unhappy family is unhappy in its own way.”

When it comes to how an organization meets, we find the opposite to be more true.  Unhappy organization are all alike; every happy organization meets in its own way.

The organizations that provide the case study examples for organizational excellence, cultural cohesion, and that achieve the enviable combination of economic performance and a healthy workplace have all discovered ways to meet that are both effective and tailored for them.