Before You Facilitate

Why Read This If You’re Not a Facilitator

You don’t have to run events to benefit from understanding how good containers work.

If you know what responsible facilitation looks like, you can:

• Recognize when a container isn’t being held well—when safety protocols are missing, when incidents are being handled poorly, when the facilitator is fawning instead of leading. That awareness lets you navigate with more care, protect yourself, or choose not to return.
• Speak up when something’s off. You’re not a passive consumer. If you see something that should be handled differently, having the language and framework to name it gives you the power to create change—even as a participant.
• Be part of the solution. The best containers aren’t held by facilitators alone. They’re held by participants who take responsibility, who understand the dynamics, who add value instead of just consuming the experience.

Knowing how things should work makes you a better participant everywhere you go.

A Note on Context

Not all facilitation looks the same. There’s a spectrum:

• A seven-day transformation retreat where deep work happens and you’re guiding people through life-changing experiences
• A weekend workshop mixing education with exploration
• A one-night play party where you’re primarily holding safety
• A casual gathering with minimal structure and a loose host

This page is written for the deep end—because that’s where the stakes are highest and the principles matter most. But the core ideas scale down. Even a casual host benefits from understanding Rescuer dynamics, proportional response, and not fawning when things get uncomfortable.

Take what’s relevant to your context. The deeper the container you hold, the more of this applies.

A Note on Severity

Facilitating sex-positive events is higher severity than most other facilitation work.

The stakes are higher. The mistakes are more costly. The dynamics are more complex. The potential for harm—and the potential for profound healing—are both amplified.

This means that having the concepts in this book deeply understood and embodied isn’t optional. Whether you learn them here or elsewhere, having these principles figured out will be imperative to your continued happiness and success as a facilitator.

If you’re facilitating in intimate spaces without this foundation, you’re playing minesweeper without knowing where the mines are.

The “Facilitators Should Be Perfect” Trap

If you’re reading the section above and thinking “the stakes are too high — I can’t afford to make a mistake” — notice that belief, because it cuts both ways.

As a participant, “facilitators are perfect” turns you into someone who attacks facilitators the moment they’re imperfect. You hold them to a standard no human can meet, and when they inevitably fall short, you treat it as evidence that they’re dangerous instead of evidence that they’re human. Your story says mistakes are unacceptable, so you treat every mistake as proof the facilitator shouldn’t be facilitating.

As a would-be facilitator, the same belief paralyzes you. You look at the role and think: I know how to do this, but I can’t guarantee zero mistakes. And if I make one, the mob will destroy me. So you never step up. The spaces that need clear-sighted facilitators the most never get one — because the people who could do it are too afraid of the standard they’ll be held to.

Being a great facilitator isn’t about never making mistakes. It’s about taking real measures to reduce them — and then knowing how to handle them well when they happen anyway. Because they will happen. The question isn’t whether you’ll face a situation you’ve never been in before. It’s whether you’ll walk your talk when you do.

Staff Readiness: Feed Yourself First

Here’s something most facilitators don’t talk about:

If you’re sexually starved, you’re a liability.

Think about it like a hungry dog at a buffet. A well-fed dog can walk past food without grabbing. A starving dog cannot. Its animal body takes over. Impulse overwhelms judgment. The same applies to facilitators and staff at sex-positive events.

When you’re sexually fed, your conscious mind has more control. You can be around intimacy without your body pulling you toward it. You make clearer decisions. Your presence is calmer.

When you’re sexually starved, the pull is stronger. Your subconscious is scanning. You’re more likely to miss cues, push boundaries without realizing it, or slip in ways you wouldn’t if you were satisfied. And if you’re carrying a scarcity mindset on top of that — a story that says opportunities like this are rare, I should make the most of this — the pull gets even stronger. That’s not just hunger. That’s hunger plus a filter that says now or never.

This isn’t about willpower or character. It’s about state management — the same logic as getting enough sleep, eating before you facilitate, and managing your emotional activation. You wouldn’t run a container while sleep-deprived. Sexual starvation is the same category of risk.

The Facilitator Standard

If you’re facilitating or assisting at sex-positive spaces, consider this professional hygiene:

Take care of your sexual needs before you facilitate.

This might mean:

• Having a partner who meets your needs
• Attending events for your own pleasure (separate from work)
• Finding regular outlets for intimacy and connection

If you’re leading a week-long retreat, make sure you’re not arriving starved. If you’re running a play party, make sure your needs have been met recently.

For Your Staff

If you have staff or assistants, consider their state too.

A recommendation: Consider making this a requirement, not a suggestion. You cannot work my events unless your needs have been met recently.

