Make Your Level 10 Meeting Multiply the Work That Follows

A meeting can end on time and still leave the hardest decision untouched. The calendar block disappears. The issue stays open. Everyone returns to work carrying a slightly different understanding of what happens next.

That is the gap I want you to examine in your next leadership meeting. Before you decide whether the conversation was productive, look at what it made possible afterward. Can someone act without asking for another clarification? Did a recurring problem get an owner? Does the team know what it agreed to stop doing?

I want a Level 10 Meeting to multiply the quality of the work that follows. That requires more than showing up with an agenda. It requires leaders who will prepare honestly, make a decision when it is theirs to make, and let an uncomfortable issue receive more attention than a comfortable update.

Give the meeting a job beyond sharing information

My standard for a leadership meeting is simple: the business should be easier to lead when the meeting ends. People should leave knowing which problems need attention, which commitments remain in place, and where they have permission to move.

Information matters, but reading information aloud is a poor use of everybody's judgment. If a team member can review an update beforehand, give them that responsibility. Use the shared time to address the decisions that actually require the people present.

That distinction takes discipline. An update can feel productive because somebody is speaking clearly and everybody else understands the story. But understanding the story does not necessarily change the situation. I want you to notice when the team keeps adding context after it already has enough to identify the issue.

At Kairos, our EOS implementation process brings tools including the Accountability Chart, Rocks, Meeting Pulse, and Scorecard into the leadership team's operating discipline. My challenge is to use that discipline to make work clearer, rather than adding another layer of reporting.

Ask yourself what your team needs from you during the meeting. A department leader may need a decision about competing priorities. Another may need authority to change a process. Someone else may need you to acknowledge that the commitment you made last week remains unfinished.

Prepare for those moments. Bring the relevant information, identify what is uncertain, and state what needs to be decided. You do not need a polished explanation for every problem. You need an accurate enough picture for the team to take responsibility for the next step.

I would rather hear a plain description of a missed commitment than a persuasive account of how busy everybody has been. The first gives the team something useful to work with. The second can consume the available time without changing a single expectation.

Deal with the issue underneath the update

Consider a hypothetical situation: proposals keep leaving your company later than promised. Sales wants faster estimates. Operations wants cleaner information. The owner asks everybody to communicate better, and the same issue returns the following week.

Before prescribing another check-in, I would want the team to locate the actual breakdown. Does anyone own the handoff? Is there agreement on what a complete request includes? Who can resolve a conflict between an urgent proposal and work already promised to an existing customer?

Those questions lead to different decisions. A missing owner calls for clear responsibility. Incomplete inputs call for a defined handoff. Conflicting commitments call for someone with authority to choose the priority. Treating all three as a communication problem leaves too much unresolved.

Stay with the specific issue long enough to understand it. Write down what is happening, where it is happening, and what the team knows rather than assumes. If the evidence is missing, assign someone to collect it. Do not fill the gap with a confident opinion simply because silence feels uncomfortable.

The owner has a particular responsibility here. If you answer every question first, you make it difficult to learn how the rest of the team sees the problem. I want you to ask for their assessment before delivering yours. Let someone disagree without having to spend five minutes proving loyalty.

This does not require endless debate. It requires enough honesty to avoid solving the easiest version of the problem. Set a clear point at which the decision will be made, name who has the authority to make it, and document any information needed before that point.

You also need the courage to close the conversation. Once the decision is made, say what it means for the work. A useful discussion should not leave every participant free to choose the interpretation they prefer.

Make commitments clear enough to survive the week

I want every commitment leaving the meeting to answer three questions: Who owns it? What will be different when it is done? When will the team know whether it happened? If those answers require another conversation, the commitment needs more work.

Return to the proposal example. Assigning someone to improve the handoff sounds reasonable, but it leaves completion open to interpretation. A clearer commitment would name the person responsible for drafting the required intake fields, identify who must approve them, and establish a date for testing the new handoff.

