A weekly huddle is the 90-minute leadership meeting at the center of the Trinity Cadence operating rhythm. It follows the same seven-segment agenda every week: opening, scorecard, priority check, headlines, to-do review, issue solving, and a closing rating. This guide walks the full agenda, gives you a copy-paste template, and tells you honestly where the format breaks.
Definition: a weekly huddle is a weekly, 90-minute leadership team meeting with a fixed seven-part agenda, where most of the time is reserved for identifying and solving the most important issues in the business.
I have run this meeting, coached it, and watched it die in more conference rooms than I can count over 30+ years as an operator and fractional COO. It is a genuinely good meeting format. It is also routinely mistaken for an operating system, and that mistake is where most of the trouble starts. Both halves of that sentence deserve a fair treatment, so here it is.
What Is a Weekly Huddle?
The weekly huddle is the weekly gear of the operating cadence: the one meeting where the leadership team looks at real numbers together and works the biggest problems to a decision. The closing ritual gives it its bite: the meeting ends with everyone rating it from 1 to 10, and the standing goal is a meeting the team honestly scores a 10. The basics are simple to state.
→ Who: the leadership team, usually three to seven people. Departments run their own version downstream.
→ When: same day, same time, every week. It starts on time and ends on time, whether or not the CEO is in the room.
→ How long: 90 minutes, of which 60 belong to issue solving.
The insight underneath the format is one I will defend anywhere: a leadership team that meets weekly against real numbers, with protected time to actually solve things, will out-execute a team that meets ad hoc to trade status updates. That insight is not proprietary to any framework. The specific agenda is just a disciplined way to act on it.
What Is the Weekly Huddle Agenda?
Seven segments, same order, every week. The clock discipline is the feature, not a suggestion.
| Segment | Minutes | What happens |
|---|---|---|
| Opening | 5 | Each person shares a personal best and a business best from the week. Gets the room human before it gets tactical. |
| Scorecard | 5 | Five to fifteen weekly numbers, each reported on track or off track. No discussion; off-track numbers drop to the issues list. |
| Priority check | 5 | Each quarterly priority reported on track or off track. Same rule: problems go to the list, not into a debate. |
| Headlines | 5 | One-line customer and employee news. Good, bad, notable. Anything that needs work becomes an issue. |
| To-do review | 5 | Last week's to-dos, done or not done. The bar is done, and the list should clear at a high rate week over week. |
| Issue solving | 60 | Pick the three most important issues. Identify the root, discuss it once, decide and assign an owner. |
| Closing | 5 | Recap to-dos, agree on what cascades to the company, rate the meeting 1 to 10. |
Issue solving deserves a closer look because it is two thirds of the meeting, and it runs in three moves. Identify means naming the root issue, which is rarely the one first stated. "We missed the ship date" is a symptom; "we have no capacity buffer in production" is an issue. Discuss means everyone says their piece once, without laps. Decide means the issue leaves the list with an owner and a next action. Solved issues do not come back; badly solved ones do, and the list keeps score on you honestly.
Copy-Paste Weekly Huddle Agenda Template
Drop this into your calendar invite or meeting doc. It is the standard format, ready to run.
Why Does the Huddle Format Work?
Four reasons, all of them portable to any meeting you run.
First, the fixed agenda removes the weekly negotiation about what the meeting is for. Nobody preps a deck. The meeting costs nothing to start.
Second, numbers come before opinions. By the time anyone is allowed to argue, the scorecard has already said what is true. That ordering kills the loudest-voice-wins dynamic that ruins most leadership meetings.
Third, the 60-minute issues block is protected. Most teams spend meetings reporting and save solving for hallways. This format inverts that, and the inversion is worth more than everything else combined.
Fourth, the closing rating creates a feedback loop on the meeting itself. Teams that rate honestly fix their own meeting inside a quarter.
Where Does the Weekly Huddle Break Down?
Now the part the template downloads skip. I have watched this meeting decay the same way in company after company, and the failure points are predictable.
The opening becomes theater. By month four it is a rote lap of "good weekend, big deal closed" that adds five minutes and zero humanity. The fix is smaller and realer prompts, not skipping it.
The scorecard goes stale. Numbers stay on the sheet because removing them feels like admitting the original pick was wrong. A scorecard nobody would fight to keep is dead weight, and reading dead numbers out loud weekly trains the team that the meeting is ritual.
Issue solving runs on anecdote. Sixty minutes of solving is only as good as the information in the room. When the issue is "why did churn tick up," a team without data in front of it discusses hypotheses and solves with a guess. The format assumes the facts walked in the door with the attendees. In most rooms they did not.
The meeting outlives the cadence around it. This is the big one. The weekly huddle is the most durable habit in any operating rhythm, so it is usually the last thing running after the quarterly planning slips, the annual session gets skipped, and the priorities stop connecting to anything. What remains looks like discipline but is a status meeting wearing the huddle's name. A weekly rhythm can only compound inside a full cadence.
The Huddle Is One Rhythm. A Company Runs on Five.
Here is the reframe that matters more than any agenda tweak: the weekly huddle is one gear in a machine, and the machine is the operating cadence. At Trinity Cadence we structure that machine as five connected rhythms.
→ Weekly Huddle. The meeting this guide covers, with the agenda pre-built by the platform from live data before anyone sits down. The four jobs are align, measure, resolve, commit; the weekly leadership meeting guide covers those jobs in full, plus a tighter 75-minute variant for teams whose prep arrives assembled.
→ Weekly Pulse. The scorecard, wired to source systems instead of hand-entered, so the numbers arrive current and the off-track ones arrive pre-flagged with context.
→ Quarterly Recalibration. Priorities (we call them Anchors) get set, scored, and reset against the annual plan, so the weekly meeting always rolls up to something.
→ Quarterly Check-Ins. The human layer: every person, their trajectory and their goals, on the same cadence as the business. People are not seats.
→ Annual Reset. The Blueprint: vision, targets, and the year's bets, revisited on schedule rather than when the wheels wobble.
The difference AI makes is specific, not cosmetic. In the Huddle, the agenda arrives assembled: Pulse numbers scored, issues ranked by impact, last week's commitments checked against what actually happened in the connected systems. The 60-minute solving block starts from evidence instead of recollection. That is the failure point of most weekly meetings fixed at the root, and it is what we mean when we say the platform is AI-native rather than AI-bolted-on.
Do You Need Special Software to Run a Weekly Huddle?
No, and most teams should start without any. The format is public knowledge and the disciplines inside it are older than any framework: fixed agenda, facts before opinions, issues worked to completion, commitments with owners. If your leadership team meets weekly and none of those four are true, start with the template above this week. It will make you better within a month.
If you are further along and evaluating operating systems as a whole, two honest resources: our guide to the major business operating systems, which treats each one fairly including where ours is weaker, and the side-by-side comparison if you want the short version. The summary position: the weekly meeting is the easy part. The cadence around it, and the data underneath it, are where execution actually compounds.
Frequently Asked Questions
What is a weekly huddle?
A weekly huddle is a 90-minute leadership team meeting held at the same time every week, built on a fixed seven-segment agenda: opening, scorecard, priority check, headlines, to-do review, issue solving, and a closing rating. Most of the time is protected for solving the most important issues in the business.
How long should a weekly huddle be?
Ninety minutes, held at the same time on the same day every week. Five short segments take the first half hour and issue solving gets the remaining sixty minutes. Starting and ending on time is part of the format, not a nicety.
Who should attend the weekly huddle?
The leadership team, typically three to seven people who own the major functions. Departments then run their own version of the meeting with their teams. It is not an all-hands and it is not optional for the people in it.
What happens in the issue solving block?
The team ranks the issues list and takes the three most important items. For each one: identify the root issue, which is rarely the one first stated, discuss it once without laps, then decide and assign an owner. Every decision leaves the meeting as a to-do with a name on it. It is the engine of the meeting.
What goes on the scorecard in a weekly huddle?
Five to fifteen weekly numbers, each owned by one person, each with a goal. Revenue, cash, pipeline, production, service metrics. The report is binary: on track or off track. Off-track numbers drop to the issues list rather than getting discussed on the spot.
What is the difference between a weekly huddle and a regular staff meeting?
A staff meeting is usually a status readout with a floating agenda. A weekly huddle has a fixed agenda, numbers reported against goals, and sixty protected minutes for solving the most important issues to completion. Status is the smallest part of it, not the whole meeting.
Do you need special software to run a weekly huddle?
No. A shared doc and the template in this guide are enough to start this week. Software earns its place when the prep automates: a platform like Trinity Cadence builds the agenda from live data, scores the scorecard, and ranks the issues before anyone sits down, so the meeting starts at the solving part.