Even if you don’t set a hard rule, do a vibe check. You can feel it when someone has hungry ghost energy — that starving, seeking, desperate-for-connection state that makes them a liability in intimate spaces. You don’t need to ask them when they last had sex. You can see it. If someone on your staff has that energy, they’re not ready to hold space. Feed them first.

Think of it like meals at a retreat. If nobody had eaten in 24 hours, you wouldn’t push forward with the curriculum. You’d stop and feed everyone first. Same logic.

The Jumpmaster Reframe

There’s a video of military paratroopers jumping from a plane. Before each jump, a jumpmaster does a final check — gear, straps, everything. In the video, someone is about to jump. Split second from the door. And the jumpmaster sees it: the static line is wrapped around the jumper’s neck. If he jumps, he’s decapitated.

The jumpmaster grabs him. Shoves him back. Saves his life.

That pre-check isn’t bureaucracy. It’s love.

When I require my staff to be sexually satisfied before working my events, I’m not just protecting participants. I’m protecting them. I’m the jumpmaster — catching something that could hurt them before they jump.

If you’re sexually starved and you make an unconscious mistake, you don’t just harm the participant. You harm yourself — your reputation, your standing, your self-image. By saying “you can’t work here until you’re fed,” I’m saying: Go take care of yourself. I won’t let you jump with a rope around your neck.

Friction Check Your Staff

Most facilitators choose staff who are nice, polite, experienced, and easy to be around. They check for the happy path — will this person be pleasant to work with when everything goes well?

They don’t check for the unhappy path.

When someone makes a mistake and a righteous predator mobilizes the room against them — and you need to make a tough call that some participants will disagree with — will your staff have your back? Or will they side with the mob because their own filters are activated too?

Before your container starts, find out. Have the hard conversations with your team: What would you do if a participant makes a mistake and another participant over-responds? What if you have to remove someone the crowd thinks is the hero? What if someone you empathize with is the one causing harm? What if one of our own staff makes the mistake — how do we handle that as a team?

Listen to how they think. Not what they say they’d do in theory — how they actually reason through it.

That last question matters more than it seems. When a staff member makes a mistake, the stakes are higher for everyone — participants question whether they’re safe, and the staff can fracture. Some take sides with the staff member who made the mistake, some take sides against them, and suddenly you have competing factions inside your own team in the middle of a crisis. A team that hasn’t been friction-checked will split along their individual filters when pressure hits. A team that has will stay coherent — because they already talked through these scenarios and know how they’ll handle them together.

If you’re a facilitator with a fawning pattern, this is especially critical. When things get hard and you have to stand up for a participant who’s being wronged — or make a call that the crowd won’t like — knowing your staff are with you is the difference between acting and freezing. You can face a righteous predator if you know your team won’t crumble behind you. If you’re not sure, it’s that much easier to fawn — to back down, appease the loudest voice, and let the container lose coherence rather than risk standing alone.

Staff who are wonderful on the happy path but narrative-locked on the unhappy path will compound the problem. If two out of three facilitators share the same blind spot — the same filter, the same wound — and something triggers it, you don’t get one person’s bias. You get the entire facilitation team reinforcing each other’s distortion. The container stops being held and starts being driven by the team’s shared blind spot.

I watched this happen at a retreat. There was a sharing exercise where all the women got to share and not all the men did — they ran out of time. Afterward, several participants — men and women — expressed that they felt sad for the men who didn’t get to share. It was a universal human feeling: some people got to be heard and some didn’t, and that doesn’t feel good.

One of the facilitators couldn’t see it that way. Her patriarchy filter turned “people feeling left out” into “men trying to take more than they deserve.” Men and women were both expressing a completely ordinary disappointment: some of us got to be heard and some didn’t. But her story about men and power overwrote what was actually in front of her. She couldn’t empathize with people wanting to be heard — because her filter had already categorized it as oppression. She felt distressed and resentful toward the participants who were asking for more sharing time. The people she was supposed to be serving had become the enemy — not because of anything they did, but because of the story she was seeing them through. That’s an us-versus-them mentality between a facilitator and her own participants. You can’t serve people you see as the opposition.

What made it worse: there were more men than women at this retreat. The men were already experiencing a compounding scarcity — fewer women to connect with at a sex-positive event where connection is the whole point. Not getting to share was landing on top of that. Her filter was so locked on “men taking too much” that the actual landscape of the container — men who already had less, now getting even less, and being resented for noticing — was completely invisible to her. Her attention was on one thing, and the thing that was probably shaping the men’s experience more than anything else wasn’t even in her field of vision.

