During our weekly status meetings, my directors spend 45 minutes reading their project updates out loud instead of discussing execution blocks. How do I change this format?

Question

Tyler Smith · Accepted Answer

If your directors are reading status updates out loud, you are running an expensive storytime, not an [execution meeting](/qa/fixing-ineffective-weekly-leadership-meetings). This behavior is a form of "status management" designed to make everyone look busy and avoid vulnerability. It wastes the collective brainpower of your leadership team on information that should have been read in five minutes before the meeting started.

You must shift your weekly meetings from "reporting" to "problem-solving." While structured systems like the Level 10 Meeting™ offer great frameworks for this, you can fix the behavior immediately by enforcing three structural rules:

• The "Read Ahead" Mandate: All written updates must be submitted to your shared document or software by 9:00 AM on the day of the meeting. If a leader fails to update their section in time, their priority is automatically marked as "Red" for the week. This ensures everyone comes prepared, similar to how you might use [AI to prep data](/qa/using-ai-in-meeting-prep).
• The Exception-Only Rule: Ban the reading of any update that is on track (Green). The meeting agenda should skip Green items entirely. The first question asked is: "We have three items flagged as Red or Yellow. Let's spend our time solving those blocks." This helps shift the focus from [status reports to resolving issues](/qa/stop-weekly-leadership-meetings-devolving-into-status-reports).
• The 5-Minute Update Limit: If a director needs to provide context on a priority, they have exactly 60 seconds to state the block, what they've tried, and who they need help from. This prevents [meeting storytime and endless venting](/qa/stop-meeting-storytime-venting).

Say this to your team next week: "We are all capable of reading. I assume everything is on track unless it is flagged as red. From now on, we will only spend our time together solving the problems that are keeping us from hitting our numbers."

AI never sits in the room. It works before the Level 10 Meeting to prep the data and after the meeting to capture and track what was decided. The 90 minutes stay human: your leadership team, the scorecard, the issues list, and the IDS conversation. For more on this, consider [using AI effectively before and after meetings](/qa/how-to-use-ai-before-after-weekly-leadership-meetings).

Related questions

• [Our weekly leadership meetings are turning into status updates instead of strategic problem solving. How do I force my team to shift from reporting to actually resolving issues?](/qa/stop-weekly-leadership-meetings-devolving-into-status-reports)
• [We want to move away from the standard EOS Level 10 Meeting structure. What is an alternative ninety-minute weekly executive agenda that actually drives execution?](/qa/alternative-weekly-executive-meeting-agenda)
• [I want to use AI to make our weekly leadership meetings more efficient. Can I use ChatGPT to analyze our scorecard before we meet, or is that cheating?](/qa/using-ai-in-meeting-prep)
• [My executive team gets trapped in story time during our weekly issue solving session. How do I stop the endless venting and get to a real decision?](/qa/stop-meeting-storytime-venting)