The Biggest Meeting Mistake? Cramming All Problems into One Session

Deep thoughts on AI and aspirations —— ByteDance Deep Thinking Circle

Many companies run their weekly meetings like this: last week’s summary, this week’s plan, everyone speaks in turn, the boss comments on each person, then adjourn. When the meeting ends, everyone breathes a sigh of relief, but looking at the minutes, almost nothing concrete was actually decided.

Patrick Lencioni, author of The Five Dysfunctions of a Team, coined a term for this phenomenon: meeting stew. Problems aren’t categorized by type—they’re all thrown into the same pot and cooked together. Tactical issues are present, strategic issues get mentioned in passing, and directional questions join the mix. After three hours, none of them get resolved.

What I want to say goes a layer deeper. The root of meeting chaos usually isn’t about whether people know how to run meetings—it’s that decision-making isn’t layered. Meetings are a company’s decision-making system. When the system has only one entry point and one clock, no amount of optimization will make it run fast.

Three Types of Problems, Each with Its Own Clock

Start by breaking problems into three layers.

The first layer is tactical problems—things that can be discussed clearly in 15 to 20 minutes: whether to switch an advertising channel this week, who handles a customer complaint. These belong in weekly meetings.

The second layer is strategic problems—things that can’t be resolved in one discussion: whether to enter a new market, whether to adjust the product line. Lencioni created a “parking lot” for these: issues that can’t be resolved in the weekly meeting get parked there for dedicated strategy sessions. This prevents them from eating up time in weekly meetings and from being half-baked week after week.

The third layer is directional problems—adjustments that affect the whole organization. There’s a vivid metaphor in the source material: the bronze chariot from the Terracotta Warriors, where the driver controls the horses’ direction with a spiked bamboo pole. Decision-making is that pole—seemingly a local action, but actually determining where everything goes. These problems belong in quarterly meetings, discussed slowly in an environment away from the office, without time pressure.

This is the first mechanism: each type of problem has its own clock. Once the clock is stable, people automatically categorize problems. When monthly meeting times are fixed, no one rushes to address strategic issues in weekly meetings; when quarterly meeting times are fixed, no one does strategy reviews every month. Conversely, if there’s only one bottomless weekly meeting, all problems get crammed in, and the weekly meeting becomes morning court: present your matter, discuss briefly, dismiss. Afterward, everyone blames the boss for deliberating without deciding, but the boss actually lacks information and time—they can’t make decisions even if they want to.

There’s an easily overlooked detail here: when reviewing objectives in weekly meetings, be qualitative only, not quantitative. Use red-orange-yellow-green to indicate progress and identify what everyone agrees has turned red. Why not look at numbers? Because this step’s purpose is to find the theme for this meeting, not transmit pressure. When weekly meetings become accountability sessions, subordinates bring polished numbers instead of real problems. If the weekly meeting’s theme doesn’t come from the front line, the meeting becomes an academic conference.

The Meeting Exit: Stop 15 Minutes Early

The second mechanism is at the exit—the moment of making the call.

The rule is simple: 15 minutes before the planned end time, stop all discussion and list the results on a whiteboard. Lencioni divides results into three types, very distinctly:

Why spend these 15 minutes? Because once meeting conclusions are ambiguous, all subsequent execution gets discounted. Demanding subordinates do things right while not clearly stating what was decided is shirking responsibility, and will require even more time later to correct. Having everyone confirm on the spot, with anyone having the right to ask the boss for clarification—this step cannot be skipped.

After listing comes an even more easily overlooked step: aligning messaging. All participants agree to communicate consistent information at a specified time to specific audiences—saying the same thing upward, downward, and externally. When communication speed varies, rumors fly everywhere. Lencioni also offers one piece of experience: don’t deliver important decisions by email—do it face-to-face. Delivery is just “I told you,” but communication allows the other party to ask questions and lets you observe their reaction. Without this two-way component, consistency doesn’t reach the next layer.

Following these rules, meeting minutes contain only four blocks: the two or three topics discussed this time, the list of decisions/resolutions/directives, who’s responsible for communicating with whom, and one item most easily missed—the confidentiality agreement. What can be discussed today and what can’t, how leaks are handled—write it down in black and white.

The confidentiality agreement is called the most critical yet most commonly overlooked part of running good weekly meetings. The mechanism is easy to understand: everyone afraid to speak truthfully, weighing consequences before speaking—it’s all because they’re uncertain whether today’s words will leak tomorrow. Without a confidentiality commitment, there’s no heated debate; without debate, meetings become mere performance.

The Prerequisite for Weekly Meetings Is Actually Outside the Meeting

There’s a very counterintuitive aspect to this design: to run good weekly meetings, you first need to run good one-on-ones.

The requirement: within the week before the meeting, the boss does at least one one-on-one with each participant. This one-on-one doesn’t solve specific work problems; rather, it lets subordinates voice what currently concerns them most: resistance in their work, gaps in their capabilities. The superior listens more and speaks less, doesn’t give instructions on the spot, and the goal is to discuss work outside of work.

Why is this needed? Because weekly meetings need real information. Without one-on-ones, information flowing through weekly meetings is either polished or simply absent, leaving only announcements. This is also why the first thing this method does is eliminate information briefing sessions: reports and instant messaging exist, so weekly meetings don’t need to spend two hours sharing updates. Information briefing is precisely the most easily replaceable function of meetings. What’s truly irreplaceable in meetings is making calls and making commitments.

One sentence worth repeating: if you find you can’t do weekly one-on-ones covering all direct reports, it’s probably not a time management problem—your directly managed team is too large.

Finally, there’s a question the boss must think through first: do I really need an executive team? Lencioni’s judgment is cold: team collaboration isn’t a virtue; it’s a choice. Some companies have a boss who is also the technical lead and largest shareholder—giving orders is actually more efficient. Such companies need an assistant team, not an executive team. Only after choosing to have a team does everything else become relevant.

After AI Takes Over Information, What’s Left for Meetings

Let me add one judgment belonging to today.

This method was written over twenty years ago, but today it seems even more valid, because it compressed meeting functions to the minimum early on: information belongs to documents and daily communication; meetings only retain exposing real problems, making decisions, and forming commitments.

This trend is now accelerating. AI can already organize data, generate minutes, and track resolution execution—the “information layer” of meeting content is being taken over by tools. This means meetings that rely on “everyone sitting together to share updates” will lose their reason to exist even faster. What’s left for meetings are three things tools can’t replace: exposing problems only known on-site, forcing responsible parties to make decisions, and having all relevant people make face-to-face commitments.

To diagnose your own company, ask three questions. Do weekly meetings still spend 20+ minutes on information briefings? In the past month’s meetings, how many decisions with traceable accountability were made? Do tactical, strategic, and directional problems each have their own fixed clock?

If you can’t answer all three questions, don’t panic. Start with the smallest action: at your next meeting, stop 15 minutes before the end and list what was decided on a whiteboard for on-the-spot confirmation. This one action alone is enough to transform many companies’ weekly meetings.