Why filament uses Worksheets

Why Filament Uses Worksheets Toolsheets

Twenty years of facilitation has taught me one counterintuitive lesson: people's compulsion to follow directions is stronger than their reluctance to share. Hand someone a card with three prompts on it and they'll complete all three. The same person would never raise their hand in an open discussion.

Every Filament session is built on this insight.

Walk into our space and you'll find cardstock everywhere. Individual cards with prompts like "I wish we would," "I wonder if we could," "I worry that we won't." Big 11x17 sheets in the middle of every breakout table, printed with the exact questions that group needs to answer. Sometimes it feels like the sheets facilitate more of the conversations than we do.

For us, these toolsheets convert sharing from performance into reporting. Instead of leaping in with improptu ideas when asked to share, participants are reading something they’ve already writtendown, after actually thinking about it. That difference sounds small, but it changes who participates.

We know who talks in most meetings: the extroverts and the people with the most power.

Everyone else waits for an opening that never comes, or decides their idea isn't worth the risk. Give everyone a card first and the math changes. I'll ask one person to share, first or last, their choice. Then when they pick who goes next, they never pick the boss. They pick the person whose answer makes them curious. Watch that happen three or four times and the room's hierarchy loosens.

In breakouts, the 11x17 sheet does the facilitating for us, too. Groups feel obligated to answer every question on the page, so the conversation stays on track without a table captain policing it. That's how a single facilitator can run a room of fifty (or five hundred) and still get quality thinking from every table.

We're not alone in discovering this. Researchers have spent decades documenting why talk-first meetings underdeliver. Diehl and Stroebe identified "production blocking" back in 1987: only one person can speak at a time, so everyone else loses ideas while they wait.

Leigh Thompson's work at Kellogg shows that writing before talking produces more ideas and more original ones, in part because early speakers anchor everyone else's thinking.

Stasser and Titus found that groups reliably discuss what everyone already knows and skip what only one person knows.

And a landmark study in Science found that the smartest teams aren't the ones with the smartest members. They're the ones where people contribute in roughly equal measure. Our cardstock, it turns out, has a bibliography.

The newest change is what happens after the session. We used to scan the sheets and send them along. Useful, but it left insight on the table. Now AI reads the handwriting on every card and synthesizes what the entire room thinks. Frame a prompt as "As I think about our strategy..." and collect fifty handwritten responses, and you get something more honest than a survey nobody trusts is anonymous and is far richer than any discussion transcript.

Nobody has ever complained about the toolsheets. Twenty years, thousands of participants, and I'm still waiting to meet the person who resents a clear prompt served with time to answer it. What people resent is being put on the spot, talked over, or handed a question that has nothing to do with them. A good toolsheet solves all three.

It's permission to think.

Sources: Diehl & Stroebe, "Productivity Loss in Brainstorming Groups" (Journal of Personality and Social Psychology, 1987) · Leigh Thompson, Creative Conspiracy: The New Rules of Breakthrough Collaboration (Harvard Business Review Press, 2013) · Stasser & Titus, "Pooling of Unshared Information in Group Decision Making" (Journal of Personality and Social Psychology, 1985) · Woolley, Chabris, Pentland, Hashmi & Malone, "Evidence for a Collective Intelligence Factor in the Performance of Human Groups" (Science, 2010)

Updated: July 8, 2026

The Decision Diary: A Simple Tool for BETTER Decisions

Most teams make decisions all the time. They just don't remember making them.

Important choices get buried in email threads, scattered across meeting notes, or made in hallway conversations that nobody else heard. A month later, someone asks "wait, didn't we already decide this?" and the whole discussion starts over.

A Decision Diary fixes this. It's a shared, running log of what your team has decided, what's still in progress, and what you're planning to tackle next. Nothing fancy. Just clarity.

Here's how to build one:

1. Document Key Team Decisions: Start by recording the major decisions your team has made recently. What were the considerations? Who was involved? What was the outcome? This retrospective helps your team learn from past decisions and highlights what worked and what didn't.

2. Track Ongoing and Pending Decisions:  Make a habit of documenting decisions that are still in progress. Which ones are in the pipeline? What needs attention? A clear log of ongoing decisions keeps your team proactive and prevents bottlenecks before they form.

3. Encourage Collaboration and Input: Share the diary and invite input from everyone. Diverse viewpoints lead to better decisions, and an open process fosters shared accountability. When people see their input reflected in team decisions, engagement follows.

