Who this is for

New L&D managers inheriting messy requests, unclear priorities, or a team that is busy but hard to steer.

What usually breaks
  • Requests are accepted before the team knows the task, audience, workflow, or evidence.
  • Priorities are negotiated in side conversations.
  • Leaders see activity, but not the operating decisions behind it.
First 15-minute move

Pull the next five requests and sort each one into training, documentation, workflow, manager support, tool issue, or measurement issue.

What to inspect this week

Look for repeated request types, hidden decision owners, unclear review gates, and metrics that only show completions.

Three ways to work the problem

Start simple, then make the system visible.

Manual way

Create a one-page operating map with request type, decision owner, review gate, and current status.

Microsoft 365 or Google Workspace way

Use Forms plus Microsoft Lists, Google Forms plus Sheets, or a simple Planner board to make intake status and decision owners visible.

AI-assisted way

Use AI to summarize recent requests into themes, likely non-training causes, missing information, and suggested triage categories for human review.

Prompt starters

Use AI to prepare the work, not replace the judgment.

ChatGPT GPT-5 family

Use an outcome-first prompt with the job, approved source material, constraints, and the exact artifact you want back.

I am working on New L&D Manager for an L&D system problem.

Goal: Help me turn the notes below into a practical next move.

Context: Help a new L&D manager turn messy request history into a practical operating rhythm.

Use these working fields: current situation, what usually breaks, what to inspect, manual move, workspace move, AI-assisted move.

Rules:
- Use only the source notes I provide.
- Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
- Separate known facts, assumptions, missing information, and next actions.
- Flag anything that needs requester, reviewer, leader, legal, compliance, LMS owner, or manager confirmation.
- Keep the output practical enough to review in a working meeting.

Source notes:
[paste approved notes here]

Return:
1. Working diagnosis
2. Known facts
3. Assumptions
4. Missing information
5. Practical next move
6. Review questions for the team

Claude 4 family

Use XML-style sections so context, source material, task, constraints, and output format stay separate.

<context>
I am working on New L&D Manager for an L&D system problem.
Help a new L&D manager turn messy request history into a practical operating rhythm.
</context>

<source_notes>
[paste approved notes here]
</source_notes>

<task>
Turn the source notes into a practical next move using these working fields: current situation, what usually breaks, what to inspect, manual move, workspace move, AI-assisted move.
</task>

<constraints>
Use only the source notes provided.
Do not invent policy details, metrics, learner needs, compliance requirements, or business context.
Separate known facts, assumptions, missing information, risks, and next actions.
Flag anything that changes scope, ownership, evidence, risk, or decision rights.
</constraints>

<output_format>
1. Working diagnosis
2. Known facts
3. Assumptions
4. Missing information
5. Practical next move
6. Review questions for the team
</output_format>

Gemini 3 family

Use a clear task, labeled input, and one example pattern. For Obsidian context, use approved excerpts, Drive exports, Google Docs, or NotebookLM source sets.

Task: Help me make progress on New L&D Manager from the notes provided.

Context: Help a new L&D manager turn messy request history into a practical operating rhythm.

Working fields:
- current situation
- what usually breaks
- what to inspect
- manual move
- workspace move
- AI-assisted move

Example pattern:
Field: Missing information
Good answer: Name the specific information to confirm, who can confirm it, and why it affects the next decision.

Rules:
- Use only the source notes provided.
- If information is missing, write "Needs confirmation".
- Keep the output concise and reviewable.
- End with the next best action.

Source notes:
[paste approved notes here]

Output format:
1. Working diagnosis
2. Known facts
3. Assumptions
4. Missing information
5. Practical next move
6. Review questions for the team

Microsoft 365 Copilot

Use goal, context, source, expectations, and output. For Obsidian context, use approved excerpts, Word summaries, OneDrive files, SharePoint pages, Teams context, or Outlook threads.

Goal: Help me make progress on New L&D Manager.

Context: Help a new L&D manager turn messy request history into a practical operating rhythm.

Source: Use the selected document, meeting notes, spreadsheet, email thread, SharePoint file, or pasted notes as the only source.

Expectations:
- Work with these fields: current situation, what usually breaks, what to inspect, manual move, workspace move, AI-assisted move.
- Mark uncertain items as "Needs confirmation".
- Do not add facts that are not in the source.
- Separate known facts, assumptions, missing information, risks, and next actions.
- Summarize the top review questions for the team.

Output:
1. Working diagnosis
2. Known facts
3. Assumptions
4. Missing information
5. Practical next move
6. Review questions for the team
Try this one thing today

Use the intake worksheet on one request and write down the decision it creates.