That’s what a blind spot on your staff looks like in practice. One facilitator with that filter is manageable — someone else on the team can see what she can’t, and more importantly, can take over when she’s triggered so the container stays in steady hands instead of emotionally charged ones. Three facilitators with that filter, and the entire team misreads the room together. No one catches it because they’re all seeing the same distortion — and no one is left to hold the container while the others are activated.

You’re not going to find staff with zero filters. That person doesn’t exist. What you’re checking for is two things: first, that no one on your team has filters so intense they’ll overwhelm their judgment when it matters most — the kind that turn participants into enemies the moment a trigger hits. And second, that whatever filters your staff do carry are different from each other. A team where one person has a patriarchy filter, another has an authority-wound filter, and a third has a conflict-avoidance filter is resilient — because when one person’s filter gets triggered, the other two can still see clearly. A team where everyone shares the same filter is fragile — because when it gets triggered, every single person on the team misreads the room at the same time, they all reinforce each other’s distortion, and no one is left to say wait, I’m seeing something different.

The Recovered Righteous Predator on Your Team

The friction check isn’t just about filtering people out. It’s about recognizing who’s uniquely valuable — and the most valuable staff member you can have might be someone who used to be exactly the problem this book warns about.

A recovered righteous predator — someone who once would have been part of the angry mob, who lived blinded by the same stories the crowd gets caught up in, and who has since grown enough to see through them — is an asset you can’t replicate with someone who’s never been there.

Here’s why: when the mob shows up, you need someone who can talk to them. Not at them. To them. Someone who can empathize with the crowd because they used to be the crowd. Someone who’s fluent in the mob’s language because they used to speak it. Someone who can code-switch — stand with you on principle while meeting the angry participants where they are, creating a felt sense of trust and safety that you can’t create if you’ve never stood where they’re standing.

If you’ve never been a righteous predator, you might see the angry mob as irrational, dangerous, or just wrong. And they might be wrong — but they don’t feel wrong to themselves. They feel righteous. They feel like protectors. They feel like the only people in the room who care. A staff member who used to feel exactly that way can reach them in a register you can’t. They can say I understand why you feel this way — I used to feel the same way and mean it. That sentence, coming from someone the crowd can sense is genuine, does more to de-escalate a room than any amount of facilitation technique from someone who’s never been on the mob’s side of the line.

That’s the staff member you want. Not someone who’s never had the impulse to join the mob — someone who’s had it, lived it, seen through it, and now fights it in themselves every day. They know the pattern from the inside. They know how it feels to be certain you’re right while causing harm. And because they know, they can see it forming in real time — and intervene before it locks in.

Don’t filter out everyone who’s ever thought like a righteous predator. Filter out the ones who still do. The ones who’ve come through it and can see both sides? Put them on your front line.

Don’t Watch Horror Before Temple

Here’s another form of professional hygiene that sounds like satire:

If my staff are consuming predator-hunting content right before working my events, they don’t get to work.

This means: no horror films, no true crime binges, no doom-scrolling through callout posts, no consent-violation discourse—right before showing up to hold space.

Why? Because of the horror movie effect. If you spend hours priming your RAS to scan for threats, you’re going to walk into a room full of friends and see predators everywhere. Every ambiguous touch becomes suspicious. Every awkward moment becomes evidence. You’re setting yourself up to see shit that isn’t real—and then react to it.

This sounds unbelievable. It sounds like a joke. “You can’t be staff if you watched a horror movie?” But that’s exactly the level of sensitivity we’re operating at. The number of unconscious filters running your perception is immense. If you’re filling your head with monsters before entering an intimate space, you are not in a state to hold it safely.

The same logic applies: you wouldn’t let someone work your event if they hadn’t slept, if they were drunk, if they were sexually starved. Mental state matters too. Filter state matters. What you consume affects what you perceive—and what you perceive affects what you do.

This is the jumpmaster check for your staff’s filters. Don’t let them jump with their RAS primed for predators.

Pre-Framing: The Flip Side

What you just read is pre-framing — your filter gets set before you walk into the room. Horror content pre-frames your staff to see threats. But the same mechanism works in the positive direction.

When you open your container by telling everyone “people here are learning, mistakes are expected, and when something goes wrong we repair with love — everyone around you is your friend,” you’re pre-framing every participant’s filter. You’re setting their RAS to interpret ambiguous moments as learning rather than threats.

This matters because the first frame applied to a situation tends to stick. If someone’s filter is already set to “safe learning environment where mistakes are expected,” then when a boundary gets crossed, their first interpretation is “that was a mistake, let’s repair.” If their filter was never set — or worse, was set by scrolling through callout posts before arriving — their first interpretation might be “predator.” And once that label lands, it’s nearly impossible to dislodge. The group’s perception crystallizes around it.

