Build a fair resource allocation plan for a small team
Splitting work evenly by headcount and splitting it by what each person can actually absorb are different plans.
- Use it for
- Anyone allocating a project's work across a small team who wants to avoid an accidental bottleneck.
Splitting a project's work evenly across a small team by headcount feels fair but often isn't realistic — people have different skills suited to different pieces, and different existing workloads, so an even split can accidentally overload one person while leaving another underused. A real allocation plan accounts for actual fit and capacity, not just even division.
When not to use this
For a project where every task genuinely requires the same skill and everyone has identical availability, an even split is already the right answer — this is for the more common case where skills and capacity actually vary.
Did this work?
The plan accounts for each person's actual skills and current load, not just an even split of tasks by headcount.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.