4. Create a Decision Wish List: Use a wish list to capture decisions your team might tackle in the future: new initiatives, long-term challenges, and unexplored directions. This keeps strategic thinking alive between planning cycles and ensures good ideas don't get lost.

5. Reflect and Adjust Regularly: Build reflection into your team's rhythm. Review decisions together, celebrate wins, and identify areas for improvement. This practice keeps your decision-making processes sharp and reinforces continuous learning.

A Team Decision Diary isn't just about tracking what's been done. It's about building collective clarity, making informed decisions faster, and aligning everyone toward the same goals. When the whole team is engaged in the process, you handle complex challenges better, avoid unnecessary delays, and create real accountability.

Last Updated: July 4, 2026

A Daily Dose of Vitamin C

In the ever-evolving landscape of business, it’s essential to nurture the core elements that make your team strong, vibrant, and productive.

At Filament, we’ve developed a set of daily check-in questions we call our “Vitamin C’s” that fuel our team's health, align us on our goals, foster collaboration, and celebrate our achievements.

What Are Our Vitamin C’s?

• Commitment: Being transparent about our priorities helps us focus and also allows the team to understand each other's workload, thereby fostering a sense of shared responsibility.

• Collaboration: Knowing what everyone is working on and how we can support one another lays the foundation for effective teamwork.

• Curiosity: Encouraging a culture of continuous learning and questioning ensures that we’re always growing—both as individuals and as a team.

• Celebration: It’s important for us to recognize and celebrate both our individual and collective achievements. These moments of acknowledgment will reinforce our values and principles, boosting morale.

How It Works:

Each morning, everyone on our team receives a Slack prompt that asks four questions that vary each day. On Monday, we focus on the week ahead. Tuesday through Thursday, we have simpler check-ins. On Friday, we reflect on the week that’s ending.

The responses are visible to the entire team, fostering an environment of openness and shared understanding.

Here are the prompts we use each day:

Monday | The Week Ahead:

• Commitment:  One specific thing I’ll focus on this week that will help me “move my metric” this week is:

• Collaboration:  Some help I may need from others to accomplish this week’s goal is:

• Curiosity:  Something we might add, change, or eliminate in our processes to improve our clients’ experience is: 

• Celebration:  One of our Principles I’d love for us to focus on this week is (and why):

Tuesday | Check-In:  

• Commitment:  An important task I completed yesterday that I’m proud of is:

• Collaboration:  Some help I gave another team member is: 

• Curiosity:  A fun question I’d love to ask all our team members is:

• Celebration: Some positive feedback I’d love to give a team member (or two) is:

Wednesday | Check-In: 

• Commitment:  The progress I’ve made so far this week on moving my metric is:

• Collaboration: One challenge I’d love some help from a team member to solve is: 

• Curiosity:  Something that made me go “hmm…” this week was:

• Celebration: One thing I did this week that is worth celebrating is:

Thursday | Check-In: 

• Commitment:   A priority for tomorrow that will help me to end the week well is:

• Collaboration:  An improvement to one of our team’s tools I’d love to make is: 

• Curiosity:  Something fun, cool, and/or surprising that I learned about a team member this week is:

• Celebration:  One way we might celebrate our clients could be:

Friday | The Week In Review:

• Commitment:  I was successful in accomplishing my weekly one thing that moved my metric in these ways:

• Collaboration:  One way we might collaborate better asynchronously is:

• Curiosity: A surprising thing I learned this week that could be useful for us is: 

• Celebration:  The most rewarding part of my work week was:

By giving us all a snapshot into our team members’ days, these Daily Vitamin C’s have transformed our team’s dynamics.

Give them a try. You might find that creating a daily habit focused on commitment, collaboration, curiosity, and celebration will pay similar dividends to your team.

Dream, Debate, Decide & Do

"I thought we already decided that."

Picture a leadership team forty minutes into a conversation about next year's budget. The head of product floats an idea for a new service line. The CFO starts pressure-testing it: what's the margin, who staffs it, what do we stop doing to fund it. Three seats down, the COO looks up from her notes and says the sentence that derails a thousand meetings a day:

"Wait. I thought we already decided that."

Nobody in that room is doing anything wrong. The head of product is dreaming. The CFO is debating. The COO believed she walked into a planning conversation about a decision made last quarter. Three smart people, one room, three different meetings.

That's the diagnosis most meeting advice misses. The problem usually isn't a bad agenda, a weak facilitator, or the wrong people in the room. The problem is that the people in the room think they're in different meetings. And because nobody named the meeting out loud, nobody knows they disagree about what kind of conversation they're having. They just know it feels like wading through wet cement.

The Four Meetings

