Most meetings fail before they start. Not because of bad agendas or the wrong people in the room, but because nobody's clear on what kind of conversation they're actually having.
Naming the type of meeting you're running before the invites go out is one of the most effective ways to make meetings more productive: it sets expectations, shapes how people participate, and cuts time lost to the wrong kind of thinking.
At Filament, we use a four-part framework called Dream, Debate, Decide, Do. Each word names a distinct mode of conversation. Knowing which one you're in changes everything about how people show up.
Dream: Explore Without Pressure
A Dream meeting is pure possibility. No evaluating, no building plans, no pressure to land somewhere actionable. The goal is unrestricted exploration — giving people room to think out loud without the weight of commitment.
This matters because most teams collapse into judgment too fast. When evaluation sneaks into ideation, ideas get smaller and safer. The assumptions embedded in "that won't work" kill good thinking before it has a chance to develop. Dream meetings protect the space where genuinely new ideas come from. They work best when the facilitator actively holds the door open: every idea welcome, no decisions yet, nothing to defend.
The rule is simple. If someone starts evaluating, redirect. There's a meeting for that. This isn't it.
Debate: Go Deeper
A Debate meeting is where you probe. You're not trying to resolve anything yet — you're trying to understand it better. That means open questions, competing viewpoints, and a willingness to sit with complexity longer than feels comfortable.
Coming prepared matters here. Participants should bring research, sharpen their positions, and be ready to defend and revise their thinking. This isn't conflict for its own sake; it's how a leadership team builds real shared understanding rather than the polite consensus that looks like alignment but isn't.
A well-run Debate meeting surfaces the actual tradeoffs before a decision gets made. That's its value. Skipping it — or cutting it short — usually means those tradeoffs surface after the decision, which is a much worse time to find them.
Decide: Make It Clear
A Decide meeting has one job: to make a decision. That means being explicit upfront about who holds the decision, what factors will guide it, and what process you'll follow to get there.
Without that clarity, Decide meetings drift into more Debate — or worse, they produce false consensus that falls apart during implementation. When everyone thinks they decided together, but means something different by it, execution suffers. Naming the decision-maker before the conversation starts changes the dynamic in the room. People can contribute without fighting for control. And when the decision lands, it's clear.
This is also where decision documentation earns its keep. A brief record of what was decided, who decided it, and why beats a meeting recap that reconstructs nothing useful.
Do: Assign and Activate
A Do meeting is about accountability. Tasks get assigned, owners are named, and timelines are set. The conversation shifts from what we'll do to who will do it and by when.
Short and specific is the goal. A Do meeting that runs long is usually a sign that a Decide meeting should have come first — or that accountability was assigned without the authority to back it up. The best Do meetings feel almost transactional, because they are. The thinking is done. Now you're translating decisions into action.
One useful check: after a Do meeting, everyone should be able to answer two questions without looking at their notes. What am I doing, and by when? If the answer requires searching through notes, the meeting didn't finish its job.
One Framework, Four Modes
The power here isn't complexity — it's clarity. When people know what kind of meeting they're walking into, they show up differently. Dreamers don't get frustrated by premature evaluation. Deciders don't get stuck in endless debate. Everyone's working from the same playbook.
This framework works because it gives teams a shared vocabulary for something they already do poorly by default: agreeing on what they're actually trying to accomplish together in a given hour. That's a small shift with a surprisingly large effect on how meetings actually feel, and what they actually produce.
Try naming the type before your next meeting. It costs nothing and changes more than you'd expect.
Last Updated: March 2026