Brief the Managers
When To Use
Learners go back to a manager who never asks what they learned. Most managers are not against the programme; nobody told them what their part was, or made it small enough to fit a week that is already full. Use this for one programme, before it runs. It answers: what does the manager say, ask and remove, before and after, so people get to use it?
When Not To Use
If you need the whole mix of assignments, coaching and courses for a role, run Build the 70-20-10 Plan. If you want to know weeks later whether the group used it, run Check Use on the Job: that reads across everyone for the sponsor, while the log here is what each manager notes as they go.
Inputs
- The programme: its objectives or top actions, its dates, and who attends, by role
- One or two real tasks where the skill should show up at work, and what managers already have in the calendar: a one-to-one, a team meeting, a shift handover
If you have none of this, I start from the programme title and one objective and mark the output as a first draft.
Approach
Transfer of training research (Blume, Ford, Baldwin and Huang, 2010): transfer relates to motivation and a supportive work environment; the evidence is correlational. The manager's part follows the required drivers of the Kirkpatrick model: reinforce, monitor, encourage, reward. The judgement is in keeping each ask small and inside a meeting that already happens. The failure this prevents: the learner comes back keen, finds the diary booked solid and the old way still the fast way, and by the time anyone asks, the handout is under a pile.
Workflow
- Ask up to three questions: which behaviour the manager should see first at work, what usually blocks it (time, tool, process, workload), and when managers already meet their people.
- Write the note to managers: one paragraph, readable in a minute, saying what the programme is for, the two conversations asked of them, and that nothing here assesses anyone.
- Write the before guide: a short conversation, its length set by you, three questions at most, in words a manager would say. Why this programme, what the person wants from it, which task they will try first.
- Fix the first on-the-job task: real work that uses the skill, within a window you set. The manager clears room for it. If nothing can move, that is the first barrier, and it goes in the log.
- Write the after guide: what did you try, what happened, what got in the way, what do you need from me. The manager listens and removes one obstacle. It is never a quiz or a demonstration on demand.
- Place the check-ins inside existing meetings, each mapped to a driver: reinforce (a prompt or the job aid), monitor (ask about the task), encourage (name the effort), reward (visible credit for using it).
- Draw the barrier log: date, category (time, tool, process, workload, other) and the condition. There is no field about the person. It goes to L&D and is read in aggregate, with groups under a size you set suppressed.
Output Format
# Manager Briefing Kit
Programme: [title] | Dates: [dates] | Behaviour to see first: [behaviour]
## Note to managers (one minute)
[One paragraph: what the programme is for, the two conversations, the first task, and that nothing here feeds a review]
## Before: [minutes] with each person
| Ask, in your own words | Listen for |
|---|---|
| [question] | [what to pick up] |
First task back at work: [real task] | Within: [window you set] | Room made by: [what the manager moves]
## After: the first conversation back
| Ask | Then do |
|---|---|
| [question] | [support given or obstacle removed] |
## Check-ins in meetings that already exist
| Date | Meeting | Driver | What the manager does |
|---|---|---|---|
| [date] | [one-to-one / team meeting] | [reinforce / monitor / encourage / reward] | [action] |
## Barrier log (conditions only)
| Date | Category | What blocked use | Sent to L&D |
|---|---|---|---|
| [date] | [time / tool / process / workload / other] | [the condition] | [yes / no] |
## Decision
[L&D lead name] and [sponsor name] agree who fixes which kind of barrier, and when the log is read, by [date].
Done When
- The note reads in a minute and each guide fits one page, in words a manager would say
- The first task is real work with a window you set, and every check-in names a driver and sits in a meeting that already exists
- The barrier log has categories and no field that describes a person
Quality Bar
- The transfer evidence is described as correlational; the kit promises no uplift
- Nothing asks the manager to test, rate or report on anyone
- A blocked first task is logged as a condition, with what would have to move; lengths, windows and dates are yours
- The kit helps a manager support learning; nothing in it feeds a performance review, and the barrier log records conditions, never people.
Next
Run ldg-plan-the-onboarding (Plan the Onboarding) to build the same support into a new hire's path.
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-brief-the-managers3description: Prepares what managers need to support learning around one programme, with a note they can read in a minute, a before and an after conversation guide, the first on-the-job task, check-in dates inside meetings that already exist, and a barrier log that records conditions, never people. Use for "run ldg-brief-the-managers", "manager follow-up after training", "training transfer", "transfer of training", "manager support for learning", "what should managers do after training", "manager conversation guide", "barriers to applying training", part of The Complete Claude Guide for L&D Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/ldg-brief-the-managers6---78# Brief the Managers9## When To Use10Learners go back to a manager who never asks what they learned. Most managers are not against the programme; nobody told them what their part was, or made it small enough to fit a week that is already full. Use this for one programme, before it runs. It answers: what does the manager say, ask and remove, before and after, so people get to use it?1112## When Not To Use13If you need the whole mix of assignments, coaching and courses for a role, run Build the 70-20-10 Plan. If you want to know weeks later whether the group used it, run Check Use on the Job: that reads across everyone for the sponsor, while the log here is what each manager notes as they go.1415## Inputs16- The programme: its objectives or top actions, its dates, and who attends, by role17- One or two real tasks where the skill should show up at work, and what managers already have in the calendar: a one-to-one, a team meeting, a shift handover18If you have none of this, I start from the programme title and one objective and mark the output as a first draft.1920## Approach21Transfer of training research (Blume, Ford, Baldwin and Huang, 2010): transfer relates to motivation and a supportive work environment; the evidence is correlational. The manager's part follows the required drivers of the Kirkpatrick model: reinforce, monitor, encourage, reward. The judgement is in keeping each ask small and inside a meeting that already happens. The failure this prevents: the learner comes back keen, finds the diary booked solid and the old way still the fast way, and by the time anyone asks, the handout is under a pile.2223## Workflow241. Ask up to three questions: which behaviour the manager should see first at work, what usually blocks it (time, tool, process, workload), and when managers already meet their people.252. Write the note to managers: one paragraph, readable in a minute, saying what the programme is for, the two conversations asked of them, and that nothing here assesses anyone.263. Write the before guide: a short conversation, its length set by you, three questions at most, in words a manager would say. Why this programme, what the person wants from it, which task they will try first.274. Fix the first on-the-job task: real work that uses the skill, within a window you set. The manager clears room for it. If nothing can move, that is the first barrier, and it goes in the log.285. Write the after guide: what did you try, what happened, what got in the way, what do you need from me. The manager listens and removes one obstacle. It is never a quiz or a demonstration on demand.296. Place the check-ins inside existing meetings, each mapped to a driver: reinforce (a prompt or the job aid), monitor (ask about the task), encourage (name the effort), reward (visible credit for using it).307. Draw the barrier log: date, category (time, tool, process, workload, other) and the condition. There is no field about the person. It goes to L&D and is read in aggregate, with groups under a size you set suppressed.3132## Output Format33```markdown34# Manager Briefing Kit35Programme: [title] | Dates: [dates] | Behaviour to see first: [behaviour]36## Note to managers (one minute)37[One paragraph: what the programme is for, the two conversations, the first task, and that nothing here feeds a review]38## Before: [minutes] with each person39| Ask, in your own words | Listen for |40|---|---|41| [question] | [what to pick up] |4243First task back at work: [real task] | Within: [window you set] | Room made by: [what the manager moves]44## After: the first conversation back45| Ask | Then do |46|---|---|47| [question] | [support given or obstacle removed] |48## Check-ins in meetings that already exist49| Date | Meeting | Driver | What the manager does |50|---|---|---|---|51| [date] | [one-to-one / team meeting] | [reinforce / monitor / encourage / reward] | [action] |52## Barrier log (conditions only)53| Date | Category | What blocked use | Sent to L&D |54|---|---|---|---|55| [date] | [time / tool / process / workload / other] | [the condition] | [yes / no] |56## Decision57[L&D lead name] and [sponsor name] agree who fixes which kind of barrier, and when the log is read, by [date].58```5960## Done When61- The note reads in a minute and each guide fits one page, in words a manager would say62- The first task is real work with a window you set, and every check-in names a driver and sits in a meeting that already exists63- The barrier log has categories and no field that describes a person6465## Quality Bar66- The transfer evidence is described as correlational; the kit promises no uplift67- Nothing asks the manager to test, rate or report on anyone68- A blocked first task is logged as a condition, with what would have to move; lengths, windows and dates are yours69- The kit helps a manager support learning; nothing in it feeds a performance review, and the barrier log records conditions, never people.7071## Next72Run ldg-plan-the-onboarding (Plan the Onboarding) to build the same support into a new hire's path.7374## About the makers7576This 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).