Ideas from Matt

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

I was facilitating a strategy session several years ago with about twenty-five senior leaders from one of the best-known companies in our region. We were there to work on strategic priorities, but that wasn't the real challenge. The real challenge was that nobody in the room seemed especially eager to try anything new.

The ideas themselves weren't the problem. There were plenty of smart suggestions on the table, and a few of them were genuinely bold. What was missing was any real appetite for risk. Almost every promising idea was immediately followed by some version of retreat: a caveat, a hedge, a reason to slow down, a reason to stay with what was familiar. It was clear that this was an organization that had learned that the penalty for a failed experiment felt worse than the penalty for standing still.

Then the CEO said something that changed the conversation.

She said, "Let's stop calling it failure. I want to call it tuition. I'm happy for us to pay tuition to learn a lesson, but I'll be damned if I'm willing for us to pay to take the same class twice."

What struck me in that moment was not just that the room relaxed, though it did. You could see people recalibrating almost immediately. The comment created permission, but it also did something more important: it established a standard. Trying something and learning from it was not only acceptable but expected. At the same time, repeating the same avoidable mistake was not.

That distinction matters. "Failure" is usually heard as a verdict. Once that word enters the room, people tend to move into defensiveness, blame, or caution. They become more interested in self-protection than in learning. "Tuition" changes the meaning of the cost. It suggests that some missteps are part of the price of doing serious work, especially when you are attempting something new. It shifts the conversation away from fault and toward learning.

But that reframe only works if the learning moves in both directions. If you paid the tuition, you owe the organization the lesson. And before you sign up for something new, you should ask whether someone else already took that class.

That means the lesson has to actually travel. Not as a vague summary, and not as a post-mortem that disappears into a folder no one opens again. The useful part is the specific knowledge that came from the attempt: what was tried, what happened, what assumptions turned out to be wrong, and what others should know before trying something similar. Organizations that get better are not always the ones that avoid mistakes. More often, they are the ones that become disciplined about turning mistakes into shared knowledge.

That is why I keep coming back to what that CEO said. Her reframe made room for intelligent risk without making room for sloppiness. It treated learning as an asset and repetition as the real problem.

Most organizations are willing to absorb the cost of learning. What they are much worse at is making sure the lesson survives the moment.

Most of us have been on both sides of this moment: someone asks for something, and neither person has a clear picture of what "done" looks like.

The requestor wants a quick, directional answer. The person doing the work assumes they need to deliver something polished and thorough. And so begins the quiet spiral of mismatched expectations, where someone over-invests in something that didn't need to be perfect, while the person waiting wonders why it's taking so long.

Here's a simple question that cuts through all of that: "Would you rather have it at 75% tomorrow, or 95% next week?"

This framing works because it makes the tradeoff between speed and quality explicit rather than leaving it buried in assumptions.

Why this question works:

• It clarifies what "done" actually means. Many requests don't require a finished product. They need a rough draft, a directional answer, something to react to. When someone chooses 75% tomorrow, they're telling you that speed matters more than polish.
• It makes the cost of quality visible. Most people underestimate the effort required to go from "pretty good" to "really good." That last 20% of quality often takes 80% of the effort. This question surfaces that tradeoff before anyone gets frustrated.
• It reveals the real purpose of the work. A request for 95% signals the deliverable is going somewhere important. A request for 75% means it's probably an input into a bigger conversation. Knowing the destination changes how you approach the journey.

The hidden benefit? This question gives the requestor permission to ask for less.

In most professional cultures, there's an unspoken expectation that everything should be excellent. But excellence takes time, and not everything deserves the same investment. When you offer 75% as a legitimate option, you're making it safe for someone to say, "Actually, I just need something to react to."

That's a gift to both sides. The person doing the work gets realistic expectations. The person asking gets what they need faster.

Try it this week: The next time someone asks you for something, offer the tradeoff explicitly. You might be surprised how often people choose 75% tomorrow.

The best professionals don't just deliver great work. They ask the right questions before they start.

Last Updated: February 2025

I'm not retiring. But I'm starting to practice.

Beginning this January, I'm taking two random days off each month. Not vacation. Not sick days. Retirement days.

Here's why.

Last year, my daughter graduated from college and is now working full-time. My parents are both struggling with their health. My mom has emerging dementia, and I watch her lose the capacity to do things I know she wishes she'd done when she was healthier. That's clarifying in a way I didn't expect.

I also had surgery for a detached retina on New Year's Eve. It's fine now, but there's nothing like a health scare to remind you that physical capability has an expiration date. The things I want to do in retirement require a body that cooperates. Waiting until 65 to discover what I love means discovering it with less capacity to pursue it.

So I'm not waiting.

Two days a month is roughly 10% of my working time. I'm not sure what I'll do with those days yet. Maybe golf one day and a museum by myself on another. Maybe a long walk or a few hours solo in a coffee shop with a book that has nothing to do with work.

The honest truth is I've never been retired before, and I don't know anyone who does it particularly well. So I'm hoping to learn now, while I still have the energy and curiosity to figure it out.

If this works, maybe I'm 20% retired next year. Then 30%. A glide path instead of a cliff.

The guilt is real, by the way. I've worked hard my entire adult life. Taking a random Tuesday off to wander feels indulgent in a way that's hard to shake. But I think the guilt is misplaced. I've watched too many people sprint to a finish line only to arrive too exhausted or too sick to enjoy what they'd been running toward.

I'd rather practice now.

My team knows this is coming. I'm telling them — and now you — because making it public makes it real. This isn't me checking out. It's me checking in on a version of my life I've never explored while I still have the chance to shape it.

Two days a month. Let's see what I learn.

'The Fortune Teller and the Four-Year-Old' is a distinctive yet simple activity, offering a refreshing departure from traditional icebreaker exercises. It’s designed to create immediate connections between individuals who may not be well-acquainted.

Here’s how it unfolds:

• Start by dividing the attendees into pairs. One participant in each pair assumes the intriguing role of the 'Fortune Teller', while the other adopts the curiosity of a 'Four-Year-Old'.
• The Four-Year-Old's mission is to ask the Fortune Teller questions about their imagined future, such as "What will I be when I grow up?" or "Whom will I marry?"
• Instead of providing fictitious predictions, the Fortune Teller responds with stories taken from their own history. For instance, in answering "What will I be when I grow up?" the Fortune Teller might share, "You’ll grow up to be an accountant in a bustling firm in Chicago." This response, disguised as a prediction, is a sharing of the Fortune Teller's own life lessons and experiences.
• To delve deeper, the Four-Year-Old is then encouraged to ask further questions about the Fortune Teller's narrative, adding depth to the conversation before moving on to their next query.
• After dedicating about 15-30 minutes to this engaging exercise, the pairs switch roles, allowing everyone to gain insights from both perspectives.

This seemingly simple exercise is a minimal time investment that yields substantial dividends, including stronger team bonds, improved communication, and a heightened sense of empathy among team members.

Moreover, it encourages participants to reflect upon their own life journeys, fostering greater self-awareness and understanding toward others.

So the next time you find yourself in a gathering with individuals you're keen to connect with on a deeper level, try out this fortune-telling exercise. It could be the key to establishing faster, more effective connections and meetings.