Workload Trends

Visualize how work is distributed across your team and over time. Spot overload, idle capacity, and bottlenecks before they become resignations or missed sprints.

Workload · Backend team · last 12 weeks

1 overloaded

• Maya
  Backend
  balanced
• Jordan
  Backend
  balanced
• Priya
  Frontend
  overloaded
• Sam
  Frontend
  light
• Alex
  Platform
  balanced

Per-member workload heatmap

Burnout signals before they hit

Sprint-over-sprint trend tracking

Slack alerts when someone is at risk

What we measure

Workload is more than open tickets

iftrue blends active assignments, in-flight PRs, review load, on-call rotations, and meeting density into a single workload score per engineer. Then tracks it sprint over sprint so you see drift, not just snapshots.

• Active work: Open tickets weighted by complexity, in-flight PRs, and ongoing investigations.
• Review load: PRs assigned for review, including the senior engineers everyone defaults to.
• Hidden load: On-call rotations, meeting density, and after-hours activity that never shows in a sprint board.

Workload composition · Priya

• Active tickets 35%
• PR review queue 28%
• On-call rotation 18%
• Meetings 14%

Total load: 95%
Sustained for: 4 weeks

Burnout signals

Leading indicators, not exit interviews

Burnout has leading indicators if you know where to look. iftrue watches them automatically and pings you in Slack the moment any threshold is crossed.

Sustained overload

Workload above 85% for 3+ consecutive weeks. The strongest single predictor of burnout.

After-hours creep

Commits and reviews happening regularly outside working hours. Occasional is fine. Chronic is a signal.

Review monopoly

One engineer reviewing more than 40% of team PRs. Bus factor risk and reviewer fatigue at once.

Meeting saturation

Meeting time exceeds 30% of working hours. Engineering output drops sharply past that line.

iftrueAPP 9:00 AM · DM to manager

Workload imbalance suggestion
Priya is at 95% load (4th straight week). Sam is at 28% with frontend capacity.

Suggested moves: PROJ-512 and PROJ-518 from Priya to Sam. Both are frontend tickets, both unassigned PRs.

Specific moves, not vague nudges

Generic "your team looks busy" alerts don't help. iftrue suggests concrete reassignments: which tickets to move, who to move them to, and why both engineers benefit. Approve the move and reassign in Jira without leaving Slack.

Who it's for

Built for engineering leaders

Engineering Managers

See workload balance across your team at a glance. Spot the engineer carrying twice the load before they burn out.

Tech Leads

Rebalance ticket assignments based on real workload data, not gut feel. Stop overloading your most senior people.

VPs of Engineering

Compare workload distribution across teams. Identify systemic capacity issues before they show up in attrition numbers.

See what your engineering org is missing.

30-minute walkthrough, tailored to your stack. No slides. Your team's data.