How do you divide work across the team so it both fits people's skills and helps them grow?

Question

Accepted Answer

Assigning work has two goals that pull against each other: **ship efficiently** and **grow people**. Always optimizing for throughput means your strongest engineer does everything important and nobody else levels up. Always optimizing for growth slows delivery. A tech lead deliberately balances the two, task by task.

## How I assign work

- **Match the task to current level, plus a stretch.** Give people work they can mostly do, with one new, slightly uncomfortable element. That's where learning happens without drowning.
- **Pair junior with senior.** On a meaty task, pairing spreads context and grows the junior while the senior's review keeps quality up.
- **Rotate ownership.** Don't let one person become the permanent owner of a critical area. Rotation kills bus-factor risk and broadens the team.
- **Give stretch tasks with support, not a cliff.** A stretch assignment needs a safety net: a clear go-to person, checkpoints, and explicit permission to ask for help.
- **Balance team throughput against individual growth.** Under a hard deadline, lean toward fit; in calmer periods, invest more in stretch and rotation.
- **Make context and expectations explicit.** Why this matters, what "done" looks like, and how much autonomy they have. Ambiguity hurts juniors most.

## Fit vs. stretch

| Lean toward fit when | Lean toward stretch when |
| --- | --- |
| Tight deadline or high risk | There's slack to absorb learning |
| Production-critical, low tolerance | Failure is recoverable |
| Person already stretched thin | Person is ready for the next level |

## Why it matters

A team is a portfolio, not a single resource. If you only ever assign for short-term efficiency, you build a brittle team that can't scale beyond its few experts and stops growing. Thoughtful assignment is one of the highest-leverage things a tech lead does: it compounds into a stronger, more resilient team over time, which ships more than any single heroic engineer ever could.

Lean toward fit when	Lean toward stretch when
Tight deadline or high risk	There's slack to absorb learning
Production-critical, low tolerance	Failure is recoverable
Person already stretched thin	Person is ready for the next level