Who this is for

Learning operations leads responsible for turning recurring L&D work into reliable workflows.

What usually breaks
  • Status definitions change by team or project.
  • Decision rights are unclear.
  • Reports show activity without explaining workflow health.
First 15-minute move

Define five statuses the team will use for incoming work and what each status means.

What to inspect this week

Look for repeated handoffs, unowned decisions, stale work, reopened review cycles, and reports that do not support action.

Three ways to work the problem

Start simple, then make the system visible.

Manual way

Map one recurring workflow from intake to publish with owner, status, review gate, and decision point.

Microsoft 365 or Google Workspace way

Use Lists, Planner, SharePoint, Excel, Sheets, Asana, or a simple Kanban board to track owner, status, age, blocker, and next action.

AI-assisted way

Use AI to summarize queue notes, identify stuck work, draft status definitions, and prepare weekly operating questions for the team.

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 Learning Operations Lead for an L&D system problem.

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

Context: Help a learning operations lead turn scattered work into a visible 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 Learning Operations Lead for an L&D system problem.
Help a learning operations lead turn scattered work into a visible 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 Learning Operations Lead from the notes provided.

Context: Help a learning operations lead turn scattered work into a visible 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 Learning Operations Lead.

Context: Help a learning operations lead turn scattered work into a visible 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

Create one visible status model for the request queue.