This article is for informational purposes only.
Most studio owners and event organizers eventually realize that the question isn't whether to provide a way for members to speak up — every studio website has a contact form — but whether anyone actually uses it. The contact form exists. The suggestion box exists. The "my door is always open" policy exists. The feedback still doesn't come.
This is a well-studied phenomenon. Harvard Business School professor Amy Edmondson has spent over two decades researching why people stay silent in organizations where they're explicitly invited to speak. Her finding — that the binding constraint isn't access but psychological safety — applies almost directly to community organizations, even though most of her research is in corporate and medical settings.
Here's what the research suggests about why members stay quiet, and what tends to change it.
The Concept, in Plain Language
Edmondson defines psychological safety as "a climate in which people are comfortable expressing and being themselves" — a shared belief that you won't be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.1
In a studio or event context: a member feels they can flag a concern without becoming the person who flagged it. Without being labeled difficult. Without subtle exclusion. Without retaliation. Without their relationship with the organizer changing.
A common misconception is that psychological safety means lowering standards or making the community "nice" in a way that prevents accountability. Edmondson is explicit that it doesn't — psychological safety is about whether people are able to raise hard issues, not whether the issues themselves get a free pass.2 Real accountability requires honest information; honest information requires safety.
Why Access Isn't Enough
Having a way to speak up is necessary but not sufficient. Members do the math on cost vs. benefit before saying anything:
The benefit: Whatever they want to flag gets addressed. Maybe.
The costs: They might be identified. The person they're flagging might find out. Other members might find out. The organizer might react badly. The relationship might shift. Nothing might happen and they'll have spent the social capital for no reason.
The benefit is uncertain. The costs are concrete. Unless the safety side of the equation is strong, the rational move is silence — even when the channel is right there.
This is why studios with detailed codes of conduct and prominent feedback forms still get blindsided by problems they "didn't know about." The members knew. They just didn't believe speaking up was safe enough to be worth it.
What Members Are Actually Watching
Members assess safety from behavior, not policy documents. Specifically:
How the organizer responds when someone speaks up about something small. A member who watches the owner react defensively to a minor complaint will not bring a major one. The reverse is also true.
Whether people who've spoken up are still in good standing. If a member who raised concerns six months ago is now subtly less included — fewer invitations, less warmth, exclusion from the in-group — every other member updates their model. The community has communicated, without any explicit policy, that speaking up has costs.
Whether anything ever visibly changes. If feedback disappears into a void, members conclude the channel exists for appearance. Visible change in response to feedback is the strongest signal future feedback will matter. (See How to Collect Anonymous Feedback at Events.)
Whether organizers model the behavior. If the owner publicly admits "I got this wrong, here's what I'm changing," that's a much stronger signal than any written policy. Modeling vulnerability is one of the most consistent predictors of psychological safety in research literature.3
How the organizer talks about absent people. If you talk dismissively about members who aren't present — "she's been complaining about this for months" — every member present updates their assumption about what you'll say about them.
The Structural Side: What the System Has to Provide
Beyond behavior, certain structural elements either enable or block psychological safety:
A reporting channel that's actually anonymous. Not just labeled anonymous — structurally anonymous, where the path from feedback to identification is technically impossible. (See Anonymous Feedback vs. Suggestion Box for the difference.) Members do the math on identifiability.
Clear policies about what happens after. Members are more likely to speak up when they know what the process looks like — not in performative detail, but enough to know it isn't opaque. "Reports are reviewed by [whom], investigated [how], with [what kind of follow-up to the reporter]" beats "we take all concerns seriously."
Visible separation from social consequences. A reporting channel that's not run by someone the reporter takes classes from feels safer than one where they'll have to face the recipient next week. Even when the recipient is the same person, framing the channel as a separate process creates psychological distance.
The ability to ask follow-up questions without identification. A two-way relay (see The Two-Way Relay Explained) lets the reporter respond to clarifying questions without giving up anonymity. They don't have to get the entire message right in one shot.
For an example of what these elements look like assembled into something a community actually displays at events, see the West Orlando Westies code of conduct referenced in How to Handle a Safety Report at Your Dance Event — the reporting QR code sits at the top of the document, not buried at the bottom, signaling that flagging concerns is part of how the community operates rather than an afterthought.
The Cultural Side: What the Organizer Has to Do
Structural elements set the floor. Cultural elements determine the ceiling.
Talk publicly about feedback you've received and acted on. Not specific reports, but the general fact: "Several people mentioned X, and we're changing Y." This normalizes feedback as something that gets responded to.
Acknowledge mistakes when they happen. "I should have handled that differently" is a powerful signal. It tells members that being honest about errors is allowed.
Don't punish people who bring you bad news. Even subtly. Even unintentionally. The reporter who brought up an instructor problem six months ago should be treated exactly the way they were treated before they reported. Members are watching.
Don't gossip about who said what. Even with trusted friends. Communities are small; word travels. If members hear that a previous report's source was discussed, they conclude theirs will be too.
Default to curiosity over defensiveness. When someone raises a concern, the first reaction is to explain or defend. The second reaction — to ask what they observed and why it affected them — is what builds safety.
Why This Compounds
A community where members feel safe speaking up has access to information no other community has. Problems surface earlier, when they're smaller and easier to fix. Risks get flagged before they become incidents. The community can correct itself because the corrections are visible.
The reverse is also true. A community where members don't feel safe gradually accumulates problems nobody mentions. The organizer believes the community is healthier than it is, because the only feedback that arrives is positive — and they react badly to the rare negative feedback that does, which reinforces the pattern.
Edmondson's broader point is that psychological safety isn't a soft thing — it's a substantial determinant of organizational performance, because it determines whether the organization knows what's actually happening.4 The same applies to a community: the safer it is to speak up, the more accurately the organizer can see.
Where to Start
If you're building this from scratch, the highest-leverage moves:
- Set up a structurally anonymous reporting channel with a two-way relay for follow-up.
- Respond visibly to feedback — close the loop publicly on changes that came from member input.
- Audit your own reactions when members bring up small things, and notice when you're defensive.
- Treat reporters the same in social contexts as you did before they reported.
- Acknowledge when you've gotten something wrong — publicly, specifically, briefly.
None of these are policy changes. All are behavioral patterns that compound over time.
The Tools
TellSafe provides the structural side — anonymous feedback via QR code or kiosk mode, a two-way relay for follow-up without identification, and clean records of what came in and what's been responded to. It started in the West Coast Swing dance community where the question of "how do we get members to actually tell us things" was driving real organizational behavior.
The tooling makes the structural part work. The cultural part is on you. Members are watching how you handle the small things — that's where they decide whether to bring you the big ones.
Sources
- Amy Edmondson, The Fearless Organization (Wiley, 2018). Definition cited in leanblog.org (2020).
- Amy Edmondson, "Psychological Safety," summary of work on accountability and standards (2025). amycedmondson.com
- Psych Safety, What is Psychological Safety? citing Caruso and Woolley 2008, in Edmondson and Lei 2014. psychsafety.com
- Edmondson, A. C., "Psychological Safety and Learning Behavior in Work Teams," Administrative Science Quarterly 44(2), 1999. JSTOR/MIT