Discussing Too Many Problems at Once Only Presents Problems, Not Solves Them

In many meetings, we often see this scenario: a whiteboard filled with agenda items, everyone taking turns speaking, each person seemingly engaged in active thinking. But when the meeting ends, the room suddenly falls silent—not a single problem has been solved. Everyone disperses, left with only a vague impression: “We discussed a lot today, but nothing got done.” This kind of meeting is a classic example of the “information dense, decision scarce” trap. Discussing too many problems at once ultimately only presents problems, without solving them.

Discussions themselves have two natures: exploratory and decision-oriented. Exploratory discussions are good for opening up thinking and helping people see the contours of a problem. Decision-oriented discussions, on the other hand, require focus, trade-offs, and convergence. When we try to accomplish both tasks at the same time, these two modes of thinking clash. Each problem is like a fork in the road—when a team frequently switches focus, it’s like taking only a few steps down each path without ever reaching the end of any one. As a result, problems multiply, and the path to a solution becomes increasingly blurred.

I once witnessed a typical example: a company held a “full-process optimization meeting” to improve customer satisfaction. During the meeting, sales talked about customer expectations, product highlighted feature gaps, customer service pointed out process complexity, and operations mentioned low conversion rates. Everyone’s points were valid, but the result was—not a single problem was solved. Because everyone was simultaneously discussing “phenomena,” “causes,” and “solutions,” each agenda item felt like an unfinished equation: too many variables, with conclusions that could never converge. Later, they changed their approach: each meeting focused on just one problem, such as “optimizing the registration process” or “reducing the cancellation rate.” The results were surprising—while the number of problems discussed decreased, the efficiency of solving them multiplied.

In reality, a team’s cognitive bandwidth is limited. The more complex an organization, the easier it is to mistakenly equate “broad coverage” with “comprehensive thinking.” But true systems thinking is not about “discussing everything”—it’s about clearly defining the boundaries of discussion. Only by breaking problems down small enough, discussing them deeply enough, and executing them quickly enough can a team achieve real progress. Otherwise, they fall into a cycle where “problems seem clear, but actions remain vague.”

A mature team will eventually learn this iron rule: less is more, and focus is power. A good discussion isn’t measured by the volume of voices, but by the depth of focus; not by the comprehensiveness of problems covered, but by the executability of actions. When an organization moves from “presenting problems” to “solving problems,” that is the moment it truly transitions from being “busy” to being “effective.”