Skip to main content
Table of Contents

Monitor Team Workload and Burnout

Avoid burnout and cognitive overload by monitoring and balancing your team's workload.

Steven Silverstone
Updated by Steven Silverstone
Table of Contents

LinearB helps you identify workload patterns that may indicate that a team member is overloaded or underutilized. Workload alerts appear in the team dashboard so you can review potential issues without having to monitor individual activity manually.

Note: Workload alerts indicate activity patterns that may require attention. They do not necessarily mean that a team member is experiencing burnout or cognitive overload.

Burnout Alert

A burnout alert identifies team members who have been active on 90% of the days in the current sprint. LinearB begins monitoring for this condition after the first 6 days of the sprint.

Sustained activity across most days of a sprint can indicate that a team member has had limited opportunity to step away from active development work. Use the alert as a signal to review their workload and determine whether any changes are needed.

When the alert appears

  • The current sprint has been running for at least 6 days.
  • The team member has worked on at least 90% of the days in the sprint.

Cognitive Overload Alert

A cognitive overload alert identifies team members with more than 6 active branches.

A high number of active branches can indicate that a developer is working across several tasks or priorities at the same time. This can increase context switching and make it more difficult to maintain focus.

When the alert appears

  • The team member has more than 6 active branches.

Underloaded Team Members

LinearB also identifies team members with 0 active tasks. These users are highlighted in yellow in the team dashboard.

Use this indicator alongside the overload alerts to identify potential workload imbalances across the team.

Review Workload Alerts

Review burnout, cognitive overload, and underload indicators from your team dashboard.

These alerts are intended as signals for further review. Consider the developer's current responsibilities, type of work, sprint activity, and other relevant context before making workload changes.

Learn More

For more information about monitoring development team health, see Dev Team Health: Vital Signs To Watch .

You can also watch 3 Data Driven Burnout Indicators .

How did we do?

Balance & Activity Metrics

Contact