The Practice Of Gratitude Circles In Workplaces

There is a specific kind of discomfort that shows up in high-performance professional environments when anyone suggests something that resembles emotional expression. It's not contempt. It's more like... bracing. Like everyone is waiting for it to be awkward and preparing to protect themselves from that awkwardness.

That bracing is useful information. It tells you that the norm of the environment is emotional concealment. That the unspoken rule is: care about the work, keep the personal dimension under wraps. And the reason that norm exists is usually historical — at some point, displaying emotion in this environment got someone punished or embarrassed, and the group adapted by collectively deciding not to go there.

The problem is that the same concealment that protects people from vulnerability also prevents the kind of trust that enables high performance. Trust is not built through process. It is built through moments where a person reveals something real and the group responds without harm. Gratitude circles, done right, are an engineered version of that moment. They create a low-stakes context for people to be briefly authentic with each other in a work setting.

The discomfort doesn't mean you shouldn't do it. The discomfort is the signal that it's actually doing something.

Gratitude as an internal experience is well-studied. Robert Emmons and Michael McCullough's foundational research from 2003 showed that people who kept weekly gratitude journals reported higher levels of well-being, more optimism, fewer physical complaints, and more time spent exercising than control groups. That research spawned an entire industry of gratitude apps, journals, and interventions.

But here's what that research doesn't capture: what happens when gratitude moves from internal to expressed — and from expressed privately to expressed publicly.

The neuroscience of public recognition activates the reward system differently than private experience does. Specifically:

When you are publicly recognized, your brain releases dopamine (the reward signal) and oxytocin (associated with social bonding and trust). But unlike the dopamine hit from a private achievement or even a private compliment, public recognition also activates the social brain network — the same systems involved in processing our place in a group, our status, our belonging. Recognition in front of others signals something that private recognition can't: you matter here, in this group, in the eyes of these people.

This matters because humans evolved as deeply social animals in small groups where status and belonging were survival issues. The feeling of being recognized by the group is not a nice-to-have. It maps onto systems that were originally tracking life-and-death information. Which is part of why public recognition lands so much harder than private recognition — and why its absence also lands hard, even in people who say they don't care about recognition.

On the giving side, expressing gratitude activates the medial prefrontal cortex, an area associated with mentalizing — thinking about other people's inner states. The act of articulating what you appreciate about someone requires you to have modeled their inner experience. That exercise of perspective-taking has downstream effects on empathy and on the quality of the relationship going forward.

Christina Karns at the University of Oregon has shown that when people choose to give to others (including giving appreciation), the neural reward signal is stronger than when they receive something. This is the "helper's high" in neural terms — and it applies to expressed gratitude. The person doing the expressing is also getting something from it, which means the practice is self-reinforcing once it's established.

Amy Edmondson at Harvard Business School coined the term "psychological safety" in a 1999 study of medical teams, and has spent the decades since documenting what it is and how it gets built. Psychological safety is team members' shared belief that the team is safe for interpersonal risk-taking. It's not about being comfortable or happy. It's about whether people feel they can speak up, admit errors, disagree with the boss, and ask for help — without being punished.

Edmondson's research and the subsequent body of work (including Google's Project Aristotle, which found psychological safety to be the single most predictive factor of team performance across 180 Google teams) consistently identifies the same mechanisms: people need evidence that being real in front of this group is safe. That evidence comes from accumulated experience, not from a policy.

Gratitude circles contribute to psychological safety through three mechanisms:

First, they normalize the expression of interpersonal recognition. When a team routinely names what they appreciate in each other, they're practicing a form of social acknowledgment that generalizes. The team that can say "I appreciate how you handled that" can also say "I need help with this" and "I got that wrong."

Second, they surface invisible contributions. One of the most corrosive dynamics in teams is the invisibility of support work — the coordination, the knowledge-sharing, the emotional labor that holds the operation together but never shows up in metrics. Gratitude circles make this work visible. When it becomes visible, people who do it feel less taken for granted, and people who benefit from it become more conscious of it.

Third, they shift the implicit narrative about what the group values. In every team, there's an implicit story about what gets rewarded. If that story is only about individual heroics and deliverables, then anything interpersonal — helping a colleague, covering for someone who's struggling, spending time on knowledge transfer — gets quietly depreciated. Gratitude circles change what gets named and therefore change what the group understands to be valued.

Gallup's research on employee engagement has consistently found that "in the last seven days, I have received recognition or praise for doing good work" is one of the twelve items most predictive of employee retention, productivity, and customer satisfaction. This item sits alongside things like having a good manager and having the opportunity to do what you do best. Not at the bottom of the list. Near the top.

The Society for Human Resource Management has found that lack of recognition is consistently in the top three reasons employees voluntarily leave their jobs. Not pay. Not workload. Not even bad managers in isolation — but the specific experience of working hard and not being seen for it.

A 2019 study published in the Journal of Applied Behavioral Science found that teams who participated in structured peer recognition practices showed a 26% reduction in voluntary turnover over a 12-month period compared to matched control teams. The practice in that study was not elaborate — a simple end-of-week five-minute peer recognition segment in team meetings.

