The leadership meeting is where a company either becomes leadership-led or stays founder-centered.
Most founders treat it as a standing update. Each person talks about their function. Issues are mentioned. A few questions get asked. Then the founder leaves with the real work: connecting the pieces, chasing follow-up, and making the calls the room did not make.
That meeting is expensive. It consumes senior time and still leaves the founder as the integrator.
A useful leadership meeting has a different job. It exists to resolve company-level issues, make the decisions that functions cannot make alone, and leave the room with owners and dates. Updates can happen in writing. The meeting should be reserved for work that requires the group.
This article explains how founders should design and run that meeting.
What the Meeting Is For
Start with purpose. If the purpose is “keep everyone informed,” the meeting will fill with status. If the purpose is “run the company together,” the agenda has to change.
A leadership meeting should do four things:
Review shared company outcomes
Resolve issues that sit between functions
Make or confirm joint decisions
Assign follow-through that does not depend on the founder
It should not be a tour of departments. It should not be the place where leaders discover basic facts they could have read in advance. It should not be a forum for every local problem that belongs inside one function.
Guidance:
Write one sentence before you redesign anything: “This meeting exists to _____.”
If the sentence is “share updates,” stop. Rewrite it until the purpose requires a decision, a tradeoff, or shared ownership.
Why Status Meetings Persist
Founders keep status meetings because they feel safe. Everyone speaks. No one has to confront a real tradeoff. The founder still hears what is going on.
The hidden cost is that the group never practices being a team. Functional leaders learn that their job in the room is to report, not to decide. Cross-functional issues get described and then parked. Accountability stays with the founder because no one left with a clear owner.
There is also a design problem. If the agenda is built by function, the conversation will stay inside functions. If the agenda is built by company issues, the conversation can move to the seams: handoffs, capacity, commitments, quality, cash, and priorities.
The meeting format teaches the team what kind of leadership is expected.
A Simple Meeting Design
Keep the design light. Complexity is not a sign of maturity.
Before the meeting
Shared outcomes and key metrics go out in writing.
Each leader submits issues that require the group, not updates about their week.
The founder or a designated facilitator chooses two or three issues that meet the test: this cannot be solved inside one function.
In the meeting
Start with shared outcomes, not individual reports.
Spend the middle of the meeting on the two or three issues that need a decision or a joint plan.
End with owners, next actions, and dates.
After the meeting
Send a short decision log.
Do not reopen settled items unless new information appears.
Do not become the unofficial project manager for every action.
Ninety minutes is enough for most teams at this stage. If the meeting regularly runs long, the agenda is doing too much reporting or too little pre-work.
How the Founder Should Behave in the Room
This is the part that determines whether the design works.
The founder’s job is not to be the smartest person on every issue. It is to keep the meeting at the right altitude, force decisions to land, and refuse work that belongs to the team.
That means:
Asking “Who owns this?” before offering a solution
Sending functional issues back out of the room
Making founder decisions only when the issue belongs in that bucket
Letting two leaders finish a disagreement instead of mediating too early
Closing the item with a name and a date
It also means not using the meeting as a personal briefing. If you need more context, get it before the meeting or in a separate conversation. Using the full leadership team as your information system trains them to perform for you rather than work with each other.
Example:
A delivery problem surfaces. Sales says customers are waiting. Operations says the commit was unrealistic. The founder who stays in hero mode starts redesigning the process live. The founder who is building a leadership team asks the two leaders to recommend a decision: slip the date, add capacity, or change the commit policy. The room then accepts or amends that recommendation. The founder stays in the conversation. The founder does not become the department of integration.
What to Keep Off the Agenda
Remove three kinds of items.
First, updates that do not require a decision. Put them in a written packet.
Second, issues owned by one leader. Those belong in a one-on-one or a functional meeting.
Third, unresolved ideas with no recommendation. “We should talk about hiring” is not an agenda item. “We need to decide whether to freeze non-critical hiring for 30 days” is.
A useful filter is this: if the item cannot end with a decision, an owner, or a clear next experiment, it is not ready for the leadership meeting.
Follow-Through Is Part of the Meeting
A meeting without follow-through is just an expensive conversation. The last ten minutes matter as much as the first.
Capture:
The decision
The owner
The date
Who else must be informed
Then stop absorbing the follow-up. If the same actions return next week still undone, that is a leadership-team issue, not a note-taking issue. Address the missed commitment in the room. Do not quietly complete the work yourself. That teaches the group that accountability is optional because the founder will catch what drops.
Example: The Same Team, Two Meeting Designs
One founder ran a weekly round-robin. Each leader spoke for ten minutes. The meeting felt inclusive and produced almost no decisions. Afterward the founder spent two days closing loops.
Another founder used the same people and the same 90 minutes. The packet went out the day before. The agenda had three items: a launch commit, a capacity constraint, and a pricing exception policy. Two decisions were made. One issue was sent back to two leaders with a 48-hour deadline. The founder’s follow-up list got shorter because the work had owners.
The talent did not change first. The meeting design did.
Practical Guidance for This Week
Do not overhaul every leadership ritual at once. Change the next meeting.
Write the purpose sentence and send it with the agenda.
Replace the functional tour with two or three company issues.
Require a recommendation for any issue that reaches the room.
End with a visible decision log.
Choose one follow-up you would normally take home and leave it with the owner.
Then watch what happens after the meeting. If issues still return to you in the same form, the meeting has not changed yet. If leaders begin resolving the seams themselves, the meeting is starting to do its job.
Looking Ahead in This Series
A leadership team is not created by putting senior people in a recurring block. It is created when those people own functions, know who decides, and use their time together to run the company.
Next week we will look at accountability without bureaucracy: how to keep commitments real without adding layers of process that slow the team down.
Paid subscribers will receive the Leadership Meeting and Cadence Workbook in our next article. It includes agenda templates, decision-log formats, pre-read structure, and a weekly-to-monthly cadence you can install directly.
Let’s Get Entrepreneurial is published by ProfSpirit LLC.