Emotional labor in software teams is the invisible work of managing feelings, yours or other people's, so the team keeps functioning. Nobody puts it on the roadmap and it never shows up in a velocity chart, yet in my view it is one of the most common hidden sources of fatigue in engineering teams. It tends to land on the same few people.
Sociologist Arlie Hochschild coined the term in 1983. In this article I separate the two kinds I find most useful to tell apart, explain what research says about their cost, show how to recognize an unfair share, and describe what team members and leaders can do to spread the load before it turns into burnout.
TABLE OF CONTENTS
What Is Emotional Labor in Software Teams?
Emotional labor is the effort of managing your emotions, or other people's, to fit what a role expects, even when that does not match how you feel. Sociologist Arlie Hochschild coined the term in 1983 after studying flight attendants. In engineering, it shows up as staying upbeat during a tense sprint, smoothing conflicts or absorbing client frustration.
Hochschild's original work focused on service jobs where employees were expected to grin and bear it for the sake of customers. Tech teams are not immune. Any time people cannot fully express what they feel, some emotional labor is happening. It often falls on the team lead, but any member of the team can end up carrying it.
Self-Focused vs Other-Focused Emotional Labor
I find it useful to split emotional labor into two kinds. Self-focused labor means regulating your own emotions to match the job. Other-focused labor means taking responsibility for the emotional climate of the team. The first is part of most jobs. The second is the one that quietly concentrates on a few people.
| Type | What It Looks Like | Example in a Software Team | Main Risk |
| Self-focused, surface acting | Showing an emotion you do not feel | Smiling in planning while you worry about a deadline | Strongly linked to impaired well-being in research |
| Self-focused, deep acting | Reframing your own feelings so the reaction is genuine | Convincing yourself a tough code review is a chance to learn | Weaker link to impaired well-being, still uses energy |
| Other-focused | Keeping the peace and managing how others react | Softening feedback, mediating conflict, absorbing client frustration | The load concentrates on the calm one or the peacemaker |
The split between self-focused and other-focused is my working framework, not a formal research taxonomy. Surface acting and deep acting, on the other hand, come directly from Hochschild's work. Both kinds consume mental energy. The difference is who pays for it.
In my view, emotional labor is sustainable only when three conditions hold:
- The effort is light. It does not take up a large part of anyone's day.
- It is shared fairly. No one or two people absorb it for everyone else.
- It is mostly self-focused. People manage their own reactions instead of the whole team's mood.
When the effort becomes intense, unevenly distributed and heavily other-focused, morale suffers. That is when I expect stress, fatigue, cognitive dissonance, lower self-confidence and eventually burnout.
What Does Research Say About the Cost of Emotional Labor?
The strongest evidence concerns surface acting. A meta-analysis of 95 studies found it strongly related to impaired well-being, with correlations between .39 and .48, while deep acting showed weak links. The World Health Organization defines burn-out as chronic workplace stress that has not been successfully managed.
That meta-analysis, by Hülsheger and Schewe, pooled 494 correlations. It also found that surface acting had a small negative relationship with performance, while deep acting was positively related to emotional performance and customer satisfaction. Emotional labor is not harmful in itself. The cost depends on the type and the load.
The WHO's ICD-11 definition describes three dimensions of burn-out: exhaustion, mental distance or cynicism toward the job, and reduced professional efficacy. Those match what I see described when someone has spent months holding a team together at their own expense.
A caution on the evidence: research on surface acting is much stronger than research on the peacemaker role inside teams. When I describe the cost of other-focused labor, I am extending that evidence with a reading of team dynamics, not quoting a study on it.
Safety matters here too. Google's Project Aristotle studied 180 teams, 115 of them engineering teams, and ranked psychological safety first among five dynamics of effective teams. Where people can say what they feel without fear, less of that feeling has to be hidden or absorbed by someone else.
How Do You Know You Carry an Unfair Share?
You probably carry an unfair share when you are the person others turn to by default to calm tension, fix moods or absorb frustration, and the rest of the team does little of that work. An unfair share means one or two people consistently manage the team's emotions while others contribute very little.
You might be doing more than your share if you:
- Mediate by default. You frequently resolve conflicts or soothe tensions.
- Edit yourself. You modulate your emotions to avoid rocking the boat.
- Track triggers. You remember everyone's sensitivities and adjust your behavior to protect others.
- Get asked to fix moods. Colleagues expect you to calm down upset teammates or repair situations.
- Feel pressure to stay positive. You believe you must be upbeat no matter what.
- Step in outside your role. You help even when it is not your responsibility, and you regularly give emotional support or advice.
- Let offenses slide. You ignore subtle slights to keep the peace.
- Shield the team from clients. You absorb client frustration so others do not have to.
When one person consistently takes on these responsibilities, it is exhausting for them. It also prevents the team from building resilience together.
How Can You Rebalance Emotional Labor?
Start by noticing and naming the work, then test what happens when you stop doing all of it. Bring the pattern to a retrospective, describe your own experience instead of managing the team's mood, and ask your lead to share the load. Awareness is the first step, and it is a practical one.
- Acknowledge it. Start noticing the moments when you take on emotional work.
- Get perspective. Talk with a coach or your team lead. Ask what would actually happen if you did not smooth things over. Sometimes the team needs to face a conflict to grow.
- Speak up in retrospectives. The Scrum Guide frames the retrospective as the moment to plan ways to improve quality and effectiveness. It is also a reasonable place to say how this invisible work is affecting you.
- Own your feelings. Practice saying: here is what I observed, and here is how it made me feel. This keeps you focused on your experience instead of controlling the team's mood.
- Ask for shared ownership. Suggest rotating who handles difficult conversations, so the work stops defaulting to one person.
What Should Team Leads and Managers Do Differently?
Leaders should make emotional work visible and shared. Create enough safety for people to voice frustration, joy or disagreement early, rotate roles such as facilitator and mediator, and notice who always absorbs tension. When conflict surfaces sooner, resentment has less time to build.
- Create safety. Make space for emotions as part of your culture. When people can express frustration or disagreement without fear, conflict gets resolved earlier.
- Rotate the peacemaker role. Do not let the same person facilitate every tense conversation.
- Notice the pattern. If one person is always the calm one, ask what they are carrying and what it costs them.
- Recognize the work. Name emotional labor in one-on-ones and performance conversations so it stops being invisible.
DORA's research points the same way: a high-trust, generative culture predicts software delivery performance, and its 2019 report adds that psychological safety predicts productivity. For related reading, see our posts on burnout prevention in software teams and engineering manager burnout.
Why Does This Matter for Distributed and Nearshore Teams?
Distributed teams have fewer informal moments to release tension, so emotional work can pile up silently. Cross-border teams also absorb client frustration across time zones and expectations. For CTOs and engineering leaders, I think the cost shows up as slower communication, uneven velocity and team leads who burn out first.
When you build or extend a distributed team, ask how emotional work is shared, not only how tickets are assigned. Dedicated teams that work inside your cadence need the same safety and fair distribution as an in-house squad, and the same goes for tech and software companies adding nearshore capacity. Our articles on distributed team trust and emotional intelligence in software engineering go deeper on the habits that make this work.
Frequently Asked Questions
How is emotional labor different from emotional intelligence?
Emotional intelligence is a skill: noticing and managing emotions, yours and other people's. Emotional labor is the work you do when a role expects you to manage emotions in a certain way. A person can be highly emotionally intelligent and still be overloaded if the team expects them to do all of that work alone.
Is emotional labor always harmful?
No. The cost depends on the type and the load. In the 95-study meta-analysis, surface acting showed strong links to impaired well-being, while deep acting showed weak ones. In my view, effort that is light, fairly shared and mostly self-focused is sustainable, and it is part of working with people.
What if I am the calm one and stepping back feels risky?
Change it gradually. Notice when you step in, ask yourself what would actually happen if you did not smooth things over, and talk with your lead or a coach. Sometimes the team needs to face a conflict to grow, and your pause is what makes room for someone else to step in.
Where can I raise this at work?
Retrospectives are a natural place, since the Scrum Guide frames them as the moment to plan ways to improve effectiveness. Describe what you observed and how it affected you, without blaming people. This works best when the team already has psychological safety, so leaders should build that first.
The Bottom Line
Emotional labor in software teams is not a flaw to eliminate. It is part of working with people. When it is heavy, uneven and invisible, it quietly drains the team. When it is named and shared, it becomes a skill the whole team builds, and that strengthens the team.
If you lead a distributed team and want to talk through how to share this load, I would be glad to continue the conversation. You can get in touch with us at any time.
References and Further Reading
- University of California Press. Arlie Russell Hochschild, The Managed Heart: Commercialization of Human Feeling (1983). https://www.ucpress.edu/books/the-managed-heart/paper
- PubMed. Hülsheger and Schewe (2011), On the costs and benefits of emotional labor: a meta-analysis of three decades of research. https://pubmed.ncbi.nlm.nih.gov/21728441/
- World Health Organization. Burn-out an occupational phenomenon: International Classification of Diseases. https://www.who.int/news-room/detail/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases
- Google re:Work. Guide: Understand team effectiveness (Project Aristotle, psychological safety). https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness
- SAGE Journals. Edmondson (1999), Psychological safety and learning behavior in work teams. https://journals.sagepub.com/doi/10.2307/2666999
- Scrum Guides. The Scrum Guide: purpose of the Sprint Retrospective. https://scrumguides.org/scrum-guide.html
- DORA. Capabilities: generative organizational culture. https://dora.dev/capabilities/generative-organizational-culture/
- Atlassian. Team Playbook: how to run a retrospective. https://www.atlassian.com/team-playbook/plays/retrospective