What's notable here is the mechanism. Gratitude circles don't retain people by making the work more interesting or the pay higher. They retain people by making the experience of the work more relationally meaningful. People don't just want to do good work. They want to know that someone noticed.

The difference between a gratitude circle that changes the culture and one that becomes a bureaucratic ritual people dread is almost entirely in the execution. Here's what works and what doesn't:

What kills it:

Mandatory specific formats. "Everyone must say something about someone in a different department" turns the exercise into a compliance task. The minute it's performative compliance, it loses the signal that makes it matter.

Vague appreciation. "I just want to say I appreciate everyone" is the social equivalent of a form letter. It tells the room that you went through the motions. Generic appreciation doesn't build trust. It makes the exercise feel hollow, and hollowness is worse than nothing because it inoculates the group against the real thing.

Inconsistency. Doing this once in a team offsite and never again is decoration. The practice works because it builds a habit and a norm over time. Occasional gratitude is nice. Consistent gratitude changes culture.

Leaders who don't participate. If the manager runs the circle but never contributes to it, the implicit message is that this is for the team but not for them. Leaders who genuinely participate — who name specific things they appreciated in specific people — model that the practice is real. Leaders who abstain communicate that it's a people-management tool they're operating, not a cultural practice they believe in.

What works:

Start with yourself as leader. The first time you run this, you go first. Name something specific you appreciated in a team member in the past week. Not their general excellence. One specific thing. "I want to name that Tomás stayed an extra hour on Wednesday when the system went down, without being asked, and walked through the issue with the client himself. That saved the account." Then invite others.

Specificity as the standard. The first few times you run this, gently encourage specificity when you hear generality. "Can you say more about what that looked like?" That question alone moves people from polite vagueness to genuine attention. Over time, the group internalizes that the norm is specificity.

Keep it short and recurrent. Ten to fifteen minutes, embedded in an existing meeting, weekly or bi-weekly. The shortness keeps it from becoming burdensome. The recurrence builds the habit and allows the cumulative effect to develop.

Make it optional within the structure. The meeting includes the practice. Within it, no one is required to speak. Creating space is different from requiring performance. Over time, as trust builds and the norm becomes established, more people will participate voluntarily.

Let it get awkward sometimes. Silence after someone says something meaningful is not a problem. Don't rush to fill it. Let it land. Some of the most powerful moments in gratitude circles are when the room goes quiet because what was just said was real.

The facilitation move that changes everything:

After someone expresses gratitude, pause and turn to the recipient. "How does it feel to hear that?" You don't always need to do this. But sometimes, a few times a year, asking that question makes the circle three-dimensional. The recipient usually hasn't thought about how it feels — they've been planning what to say back. Asking the question invites genuine real-time response. And hearing a colleague say "it means a lot because I wasn't sure anyone noticed" is the kind of moment that changes how a team understands itself.

A team of twelve people, doing fifteen minutes of genuine appreciation for each other twice a month, accumulates over a year into something qualitatively different from a team that doesn't. The individual moments are small. The cumulative effect is a group of people who actually know each other a little — who have stated out loud what they value in each other, who have been seen for real contributions rather than only metric-tracked deliverables.

What happens in those groups when hard things come up — budget cuts, missed targets, conflict — is different. Not because they've been made optimistic. But because they've built a relational substrate that can take weight. A network of genuine acknowledgment is load-bearing in ways that a network of professional politeness is not.

Now scale that. Imagine that as the operational norm in hospitals, where staff who feel seen and valued make fewer errors and have better patient outcomes. In schools, where teachers who receive genuine recognition from colleagues and parents stay in the profession rather than burning out. In governments, where decision-makers who are embedded in cultures of genuine acknowledgment make different choices than those surrounded by performance and political positioning.

The problem the world has — the violence, the extraction, the collective failure to care for the people at the margins — is not primarily a problem of resources. It is a problem of disconnection. Of people who have never experienced being genuinely seen deciding, consciously or not, that others don't need to be seen either.

Gratitude circles are a small practice. But small practices are how culture moves. And culture is what determines everything.

You don't need buy-in from the whole organization. You need a team meeting that's already happening and the willingness to try something that might be awkward for two minutes.

At the start of your next team meeting, say: "Before we get into the agenda, I want to try something. I'm going to name one thing I genuinely appreciated in someone on this team in the past week. Then I'll invite anyone who wants to do the same." Then do it. Be specific. Be brief. Invite.

Some people will do it right away. Some won't. That's fine. Do it again next meeting. And the one after. Pay attention to what starts to shift.

The test of whether it's working is not whether everyone smiles. The test is whether, over time, people are more willing to say hard things in the room. Gratitude and honesty are connected. The capacity to say "I appreciate what you did" and the capacity to say "I think this decision is a mistake" come from the same root — the belief that being honest in front of these people is safe.

You build the second by practicing the first.