Your opening remarks aren’t a formality. They’re inoculation — you’re installing the group’s immune system before anyone gets sick.

Will You Play With Participants?

One of the first decisions you need to make as a facilitator is whether you will engage in intimate or sexual play with participants in your container.

Some facilitators choose not to. Others choose to participate fully. Both are valid choices—but each comes with tradeoffs you need to understand.

If You Choose NOT to Play

Pros:

• Cleaner power dynamics—no questions about whether your authority influenced a participant’s consent
• Easier to stay objective when conflicts arise
• Less personal risk of being involved in a mistake or accusation
• You can focus entirely on holding the container

Cons:

• May feel disconnected from what participants are experiencing
• Less experiential understanding of the vulnerabilities involved
• Some participants may perceive you as outside the experience rather than part of it

If You Choose TO Play

Pros:

• Deeper connection with participants—you’re in it together
• Leading by example—showing how to navigate these spaces, not just telling
• Direct understanding of participant experience and vulnerabilities
• Can model good behavior in real-time

Cons:

• Power dynamics become more complex—did they say yes because they wanted to, or because you’re the authority figure?
• You will eventually make mistakes or have mistakes made against you
• You are now subject to over-responses, accusations, and the same dynamics you’re trying to manage
• Harder to stay objective when you’re personally involved in conflicts

The Acceptance

If you choose to play with participants, you must accept that mistakes and over-responses will eventually occur.

This isn’t a possibility—it’s a certainty. Play long enough and:

• You will cross someone’s boundary accidentally
• Someone will cross yours
• Someone will over-respond to a mistake you made
• You’ll have to navigate being both facilitator and participant in a conflict

This isn’t a reason not to play. But it IS something you must go in with eyes open about. If you’re not prepared to handle being on the receiving end of the dynamics this book describes, you’re not ready to be a facilitator who plays.

Some of the best facilitators never touch a participant. Some of the best facilitators are fully in the mix. What they have in common is clarity about their choice and how to handle what comes with it.

The Promise

One of the most powerful things a facilitator can do is establish clear rules at the beginning of a container—and make an explicit promise:

As long as you follow these rules, you are safe. You will not be kicked out. You will not be punished. You have room to experiment, make mistakes, and learn. I have your back.

This principle shows up in any high-performance environment: when people know exactly what the boundaries are, and know they’re protected as long as they stay within them, they can relax. They can take risks. They can fail and learn without fear.

This Applies to Staff Too

The promise isn’t just for participants. Your staff need it too.

At events where staff play with participants, mistakes can occur between them—just like between any two people. Staff should have clear boundaries about what happens when mistakes occur, so they’re not operating in fear either.

You can:

• Use the same promise for everyone — participants and staff operate under identical rules
• Modify the promise for staff — perhaps staff have additional responsibilities, or slightly different expectations given their role

Either way, make it explicit. Staff who don’t know where they stand will fawn, over-function, or hold back in ways that don’t serve the container.

Why This Matters

Without clear rules, participants are anxious:

• “What if I do something wrong?”
• “What if someone gets upset with me?”
• “What if I make a mistake and get kicked out?”
• “What counts as ‘too far’?”

This anxiety creates fawning, over-caution, and inauthentic participation. People can’t fully show up if they’re afraid of invisible tripwires.

With clear rules, participants feel contained:

• “I know what’s expected of me”
• “I know what will get me in trouble”
• “I know that mistakes are okay”
• “I know the facilitator has my back if I’m operating in good faith”

Suggested Guidelines

Here’s a starter set of rules you might adapt for your container:

You are safe as long as you:

1. Operate in good faith — You’re trying to do right by others, even when you make mistakes
2. Communicate honestly — You don’t deliberately deceive or manipulate
3. Respect stated boundaries — When someone says no or stop, you stop
4. Check in when uncertain — If you’re not sure, you ask
5. Take responsibility for your mistakes — When something goes wrong, you own your part
6. Treat others with dignity — Even in conflict, you don’t attack character or threaten

Mistakes are expected and okay:

• Accidental boundary crossings (unconscious, unintentional)
• Miscommunications
• Getting triggered and needing to step away
• Trying something that doesn’t work
• Not knowing something you “should” know

These will result in being asked to leave:

