Playbooks

Short operating playbooks for L&D systems work.

These are practical implementation paths for teams that need to put a better system in place without waiting for a full transformation project.

Start with one system

Use a playbook when the pattern needs to become repeatable.

Playbooks connect the field notes, templates, examples, and glossary into a week-sized implementation path.

Fix Training Intake in One Week

A five-day operating playbook for turning vague training requests into clearer decisions, better scope, and a repeatable intake rhythm.

  • Use whenTraining intake is treated like a form instead of a decision system.
  • StartRun the Day 1 request sort with five recent requests before changing the intake form.
Open playbook

Clean Up SME Review in 10 Business Days

A ten-business-day playbook for turning SME review from a vague approval gate into a visible decision system.

  • Use whenSME review breaks when fact-checking, workflow validation, preference editing, risk review, and approval all land in one overloaded pass.
  • StartTake one messy review thread and tag every comment before responding to any of them.
Open playbook

Build a Measurement Plan Before the Dashboard

A five-day playbook for defining the decision, behavior, evidence, owner, and caveat before the team builds another L&D dashboard.

  • Use whenMeasurement gets weak when the team starts with available data instead of the decision the evidence needs to support.
  • StartBefore building the next dashboard, write the decision, behavior, signal, owner, and evidence limit on one page.
Open playbook

Clean Up a Content Library Without Boiling the Ocean

A ten-business-day playbook for cleaning one slice of a learning library by task, owner, source, use, duplicate risk, and retirement rule.

  • Use whenContent libraries become hard to trust when every asset stays live, ownership is unclear, and the team tries to clean everything at once.
  • StartPick one content slice and classify every asset as keep, update, merge, archive, retire, or needs owner before editing.
Open playbook

Set LMS Governance Rules Before the Next Request

A ten-business-day playbook for turning repeated LMS requests into visible rules for reports, permissions, catalog structure, ownership, and review.

  • Use whenLMS work becomes noisy when reports, permissions, catalog rules, admin rights, and ownership decisions live in tickets, memory, and side conversations.
  • StartPull the last ten LMS requests and sort each one into a governance lane before answering the next one.
Open playbook