Why Your Meeting Went Back to Status Updates

Last week’s issue was about sitting down at the bank already knowing what the lender will see. This week is about a room you are in every week and the meeting you just want to be over. Somewhere around the sixth week is when this feeling usually happens. You created the new formatted agenda. It included a look back at last week’s list, the at-risk lines, and a summary at the end. For a month and a half, it worked. Then one Monday, you just felt it, and the hour was department updates again. Sales gave their update, then Operations, and finally Finance, as usual. Everyone left informed. Nothing got decided.

Nobody chose to go back to their old ways. The team just let it slip back into business as usual on its own. Everyone knows, deep down, that once a meeting slides, it will slide again unless you fully commit to the new cadence.

The Commitment Nobody Asked About Again

Years ago, our leadership team committed in a leadership meeting to a new inventory system. We were shipping large orders all over the country, and we had automated how we tracked them. We all knew it was on the list.

The manager who owned the system decided the old way was easier and kept using it.

Two weeks slipped by before anyone noticed. By then, more than twenty large orders had shipped to the wrong customers across the country. We found out when customers called in. That was our detection system. Our customers.

Our failure to implement the new system cost us several thousand dollars in freight. But more than that, it cost us something harder to get back. It cost us our credibility with customers who had trusted us to get it right. When our customers started calling, our president asked, “Why didn’t our new system catch it?” Nobody in the room knew the new system wasn’t being used out there on the floor.

Here is the thing. That failure belonged to the management team, not to the manager. Nobody asked him again, because there was no place on any agenda where “are we actually on the new system” had to come back. A commitment nobody has to answer for again isn’t a commitment, and both customers and team suffer for it.

We had weekly meetings as usual. We quietly stopped asking follow-up questions, assuming things were getting done.

What the Slide Looks Like

The slide has an order. It is the same order almost every time, because it follows comfort.

First to go: the look back. The ten minutes, right after the scoreboard statuses, where last week’s action items get read aloud, done or carried forward, and somebody brings up the follow-through rate. It is the only block that can make a person look bad, so it is the first one the team decides to “pick up next week.” Once it is dropped from the list, it has nowhere to come back to. The team learns that fast.

Then the issues block is replaced with reports. Thirty-five minutes are intended for the at-risk lines. Without the look-back starting the discussion, one department head opens with what happened this week, and the other department leaders follow suit. By minute forty, the hour has been informational and at-risk items have been mentioned. They have not been decided.

Last to go: the read-back. The meeting closes with the new commitments read back with a name and a date. It sits at the end, so it is what gets cut when the hour runs long. And the hour always runs long once the reports start. Once again, you feel the death-by-meeting syndrome. It’s a gradual slide toward the easiest version of the hour. It’s still a good agenda. You dropped three blocks because of old habits, and you stay stuck in the operational details.

What It Looks Like When It Holds

Same hour, same people, same four blocks from the 60-minute agenda. The difference is what happens at three moments.

The list comes before any report. Five minutes of statuses, then last week’s commitments, read aloud. Done or carried. Anything carried gets a fresh date on the spot, or is killed on purpose. After twelve weeks of that, “Are we on the new system?” cannot go unasked, because it sits on the list with a name next to it.

“At risk” ends in one of two ways. A decision with an owner and a date, or a plain sentence about what needs an answer and who owns it. A report that ends with “so that’s where we are” is not one of the two ways. Someone has to be allowed to say “that’s an action item, put it in the notes,” without fear of calling people out.

The read-back is protected. When the hour runs long, an issue gets carried to next week. The read-back does not. It’s ten minutes, every time, even when your team would rather leave.

The Reset

You do not need a new agenda. The one you have is fine. You need three actions, and the owner has to take the first one.

Put the look back in the second block of the hour, right after the statuses and before a single report. Don’t put it at the end when you have run out of time. Nobody wants to hear a bad follow-through rate; they need to hear it.

Send the reports the day before. Write down anything that the team can read and send it Sunday night or Monday morning. Use the hour for the at-risk lines and nothing else. If a department head has nothing at risk, they have nothing to say in the issues block, and that is a good week for them.

Give the read-back a bodyguard. Someone other than the owner, whose only job at minute fifty is to say “we’re reading back now.” When the meeting owner is also the one deciding whether to cut the close, the close gets cut. Hand that job to someone else.

None of this should require a new tool or additional meeting time. It puts the look-back before the reports. After that, the team knows those questions will come back. That is the difference between a meeting that makes decisions and a meeting where nothing gets done.

The Test

Run this test with last week’s meeting:

• Were last week’s action items read aloud, and did anyone mention the follow-through rate?
• When something was at risk, did it end in a decision or an agreement to move it forward, or did it end with “so that’s where we are”?
• When the hour ran long, what got cut: an issue, or the read-back?

If the first one stopped you, that is the block that went first, and it is where the reset starts.

The one-page agenda is free at alinement.com/brief/tools/sixty-minute-agenda. Print it again, hold the first fifteen minutes to what it says, and run it Monday.

Which meeting block slid first with your team: the look back, the issues, or the read-back? Share your thoughts.

P.S. Next week: why you are losing deals to competitors half your size, and the two hours a month that change it.