1. Threats or acts of physical violence — Verbal, physical, or implied. This includes intimidation through body language—walking up to someone aggressively, getting in their face, making them fear you might assault them. You don’t have to say “I will punch you” for it to count. Interpretation is up to the facilitators and is not up for debate. Non-negotiable. (See: Threats of Violence Must Be Stopped Immediately)
2. Intentional malice — Deliberately trying to harm someone. If you’re intentionally malicious, you’re out. Not because of judgment, but because we can’t risk escalation.
3. Repeated boundary violations after being told — One mistake is human. Continued violation after clear communication is a pattern.
4. Using victim status as an excuse to attack — Whether it’s your own victimhood or someone else’s you’re “protecting,” victim status is not a license to attack. Defense is acceptable; aggression disguised as defense is not. (See: Power Dynamics)
5. Destroying someone’s reputation — Overt attempts to damage someone’s character or rally others against them. If you’re trying to get people to turn on someone rather than resolving the issue directly, you’ve crossed from defense into aggression.

Defense vs. Aggression

When something goes wrong—a boundary violation, an unwanted touch, a miscommunication—you have rights:

Defensive actions are always acceptable:

• Removing yourself from the situation
• Separating someone you care about from harm
• Saying “stop” or “no” firmly
• Having strong emotions
• Taking space to process
• Reporting to facilitators

These are protective. They create safety.

Aggressive actions are not acceptable:

• Using the incident as an excuse to publicly attack their character
• Mobilizing others against them before verification
• Responding to a MEDIUM severity infraction with HIGH severity action—that’s attack, not defense
• Calling your aggression “defense” when you’re really indulging your anger

Here’s the key: Defense protects. Aggression punishes.

Your Rights Regarding Removal

You DO have the right to:

• Ask the facilitators to enforce our stated agreements
• Request that we review whether someone has violated a removal-worthy rule
• Expect us to act if someone has genuinely crossed those lines

In fact, we welcome it. We invite you to help us walk our talk and maintain our integrity. If you see us failing to uphold our own agreements, tell us. Be an ally in keeping this container safe. We want that partnership.

You do NOT have the right to:

• Demand that someone leave if they haven’t violated the stated rules
• Pressure facilitators to remove someone based on your anger rather than the agreements
• Treat your emotional reaction as equivalent to a rule violation

If your primary goal is to make sure you and others are safe, you’re in defense. If your primary goal is to make the other person pay, you’re in aggression—even if you’re calling it “holding them accountable.”

When you’re activated and angry, it’s easy to blur this line. That’s why we name it upfront: strong emotions are welcome, defensive actions are protected, but using an incident as license to attack will not be tolerated.

Why This Benefits You (The Facilitator)

These rules aren’t just for participants. They’re for you.

Clarity on when to act: When you’ve clearly stated what will result in removal, you don’t have to agonize. In the heat of a situation, ask: “Did they violate one of my stated rules?” If yes, act. If no, work through it. The rules become your decision-making framework — no second-guessing.

Accountability to your own values: Writing it down and sharing it publicly keeps you honest. If you say “threats of violence result in removal” but then let it slide because you’re scared of the person, a participant can point to your own rules and help you walk your talk.

Protection from accusations of targeting: When everyone knows the rules upfront, your enforcement looks like consistency, not personal vendetta.

Example: How to Present This

This should be communicated at the very beginning of your container — not after someone makes a mistake, not as a reaction to conflict. When it’s established upfront, it’s a framework for safety. When it’s announced mid-conflict, it looks like targeting. Here’s language you might use:

“Before we begin, I want to make a sacred promise to you.

This promise is the foundation everything else rests on. It’s the prime directive of this container. Every decision I make as your facilitator will orient around it.

Here is my promise:

As long as you operate in good faith—communicating honestly, respecting stated boundaries, checking in when uncertain, and treating others with dignity—you are safe here. I have your back.

You can make mistakes. You can try things that don’t work. You can get triggered and need to step away. You can not know things you ‘should’ know. None of that will get you removed. You are protected.

There are five things that will break this protection:

1. Threats or acts of physical violence—verbal, physical, or implied through body language. Interpretation is up to me, not up for debate.
2. Intentional malice—deliberately trying to harm someone
3. Repeated boundary violations after being told to stop
4. Using victim status as an excuse to attack—yours or someone else’s. Victim status is not a license to attack.
5. Destroying someone’s reputation—trying to damage someone’s character or rally others against them

If you cross these lines, I cannot guarantee your place here.

One exception: In rare cases, I may need to ask someone to leave—or to step out temporarily—for emergency safety reasons, even if they haven’t broken these rules. This isn’t punishment; it’s protection. If I ever need to do this, I’ll explain why, and it won’t affect your standing in future events. This exception exists for genuine emergencies—not as a loophole for arbitrary removal.

One more thing: If something goes wrong—if someone crosses a boundary—you have every right to strong emotions. You have every right to remove yourself, protect yourself, and report to us. These are defensive actions and they’re always acceptable.

What’s not acceptable is using an incident as an excuse to attack. If your response shifts from protecting yourself to punishing someone else—public attacks, mobilizing others, demanding removal based on anger—that’s aggression, not defense. Even if you’re angry, even if the incident was real.

