Role Paths

Start from the job you are trying to do.

Use these paths when you know your role in the work but do not know whether the next useful move is a template, example, field note, glossary term, or small operating change.

Choose the pressure point

Each path gives you one practical move in the first minute.

The goal is not to read everything. The goal is to find the next useful action and the resource that helps you take it.

New L&D Manager

Stabilize intake, priorities, ownership, and measurement before the team becomes a request desk.

  • Use whenThe team is doing a lot of work, but the operating rhythm is not visible enough to protect focus or prove value.
  • First movePull the next five requests and sort each one into training, documentation, workflow, manager support, tool issue, or measurement issue.
Open path

Solo Instructional Designer

Protect scope, separate SME feedback, and turn one-off production into reusable working patterns.

  • Use whenThe ID becomes the place where unclear scope, review confusion, and maintenance debt all land.
  • First moveBefore building, ask what task the learner needs to perform and what evidence would show readiness.
Open path

Learning Operations Lead

Make intake, queue health, governance, publishing, and reporting visible enough to manage.

  • Use whenThe work exists in tickets, meetings, spreadsheets, and memory, but the operating system is not clear enough.
  • First moveDefine five statuses the team will use for incoming work and what each status means.
Open path

LMS Owner or Admin

Turn platform requests into governance decisions, reporting definitions, and clean admin routines.

  • Use whenThe LMS is expected to solve reporting, access, catalog, and migration issues without clear governance.
  • First moveChoose one repeated LMS decision and write the owner, rule, affected audience, and review trigger.
Open path

AI-Curious L&D Team

Move from scattered AI experiments to one bounded workflow with source rules and review gates.

  • Use whenAI is being tried everywhere, but the team has not named where it helps, what it can use, or who reviews the output.
  • First movePick one low-risk workflow and define what AI can do, what it cannot do, and who reviews the output.
Open path

Team Trying to Prove Impact

Move from completion reporting to evidence that supports decisions about readiness, behavior, and workflow impact.

  • Use whenThe evidence is available, but it is not strong enough to support the decisions leaders need to make.
  • First moveWrite the decision first: what will change if the evidence says the program is or is not working?
Open path

Team Drowning in SME Review

Separate review comments into decision categories so review can close without burying the work.

  • Use whenSME review is overloaded because every kind of decision is being routed through one review step.
  • First moveLabel every comment in the next review before responding to any of them.
Open path

Team Rebuilding a Content Library

Rebuild around tasks, ownership, review signals, and retirement rules instead of another content pile.

  • Use whenThe rebuild will repeat the same debt unless content ownership, task fit, and retirement rules are visible.
  • First movePick one content area and sort assets by keep, update, merge, archive, and needs owner.
Open path