Running Effective Problem-Solving Meetings

Groups do much of their problem-solving in meetings — and most meetings are bad. They wander, exhaust people, and decide nothing. Since meetings are where collective problem-solving actually happens, running them well is a high-leverage skill. A single well-run meeting can outperform ten aimless ones.

Purpose and the right people

Every effective meeting starts with a clear purpose: what decision or output must exist by the end? A meeting without a defined outcome is a conversation, not a working session. And only the people needed to reach that outcome should attend — more attendees mean more coordination cost and diffused responsibility.

Structure: pre-reads, agenda, time-boxing

Great problem-solving meetings often front-load the thinking. A written pre-read — a document laying out the problem and options — lets people arrive informed rather than being talked at. A tight agenda and time-boxing (fixed time per item) keep discussion from sprawling. Structure protects the group's scarce attention.

Clear decisions and action items

A meeting's value is realised only in what happens after. Every problem-solving meeting should end with explicit decisions, clear decision rights (who actually decides), and concrete action items — who does what by when. Ambiguity here is how good discussions evaporate into nothing.

A team must choose between two suppliers. The organiser circulates a one-page pre-read with the options and trade-offs a day early. The meeting opens with five minutes of silent reading, then focused discussion of the key uncertainties, a clear decision by the named decision-maker, and a short list of who will do what next. Thirty minutes; real outcome. No slideshow, no meandering.

Structure taken to extremes becomes bureaucracy — meetings so procedural that no real thinking happens, or so many pre-reads and forms that people drown in process. And some problems genuinely need loose, exploratory conversation, not a rigid agenda. The skill is matching the structure to the task: tight for decisions, looser for early exploration.

Amazon is well known for an unusual meeting practice introduced under founder Jeff Bezos: instead of slide presentations, meetings often begin with participants silently reading a carefully written narrative memo (famously around six pages) for the first portion of the meeting. Bezos has publicly explained the reasoning: writing in full sentences forces the author to think through the logic far more rigorously than bullet points allow, and silent reading ensures everyone engages with the actual argument rather than a charismatic presenter. Amazon also favours 'two-pizza teams' — small enough to be fed by two pizzas — to keep groups nimble. Whatever one thinks of the specific format, the underlying principles are sound and widely applicable: force clear thinking through writing, make sure everyone truly engages with the substance, and keep the group small enough to be effective. These are practical ways to make meetings serve problem-solving rather than waste it.

• "A meeting is for discussing." It should be for reaching a defined outcome.
• "Invite everyone who might be interested." More attendees dilute focus and responsibility.
• "Presentations are the best way to share information." Written pre-reads often force clearer thinking and better engagement.
• "The discussion is the deliverable." Value comes from decisions and action items, not talk.

Before your next meeting, write one sentence: 'By the end, we will have decided/produced ___.' If you can't, the meeting may not be needed — or needs reshaping.

Think Like a Maester: A meeting earns its cost only by producing a decision or output — start from the outcome and work backward.

1. What should every effective meeting start with?
2. Why can a written pre-read beat a presentation?
3. What is time-boxing?
4. What three things should a problem-solving meeting end with?
5. What principles underlie Amazon's six-page-memo practice?

Effective problem-solving meetings start with a clear purpose and only the necessary people, front-load thinking through written pre-reads, and stay focused with a tight agenda and time-boxing. They end with explicit decisions, clear decision rights, and concrete action items — because value comes from what happens after. Amazon's six-page-memo and two-pizza-team practices illustrate the durable principles: force clear thinking through writing, ensure real engagement with substance, and keep groups small.

• Decision Frameworks
• Aligning People Around a Solution