Why is this needed?
Clarify the pressure, risk, behavior, or operational problem creating the learning request.
Use this to avoid solving the wrong problem.Field Guide
Use this field guide to pressure-test a learning request before it turns into another content deliverable. Inspect the context, people, tools, support, and measurement around the work so you can recommend the smarter next move.
What this helps you do
This guide helps you slow down just enough to avoid building the wrong thing beautifully. Use it when a stakeholder asks for a course, job aid, refresh, onboarding asset, or learning campaign and you need to understand what will actually help people perform.
What to inspect
Each lens helps you check one part of the system around the learning. A low score does not mean the project is bad. It means that part of the experience needs more design attention.
Clarify the pressure, risk, behavior, or operational problem creating the learning request.
Use this to avoid solving the wrong problem.Identify the learner, manager, support role, stakeholder, or team that shapes the behavior.
Use this to design beyond the learner alone.Check whether people need information, examples, scenarios, decision practice, or coaching feedback.
Use this to avoid dumping information.Look for job aids, templates, checklists, systems, references, or interface cues that help at the moment of need.
Use this to reduce memory burden.Inspect where people go when they are unsure, rushed, stuck, or facing an edge case.
Use this to prevent post-launch abandonment.Look beyond completion toward behavior, readiness, confidence, transfer, quality, or workflow signals.
Use this to measure capability, not just activity.Field guide tool
Rate each part of the learning system. The goal is not a perfect score. The goal is to see where the experience needs more support.
Is the real performance problem or workflow need clearly defined?
Are the learner, support roles, stakeholders, and reinforcement points clear?
Does the content help people practice judgment, not just receive information?
Are usable tools, references, or job aids available in the workflow?
Can people get help after the learning moment when uncertainty shows up?
Does measurement look beyond completion and toward real performance signals?
Failure signals
People complete the learning but still feel unsure what to do next.
Managers or support teams do not know how to reinforce the behavior.
Resources are technically available but practically invisible.
Success is measured mainly by completion, attendance, or launch status.
Design questions
What does the learner need to do differently?
Where does this show up in the real workflow?
What could confuse people?
What support exists after completion?
Request a Field Guide
Have a learning design problem, audit idea, checklist, framework, or messy stakeholder conversation that deserves a practical guide? Send it in. The best Field Guides usually start with a real design problem.
Build smarter learning systems
The strongest learning experiences are rarely one object. They are connected systems that help people move with more clarity, confidence, and consistency.