Why You Hate Meetings and What You Can Do About It (Part Two)

In part one of this blog, we looked at the key to keeping meetings on track and productive. It’s NOT discussing problems the moment they arise, as counterintuitive as that may seem. The best way to resolve Issues is to put them on a list as they come up and discuss them during a segment of the Level 10 Meeting dedicated solely to IDS:  Identify – Discuss – Solve.

The Four Steps to Conducting a Good IDS Session

Prioritize Your Issues

Look at the Issues List and identify the three most urgent Issues, then number them 1-2-3 in order of priority. By addressing your most pressing problems first, you ensure that even if it takes you a whole hour to solve one Issue, you have at least solved the most important one.

Identify

Get to the root cause of the Issue. Let’s say the Issue you’re discussing is that a key target wasn’t met last week. First, ask why it wasn’t met. If the answer is, “Well, it’s because we didn’t get some shipments out on time,” then ask why the shipments went out late. If that answer is, “Because we were short-staffed,” ask why we were short-staffed, and so on. Keep asking “Why?” until you reach the root cause of the Issue, then move on to the “D” in IDS.

Discuss

Talk about the Issue until it’s resolved, but do it without going down “rabbit holes” of endless talk. There are two rules for discussing an Issue:

  • Only one person talks at a time. Everyone else listens, and no one interrupts with an objection.
  • Everyone gets a chance to say whatever they want to say about the Issue at hand, but they only say it once. Anything more is politicking. Once everyone has said their piece, move on to solving it.

Solve

Determine what you or your team has to do to solve the Issue. When you know what the solution is, assign it to the person who should be responsible for it, and then hold them accountable for getting it done by asking if it’s done in the “To-Do Review” portion of your next Level 10 Meeting.

Now that we’ve learned how to solve our key Issues, let’s review the full Level 10 Meeting agenda.

The Level 10 Meeting Agenda

Segue (5 minutes)

The segue is nothing more than each person at the table sharing one item of personal good news and one item of business good news.  To some, this may seem like a waste of valuable time, but it actually performs a critical psychological “trick” that helps the meeting go better from start to finish. By sharing good news, especially personal news, you shift your frame of mind, helping you “unplug” from whatever you were doing before the meeting so you can transition from working in the business to working on it. If you don’t think it’s valuable, do it for a few weeks anyway, then skip it for a week and see how things go. You’ll be sure never to omit the segue again!

Scorecard Review (5 minutes)

Briefly review the Measurables you are tracking to see how you performed this week. If you didn’t meet a key target, don’t ask why at this point. Put it on the Issues List to discuss during the IDS session.

Rock Review (5 minutes)

Have each person who is responsible for a Quarterly Rock report on whether they are “on track” to complete the Rock by the end of the quarter or “off track”, meaning they are behind schedule or otherwise not likely to complete it this quarter. If a Rock is off track, don’t discuss it now; put it on the Issues List.

Customer/Employee Headlines (5 minutes)

Give everyone in the room an opportunity to share any major customer or employee developments with the rest of your team. Again, if Issues come up, don’t discuss them; drop them down to the Issues List.

To-Do Review (5 minutes)

This is where you go over the “To-Do” items that were assigned in last week’s Level 10 Meeting and cross off those that have been accomplished, or “done.” A 90% completion rate is the minimum acceptable. If anyone is completing less than 90% of their tasks, it is an Issue that should be added to the Issues List.

IDS (60 minutes)

Take one hour to resolve Issues using the method described at the top of this post. Again, as you discover the solution(s) to an Issue, turn it into a To-Do and write it on the to-do list to be reported on next week.

Conclude (5 minutes)

There are three items to cover in the conclusion portion of the meeting:

  • Recap your “To-Do” items and who is responsible for each one.
  • Discuss any “cascading messages.” This means identifying messages that need to be communicated to lower levels of the company or to anyone not present at the meeting. Clarify not only the message, but who is responsible for getting it to whom.
  • Rate the meeting. Each person in the room rates the meeting’s effectiveness on a scale of 1–10, with 10 being the most effective. If your average is below an 8.5, then this may be an Issue in itself; failing to stick to the IDS rules or yielding to the temptation to discuss Issues the moment they come up are your most likely reasons for dissatisfaction.

If you find you don’t do such a great job at using the Level 10 agenda right away,  don’t worry! Don’t give up too quickly. It can take a little time to adapt to conducting meetings this way because it isn’t always easy to break the bad habits that cause meetings to run amok in the first place. I have a weekly Level 10 Meeting with my Integrator, and it took her several weeks to get the hang of it when we first started. Persevere! Once you get the hang of it, you’ll be amazed at how much you can accomplish in only 90 minutes a week.

Related Reading: Level 10 Meeting

Ready to Take Meetings to the Next Level?

If you’re ready to stop hating meetings and start making them more productive, connect with an EOS implementer! An EOS Implementer can help you master the Level 10 Meeting and gain traction every week.

Picture of Ken DeWitt

Ken DeWitt

Ken DeWitt is a six-time entrepreneur and seasoned financial expert serving Central Alabama. With a background as a CPA and Fractional CFO, Ken has advised more than 150 companies across his career. After witnessing too many business owners, including his own father, struggle without the right support, Ken found the Entrepreneurial Operating System and a better way forward. Today, he helps entrepreneurial leaders bring structure to their vision, build stronger teams, and create businesses that support the lives they want to live. View my EOS Implementer Profile

Related Posts

Subscribe to the EOS Blog

Subscribe to the EOS Blog:

LOGIN TO

Base Camp

LOGIN TO

Client Portal

LOGIN TO

ORGANIZATIONAL CHECKUP

Search the EOS Worldwide Blog