The Anxiety Party: Surface Team Fears Before They Fester
The "anxiety party" is a fast way to surface team concerns before a project: everyone writes their biggest fear anonymously on a sticky note, you collect and shuffle them, read each aloud, and turn the most common ones into concrete mitigations. Anonymity unlocks honesty, shared recognition lowers anxiety, and the mitigations turn worry into real risk management.
Before any significant project, people are quietly worried — about the timeline, a dependency, a skill gap, a teammate who's overloaded. But most of those worries never get said. Voicing a fear out loud feels like admitting weakness or jinxing the launch, so everyone sits on theirs, assuming they're the only one. Meanwhile the named-but-unspoken risks go completely unmanaged. The anxiety party flips this: it makes naming fears the explicit, structured task, and does it anonymously so honesty is safe.
Why unspoken worries are the dangerous ones
A worry you can see, you can plan for. A worry that stays in someone's head does damage twice over: the risk itself goes unmanaged, and the person carrying it burns energy on private dread. Worse, the isolation compounds it — each person assumes their concern is unique, maybe even a sign they're not up to the job, so they stay quiet, which keeps everyone else quiet too. Surfacing the fears anonymously breaks the loop in one move. Suddenly people see how much overlaps, the anxiety drops because it's shared, and the room can actually do something about the risks.
How do I surface my team's concerns?
You need sticky notes (or an anonymous digital equivalent) and about twenty minutes, ideally before a project kicks off.
- Everyone writes their biggest fear, anonymously. Each person writes their single biggest worry about the project on a sticky note — no names. Anonymity is doing the heavy lifting here; it's what makes people honest.
- Collect and shuffle. Gather all the notes and mix them up so no one can trace a fear back to its author. The shuffle protects the anonymity that makes the whole thing work.
- Read each one aloud and discuss. Go through them one by one. As you read, people will hear their own private fear come up — sometimes more than once — and visibly relax. Discuss each briefly: is this likely? how bad would it be?
- Turn the most common fears into mitigations. Don't stop at catharsis. Take the fears that recurred or scared people most and assign each a concrete action: a check-in, a backup plan, an earlier deadline, a conversation with another team. This is what converts an emotional release into actual risk management.
A worked example
A team kicking off a tight product launch runs an anxiety party. The notes come back and, read aloud, a pattern jumps out: four separate people wrote some version of "we're depending on the data team and they're swamped." Nobody had said it in planning because it felt like criticizing a sister team. Now it's undeniable. Instead of stewing, the team turns it into a mitigation: a named owner will sync with the data team this week and lock down the timeline in writing. Two other recurring fears get backup plans. The launch still has risks, but they're now visible, owned, and managed — instead of four people quietly losing sleep over the same thing in parallel.
When the anxiety party is most useful
It's ideal at the start of a project, sprint, or any high-stakes initiative — anywhere uncertainty is high and stakes are real. It pairs naturally with a pre-mortem. The non-negotiable is genuine anonymity: if people suspect their note can be traced, they'll soften it and you'll get nothing useful. It's less suited to tiny teams where handwriting or phrasing gives people away, and it's not a substitute for ongoing psychological safety — it's a structured moment that benefits from, and contributes to, that safety.
The takeaway
The risks that sink projects are usually the ones nobody felt safe enough to name. The anxiety party makes naming them the task, protects honesty with anonymity, and — crucially — turns the loudest fears into owned mitigations. Run it before your next big project and trade four people's private dread for one shared, manageable list.
This is one of Funstorming's 100 quests — bite-sized soft skills methods you actually put into practice, not just read about. Try it, then bring your result (or your sticking point) to the Funstorming community of practice (CoP), FunHub | Your Soft Skills Playground.
#funstorming #softskills