Hidden prerequisites: Why “simple” training becomes difficult

A task can look simple in an SOP and still be difficult to learn.

The problem is often not the final instruction. It is the knowledge, vocabulary, tool familiarity, role context, and judgment that the instruction silently assumes.

Experts perform many of these prerequisite actions automatically. Because the supporting knowledge is no longer effortful, it becomes easy to omit from training. The learner then encounters a “simple” direction that depends on several capabilities they have never developed.

The practical solution is to walk backward from the required workplace performance until every important dependency is visible.

Key takeaways

• A short task description may conceal many component skills and decisions.
• Experts are especially likely to omit prerequisites that have become automatic.
• Prerequisites can involve concepts, language, tools, roles, procedures, or judgment.
• Not every prerequisite belongs in the course; some should be assessed, linked, or provided as performance support.
• A prerequisite map should connect source requirements to learning activities and evidence.

“Simple” describes the expert’s experience, not the task

Consider the instruction:

Document the incident and notify the appropriate supervisor.

To an experienced employee, that may feel straightforward.

But successful performance could require the learner to:

• recognize what the organization classifies as an incident;
• distinguish immediate response from later documentation;
• know which supervisor is responsible;
• understand the escalation schedule;
• access the reporting system;
• select the correct report type;
• use appropriate factual language;
• protect confidential information;
• know the submission deadline;
• recognize when another authority must also be contacted.

The sentence is short. The capability is not.

Instructional difficulty is often hidden by compressed expert language. A source document is usually written to define or govern work, not to reveal every dependency needed to learn that work.

Experts compress what beginners need to see

With experience, separate actions become organized into larger chunks.

An expert may perceive “complete the intake” as one familiar unit. A beginner may need to identify the required records, locate the correct system, interpret several fields, ask the right questions, recognize missing information, and route the result.

This compression makes expert performance efficient. It can also create an expert blind spot during training design.

Subject-matter experts may:

• use undefined terms;
• skip transitions;
• omit why a decision changes;
• assume familiarity with tools;
• reference another procedure without naming it;
• present exceptions before the basic model is clear;
• say “use judgment” without showing the cues that guide judgment.

The answer is not to distrust experts. It is to use a method that helps them unpack what has become automatic.

Start with a precise performance statement

Do not begin by listing content.

Write what successful performance looks like under realistic conditions.

Weak statement:

Understand client onboarding.

Stronger statement:

Given a new client record, the coordinator verifies the required information, identifies missing consent, completes the correct setup steps, and routes unresolved issues to the designated role.

The stronger statement gives you several things to analyze:

• inputs;
• decisions;
• actions;
• quality criteria;
• tools;
• handoffs;
• exceptions.

Carnegie Mellon University's learning principles emphasize that learners must develop component skills, practice integrating them, and know when to apply what they have learned. Source: Carnegie Mellon University, “Principles of Learning”. A performance statement creates the starting point for identifying those components.

Walk backward through the task

Ask the performer—or observe the work—one decision at a time.

For each action, ask:

1. What must the employee notice?
2. What must they know to interpret it?
3. What choice must they make?
4. What rule or principle guides that choice?
5. What tool or resource must they use?
6. What previous action must already be complete?
7. What exception changes the normal sequence?
8. What would a beginner commonly do wrong?
9. How would we know the action was performed correctly?

Continue until you reach knowledge or skills that can reasonably be assumed, checked, taught, or provided at the point of work.

Task analysis is a longstanding instructional-design method for describing the knowledge and performance components of work. Different methods fit different kinds of tasks, so the map should be treated as a design representation rather than a perfect copy of cognition. A practical reference is Jonassen, Tessmer, and Hannum's Task Analysis Methods for Instructional Design. Source: Routledge book page.

Look for five kinds of prerequisites

A useful prerequisite review covers at least five categories.

Conceptual prerequisites

These are ideas and relationships required to interpret the task.

Example:

Understanding the difference between an incident, a complaint, and an emergency.

Language prerequisites

These include vocabulary, abbreviations, labels, and organization-specific terms.

Example:

Knowing that “EVV exception” refers to a particular electronic visit verification condition rather than any unusual visit.

Tool prerequisites

These involve software, equipment, forms, access credentials, navigation, or data entry.

Example:

Being able to find the correct reporting form and attach required evidence.

Role and process prerequisites

These explain who owns a decision, where a handoff occurs, and how this task connects to previous or later work.

Example:

Knowing which supervisor is on duty and what happens after notification.

Decision prerequisites

These include conditions, cues, thresholds, priorities, and exceptions.

Example:

Recognizing when immediate safety action must happen before documentation.

Separate required memory from available support

Finding a prerequisite does not automatically mean adding another lesson.

Decide whether the employee must:

• remember it;
• recognize it;
• perform it;
• know when it applies;
• find it quickly;
• verify it with another person or source.

Some knowledge must be immediately available. A worker may need to recognize a serious safety risk without searching a manual.

