Build the 70-20-10 Plan
When To Use
The programme is all classroom and nothing happens back at work. People leave the room with a folder, and the next week holds the same tasks, the same meetings and nobody to try the new thing with. Use this for a role or a programme. It answers: what will people do at work, and with whom, so that the course is one part of the learning and not all of it?
When Not To Use
If you only need the manager's conversations around one programme, run Brief the Managers. If the formal modules are not yet in order, run Map the Curriculum first. For a new hire's first weeks, use Plan the Onboarding.
Inputs
- The role or programme and the capabilities it should build, each with the goal or action it serves (from your action map, if you have one)
- The real work of the role over the coming period: projects, recurring tasks, problems that land on the team
- The formal pieces that exist or are planned, and who could coach, mentor or pair up, by role
If you have none of this, I start from the role and one capability and mark the output as a first draft.
Approach
70-20-10, from its originators' public page: development comes mostly from challenging assignments and developmental relationships, with coursework as one part. Its originators call it a guideline, not a formula. So the judgement is in choosing the experience that teaches this capability, and no ratio is worth defending. The failure this prevents: a slide that says most learning happens on the job, with nothing behind it, so "on the job" quietly means "work it out alone" and the course is still the only thing anyone can point to.
Workflow
- Ask up to three questions: which capability matters most for this role, what real work in the coming [period] could stretch people on it, and who already does it well, by role.
- Write one line per capability, tied to the goal or action it serves. A capability tied to nothing is parked with a note, never planned.
- Match an assignment to each capability: real work that forces it, such as leading a handover or taking a first difficult call. Different experiences teach different things, and "shadowing" alone teaches watching. Each assignment has an owner, a support person and a check-in date, and it is offered to people, never assigned as a test.
- Tie a relationship to each assignment: coaching, mentoring or peer learning. Say who meets whom by role, how often, and the first topic. "Find a mentor" is a wish.
- Add only the formal pieces an assignment needs people to know or practise first, and place each just before the assignment that uses it. A course that serves no assignment comes off the plan.
- Check the mix against the work, never against a ratio: every capability has at least one assignment and one relationship. No percentage appears anywhere. If the role truly needs more coursework, the plan says so and says why.
- List what the plan needs from others (time released, access, a coach's hours) so the sponsor sees the cost before approving.
Output Format
# 70-20-10 Plan
Role or programme: [role / programme] | Period: [start to end] | Plan owner: [role]
## The plan, one row per capability
| Capability, and the goal or action it serves | Assignment (real work) | Relationship (who meets whom, how often, first topic) | Formal piece needed first |
|---|---|---|---|
| [capability: goal] | [assignment] | [coaching / mentoring / peer: role and role, cadence, topic] | [module, or "none"] |
## Owners and check-ins
| Assignment | Owner | Support person | Check-in date | What the check-in looks at |
|---|---|---|---|---|
| [assignment] | [role] | [role] | [date] | [what was tried, what is needed next] |
## Parked
| Capability or course | Why it is parked |
|---|---|
| [item] | [tied to no goal / serves no assignment] |
## What this needs from others
[Time released, access, coaching hours, each with who must agree]
## Decision
[Sponsor name] and [L&D lead name] approve the assignments, the support people and the time they need by [date].
Done When
- Every capability has at least one assignment and one relationship
- Every assignment has an owner, a support person and a check-in date
- Every formal piece sits just before the assignment that uses it
- No percentage or ratio target appears anywhere in the plan
Quality Bar
- Assignments are real work in the role, never "exposure" or "shadowing" on its own
- Relationships name roles, a cadence and a first topic
- The formal list is cut to what the assignments need, not the full catalogue
- Check-ins ask what was tried and what is needed next; they are support, not inspection
- The plan is built for a role; assignments are offered, nothing records who did well, and the sponsor and the L&D lead approve it.
Next
Run ldg-space-the-practice (Space the Practice) to keep the formal pieces from fading.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: ldg-build-the-70-20-10-plan3description: Builds a plan that carries learning into the work of a role, with real assignments matched to each capability, coaching and peer learning tied to those assignments, only the formal pieces the assignments need, and an owner and a check-in date for each, with no percentage targets. Use for "run ldg-build-the-70-20-10-plan", "70 20 10 model", "70-20-10 learning", "learning in the flow of work", "on-the-job learning plan", "development plan for a role", "stretch assignments for a role", "nothing happens after the course", part of The Complete Claude Guide for L&D Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/ldg-build-the-70-20-10-plan6---78# Build the 70-20-10 Plan910## When To Use11The programme is all classroom and nothing happens back at work. People leave the room with a folder, and the next week holds the same tasks, the same meetings and nobody to try the new thing with. Use this for a role or a programme. It answers: what will people do at work, and with whom, so that the course is one part of the learning and not all of it?1213## When Not To Use14If you only need the manager's conversations around one programme, run Brief the Managers. If the formal modules are not yet in order, run Map the Curriculum first. For a new hire's first weeks, use Plan the Onboarding.1516## Inputs17- The role or programme and the capabilities it should build, each with the goal or action it serves (from your action map, if you have one)18- The real work of the role over the coming period: projects, recurring tasks, problems that land on the team19- The formal pieces that exist or are planned, and who could coach, mentor or pair up, by role20If you have none of this, I start from the role and one capability and mark the output as a first draft.2122## Approach2370-20-10, from its originators' public page: development comes mostly from challenging assignments and developmental relationships, with coursework as one part. Its originators call it a guideline, not a formula. So the judgement is in choosing the experience that teaches this capability, and no ratio is worth defending. The failure this prevents: a slide that says most learning happens on the job, with nothing behind it, so "on the job" quietly means "work it out alone" and the course is still the only thing anyone can point to.2425## Workflow261. Ask up to three questions: which capability matters most for this role, what real work in the coming [period] could stretch people on it, and who already does it well, by role.272. Write one line per capability, tied to the goal or action it serves. A capability tied to nothing is parked with a note, never planned.283. Match an assignment to each capability: real work that forces it, such as leading a handover or taking a first difficult call. Different experiences teach different things, and "shadowing" alone teaches watching. Each assignment has an owner, a support person and a check-in date, and it is offered to people, never assigned as a test.294. Tie a relationship to each assignment: coaching, mentoring or peer learning. Say who meets whom by role, how often, and the first topic. "Find a mentor" is a wish.305. Add only the formal pieces an assignment needs people to know or practise first, and place each just before the assignment that uses it. A course that serves no assignment comes off the plan.316. Check the mix against the work, never against a ratio: every capability has at least one assignment and one relationship. No percentage appears anywhere. If the role truly needs more coursework, the plan says so and says why.327. List what the plan needs from others (time released, access, a coach's hours) so the sponsor sees the cost before approving.3334## Output Format35```markdown36# 70-20-10 Plan37Role or programme: [role / programme] | Period: [start to end] | Plan owner: [role]38## The plan, one row per capability39| Capability, and the goal or action it serves | Assignment (real work) | Relationship (who meets whom, how often, first topic) | Formal piece needed first |40|---|---|---|---|41| [capability: goal] | [assignment] | [coaching / mentoring / peer: role and role, cadence, topic] | [module, or "none"] |42## Owners and check-ins43| Assignment | Owner | Support person | Check-in date | What the check-in looks at |44|---|---|---|---|---|45| [assignment] | [role] | [role] | [date] | [what was tried, what is needed next] |46## Parked47| Capability or course | Why it is parked |48|---|---|49| [item] | [tied to no goal / serves no assignment] |50## What this needs from others51[Time released, access, coaching hours, each with who must agree]52## Decision53[Sponsor name] and [L&D lead name] approve the assignments, the support people and the time they need by [date].54```5556## Done When57- Every capability has at least one assignment and one relationship58- Every assignment has an owner, a support person and a check-in date59- Every formal piece sits just before the assignment that uses it60- No percentage or ratio target appears anywhere in the plan6162## Quality Bar63- Assignments are real work in the role, never "exposure" or "shadowing" on its own64- Relationships name roles, a cadence and a first topic65- The formal list is cut to what the assignments need, not the full catalogue66- Check-ins ask what was tried and what is needed next; they are support, not inspection67- The plan is built for a role; assignments are offered, nothing records who did well, and the sponsor and the L&D lead approve it.6869## Next70Run ldg-space-the-practice (Space the Practice) to keep the formal pieces from fading.7172## About the makers7374This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).