Manager Check-In Guide
When To Use
Learners go back to a manager who never asks what they learned, and the new skill goes quiet under the old workload. Use this for a programme where managers have agreed to take a real part, before it starts, so each of them knows what to say, when, and what to clear out of the way. It answers one question: what does the manager ask, do and remove, in meetings they already hold?
When Not To Use
If managers have not agreed to take part, only Manager Briefing Note applies: two short messages from you and nothing more. If you need the assignments themselves across a programme, run 70-20-10 Programme Plan; this guide is the manager's conversations around them.
Inputs
- The programme: what it teaches, its dates, who attends by role, and the practice task people will be offered.
- What usually blocks use at work, the meetings managers already hold with their people (a one-to-one, a team meeting), and who owns the programme inside the organisation.
If you have none of this, I start from the programme title and one task where the skill should show up, and mark the output as a first draft.
Approach
Blume, Ford, Baldwin and Huang's 2010 meta-analysis relates transfer to a supportive work environment; it is correlational, and the guide says so. The manager's part follows the idea of support and accountability at the Kirkpatrick model's Level 3 (Kirkpatrick Partners): behaviour at work, backed by the people around it. The failure it prevents is a guide written as a compliance checklist, which turns "what did you try?" into a quiz and teaches people to say it went fine.
Workflow
- Ask at most three questions: which task should the manager see attempted first, what usually blocks it (time, tool, process, workload), and which meetings do managers already hold with their people?
- Write the before conversation,
[minutes] long, three questions at most and in words a manager would say out loud: why this programme, what the person wants from it, which task they will try first. The task comes from the Practice Assignment; the guide only refers to it.
- Write the after conversation: what did you try, what happened, what got in the way, what do you need from me? The manager asks, listens and removes one obstacle. It is a conversation, never a quiz or a demonstration on demand.
- Place check-ins at
[intervals] inside meetings that already exist. Each has one thing the manager does: a prompt, a question about the task, naming the effort, or visible credit for use. A new meeting created for this is the first one to be cancelled.
- Build the barrier log: date, category (time, tool, process, workload, other), the condition described. No field for a name or a judgement. It goes to the trainer or the programme owner and is read in aggregate, groups under
[minimum group size] suppressed.
- Write the limits on the guide: the evidence is correlational, no uplift is promised, and nothing here feeds a performance review. If the organisation asks how the log may be kept or shared, check with a qualified adviser.
- Cut for a manager's real week: each conversation on one page, and no message from the trainer inside the guide. The programme owner hands it over; managers decide how they use it.
Output Format
# Manager Check-In Guide
Programme: [title] | Dates: [dates] | Task to try first: [task, from the practice assignment] | Programme owner: [role]
## Before the programme ([minutes])
| What you ask, in your words | Why it helps |
|---|---|
| [question] | [reason] |
## After the programme ([minutes])
| What you ask | What you do next |
|---|---|
| What did you try? | [listen; no demonstration asked] |
| What got in the way? | [one obstacle you remove] |
| What do you need from me? | [support agreed] |
## Check-ins
| When | Existing meeting | The one thing you do |
|---|---|---|
| [interval] | [one-to-one / team meeting] | [prompt / question about the task / naming the effort / visible credit] |
## Barrier log (conditions only, read in aggregate)
| Date | Category | The condition that blocked use |
|---|---|---|
| [date] | [time / tool / process / workload / other] | [condition, no name] |
Goes to: [trainer or programme owner] | Groups under [minimum group size] suppressed | Limits: the evidence behind this guide is correlational; it promises no result and feeds no performance review.
## Decision
[Programme owner] and [sponsor] decide who acts on the barrier themes and how often they are read, by [date before the programme starts].
Done When
- Both conversations fit on one page each and sound like a manager talking.
- Every check-in sits in a meeting that already exists and asks one thing of the manager.
- The barrier log has categories and no field for a name or a judgement.
Quality Bar
- Three questions at most in the before conversation; a fourth turns it into an interview.
- The evidence is described as correlational, with no promised uplift.
- The guide carries no message from the trainer and no rating of any manager's follow-through.
- The barrier log records conditions, never the person, and nothing in the guide feeds a performance review.
Next
Run fac-session-feedback-form (Session Feedback Form) to hear from participants about the session itself.
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: fac-manager-check-in-guide3description: Builds the guide a manager uses around a programme, with the before and after conversations in the manager's own words, check-ins placed in meetings that already exist and a barrier log of conditions. Use for "run fac-manager-check-in-guide", "manager check-in after training", "manager conversation guide", "post-training conversation", "training transfer with managers", "how managers support training", "barriers to applying training", "the manager never asks what they learned", part of the Claude for Trainers and Facilitators Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/fac-manager-check-in-guide6---78# Manager Check-In Guide910## When To Use11Learners go back to a manager who never asks what they learned, and the new skill goes quiet under the old workload. Use this for a programme where managers have agreed to take a real part, before it starts, so each of them knows what to say, when, and what to clear out of the way. It answers one question: what does the manager ask, do and remove, in meetings they already hold?1213## When Not To Use14If managers have not agreed to take part, only Manager Briefing Note applies: two short messages from you and nothing more. If you need the assignments themselves across a programme, run 70-20-10 Programme Plan; this guide is the manager's conversations around them.1516## Inputs17- The programme: what it teaches, its dates, who attends by role, and the practice task people will be offered.18- What usually blocks use at work, the meetings managers already hold with their people (a one-to-one, a team meeting), and who owns the programme inside the organisation.19If you have none of this, I start from the programme title and one task where the skill should show up, and mark the output as a first draft.2021## Approach22Blume, Ford, Baldwin and Huang's 2010 meta-analysis relates transfer to a supportive work environment; it is correlational, and the guide says so. The manager's part follows the idea of support and accountability at the Kirkpatrick model's Level 3 (Kirkpatrick Partners): behaviour at work, backed by the people around it. The failure it prevents is a guide written as a compliance checklist, which turns "what did you try?" into a quiz and teaches people to say it went fine.2324## Workflow251. Ask at most three questions: which task should the manager see attempted first, what usually blocks it (time, tool, process, workload), and which meetings do managers already hold with their people?262. Write the before conversation, `[minutes]` long, three questions at most and in words a manager would say out loud: why this programme, what the person wants from it, which task they will try first. The task comes from the Practice Assignment; the guide only refers to it.273. Write the after conversation: what did you try, what happened, what got in the way, what do you need from me? The manager asks, listens and removes one obstacle. It is a conversation, never a quiz or a demonstration on demand.284. Place check-ins at `[intervals]` inside meetings that already exist. Each has one thing the manager does: a prompt, a question about the task, naming the effort, or visible credit for use. A new meeting created for this is the first one to be cancelled.295. Build the barrier log: date, category (time, tool, process, workload, other), the condition described. No field for a name or a judgement. It goes to the trainer or the programme owner and is read in aggregate, groups under `[minimum group size]` suppressed.306. Write the limits on the guide: the evidence is correlational, no uplift is promised, and nothing here feeds a performance review. If the organisation asks how the log may be kept or shared, check with a qualified adviser.317. Cut for a manager's real week: each conversation on one page, and no message from the trainer inside the guide. The programme owner hands it over; managers decide how they use it.3233## Output Format34```markdown35# Manager Check-In Guide36Programme: [title] | Dates: [dates] | Task to try first: [task, from the practice assignment] | Programme owner: [role]37## Before the programme ([minutes])38| What you ask, in your words | Why it helps |39|---|---|40| [question] | [reason] |41## After the programme ([minutes])42| What you ask | What you do next |43|---|---|44| What did you try? | [listen; no demonstration asked] |45| What got in the way? | [one obstacle you remove] |46| What do you need from me? | [support agreed] |47## Check-ins48| When | Existing meeting | The one thing you do |49|---|---|---|50| [interval] | [one-to-one / team meeting] | [prompt / question about the task / naming the effort / visible credit] |51## Barrier log (conditions only, read in aggregate)52| Date | Category | The condition that blocked use |53|---|---|---|54| [date] | [time / tool / process / workload / other] | [condition, no name] |5556Goes to: [trainer or programme owner] | Groups under [minimum group size] suppressed | Limits: the evidence behind this guide is correlational; it promises no result and feeds no performance review.57## Decision58[Programme owner] and [sponsor] decide who acts on the barrier themes and how often they are read, by [date before the programme starts].59```6061## Done When62- Both conversations fit on one page each and sound like a manager talking.63- Every check-in sits in a meeting that already exists and asks one thing of the manager.64- The barrier log has categories and no field for a name or a judgement.6566## Quality Bar67- Three questions at most in the before conversation; a fourth turns it into an interview.68- The evidence is described as correlational, with no promised uplift.69- The guide carries no message from the trainer and no rating of any manager's follow-through.70- The barrier log records conditions, never the person, and nothing in the guide feeds a performance review.7172## Next73Run fac-session-feedback-form (Session Feedback Form) to hear from participants about the session itself.7475## About the makers7677This 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).