Back to playbooks

Learning Work Allocation

Use this playbook when a team is adopting AI in day-to-day work and needs to protect the reps juniors need to build judgment.

What problem this playbook solves

The first visible AI gain often comes from taking away repetitive junior tasks. That can be useful. It can also destroy the training path if those tasks were where people learned to notice patterns, make tradeoffs, and catch mistakes. The same AI assist can help an experienced practitioner move faster and prevent a newer practitioner from ever building the underlying skill. That is why access and workflow should vary by demonstrated competence, not only by role.

Failure pattern to prevent

• junior staff become prompt operators instead of practitioners
• baseline independent skill never forms
• seniors inherit review-only work with no protected time
• the team confuses “output still ships” with “the system is still learning”

Minimum floor

Before shifting work to AI, answer:

1. What learning function does this task currently serve?
2. What replaces that learning function if the task is automated?
3. Who reviews the AI-assisted output, and with how much protected time?
4. What work must still be done first without AI so independent judgment can form?

If those answers are vague, the work should not be fully automated yet.

Operating steps

1. Zone the work

For each recurring task, classify it as:

• learn first without AI
• learn with AI after baseline competence
• AI-assisted with human review
• AI-suitable only for experienced staff

2. Protect learning work

• reserve a defined share of junior-access tasks for first-pass human work
• require manual baselines on core tasks before heavy AI assistance
• keep pair-review and shadow-review rotations active

3. Scope access by competence

• do not give the same AI permissions to every level by default
• increase automation scope with demonstrated judgment, not just tenure

4. Protect mentorship as capacity

• schedule mentorship time explicitly
• treat review and teaching load as part of staffing, not invisible overhead

5. Run manual flight checks

• require periodic unassisted or minimally assisted work samples
• compare assisted output against independent baseline performance

Metrics and tripwires

Track:

• share of junior work completed first without AI
• mentorship hours per junior
• completion rate on baseline manual tasks
• reviewer confidence in junior independent skill
• defect or rework rates tied to AI-assisted junior output

Tripwires:

• juniors cannot complete core tasks without AI support
• teams cannot name where judgment formation now happens
• AI-assisted volume rises while mentorship time falls

Owner

• line managers
• team leads
• learning and development partners where present

Bridge language

“Protect the reps, not just the output.”

“If AI saves time but nobody is learning the craft, the team is spending down its future.”

Back to playbooks