Back to all posts

Why Meetings End with Everyone Nodding and Nothing Getting Done: A Conversation with Mike Simmons

Catalyst Sale’s Mike Simmons on said vs. heard vs. remembered, the three jobs of any meeting and how to help reps hold themselves accountable.
November 17, 2026
Brian Trautschold

Table of contents

See the System in Action

Book a Demo

Catalyst Sale’s Mike Simmons on said vs. heard vs. remembered, the three jobs of any meeting and why a leader’s job is to help reps hold themselves accountable.

Every sales leader has run a meeting where everyone nodded, everyone agreed and nothing happened afterward. I sat down with Mike Simmons, founder of Catalyst Sale, on the Sales Operator Series to ask why. Mike has worked in high-growth tech for more than two decades and spends his time in rooms with CROs, owners and leadership teams. We’ve known each other for almost a decade, and it was fun to catch up.

Meetings might sound like a dry topic, but trust me that Mike makes them pop off the whiteboard.

Here’s a recap of our conversation. You can watch the full episode below.

Why do meetings end with everyone nodding and nothing getting done?

When I asked Mike what comes up most with the leaders he talks to, he said the topic getting the most attention is something he calls “said, heard, remembered.” When teams communicate, there are things that are said, things that are heard and things that are remembered, and very rarely are all three the same. Everybody nods, then leaves with a different understanding.

He told me about a global offsite he’d just run in Vienna for a large organization, led by its global CFO. The question in the room was why things discussed in meetings don’t get done once people go back to work. The group of 30 represented 12 countries, and English was the business language but not everyone’s first. Assumptions crept in. Mike’s point is that the same happens inside your own organization. Say “write it in black,” and nobody asks where to write it, how long it needs to stay or what should happen with it.

What is the most important question a leader can ask?

“What did you hear me say?”

Mike says this is a critical question that most sales leaders fail to ask. When you do ask it, the hard part follows: be quiet and listen, don’t interrupt, let them finish, and then clarify what needs adjusting. And take ownership. If they didn’t hear it right, you didn’t communicate it effectively.

If you’re leading a room, he suggests flipping it: “Here’s what I heard everyone say. These are the top three things we need to focus on, and these are the three things getting in the way.” No more than three. If someone’s struggling to do one thing today, the last thing they need is five. Mike’s formula is to deconstruct, isolate variables and simplify.

He also noted that the noise out there is huge. Many tools are designed to distract you, so it’s no surprise people struggle to execute.

Why shouldn’t leaders hold their teams accountable?

This was a spicy one. Mike says people see his “said, heard, remembered” idea and think it’s a way to hold their people accountable. He doesn't think that's the best way to look at it. It’s not your responsibility as a leader to hold your team accountable. It’s your responsibility to help them hold themselves accountable.

Part of the reason is that having people raise their hands and say what they’ll do is important, but it isn’t enough. Many things influence whether behavior changes after the meeting, which is where the COM-B model comes in (developed by Susan Michie and colleagues). It looks at three things:

  • Capability: do they have the knowledge and skill? Mike joked that he’s “not built to dunk basketballs.”
  • Opportunity: do they have the time, access and conditions to do it?
  • Motivation: do they care?

If any of those is missing, behavior change won’t happen. So before you blame effort, figure out which one is the real gap.

How can a sales manager call plan their own team meeting?

I asked how a manager with eight reps could put this into practice. Mike’s first piece of advice: do what you ask your team to do with customers. Go into your meeting with a call plan.

  1. Who’s going to be in the room? What do you anticipate their objectives are, and why are they spending time and attention on this?
  2. What are your objectives as the leader? Limit it to three, and Mike says you get bonus points for one.
  3. What do you want people thinking, feeling, saying and doing before they walk out?
  4. What are the desired next steps? Again, no more than three, and Mike wants to own two of the three himself. That way he can trade with the team, use them as reminders and help people hold themselves accountable for the other one.

Mike says it’s call planning 101, and that your team probably isn’t doing it because they’ve been given scripts and told to “MEDDPICC everybody to death.” He also shared that in his days running forecast meetings, his main goal was to sit on the side of the table where the round robin didn’t start.

A practical definition of multi-threading

While describing how he brings customers together from multiple perspectives, Mike gave the best definition of multi-threading I’ve heard. It isn’t having the same conversation with eight different people and letting them hang out. It’s having those conversations and pulling the information together so you can deliver something in context for each person.

What are the three jobs to be done of any meeting?

This part resonated with me. In a lot of companies, there’s a senior leadership meeting every Monday, and no one says whether we’re updating, disseminating or deciding. Mike applied Clayton Christensen’s “jobs to be done” idea to meetings. His view is that any meeting has one of three jobs, and you can only do one at a time. Try to do more and you end up with a parking lot of items that get deferred while everyone gets frustrated.

