Task decomposition and prerequisites
6 min read
Lesson objectives
- Map a conditional service request into prerequisites, decision branches, and an authorized routing action.
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.
Once a learnable part of the gap is established, do not reduce the task to its name. “Classify the request” sounds like one action, but it includes reading the message, extracting intent, comparing it with category definitions, deciding whether the data suffice, and recording and routing the decision. Task decomposition describes observable actions in the order needed for performance, including decisions and boundary cases. The order of screens is not necessarily the order of reasoning; a worker may need to know a rule before selecting a button that appears later.
Obtain the approved rule and ask the subject expert for two straightforward and two difficult examples. Have them perform the task aloud on fictional data. At each point ask which input they used, which rule they favored, and what would make them stop or request clarification. Compare that account with actual workflow records or a safe test environment. Experts sometimes skip a step they have internalized; observation helps reveal it. But do not write a new rule from your own inference when its authority is unsettled. Record who owns the category definitions.
Draw a four-column map: performance step, input, decision or action, and evidence of correctness. For example, “read the customer's sentence” takes the request text and extracts whether the customer wants to retain the service while changing the date; evidence is a quoted decisive phrase. “Compare with category rule” takes the definitions of date change and cancellation, then chooses a category or asks for clarification; evidence is a match to the definition without inventing unstated intent. “Record and route” takes the chosen category and the worker's permissions, sends it to the right team, and checks the routing log. This separation prevents a quiz on category names from masquerading as a measure of decisions on ambiguous messages.
The critical addition is prerequisites. A worker does not need the history of instructional design theory to classify a request. They do need to know what a complete request is, the category definitions, where to find the rule, and when to stop for missing evidence. Sort prerequisites into prior concepts, tools or authority, and information available during performance. A reference card can replace memorization of some detail, but learners must practice finding and using it. If an assessment requires a rule unavailable during learning or the test, fix the design before blaming the learner.
Compare a countercase: “If next week is unavailable, cancel the request.” The first preference remains a date change, but the fallback is now a conditional cancellation. If the system cannot represent both conditions, do not force the message into one category and discard meaning; follow the approved escalation path. This small change in wording tests both conditional reasoning and decision authority. Present the two cases together so the learner sees why the work path changes, rather than merely observing another option label.
A task map can become an unhelpful long checklist. The number of steps is not depth; the decision points, reasons, and checks matter. Ask a new worker to perform a novel case using the same reference they will have on the job. If they fail to extract intent, improve language examples. If they cannot apply the rule, improve its display and practice. If they complete the decision but routing is rejected, return the defect to the system owner. The map locates the intervention instead of reteaching everything.
Mark places where the specialist must pause too: an unapproved category definition, unknown routing authority, or a case the expert cannot settle. Do not fill those gaps with guessed rules in an activity. Record questions for the rule owner and use only settled cases in the interim lesson. Once an answer is approved, revisit the map, outcome, and assessment together so the bank does not test an older rule than the explanation teaches.
Lesson summary
Once a learnable part of the gap is established, do not reduce the task to its name.