Poor Resource Allocation—When Star Performers Burn Out

Sarah is on three critical projects—60 hours/week. Mike has capacity but is labeled "less experienced"—35 hours, routine tasks. Sarah takes sick leave—two projects standstill. The manager: "I did not know Sarah was this loaded."

Poor resource allocation = decisions based on reputation, not data. Result: burnout, bus factor of one, underutilized talent.

Scaling organizations feel this sooner: headcount +50% but throughput +10%—because the same reliable people get overloaded again and new hires need long onboarding. Data-driven allocation supports the right call before reorg or hiring freeze.

Signs

Sign	Meaning
Same two people always on critical work	Concentration risk
Estimates without "who is free?"	Fantasy planning
Cross-project conflict invisible	One person, two sprint commitments
Hiring lag—overload visible months late	No leading indicator

Cost

Star performer turnover
Quality drop under overload
Slow projects despite "busy team"
Unfair perception—"Mike is lazy" vs "Mike is under-assigned"

Five Steps for Fair, Effective Allocation

1. Capacity baseline per person

Available hours/week minus meetings, PTO, on-call. Not 40h fantasy—24–28h focused is realistic.

2. workload_heatmap before assign

Before assigning new work: check heatmap—who is red, who is green. Rule: red = no new critical until relief.

3. Skill vs availability—two axes

Sarah is skilled but red—pair with Mike or defer. Skill matrix in wiki/team profile helps.

4. Portfolio-level allocation

Single-project PM sees only their world—PMO portfolio: same person on four red projects. portfolio_overview shows conflict.

5. Rebalance at sprint boundary

Planning: "Sarah at 140%—move task B to Mike or hire contractor." Conscious trade-off.

Example: Invisible Portfolio Conflict

Alex: senior dev—Project A (critical release), Project B (POC), Project C (support escalation). Each PM thinks Alex is "50%"—total 150%.

Sprint 3: A slips—Alex on B POC. Sprint 4: C production fire—A slips again. PM A: "Alex is unreliable." Reality: allocation invisible.

Fix with workload_heatmap + portfolio:

Heatmap: Alex 145%—red three weeks
portfolio_overview: same person on three critical paths
Rebalance: B POC → junior pair; C support → rotation schedule
simulate_scenario add_people: hire vs delay B

Six sprints later: Alex 85%, A on time. Data-driven rebalance—not hero narrative.

Skill Development vs Overload

Mike "under-utilized"—opportunity: pair with Sarah on knowledge transfer, not only routine tasks. Allocation is not just load balance—growth path matters. wiki + goals track skill growth alongside capacity.

Leading Indicators Before Quit

Sustained red workload_heatmap + overtime time logs + missed PTO = conversation before resignation. Reactive HR after quit costs more than proactive rebalance.

How WKFGo Supports Resource Allocation

workload_heatmap: Visual capacity across people/projects
Time tracking / assignments: Actual load from user-task data
Portfolio overview: Cross-project who-on-what
Teams: Membership and role clarity
Reports: get_user_performance—overload patterns
simulate_scenario add_people: Forecast before hire

WKFGo shows the picture—manager action to reassign, hire, or cut scope is still required.

Pre-Assign Allocation Checklist

workload_heatmap checked—assignee not red
Portfolio—same person not on 3+ critical paths
Capacity baseline (realistic hours) considered
Skill match or pair plan for growth
Rebalance in planning if overload
simulate_scenario if hire/defer choice

Sprint planning allocation five-minute gate

Before any new assignment in planning, run this gate—takes five minutes, prevents burnout weeks:

Open workload_heatmap for the proposed assignee—is she red (>100%) for the next two weeks?
Check portfolio_overview—same person on how many critical paths across projects?
If red: move task, pair with junior, defer, or trigger simulate_scenario add_people—document trade-off.

Subtract realistic capacity: 40h/week minus meetings, PTO from calendar events, on-call—often 24–28h focused. Sustainable target is 70–80% utilization, not 100%. Making the heatmap part of every planning agenda beats quarterly reorg fire drills after a star performer quits.

Document the trade-off in the decision log when you defer—teams accept delay with visibility, not silence. Pair under-loaded teammates with seniors for knowledge transfer, not only routine tasks.

Sprint planning allocation gate

Before any new assignment: open workload_heatmap for the assignee—is she red for the next two weeks? Check portfolio_overview for cross-project critical paths. If red, defer, pair, or run simulate_scenario add_people and document the trade-off in the decision log. Sustainable target is 70–80% utilization, not 100%.

Frequently Asked Questions

Does heatmap replace 1:1 conversation?

No—it complements; conversation with data beats conversation without.

Contractor vs internal redistribute?

simulate_scenario both—compare cost and delay.

Harder for remote/async teams?

Yes—time tracking and explicit availability in calendar events help.

Is 100% utilization the goal?

No—buffer for interrupts and learning; 70–80% is sustainable.

Improve allocation with capacity baselines, pre-assign workload_heatmap checks, and portfolio conflict review—save star performers from "always available."