Bottleneck Huddle for Small Teams

Your team can spend the week arguing about the second and third problems while the first one quietly eats the quarter. Databricks was valued at $190 billion. Databricks CEO Ali Ghodsi said his team holds an 8 a.m. session on Mondays, Wednesdays, and Fridays to pinpoint the company's largest bottleneck. The useful part is the shape: one recurring meeting that forces a choice, assigns an owner, and keeps the main thing from being displaced by the calendar.

Most meetings do not solve that problem. A 2024 Atlassian survey indicated that the majority of meetings are poor at sharing information. In that survey, 77% of respondents said meetings create more meetings. Most meetings are built to share updates, not to make a decision. A small team needs a meeting that earns its slot by producing a decision, a name, and a next step.

The huddle is a decision, not a status update

Databricks had about $1.5 million in revenue in 2015. Ali Ghodsi received the Databricks CEO position as a trial arrangement and was not paid a CEO salary at that time. Ghodsi recommended identifying the single largest bottleneck and devoting an extreme, disproportionate level of focus to it for two or three years. A small team does not need that scale or cadence. It needs one recurring priority.

The ritual matters less than the discipline. The bottleneck gets named before the team starts doing other work. A status update gives everyone a reason to talk, but it does not force anyone to choose. The huddle should be short, steady, and simple enough that the team can keep it.

Run the bottleneck huddle in order

Use the same order each time. The note should be short enough to read in the room and clear enough to read after the next huddle. The team should not need to replay the meeting.

• Name the current bottleneck in one sentence at the top of the note. If the room describes different problems, the huddle has failed and needs a sharper question.
• Assign one owner, a person with enough authority to make the next call. The note should show a name, not a shared responsibility.
• State the concrete blocker: a missing decision, a dependency, a capacity gap, or a broken process. The room should know what would clear it.
• Commit to the next step and the time it takes, small enough to finish before the next huddle. The note should carry an owner, a task, and a date or a duration.
• Write the decision log line: bottleneck, owner, blocker, next step, and any decision made. The line should explain why the main thing changed or stayed the same.
• Protect the main thing: no new topic displaces it; log new issues as candidates for next time. The huddle ends with the same main thing unless the owner has evidence that it is no longer the bottleneck.

The common mistake is choosing a next step that is really a project. If it needs a long stretch of planning, it is too big for the huddle. Break it into the smallest action that moves the bottleneck.

Keep the main thing on the calendar

Put the huddle on a recurring calendar block and keep it short enough that people will attend. The invite should be simple: no deck, no long agenda, no pre-read. The recurring bottleneck meeting earns its slot because it produces a decision, not a status update. If the team needs more time, the bottleneck is probably too large and needs to be split.

Protect the owner's surrounding calendar blocks. The owner needs room to clear the blocker, not just report on it. If the huddle runs often, the team should be able to point to the same main thing unless the evidence has changed.

The huddle is done when the note has a name, a blocker, a next step, and a log line. The next huddle starts from that line, not from a fresh argument about what matters.