A one-page tool for sorting SME feedback into fact issues, workflow issues, preferences, approval calls, risk issues, and unclear comments before the team revises anything.
- Use whenReview comments conflict or point in different directions.
- Systems moveTreat every review comment as a system signal. A comment might reveal a bad source, a missing owner, an unclear workflow, a hidden risk, or a preference that needs a budget.
A one-page question set for slowing down vague training requests before the team accepts the requested format.
- Use whenA requester asks for a course before naming the task.
- Systems moveTreat the requested training as an input, not the answer. The request is a clue about a larger system made of people, policies, tools, handoffs, incentives, information, and evidence.
A one-page ladder for moving from completion data toward stronger evidence of readiness, behavior, adoption, manager observation, workflow impact, and business contribution.
- Use whenA leader asks for impact but the team only has completions.
- Systems moveStart with the decision the evidence needs to support. Then choose the smallest credible signal that connects learning to readiness, behavior, adoption, workflow, or contribution.
A one-page scorecard for turning manager observation into credible behavior evidence without asking managers to complete another heavy form.
- Use whenThe team needs evidence beyond completion, but a full dashboard is not ready.
- Systems moveTreat manager observation as a lightweight evidence system. The goal is not to make managers evaluators. The goal is to give them one shared behavior, one visible criterion, and one follow-up action.
A one-page tool for moving stale, risky, duplicate, or unowned content into a visible quarantine state before the team deletes, rewrites, or leaves it live.
- Use whenNobody can tell whether an asset is current, duplicated, risky, or still owned.
- Systems moveCreate a visible middle state between trusted and deleted. Quarantine gives the team a way to reduce learner risk while preserving enough history to make a better decision.
A one-page card for turning a vague LMS report request into a definition that names the decision, audience, metric, source field, cadence, and caveat.
- Use whenA leader asks for a report before naming the decision it should support.
- Systems moveTreat a report request as a decision-design problem. The first job is to define what decision the report supports and what the data can honestly say.