Every working conversation is doing one of four jobs. There are only four meetings: Dream, Debate, Decide, and Do.

Each one asks something different of you before you walk in, and each one has a different definition of success. Get those right and the meeting mostly runs itself. Mix them without saying so and even a great agenda can't save you.

Dream

The job: Explore possibilities. Generate options you don't have yet.

What you bring: Ideas. Including the ones you'd normally keep to yourself. The pre-work for a Dream meeting is simple: get people thinking about the question before they gather, so the meeting starts with material instead of blank stares.

What good looks like: More options at the end than the beginning, and nobody punished for the strange ones. A Dream meeting makes no commitments and closes no doors. That's not a bug. Deciding too early is how organizations end up choosing from a menu of two mediocre options because nobody made space to find the third.

A tool that helps: Easy / Hard / Safe / Crazy. One big sheet, a "How might we..." question at the top, four quadrants below. Easy: what are some easy things we can do right away? Hard: what are some hard things we can begin to explore? Safe: what are the safe things everyone is expecting us to do? Crazy: what are a few things so crazy they just might work? Groups as small as two or as large as seven work one sheet together. Don't censor on the way in. Crazy is where the good ones hide.

Debate

The job: Build understanding. Test ideas against each other and against reality.

What you bring: A point of view, and the willingness to have it changed.

What good looks like: The group understands the real disagreement, which is frequently not the one they walked in with. Debate is not combat and it is not consensus-building. It's how a group finds out what it actually thinks before it has to commit.

A tool that helps:The Confidence Compass. Each person states their position, their confidence in it as a percentage, and what would change their mind. That last question does the heavy lifting. We've watched two executives argue for twenty minutes before the Compass revealed they were at 55% and 60% confidence, worried about the same thing. What looked like disagreement was shared uncertainty. That's a completely different conversation, and a much shorter one.

Decide

The job: Evaluate options and commit to one.

What you bring: Knowledge of who the decider is and how the call gets made, before anybody walks in.

What good looks like: A decision, obviously. But also this: everyone leaves knowing what was decided, who decided it, and why. Most Decide meetings fail before anyone speaks, because people think they're arguing about the answer when half of them haven't agreed on the question.

A tool that helps:The Decide Guide. It's a preparation document, not an agenda, and it gets filled out before the meeting is scheduled. Five phases: Frame the question. Lay out the options. Agree on the criteria before applying them to the options, because criteria chosen after the fact are just justifications. Make the call. Assign what happens next. The Guide also carries a prerequisite check: has this group Dreamed? Has it Debated? If not, don't pretend the calendar invite makes it a Decide meeting. You can't decide what you haven't explored.

Do

The job: Turn the decision into motion. Plan, assign, coordinate.

What you bring: Your capacity and your calendar.

What good looks like: You leave knowing who's doing what, by when. That's the whole test. A Do meeting that ends without names and dates attached to work is a Debate meeting wearing a disguise.

A tool that helps: The commitment check. Before anyone leaves, go around the room: each person says out loud what they own and when they'll deliver it. It takes four minutes. It converts "we should" into "I will," and it surfaces the overloaded person now instead of at the deadline.

The expensive part: mixed meetings, unnamed

Here's what happens without the vocabulary. A team schedules a "weekly sync." Inside that hour, someone dreams, someone debates the dream, someone tries to decide, and someone else just wants to know what to do by Friday. Every one of them leaves frustrated, and every one of them blames the meeting.

One meeting trying to do two jobs does both badly. Dreaming gets strangled by premature evaluation. Debating gets cut off by someone pushing for a decision. Decisions get relitigated because half the room never got to debate. And the person who came ready to Do sits through ninety minutes of exploration wondering why they were invited.

Sometimes you genuinely need two of these conversations in one room on one day. Fine. Have both. Just name the seam: "For the next twenty minutes we're dreaming. No evaluation. Then we'll switch and pressure-test." Two meetings, two purposes, both clear. The failure isn't mixing. The failure is mixing without telling anyone.

The fix is three sentences

Before you send the next invite, finish these three sentences from our Meeting Guide:

We're gathering to dream / debate / decide / do (about) ______.

It is important for us to do this together, and at the same time, because ______.

And by the end of this meeting we'll have ______.

The first sentence names the meeting, so everyone arrives in the same one. The second is the honesty test: if you can't finish it, you don't have a meeting, you have an email. And the third defines done, so the meeting ends when the work does instead of when the calendar says so.

Put all three in the invite. Everyone who accepts knows what kind of conversation they're walking into, why they're in the room, and what they're building together.

