How to Solve Problems in Team Meetings (Instead of Just Talking About Them)

Watch a typical leadership meeting and you’ll see the same pattern. Someone raises a problem. Everyone agrees it’s a problem. Three people tell stories about it. The conversation drifts to a related problem. The clock runs out. “Let’s pick this up next week.”

Next week, it happens again.

Step 1: Keep a running issues list

An issues list is simply where problems go to get solved. Anything that needs the team’s attention goes on it:

• Off-track numbers from the scoreboard.
• Quarterly goals that are slipping.
• Problems raised by anyone during the week.
• Ideas and opportunities that need a decision.
• To-dos that keep slipping.

Keep it in one shared place. Anyone on the leadership team can add to it at any time. The rule: if it’s bothering you, put it on the list rather than complaining in the hallway.

Step 2: Prioritize the top three

At the start of the issue-solving block, look at the whole list and pick the three most important. Not the easiest. Not the newest. The ones that matter most to the business.

Then solve them one at a time, starting with number one. Don’t move on until it’s solved.

Step 3: Find the real issue

The issue as stated is often a symptom. “Sales are down” is a symptom. “Web leads aren’t getting called within a day” might be the issue. “Nobody owns lead follow-up since the coordinator left” might be the real issue.

Ask “why?” a few times. Look at the numbers. The person who raised it should be able to say in one sentence what the root issue is before the team discusses solutions.

Step 4: Discuss it once

Everyone gets to speak. Nobody repeats a point someone already made. The facilitator watches for two failure modes:

• Tangents — related issues that belong on the list, not in this discussion.
• Politicking — people defending territory instead of solving the problem.

Healthy debate is good. Repetition is not.

Step 5: Decide

At some point, someone has to make a decision. Ideally the team reaches consensus. If not, the person who owns the area — or the integrator — decides. A good decision now beats a perfect decision in three weeks.

Then the decision sticks. No re-arguing it in the hallway after the meeting.

Step 6: Assign the to-do

Every solved issue produces at least one to-do with an owner and a due date — usually within a week. Without a to-do, the “solution” is just an opinion. The to-do gets reviewed in next week’s meeting.

A note on EOS and IDS

If you run EOS, you’ll recognize this as IDS — Identify, Discuss, Solve — one of EOS’s best-known tools. Many systems use some version of the same discipline. Whatever you call it, the sequence is what matters: root issue first, one discussion, a decision, a to-do. See EOS tools explained.

What healthy issue-solving looks like

• Leaders raise issues about their own areas, not just others’.
• The owner’s ideas go on the list like everyone else’s.
• The team solves the same few recurring issues once, instead of every quarter.
• Hard people issues get raised, not avoided.
• The list gets shorter over time, then refills with better problems.

Common mistakes

• Discussing during the reporting part of the meeting. Park it; solve it in the issues block.
• Solving symptoms. Dig for the root.
• Letting the loudest voice decide. The facilitator’s job is to hear everyone.
• No to-do. A decision without an owner is a wish.
• Avoiding people issues. These are often the root cause of everything else.

Where this fits

Issue-solving is the most important part of the weekly leadership meeting agenda and the quarterly planning meeting. It’s the Strategy part of the BOSS framework in action: issues are what stand between you and your Quarterly Goals.

An example from a real meeting

Here’s how one issue might move through the steps. The scoreboard shows customer complaints off track for the third week. On the list it reads “complaints up.” The team asks why: most complaints are about missed arrival windows. Why? The schedule is built the night before without checking crew capacity. Why? Nobody owns final schedule review since a coordinator left. That’s the real issue. Discussion takes ten minutes. Decision: the operations manager owns the daily schedule check by four in the afternoon, using a short checklist. To-do: draft the checklist by Friday. Next week, the to-do is done; two weeks later, the complaints number is back on track. One issue, solved once, instead of discussed for a month.

Next steps

Start an issues list this week. In your next meeting, pick the top three and solve them using these steps. If your team keeps getting stuck on the same issues, an outside facilitator can help — request a strategy call.