liveBook · Manning

Work-life balance

As explained in Think Like a Software Engineering Manager

Work-life balance is the degree to which work demands are compatible with a person’s personal life, health, and nonwork responsibilities.

A team can meet a tight deadline and still be working in a way it cannot sustain. Work-life balance means making work demands compatible with people’s personal time and well-being. For an engineering manager, it is part of setting realistic expectations—not a reason to ignore business needs, but a reason to challenge excessive workload demands. section 2.5.6 section 3.2.8

Make balance visible in everyday decisions:

  • Set achievable goals and deadlines, distribute work fairly, and check capacity during agile ceremonies. Address signs of strain rather than treating overtime as the default. section 3.2.8
  • Ask what is causing stress. Team meetings and check-ins can surface concerns; workload changes, flexible schedules, and process improvements may help. section 3.2.2
  • Respect time away. Avoid contacting people on vacation, give them space during illness or bereavement, and model the boundaries you want the team to keep. section 3.2.8
  • Watch for demands that make a role hard to sustain, including long hours, extensive commutes, meeting fatigue, and expectations of constant online presence. Some fixes are within a manager’s reach; others need higher-level action. section 8.2.1

When a busy team starts to struggle

On a high-performing team with tight deadlines, missed deadlines, lower productivity, and declining morale may look like ordinary workload fluctuations. Persistent signs, paired with conversations about stress and exhaustion, call for a closer look at burnout and the team’s workload. section 3.2.8

Small signals matter too. Sending late-night emails can imply that others should be available then. Use Send Later, or mark a message for reading the next day. Ask the team whether the boundaries you intend are the ones they experience. section 11.4.3 section 3.3.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Gives practical actions for goals, capacity, communication, and boundaries rather than a formal measure of balance.
Examples
Uses a stressed team facing tight deadlines and workplace signals such as late-night emails and meeting fatigue.
What it assumes
Assumes responsibility for a team’s workload and communication; states the recommended actions without requiring a formal model.
What you can do after
Practice/perform it by checking workload, inviting concerns, protecting time off, and modeling reasonable communication boundaries.
How it connects
Connects work-life balance to burnout, employee morale, attrition, capacity planning, and expectation management.

Also explained in

Compare how 2 books explain work-life balance →

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.