Be careful about turning one decision into twelve assignments. The goal is to remove a problem, not create a project so elaborate that nobody can complete it alongside existing responsibilities. Choose the smallest meaningful action that will move the issue toward resolution.

Then look at capacity. If the person taking ownership already has several urgent commitments, decide what changes. You may need to remove work, adjust a deadline, or choose a different owner. Giving another task to the most dependable person without making that tradeoff deserves scrutiny.

I also want the person accepting the commitment to state it back in their own words. That brief step gives the team a chance to catch a mismatch before it becomes a missed expectation. Agreement should be clear enough that the person can explain both the assignment and the reason for it.

At the next meeting, begin with what actually happened. If the commitment was completed, confirm whether it addressed the problem. If it was missed, examine the cause without letting the explanation erase the obligation. An unclear assignment, an unavailable resource, and a choice to ignore the task need different responses.

Leaders belong inside this standard. When your name is attached to an unfinished commitment, own it without special treatment. Tell the team what happened and what you will do next. Do not ask them to practice a form of accountability you regularly excuse yourself from.

Protect the value after everyone leaves

The meeting's value depends partly on what you do between meetings. If you reverse an agreed decision in a private conversation and fail to inform the affected people, you have introduced confusion that another meeting will eventually need to repair.

There will be legitimate reasons to change direction. New information arrives. A customer requirement changes. An assumption turns out to be wrong. When that happens, identify the reason, involve the appropriate decision owner, and communicate the revised expectation to everyone affected.

What I want you to avoid is changing course simply because the next person who approached you made a compelling argument. Your team needs to know whether a decision is settled, being tested, or still under discussion. That distinction lets people act with appropriate confidence.

The same discipline applies to communicating beyond the leadership team. Before closing the meeting, decide what other employees need to know and who will tell them. Give them the relevant decision and expectation without distributing sensitive details they do not need.

For the next month, I would pay attention to a few practical signals: repeated issues, commitments that remain unfinished, and decisions that require follow-up clarification. Use those observations to improve how the team works. Do not turn the review into another elaborate administrative task.

This is also where business discipline connects to the rest of your life. I want leaders to consider whether preventable confusion at work keeps claiming attention they intended to give their family, health, or faith. Improving a meeting will not solve every boundary problem, but it is worth examining the problems you keep carrying home.

The force multiplier is the work your team can complete because a decision became clear. Protect that clarity. Let people execute, require them to bring back the result, and use the next meeting to address reality rather than repeat last week's promises.

Action Items From Today

1. Audit one recurring issue. Before your next Level 10 Meeting, find an issue that has appeared more than once without a clear resolution. Write a two-sentence description of the actual problem and name the decision you believe it requires.

1. Prepare the facts you already own. Update the numbers and commitments for which you are responsible before the meeting begins. Mark missing information plainly, and bring a plan for obtaining it rather than presenting an assumption as a fact.

1. Finish one commitment before creating several more. Choose a meaningful next action for the issue you discuss. Record one accountable owner, an observable result, and a due date, then have the owner confirm the assignment in their own words.

1. Make the capacity tradeoff visible. Ask what the new commitment competes with. Decide which existing work can wait, which resources are required, or whether the assignment belongs with someone else before adding it to the list.

1. Check the decision's path through the company. Identify who needs to know what was decided and assign responsibility for communicating it. At the next meeting, ask whether people could act on the decision without returning for clarification.

Five Bridges Challenges

• Internal: Bring one unfinished commitment of your own to the next meeting without rehearsing a defense. State what you committed to, what happened, and the correction you will make, then accept the same follow-up you expect from your team.

• Relationships: Ask a colleague whether your response to disagreement makes it easier or harder to raise an issue with you. Listen without correcting their account, and choose one behavior to practice differently in the next leadership discussion.

• Environment: Review how your team records and communicates decisions. Make one improvement this week that helps people find the owner, expected outcome, and due date without having to interrupt someone or search several message threads.

Bring a real issue to your next meeting and stay with it long enough to create a clear next step. Then give the person responsible the authority, capacity, and accountability to finish the work.

Inspire & Impact,

Josh