1. Convey information and get feedback

You’re sharing information and expecting questions or confirmation that people understood. Mike says you often learn more from the questions people ask than from the information you share. Treat your team as your internal market and don’t dismiss questions. As a leader, ask the question you have, because someone else probably has it too and lacks the confidence to raise it. And if you’re not open to feedback, he says, just record it and send the video.

2. Make a decision

Put a line in the sand: yes or no, do or do not. To run it well, define exactly what you’re deciding, then lay out at least two criteria for how you’ll decide, and share it all in advance so the conversation is about the decision. Mike draws on the Eisenhower matrix: decide on importance alone and you get stuck, decide on urgency alone and others drive you, but using two axes gives you a speed bump to gain perspective and de-risk. And a decision meeting isn’t a problem-solving meeting. If you try to do both, you’re doing too much.

I liked the binary nature of this. The outcome isn’t “we’ll try hard,” it’s yes or no.

3. Collaborate

This is where Mike says we waste the most time, with ideas dismissed, people checked out and others brute-forcing their point of view. He works through three types:

  • Problem solving: his “hexagon” of what, who, why, how, when and what’s next.
  • Process design: designing for a specific experience, using board game metaphors like Game of Life for the customer journey, Chutes and Ladders for the sales process and forecasting, and Monopoly for the rep’s approach.
  • Strategy and tactics alignment: a three-by-three model to build your game plan.

These are hard to run internally because we all have blind spots, and leaders often want to be the star. A new manager tends to try to train when they should coach. Bringing in an external facilitator lets you sit back, observe and hear things you’d miss while thinking about what to say next.

How do decision criteria help your team push back on shiny objects?

Mike pointed to something every sales team knows. A leader returns from a conference or finishes a book and throws something shiny over the fence. If your team has decision criteria, he says, they’re comfortable pushing back with “How does this align with what we’ve decided is important?” He called these guiding and operating principles for the business, not core values. They also help people make decisions in the field, which builds better leaders.

How can sales teams adapt faster when everything is changing?

I closed by asking what leaders should do when they need to roll out a new process or respond to new competitors and want everyone bought in. Mike went back to said, heard and remembered. The gap between said and heard is usually distraction, since people get messages through Slack, text, email and video. So simplify, create clarity and connect the new thing to what people already know. There’s nothing new under the sun, as he put it, and your team already knows a lot. They just get distracted.

Then take action, because you can’t reflect on what you’re going to do, only on what you did. Ask whether they did the work, why not if they didn’t, whether the work worked and whether you gave it enough time.

Mike says leaders often misdiagnose. They think they need to solve for execution when the real issue is communication, alignment or confusion. His answer for adapting is to iterate, and he pointed me to John Boyd’s OODA loop: observe, orient, decide, act. Working in loops, he says, helps you decide faster based on actual data and adapt to what your customers need, not just what the market says you should do.

He also had a pointed take on methodologies. If MEDDIC worked, he argued, it wouldn’t have become MEDDPICC, SPICED or BANT. We treat them as dogma because we want to belong to a group that says it works. His advice is to ask your internal and external customers, simplify through reduction, isolate variables, test, and let the data tell its story. His version of Einstein: “as simple as possible, complex as necessary.”

What I’m taking away

My biggest takeaway is that many of the execution problems we diagnose in sales teams may actually be communication problems. Before adding another process or tool, check whether the team heard what you said and whether the meeting you ran had one clear job.

For managers, start small. Call plan your next team meeting, name its job, limit it to three objectives and ask your team what they heard.

To hear the whole conversation, watch the full episode on the Sales Operator Series. You can find Mike and his work at catalystsale.com.

See the system in action

Book a Demo
RESOURCES FOR REVENUE TEAMS

Insights for high-achieving sales teams

View All
Revenue Strategy
Why Meetings End with Everyone Nodding and Nothing Getting Done: A Conversation with Mike Simmons
Catalyst Sale’s Mike Simmons on said vs. heard vs. remembered, the three jobs of any meeting and how to help reps hold themselves accountable.
Read More
Product Tips & Tricks
How To: Build Coaching Templates Every Team Can Use (A Guide for Admins)
Coaching templates set the agenda, the instructions managers see, who can use it, and the metrics and ratings admins care about. Build it once, and every Session created from it starts in the same place.
Read More
Company News
New: Scheduled Skills for No-Click Coaching Insights (Delivered to Your Inbox)
New capability runs AI Skills automatically on a set cadence and delivers insights straight to managers' inboxes, closing the gap between knowing what to coach and coaching consistently.
Read More

Stop chasing targets, start predicting revenue

Transform your revenue org into a high-performing growth engine with structured insights, top-down visibility, and built-in consistency.

Book a Demo