And when the stakes are high, or you suspect people are arriving in different meetings anyway, open with a two-minute expectations check we call I Wish / I Wonder / I Worry. Everyone writes against three prompts: I wish we would... I wonder if we could... I worry that we won't... Then everyone shares. It takes five minutes, and it surfaces the mismatches before they cost you forty. The person who wishes you'd revisit last quarter's decision gets to say so at minute two instead of derailing minute forty.

We'll be honest about what we learned rolling this out ourselves: it was the hardest habit to build and the highest-payoff habit we've kept. Hard because "let's discuss" is comfortable and the three sentences force the organizer to know what they actually want. If you can't finish them, you've learned something important before the meeting ever happens. Maybe it's two meetings. Maybe it's an email. Maybe it's not ready to be a meeting at all.

Bigger than meetings

The framework earns its keep on the calendar, but the real compounding happens in conversations nobody scheduled.

A CEO stops someone in the hallway and asks, "What do you think about moving the launch?" What kind of question is that? If it's a Dream question, the honest answer is speculative and half-formed, and that's fine. If it's a Decide question, that same half-formed answer just became input to a call the CEO makes at 4 PM.

Without shared vocabulary, people guess. And when the stakes feel high, they guess conservative: they hedge, they say what's safe, they save the interesting thought for never. With the vocabulary, something better becomes possible. The person can ask: "Is this a dreaming conversation, or are you deciding?"

That question is permission. Permission to think out loud without it being held against you. Permission to disagree without it being read as obstruction. Permission to ask the CEO to clarify, which in most organizations feels vaguely insubordinate right up until everyone has words for it. Teams that adopt the Four Meetings don't just run better meetings. They have better conversations, because everyone can finally tell each other what kind of conversation they're in.

Try it this week

Open your calendar. Look at the next five meetings and label each with one word: Dream, Debate, Decide, or Do.

The ones you can label will get sharper the moment you share the label. The ones you can't label are the ones costing you the most, and now you know where to look.

Last Updated: July 8, 2026

The Fortune Teller

'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 "Who 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 investment of time 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.

Last Updated July 3, 2026

Tuition vs. Failure

We were facilitating a retreat for a few dozen senior executives when the conversation turned to a bold strategy and the risk it might fail.

That's when the group's new leader said something I've never forgotten:

Let's stop talking about failure. It's a scary word we've been conditioned to avoid all our lives. Let's call it tuition instead.

We should be happy to pay tuition, because lessons are the only way this organization improves.

But I'll be damned if we're going to pay to take the same class twice.

The room understood immediately. They had permission to try things that might not work and an obligation to share what they learned when they didn't.

I've told this story countless times, and I still picture her team opening their meetings with: "So, who wants to share what we learned in class this week?"

What tuition has your organization paid lately?

Last Updated: July 2, 2026

Four Scary Meeting Creatures

Four creatures appear in every meeting: Elephants, Zombies, Squirrels, and Porcupines.

Inspired by an exercise called Elephant, Dead Fish, Vomit invented by Airbnb (and shared in the wonderful book Rituals for Work), Elephant, Zombie, Squirrel, Porcupine is a group conversation “tool” designed to nurture more honest dialog among people who work together. Here’s how to use it:

During every all-hands meeting, carve out time to discuss the following:

• Elephants: Big things people are worried about but not talking about.

• Zombies: Old issues, projects, or ways of working that never seem to go away.

• Squirrels: Things that might be distracting the organization or team from focusing on the work that matters most.

• Porcupines: Touchy subjects that might feel too hard to handle.

By naming each of these creatures, your group can have deeper conversations to help you get past the barrier each one of these entities poses.

Dump the Hour-Long Keynote

Here's an "alternative" keynote format that combines the best of TED Talks, drives conversational engagement, makes room for introverts and extroverts to think and process alike, and delivers a connection between speakers and audience members. It is lightly edited from its original form as posted in a Tweet-stream here.

First, this works best when the room is set in rounds with 4-8 attendees. It can work in auditoriums or when a room is set as "classroom" style -- and don't get me started on what an oxymoron that is -- but it works best in rounds.

Before the speaker begins, every audience member gets a worksheet with room for notes, a place to doodle, and a few prompts like: What was the most compelling thing you heard? What did you disagree with? What would you like to know more about? etc.

On the agenda, the keynote is given an hour (so it looks familiar to those too afraid of big changes), but it is broken down differently:

• Minutes 1-15: The speaker gets 15 minutes to make their three key points. They can use slides if they want, but it is best to limit the number if you can.