This is my promise. This is my commitment. This is the ground we stand on.

Inside these lines, you are safe. Outside them, you are not. Know where they are, and you can relax inside them.“

You can adapt this language to your style. The key is: say it early, say it clearly, and put it in writing if possible.

When the Facilitator Is the Target

Everything above addresses what happens when participants conflict with each other. But the promise matters most in the scenario nobody plans for: when someone accuses the facilitator of being the problem.

If a righteous predator attacks a facilitator — publicly calling them a predator, demanding their removal, rallying the room — and they successfully Narrative Lock the group into believing the facilitator is the threat, the container’s integrity is at maximum risk. Not because the facilitator did something wrong, but because the person everyone relies on to hold the container is the one being questioned.

Without a pre-established promise, the facilitator has no ground to stand on. Every decision they make looks self-serving. “Of course they’re not removing themselves — they’re the predator.” The righteous predator’s story becomes the only story, because the facilitator’s authority — the only thing that could counter it — has been undermined.

With a promise, the co-facilitators can step in and honor the agreements made at the beginning of the container. They don’t have to make judgment calls under pressure. They don’t have to take sides. They just follow the promise: threats of violence result in removal. Destroying someone’s reputation results in removal. The person making accusations is either within the agreements or they’re not. The promise decides — not the popularity of the accusation.

The promise also protects facilitators from their own fawning. Without pre-committed agreements, a facilitator facing an angry person has to make a judgment call in real time — and fear can drive them to appease the loudest voice instead of doing the right thing. They might tolerate threats to avoid hate mail. They might sacrifice the person who made a mistake to keep the angry person calm. That’s not a facilitation decision. That’s a trauma response. The promise removes that trap — the decision was already made before the fear showed up. The facilitator doesn’t have to be brave in the moment. They just have to honor their word.

The group might disagree with the call. That’s fine. But they can see the promise being honored. They can see that the facilitators do what they said they would do, even when it’s hard, even when the facilitator themselves is the one under fire. That’s integrity — and integrity holds containers together when nothing else can.

This is why the promise needs to be made by the entire facilitation team, not just the lead. If the lead is the one being accused, the co-facilitators need to be empowered — and committed — to uphold the same agreements. A promise that only one person can enforce is a promise that breaks the moment that person is targeted. The promise is what holds the container — not any individual facilitator’s personal authority. If the container can only survive as long as the lead facilitator’s authority goes unchallenged, it was never solid to begin with.

When the Facilitator Fawns

Everything above assumes the facilitator acts. But what happens when they don’t?

A participant makes a LOW-severity unconscious mistake — a momentary boundary crossing, immediately recognized. They repair with the person whose boundary was crossed that same night. The person whose boundary was crossed says they feel complete. By all accounts, it’s handled.

Then another participant responds with threats of violence, public attacks on their reputation, and demands that the person who made the mistake be removed. The facilitator watches this happen. They know the mistake was LOW to MEDIUM severity and doesn’t warrant a HIGH severity response. They know the person making threats is the one creating danger. And they don’t act — maybe because they’re afraid, maybe because they’re unsure, maybe because they’re hoping it resolves on its own. Whatever the reason, the person who needed protection doesn’t get it.

That’s facilitator fawning. And it’s the most damaging form of under-response in a container, because the facilitator’s silence doesn’t just fail to stop the harm. It enables it.

Here’s what makes this so painful to look at in hindsight: the difference between a forgettable incident and months of lasting harm is usually a few decisions made in the first hour. The original mistake — a momentary boundary crossing, already repaired — was a few hours of discomfort at most. Everything after that is determined by how the facilitator handles it. Remove the public defamation before anyone sees it, handle the righteous predator privately instead of giving them a stage, provide context to the group before the angry person’s story becomes the only story — and the person who made the mistake goes home thinking that was a rough night. Not my life was destroyed. Almost all of the suffering comes from the handling, not the incident.

Why Facilitator Silence Is Different

When a participant sees something wrong and stays silent, that’s one person’s fear. When a facilitator sees something wrong and stays silent, the group reads it as authority. The facilitator is the person everyone is looking to for guidance on what’s acceptable. If they’re not stopping it, it must be okay. If they’re not contesting the accusations, they must be true. If they’re not protecting the person being attacked, the person must deserve it.

The righteous predator’s narrative becomes the group’s narrative — not because everyone agrees, but because the person with the most leverage to offer a different narrative is silent. Other participants can challenge it, but their words carry less weight. People who privately disagree stay quiet too, because they can see what happens when someone challenges the righteous predator: the facilitators don’t intervene. Why would a participant risk speaking up when the people responsible for safety won’t?

