Distinguishing a performance gap from a learning gap
6 min read
Lesson objectives
- Separate a learnable classification error from an approval bottleneck in a new request log and justify the next test.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
When an operations manager says, “We need a course because customer requests are late,” do not open the authoring tool yet. Lateness is a symptom; training is one possible remedy for a specific cause. First define required performance, gather evidence about actual work, and identify the portion a learning experience could address. An employee may know the procedure but be waiting for permission they cannot grant. Explaining it again will not remove the queue. A new employee may have the right tools but confuse an exception with a routine case; decision practice may help there.
Define the unit of performance before calculating a gap. “Improve service” is too broad. A checkable statement is: “After a complete request arrives, the intake worker identifies its category and routes it to the authorized team within one working day.” Specify when the clock starts and stops and which requests count. A report timed from initial receipt cannot be compared directly with one timed from data completion. The aggregate late rate locates a problem; it does not reveal its cause.
Write a five-line decision card:
- expected behavior and context
- observed behavior and evidence source
- provisional causal explanation
- a small discriminating check
- and the action within your authority
Review a sample of timestamped records, observe the workflow, and speak with the worker and process owner where feasible. Remove personal details the design does not need. Neither one employee’s account nor a manager’s belief is a representative finding. Ask what changed: a tool, an approval requirement, or a category rule that recent hires have not practiced?
Separate a skill gap from a workflow barrier and a rule or incentive barrier. A skill gap is plausible when inputs, time, and permission are available but a person misses a teachable and testable step. A workflow barrier exists when the person knows the step but a system hides a field or approvals queue up. The rule itself may be ambiguous, or a measure may reward behavior opposed to the stated goal. Causes may coexist. Use a table with three questions and evidence for each answer: Does the worker know what to do? Can they do it with current tools and authority? Do records show they did it? If the person classifies a case correctly but the routing button is disabled for their account, escalate the defect to the system owner. If the button works but two categories are confused, design practice around the category boundary. When uncertain, combine a short safe simulation with a permission-log review before recommending a full course.
In that activity, a learner reads “I need another date; please do not cancel my request,” chooses a date change, and identifies the decisive words. “I no longer need the service; cancel the request” calls for cancellation. “The date may not work for me” is insufficient for a definite category and calls for clarification. Feedback explains the consequence of routing to the wrong team. Assess learning with novel cases, rather than the worked ones. Later, report approval waiting time separately from classification errors. A good test score supports a claim about the rule under test conditions; it does not by itself establish workplace transfer or improvement in the overall indicator.
Lesson summary
When an operations manager says, “We need a course because customer requests are late,” do not open the authoring tool yet.