liveBook · Manning

Employee morale

As explained in Think Like a Software Engineering Manager

Team morale is the collective confidence, enthusiasm, and emotional state of people in a team or organization.

A team may be delivering work while its members are growing quieter, missing meetings, or worrying about who will leave next. Employee morale is the team’s shared confidence, enthusiasm, and emotional state. For an engineering manager, it is a measure of team health alongside business results, development velocity, and operational performance—not a substitute for them. High morale supports collaboration, open communication, and engagement; low morale can undermine all three. section 1.2 section 1.2.3 section 3.2.2

Check for patterns rather than relying on a single impression:

  • Observe participation and communication in meetings and everyday interactions. Repeated absences, disengagement, or reduced communication may signal trouble. section 1.2.3 section 3.2.2
  • Make room for candid one-on-ones and informal conversations; use periodic team surveys to gather feedback beyond what people say publicly. section 1.2.3
  • Watch for stress, burnout, turnover, declining productivity, and reduced accountability. Discuss what is driving the pattern before choosing a response. section 3.2.2

Respond to the cause, not just the mood:

  • Discuss concerns openly, help balance workloads or offer flexible schedules when stress is involved, and provide challenging work when someone feels underused. section 3.2.2
  • Recognize contributions, create opportunities to develop skills, and support career progression. Team activities can help people connect, but they are only one possible response. section 1.2.3 section 3.2.2
  • Examine leadership decisions too. Competition and rewards may improve business results while discouraging openness; restrictive rules without feedback can damage trust. section 1.3.4 section 1.3.1

When a decision creates stress

A manager introduced core working hours to improve coordination, then heard in one-on-ones that the rule conflicted with personal obligations and reduced flexibility. Rather than defend the decision, the manager brought the concern to the team and treated the feedback as a reason to adjust course. Ask: which of your well-meant practices might be making someone’s work harder? section 3.3.1

Departures can also unsettle those who remain. Explain the departure process and plans for knowledge transfer, reprioritizing tasks, and hiring so people are not left guessing about their workload or future. Morale is something to revisit as circumstances change, not a score to collect once and forget. section 8.3.1 section 1.2.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides warning signs, monitoring methods, and practical responses, but no fixed morale-scoring formula.
Examples
Uses core working hours that caused stress and a departure that left remaining employees uncertain.
What it assumes
Assumes responsibility for an engineering team but explains morale through observable behavior and conversations rather than a formal measurement system.
What you can do after
Practice/perform it by checking engagement, discussing concerns, and adjusting workload, recognition, or communication.
How it connects
Connects morale to developer velocity, attrition, trust, and leadership styles.

Also explained in

Compare how 3 books explain employee morale →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.