This is the cascade: one person over-responds. The facilitator fawns. The group reads the fawning as endorsement. The righteous predator’s story becomes the only story. Participants who disagree go silent. And the person who made the original mistake absorbs every layer — the attack, the abandonment, the group’s judgment, and the reputation damage. Not one harm. Five.

What Facilitator Fawning Looks Like

It rarely looks like doing nothing. It usually looks like doing something — just not the thing that matters.

Before the group gathers: A participant publicly attacks another participant’s reputation — writing their name somewhere visible as an act of defamation, making accusations impossible to miss. The facilitators see it but don’t remove it before the group gathers. By the time participants walk in, the accusation is the first thing they see. The facilitator’s inaction made it the group’s first frame. Every participant who walks in and sees it asks themselves: does this person deserve this level of anger? Before a single fact has been shared, the attacked person’s reputation is already in question — because if this were a disproportionate, irrational response to what was probably an unconscious mistake, the facilitators would have removed it. They didn’t. So maybe it’s warranted. Maybe this person really did something that bad. The facilitator’s inaction gives the accusation perceived validity simply by letting it stand. Remove it immediately — whether or not participants have already seen it. And if someone is angry enough to publicly deface a space to attack another person’s reputation, staff need to find them immediately — both to make sure they’re not continuing to do it elsewhere, and to assess whether they’re an immediate threat to the individual or the container. Either way, name it to the group: “Someone violated our agreements by publicly attacking another participant’s reputation. That is not acceptable in this container, and it has been removed.” Even if every participant already saw it, the facilitator publicly naming it as a violation changes the frame — from “maybe this accusation is valid” to “this was an over-response that broke our agreements.”

During the public processing: The facilitator sets up a format for the two participants to “share emotions” with each other, but doesn’t guide their participants or audience through the process. No context is given to the group. Nobody shares the facts that would let the room assess proportionality for themselves — that repair already happened, that the person whose boundary was crossed already said they felt complete. The facilitator doesn’t need to declare “this is disproportionate.” They just need to provide the context. The room can see the severity mismatch on its own — if it has the facts. The righteous predator makes threats of violence, and the facilitator doesn’t name it: “Threats of violence are outside the boundaries of this container.” Doesn’t state consequences. Doesn’t enforce the time structure when the righteous predator talks over it. Doesn’t interject when the situation needs guidance.

Instead of a facilitated resolution, it becomes a public trial run by the angriest person in the room. The facilitator is present but not leading. They’ve outsourced the container to the person least qualified to hold it. (For what this looks like when done well — rapport first, questions instead of declarations, guiding the room to see the disproportionality rather than announcing it — see Guiding Public Repair.)

After the public processing: The facilitator doesn’t communicate — to the group, to their staff, to anyone — that what happened wasn’t aligned with what they believe is right. Staff members walk away with the righteous predator’s story as the only story. Some of them treat the person who was attacked with contempt. The facilitator never corrects this, because correcting it would mean admitting they fawned — and admitting that feels harder than letting the wrong story stand.

What Facilitators Are Afraid Of

Facilitator fawning isn’t random cowardice. It’s a specific fear response, and it usually comes from one of these:

• Fear of escalation — They’re already making threats. What if challenging them makes them violent? What if they turn on the facilitators?
• Fear of organizational damage — What if the righteous predator writes public attacks about the organization? What if they rally others against it? The facilitator protects the organization’s reputation by sacrificing an individual’s.
• Fear of the group turning — If the group has already been narrative-locked by the righteous predator, challenging the narrative means the facilitator becomes the next target.

Every one of these fears is real. And every one of them produces the same result: the facilitator does less than they know is right, and someone who needed protection doesn’t get it.

When Protection Goes to the Wrong Person

The most painful version of facilitator fawning is when the facilitator protects themselves or their organization instead of the person who needs it.

It looks like this: someone over-responds — the response is clearly disproportionate to what happened. The person being attacked should be defended. But defending them would mean confronting the righteous predator — and the righteous predator might retaliate against the facilitator or their organization. Hate mail. Public accusations. Reputation damage. So the facilitator doesn’t confront it. The attack lands on the individual instead. The person who was attacked gets removed, not the person attacking.

The facilitator’s reputation goes relatively unchanged. The individual’s doesn’t. Whatever the facilitator’s reasons for not acting, the result is the same: the reputation damage the facilitator avoided lands on the person they knew was being disproportionately attacked.

Warning Signs You’re Fawning Instead of Facilitating

