The Operating Rhythm
Ineffective Leadership Meetings: How to Tell Yours Is a Status Report


Jon Wilhoit
Jon Wilhoit is a Professional EOS Implementer based in Atlanta. He has over 40 years of experience working with and for small and medium sized businesses, helping them increase revenue and profitability, and building high-quality teams.
A status-report meeting is one where the team reports and nobody solves. Each person takes a turn, describes the state of their piece of the business, and the group leaves with the same problems it brought. I call that reading the mail. If your weekly leadership meeting sounds like this, you have a status report with a calendar invite, and the fix starts with how you handle updates.
What a status-report meeting looks like
Each participant gives an update on the progress of their piece of the world. Take a sales pipeline meeting. Each rep reviews their current pipeline: “For Deal A, the total contract value is $X, it’s on schedule to close on Y date. We’re at this stage of the sales cycle, and my next step is ______. For Deal B…” And so it goes.
I don’t sit in on a client’s leadership meeting until the team uses the structured weekly agenda I teach. Before that, A validator runs the meetings I see. The leader wants confirmation that everything is on track. Everyone else zones out.
Participants get good at a game I call Kill the Clock. They drag out their updates until little time remains for questions that could put them on the spot. A leader who gives a two-minute warning leaves room for questions, but those questions dig for validation that the rep is telling the truth. They skip the real issues and the opportunities that drive the business. The two-minute warning gives every update the same weight, and one person’s issue could be worth the entire meeting.
Signs your leadership meeting is a status report
Six signs show up in these meetings.
Updates run long and spark discussion
Each update starts as a report and ends as a conversation. Nobody stops it, because the conversation feels productive. Much of that discussion supports an excuse or satisfies curiosity.
The same arguments come back every week
The team beats an issue to death, agrees to do homework, and reconvenes to beat it again. The discussion stays on the surface and does not reach the root cause, so the same issue returns.
The loudest voice sets the direction
The loudest voice or a domineering leader drives the conversation. People restate opinions, and the conversation has no clear objective.
Easy issues eat the clock and hard ones get punted
A simple issue takes the whole meeting because everyone understands it and has a view. The important issue waits for next week. Missing trust makes this worse, because the team avoids the key issues.
Decisions end in more homework
I see four reasons decisions stall: lack of accountability, lack of information, fear of the pain of change, and no time because less important issues control the clock.
People leave drained and nobody owns an action
The team walks out tired, and issues turn into fires. If nobody can name an action the team took because of the meeting, the meeting produced none.
Why teams drift into status reporting
Teams drift into status reporting because it is the easy default, and the discipline to avoid it does not feel natural. Four causes show up in the meetings I see.
A domineering founder. The founder sets the direction, and the team follows.
A weak meeting leader. Nobody holds the agenda, so updates expand to fill the time.
Surface-level discussion. The team talks about the symptom and does not find the root cause.
Endless updates. Updates leave no room for the issues that matter.
What a meeting that solves issues looks like
A meeting that solves issues keeps updates short and spends its time on the most important issues. Updates state the numbers. Anything that needs discussion goes onto the issues list instead of triggering a discussion on the spot. The team picks the top three issues, finds the root cause of each, weighs a few options, names one owner, and moves on.
Here is the same sales update in a meeting that solves. It starts with the sales leader, not the rep. The leader says: “OK, I read your update report. It seems all your deals are on track for your projected close dates. Deals C and D are your biggest deals and have a couple of incomplete steps in our sales process. What are the two biggest concerns for each of those deals?” The leader and the team dig in and help the rep build a plan to maximize the likelihood of closing those deals.
Compare the status-report version. The usual follow-up questions ask whether you are meeting the decision maker, whether you qualified the deal with a sales qualification method, and when the leader can meet the decision maker. Those questions seek validation. They do not build a plan.
For the full format, the agenda, and who attends, read How to Run an Effective Leadership Meeting.
When an update belongs in the meeting
Updates belong in the meeting. They need their own section. The update section holds updates and nothing else, and the issue-solving section solves the most important issues. The team can prioritize issues after every update is in.
Here is what happens when the order breaks. The first update sparks a debate about how to handle an objection from a new competitor. The topic is important, and everyone has an opinion. The debate uses 80% of the meeting. The remaining participants give a cursory overview of their updates, and everyone leaves for another week. Nobody meets that objection during the week, but two of the participants who had no chance to give their updates lose key deals because they got none of the input they needed. If all the updates had come first, the sales leader could have put pursuit strategies for those two deals at the top of the list, and the meeting would have returned more for the time invested.
Real leadership shows up when an update sparks a debate. The leader stops the conversation and writes the issue on the list.
How to change the next meeting
Make one change first. Run all the updates, with no discussion. When an update sparks a debate, stop it, write the issue on the list, and move on. After the updates, prioritize the list and solve the top issues. It does not feel natural to cut someone off, write their issue down, and move on. The team has to practice it.
Owners tell me their meetings are fine. If you believe that, ask yourself these questions:
What actions has your team taken as a result of the discussion in your meetings?
How does your team benefit from your meetings other than being up to date on each other’s activity?
What are five “meaty” issues your team resolved in your last two meetings?
What percentage of time would remain if you stripped out all updates?
If every team member sent their update to the team in advance, and every team member had to know those updates, what would your meeting look like?
A real example
I worked with a software company team whose leadership meetings did not work. Everyone focused on their own domain. Conversations had no clear objective. People restated their opinions, or the loudest voice drove the direction. People left drained, and issues turned into fires.
When the meetings changed, the owner noticed what every owner notices: the team had wasted so much time. The change is a major breakthrough when everyone on the team understands how efficient it is. Nobody gets their feelings hurt, and the company benefits.
Frequently asked questions
Why do our leadership meetings feel like a waste of time?
They feel like a waste because the team reports and nobody solves. Updates run long, discussion drifts, and the important issue waits. Updates that state the numbers, an issues list, and a top three fix that.
How long should an update take?
An update takes as long as it needs to state the numbers, and then it stops. If an update needs discussion, it is an issue, and it goes on the list.
How do I know my meeting worked?
You can name the issues your team resolved, and each one has an owner and a next step. The five questions above give you a quick check.
Should this meeting be an email?
Run the last question above. Strip out the updates and see what time remains. If every update could arrive by email and nothing remains, you have a report, and a meeting adds nothing. If issues remain, hold the meeting for them.
Key takeaways
A status-report meeting is one where the team reports and nobody solves.
Long updates, repeat arguments, a loud voice, easy issues, more homework, and drained people are the signs.
Updates state the numbers. Discussion goes on the issues list. The team solves the top three issues, names an owner for each, and moves on.
If your meeting sounds like this, schedule a call with me. We can talk through how your team meets today. For follow-through after the meeting, read How to Hold a Leadership Team Accountable (Without Constant Friction).
More Articles from Jon
The Founders Problem
4
Why Did My Business Stop Growing
A business stops growing when its leaders face new problems with old habits. Jon Wilhoit, an Atlanta EOS Implementer, explains the signs and the first change.
Building The Team
11 minutes
Business Coach vs. Consultant vs. Facilitator: Which Does Your Leadership Team Need?
Business coach vs. consultant vs. facilitator: each solves a different problem. Here's how to tell which one your leadership team actually needs.
Our Promise