• Minutes 16 - 20: Once the speaker's 15 minutes are done, the room gets 5 minutes of silence to contemplate what they just heard and complete the worksheet. This is ridiculously hard for extroverts but loved by introverts. It is OK if some take out their phones, though only a few will.

• Minutes 20 - 40: After the silent time is over, each table gets 20 minutes to talk with one another about what they just heard, what they liked, etc. Ideally, they'll follow the framework from the worksheet, but it isn’t terrible if they do a bit of networking, too. During table time, the speaker can roam around the room and engage one-on-one with audience members who have specific questions. However, each table's key deliverable during this period is ONE question they'd collectively like to ask the speaker.

• Minutes 41-60: For the last 20 minutes of the hour-long keynote slot, each table can ask their question of the speaker. If you have a lot of tables, obviously you'll only pick a few, but every table can still submit their question for the speaker to answer later if they're able. In case it’s not obvious, the reason the table must ask a question collectively instead of allowing individual questions is to eliminate the long-winded, self-important audience member from asking their 5-minute, "I'm so smart, don't you agree" question that bores the rest of the room to tears.

We've found this is so much better than the traditional "sage on the stage" hour-long keynote. It is easier for the speakers, better for the audience, and more fun to boot! I hope you'll try it and let me know if it works for you.

Innovate With Great Questions

Mitch Ditkoff at Idea Champions shares a great list of questions to ask senior leaders before hiring an innovation consultant. Because so many of them also apply to the work we do at Filament I thought I'd share a few that will be added to our client assessment toolkit:

1. Do you have a clear, compelling vision of our organization's future? If not, are you willing to create one?

2. Are you personally committed to fostering a culture of innovation? Are other senior leaders on the same page with you? If not, are you and your colleagues willing to get on the same page within the next few weeks?

4. Are you willing to challenge the status quo?

5. Are you open to receiving new ideas from the workforce -- and are you willing to establish a process that will make it easy for them to do so?

9. Are you willing to go beyond "command and control", empower people, and push decision making further down the food chain?

Rethink One Day Events

We’ve been working on a new way to run a one-day conference (or conference track) that blends a mix of collaborative, traditional, and un-conference elements for a client, and thought we’d share it with you.

• Begin by framing a "How might we ...?" challenge that's relevant to the entire group (or as many of them as practicable). It can be general, such as "How might we be more innovative in X?" or specific, "How might we keep invasive bug species off trans-ocean ships?"

• The first session of the day -- after the challenge has been shared -- explains why the challenge is so important to solve (imagine an inspirational keynote mixed with a football coach's pre-game speech mixed with a fiery sermon, and you'll get the idea). Then, for the next 2-3 sessions, ask your speakers and panels to approach the challenge from different angles and share their best practices, success stories, tools they might recommend, etc.

• Once the morning insight sessions level the playing field a bit between experts and novices, take a 90-minute lunch to give people enough time and space to process their early thoughts and ideas in an "Idea Gallery" by posting a handful of problem-shaping questions they'll answer on post-it notes.

• After lunch, challenge people to form teams of 5-7. Make sure you have a "want a team" area for people who don't know anyone to quickly find peers to work with.

• For the rest of your afternoon (2-3 hours), challenge the teams to build a solution to the problem they've been discussing all day. Allow them to initially propose three ideas they'll have to winnow down to one. If you want, you can give each team a different constraint for their solution, such as "Your team can't spend money to solve this problem," or "Your solution must be implementable in six months."

• At the end of the afternoon, teams must "pitch" their main idea. You can do this "shark tank" style, or have a bit more fun with it by rewarding the most innovative solution, the most creative pitch, or even the silliest idea.

• After the pitches, give each team a table and ask one of the team members to remain there. Then, allow everyone else to roam around the room and engage more deeply with different teams to learn about the solutions they proposed. A favorite twist: Give each team a tri-fold display board (like from a science fair project) and ask them to create their pitch on the board. Give them access to art supplies. Then, after the pitches, convene your "Idea Fair” (did I mention that happy hour should start in the middle of this afternoon process?).

If you're doing this for a multi-track conference, you can do these in parallel for different challenges, and then bring everyone together at the end of the day to see everyone else's ideas and "Idea Fair" boards. Feel free to charge sponsors to participate in the teams, so long as they promise not to sell too hard.

At the end of the day, you've challenged folks to think about a problem they're facing, added more networking and collaboration, made room for some traditional conference elements, and built solutions (in an easily sharable format) that will be valuable to everyone. (Originally shared on Twitter).