• You feel like you can’t tell the angry person no — because you’re afraid of what happens if you do, so you stop setting boundaries, and the container drifts into their hands
• You know what should happen but you’re not doing it
• You’re letting the angriest person set the terms of every conversation
• You’re not enforcing your own time structures or agreements
• You haven’t told the group what you actually think should have happened
• You removed the person receiving threats to appease the person making them
• You know the group is carrying a distorted story and you haven’t corrected it

What Should Happen Instead

Name it immediately. When threats of violence happen, say it out loud: “Threats of violence are not acceptable in this container. If they continue, you will be asked to leave.” This isn’t confrontation. It’s the promise being honored. The decision was already made before the fear showed up.

Handle it privately first — don’t give the righteous predator a stage. If someone is making threats and attacking another participant’s reputation, the worst thing you can do is put them in front of the entire group and let them perform their rage with an audience. Every participant who watches becomes a witness to the narrative you’re allowing to be broadcast. Handle it privately: talk to the righteous predator alone, talk to the person who was wronged alone, establish what actually happened, set boundaries — and THEN decide what the group needs to hear, and frame it yourself. The group should hear your framing first, not the angriest person’s. Every minute you delay is a minute the righteous predator’s story spreads unchecked.

Provide context before public processing. If the group does need to hear about what happened, the people directly involved should speak first — starting with the person whose boundary was actually crossed. If that person says they feel complete, the group needs to hear that before the righteous predator frames the narrative.

If there are threats of violence, both people may need to leave. The person receiving threats leaves for their safety — with a full refund and an explicit invitation back. The person making threats leaves because they violated the container’s agreements — with clear conditions for what needs to happen before they can return. The facilitators handle the group without either person present. This isn’t punishment for the person who made the original mistake. It’s protection. And calling it what it is — protection, not exile — matters.

Facilitate, don’t spectate. If you do set up a format for two people to process together, guide it. Interject when someone makes threats. Point out what’s happening. The group is looking to you to help them see clearly.

Protect reputation immediately. If someone’s reputation has been publicly attacked in your container — their name written somewhere visible as defamation, accusations made in front of the group — pause the container and address it before anything else. Don’t continue the schedule while one of your people has been publicly disgraced. Taking care of them first — before the agenda, before the curriculum — shows everyone that you value people over process.

Don’t celebrate fawning as resolution. If one person screamed threats and the other person apologized and submitted, that’s not resolution. That’s one person being pressured into compliance. If the person making threats never recognized any wrongdoing, and the person who made the original mistake did all the apologizing — that’s submission, not repair. Real resolution requires the righteous predator to see their own over-response, not just the other person’s mistake.

Communicate after. If you made a decision under pressure that wasn’t aligned with what you believe is right, say so — to your staff, to the group, to the person who was affected. Silence after a bad call is a second under-response. Your staff need to know what you think should have happened, or they’ll carry the righteous predator’s story as the truth.

Assign protection. If someone in your container has received threats of violence, they need a staff member with them. Not as surveillance — as safety. They shouldn’t be walking the grounds alone, packing alone, or unable to get food because the person who threatened them is blocking the lunch table. Physical safety is the baseline, and someone who’s been threatened deserves to feel held, not abandoned.

If You Realize You Fawned

You will. If you facilitate long enough and you have a fawning pattern, there will be a moment where you look back and realize: I didn’t do what I knew was right, because I was afraid.

That’s not the end. That’s the beginning of repair.

Making it right as a facilitator who fawned means:

1. Acknowledge it — to yourself first, then to the person you failed. Not “I could have done better” — that’s a hedge. “I was afraid, and I didn’t protect you when I should have.”
2. Tell the truth to your community. If the group is carrying a distorted story because you didn’t correct it, correct it now. Explain what happened, how you failed, and what should have happened. This is the hardest step and the most important one.
3. Set the boundaries you should have set. If someone made threats of violence and you didn’t set a boundary with them, set it now. It’s late. It’s still necessary. Tell them what they did wasn’t acceptable and what needs to happen before they can return.
4. Ask the person you failed what would make it right. Not what you think is reasonable. What they need. You under-responded. The repair should be proportional to the harm — and the harm includes every layer of the cascade: the attack, the abandonment, the reputation damage, and the time they spent unprotected.
5. Change your systems. If you didn’t have a promise, create one. If you had one and didn’t honor it, figure out why and build the structure that prevents it next time. The promise exists specifically to make facilitator fawning harder — the decision is pre-made, so you don’t have to be brave in the moment.

Facilitator fawning isn’t a character flaw. It’s a pattern — the same pattern this entire chapter describes. The same fear, the same override, the same cost. The difference is that when a facilitator fawns, the cost isn’t just theirs. It cascades through every person in the container who needed them to act and watched them freeze.