What This Is And What It Isn't
I need to be upfront here because this is a topic that comes up in a lot of team meetings with people who've read a LinkedIn article and suddenly feel qualified to rebrand something. "Secret Sessions" is not a recognized framework in organizational psychology or team dynamics literature. There is no established model by this name in any academic journal, Harvard Business Review publication, or major consulting firm's methodology. What you will find online are vague blog posts, AI-generated content farms, and a few course sellers using the phrase as marketing language for nothing more than basic facilitated brainstorming wrapped in dramatic terminology. The concept people are referring to when they use this phrase generally maps onto one or more real practices: confidential round-table discussions where team members share unfiltered feedback, anonymous input-gathering sessions before meetings to reduce groupthink, or facilitated dialogue exercises modeled after techniques like "start-stop-continue" or "fishbowl discussions." None of these are secret. None of them are new. The "secret" part is entirely a branding choice. I ran into this exact framing last year when a department head at a mid-size company asked me to evaluate a "Secret Sessions" workshop their leadership team had purchased from a consulting outfit. I reviewed the materials. It was a three-hour facilitated session where senior leaders filled out anonymous prompts on index cards, then went around a room sharing them. That's it. The same process exists in virtually every team dynamics textbook published since the 1990s under names like "anonymous feedback round" or "structured silent brainstorming."
How The Actual Practice Works
If you want to run what people calling this model are actually describing, here is the plain version without the marketing gloss. You gather a team in a room or on a video call. Before the session, each participant privately writes down honest observations about team dynamics, collaboration blockers, or process friction — things they would not normally say in a group setting. These are collected anonymously. Then the group reviews them together in a structured format where the focus is on patterns, not individuals. The mechanics matter more than the branding. Specifically: Anonymous pre-work is the engine. Without it, you get the same social conformity effects that make regular team meetings unproductive. People hedge. They defer to the most senior person in the room. They avoid mentioning anything that might create interpersonal tension. The anonymity removes that pressure in a measurable way. Studies on anonymous versus named feedback consistently show higher candor and more actionable detail when identities are withheld.
Facilitation is non-optional. A group given anonymous complaints without a structured process will either spiral into blame or sit in silence. A facilitator who knows how to cluster themes, ask clarifying questions without putting people on the spot, and redirect venting toward process improvement makes the difference between a two-hour gossip session and something that actually changes how the team operates. Action items must follow immediately. If the session produces observations but no concrete commitments, participants learn quickly that this is theater. I've seen teams run these repeatedly for months with zero behavioral change, and the cynicism that builds is worse than having no session at all. The rule I use is simple: every theme that surfaces gets a named owner and a date. No exceptions.
Get the Full Details
The Counter-Intuitive Part Most People Miss
Here is something that isn't in any of the promotional material: the most valuable output of this kind of session is often the things that don't get said out loud. When you collect anonymous input, you'll typically see a pattern where the bulk of written comments are operational friction — unclear ownership, redundant approval steps, communication bottlenecks. The dramatic or personal complaints are usually in the minority. Teams tend to underreport interpersonal conflict in anonymous formats because even anonymity doesn't fully override the discomfort of putting negative observations in writing. The absence of certain topics is itself data. Another thing beginners routinely botch: mixing session types destroys the psychological safety. I once observed a leader try to combine anonymous team dynamics input with a performance review conversation in the same meeting. Half the participants walked out convinced they'd been set up. The remaining submissions were sanitized to the point of uselessness. These are separate processes with different rules, different facilitators, and different follow-through. Don't conflate them.
When This Approach Fails Completely
I need to be clear about the limitations because people selling this model rarely discuss them. This approach breaks down in several specific scenarios: Very small teams (under five people). Anonymity loses meaning when everyone knows everyone's handwriting, writing style, and typical concerns. In a five-person team, anonymous feedback becomes guesswork for everyone involved, and the guessing game undermines trust more than honest direct conversation would. Teams with active psychological safety issues. If people already believe that speaking up leads to retaliation — even subtly — adding an anonymous layer won't fix that. It might temporarily surface more information, but the root problem remains and will resurface. The workaround in these cases is to address the safety issue first through one-on-one conversations and structural changes before attempting any group session.
Organizations that refuse to act on findings. This is the most common failure mode. I've worked with teams where the leadership collected anonymous feedback, nodded at it during the session, and then returned to exactly the same behaviors the next week. After the second or third time this happens, participation drops to near zero. The team learns the session is performative, and rebuilding that willingness takes significantly more effort than simply changing the underlying behavior in the first place.
A Practical Walkthrough
Here is a concrete version you can actually implement without buying anything: Send participants a brief prompt 24 hours before the session asking them to write down three things: one process that wastes their time, one communication pattern that causes problems, and one suggestion that would materially improve how the team works together. Collect responses through a tool that strips identifying information — Google Forms with anonymous submission, a shared document where names are removed, or physical cards collected in a box. During the session, cluster the responses by theme on a whiteboard or shared screen. Do not read them aloud with attribution. Group similar items. Ask the team to vote on the top three themes. For each theme, identify one specific change to test over the next two weeks. Assign an owner. Schedule a check-in.
This takes about 60 to 90 minutes for a team of 8 to 15 people. It costs nothing to run. The only real investment is the discipline to follow through on the action items, which is where most attempts fail.
The Alternatives Worth Considering
If your main goal is improving team dynamics and collaboration, there are established frameworks with far more research behind them that don't require rebranding basic practices. Psychological safety assessments based on Amy Edmondson's work give you a measurable baseline. Retrospective frameworks from agile methodology (like sprint retrospectives with rotating formats) produce similar anonymous-input benefits on a regular cadence without the ceremony. Team health checks from organizations like the Workfront Institute provide validated survey instruments that track collaboration quality over time. The Secret Sessions framing isn't wrong in its mechanics. It's just marketing dressing around practices that have been documented, studied, and refined for decades. The value isn't in the name. It's in doing the work consistently and acting on what you find.