Other details are better supported externally. Long exception tables, changing contact lists, and rare technical specifications may belong in a reliable job aid or searchable reference.

A practical classification is:

Requirement	Best treatment
Frequently used decision rule	Teach and practice
Safety-critical first action	Teach, retrieve, and verify
Rare detailed exception	Provide searchable support and practice finding it
Tool operation	Demonstrate and practice
Existing prerequisite	Diagnose and allow a faster path
Role-specific detail	Assign only to affected learners

This keeps prerequisite analysis from turning into content accumulation.

Distinguish missing prerequisites from poor task design

A learner may fail even when the required knowledge is present.

The barrier might be:

• an inaccessible tool;
• contradictory instructions;
• unclear responsibility;
• missing permissions;
• an unrealistic workload;
• a form that does not match the procedure;
• incentives that reward the wrong action.

The CDC recommends examining both individual and system causes when assessing training needs rather than assuming a performance gap requires instruction. Source: CDC, “Assess Training Needs”.

Before adding prerequisite content, ask:

Would a knowledgeable, motivated employee with the current tools be able to perform correctly?

If the answer is no, redesign the environment as well as—or instead of—the training.

Diagnose before reteaching

Some learners already possess the prerequisite.

Use a short, low-stakes check to determine whether support is needed:

• define an essential term in context;
• classify two contrasting situations;
• explain the reason for a decision;
• complete the first part of the task;
• demonstrate access to the correct tool;
• identify the responsible role.

Research on prior knowledge consistently shows that what learners already know affects how they understand new material. A systematic review of knowledge activation also found that effectiveness depends on the amount and accuracy of prior knowledge and on the activation technique. Source: Hattan, Alexander, and Lupo, “Leveraging What Students Know”.

Those findings come mainly from educational reading contexts. Workplace teams should use them to guide design, then verify with real tasks and employees.

Build the learning sequence from dependencies, not document order

An SOP's section order may reflect legal, operational, or editorial needs. It is not necessarily a learning sequence.

A document might define exceptions first, place key vocabulary in an appendix, and reference another policy without explaining the relationship. Turning each heading directly into a lesson preserves the source structure but may preserve its hidden prerequisites as well.

A learning sequence should usually:

1. orient the learner to the outcome and context;
2. establish essential vocabulary and concepts;
3. show the normal case;
4. model the decision process;
5. provide guided practice;
6. introduce meaningful variations and exceptions;
7. require independent application;
8. connect to job aids and workplace evidence.

This order is not universal. The prerequisite map should determine what must come first.

Represent prerequisites as a graph

A linear outline can show order. A graph can show dependency.

Useful nodes include:

• source requirement;
• concept;
• term;
• tool operation;
• role;
• task;
• decision;
• exception;
• learning activity;
• assessment;
• evidence.

Useful relationships include:

• prerequisiteOf;
• performedWith;
• ownedByRole;
• validUnderCondition;
• changesDecision;
• demonstratedBy;
• derivedFrom;
• supportedByJobAid.

For example:

Incident definition
prerequisiteOf
Incident classification decision

Classification decision
changesDecision
Reporting path

Reporting path
performedWith
Reporting system

This representation makes hidden dependencies reviewable and supports future impact analysis when a source changes.

How this can shape LoreGraph

LoreGraph helps organizations transform workplace documents into structured learning. A prerequisite-aware workflow could go beyond converting headings into lessons.

It could help a creator:

• extract candidate concepts and tasks;
• identify cross-document dependencies;
• flag undefined terms;
• distinguish normal cases from exceptions;
• map requirements to practice and evidence;
• identify content better delivered as a job aid;
• review which prerequisite relationships are source-supported and which are inferred.

Learn more about LoreGraph.

Human review remains essential. AI can propose a dependency, but a subject-matter expert must confirm whether it is operationally correct and current.

Common mistakes

Avoid these errors:

• Explaining only the final step: The learner still lacks the structure beneath it.
• Adding every prerequisite to every course: Diagnose, target, and link instead.
• Assuming the source order is instructional order: Governing documents and learning experiences serve different purposes.
• Using tenure as proof: Experienced employees can have gaps in a changed or unfamiliar domain.
• Teaching a tool without the decision: Button knowledge is not judgment.
• Teaching a decision without the tool: Understanding is not executable performance.
• Ignoring cross-document dependencies: A course may depend on a definition or process maintained elsewhere.
• Treating an environment problem as a knowledge gap: Fix the system when the system blocks correct work.

Next step

Choose one instruction that experts describe as “simple.”

Write the final performance on the right side of a page. Then walk backward through every decision, action, tool, role, concept, and term required to reach it.

For each dependency, decide:

• already demonstrated;
• must be taught;
• must be practiced;
• should be available as support;
• belongs to another role;
• or reveals a non-training problem.

The task becomes teachable when its hidden structure becomes visible.