The request says the team needs training. The screen says the team needs access.
Before building a lesson, watch someone attempt the work. Name the expected output. Check the instructions, inputs, and permissions available at the moment of the attempt. Then decide which gap instruction can address.
CDC's needs-analysis guidance starts by investigating the gap before selecting a solution. It identifies training alongside possible changes to policy, technology, organization, and procedures. The business worksheet below adapts that distinction. It is a proposed consulting method, with fictional evidence, rather than a CDC business standard or endorsement.
Define One Task With an Inspectable Finish
Consider a fictional service company introducing a supplier-intake workflow. A coordinator receives a request packet, checks its completeness, and prepares a draft record for review. A separate approver decides whether the supplier can proceed.
The coordinator has no authority to approve suppliers, place orders, or change payment instructions. Keep those boundaries outside the exercise.
Define the task before observing it:
Given the current intake checklist, a synthetic request packet, and draft-record access, prepare a reviewable intake record. Record missing inputs and route unresolved questions to the designated reviewer. Leave approval pending.
A reviewable record contains the request identifier, requested service, requester, required-document status, selected next step, and a reference to the source packet. These fields are invented for this example. Replace them with the fields your process owner confirms.
The stated conditions matter. A coordinator working from an outdated checklist is attempting a different task from someone using the current version. Record the version used. If nobody can identify the authoritative checklist, resolve that question before diagnosing a learning need.
Define the finish as a visible result. “Comfortable with supplier intake” gives the observer nothing to inspect. “Draft contains the required fields and remains pending approval” gives the observer an output and a boundary.
Observe the Attempt Without Writing a Verdict
Arrange an observation using synthetic records and an agreed task. Explain that the review concerns the workflow and its support. Keep employee ratings and disciplinary conclusions outside the document.
Ask the coordinator to perform the task using the resources normally available. Allow the reference checklist if normal work allows it. Record help you provide. An observer who quietly supplies every missing answer has changed the conditions.
Use descriptions of actions. “Could not open the draft screen” records an obstacle. “Needs confidence” guesses at a cause. “Selected complete while the required attachment was absent” records a decision worth investigating.
In the fictional observation, the coordinator encounters four distinct gaps. The draft screen denies access. One packet lacks its requested-service description. Two instructions disagree about where incomplete packets go. After those conditions are corrected in the practice environment, the coordinator still misclassifies a missing attachment.
That final observation makes a narrow learning need plausible. It does not establish that every delay, missing field, or unfinished intake comes from the same cause.
Ask the coordinator to explain which rule they applied. Their answer can identify a misunderstood distinction or reveal another contradiction. Preserve the explanation alongside the observed action. Do not replace either with your interpretation.
Separate Learning Needs From Blocked Work
For this analysis, a learning need means the task requires knowledge or practice the learner has not yet demonstrated under the stated conditions. First check whether those conditions permit the task.
For an access failure, assign an access owner. Record which capability is unavailable and which task it blocks. Training can explain how to request permission. It cannot grant the missing permission.
For a missing input, identify the required field or document. Ask who supplies it and what the coordinator should do while waiting. A lesson cannot manufacture a supplier's missing service description.
For contradictory procedures, ask the process owner to select the governing instruction. Record its version and remove ambiguity from the training brief. Avoid teaching a personal workaround as the official process.
For a possible skill gap, repeat the relevant decision with a different synthetic packet after prerequisites are available. The learner may need practice distinguishing an incomplete packet from a complete packet awaiting approval. Keep that proposed need tied to the observed classification task.
Mixed findings are allowed. The same workflow may need corrected access and a short practice exercise. Give each remedy its own owner. Do not hide infrastructure work inside a broad training assignment.
Copy This Needs-Analysis Worksheet
Use one row per observed gap. Keep the evidence close to the proposed cause. Record the answer when a question is resolved. Keep unanswered questions visible.
| Task | Evidence | Possible cause | Learning need | Non-training remedy | Unresolved question |
|---|---|---|---|---|---|
| Open a draft record | Practice screen returns access denied | Required role unavailable | Not established | Access owner checks the assigned role | Does the approved role permit draft creation? |
| Describe the requested service | Synthetic packet has no service description | Request input missing | Not established | Request owner supplies the missing input | What status applies while the input is absent? |
| Route an incomplete packet | Checklist names intake review; guide names approval queue | Procedures conflict | Not established | Process owner selects the governing rule | Which document and version control this step? |
| Classify an attachment gap | After prerequisites are corrected, learner marks the incomplete sample complete | Decision rule may be misunderstood | Practice recognizing required versus optional attachments | Add a clear attachment example to the checklist | Does a second case show the same misunderstanding? |
| Prepare a pending draft | Learner completes all required fields using the checklist | No gap observed in this attempt | None identified for this case | None proposed | Has the exception path been observed separately? |
These entries are fictional observations. They illustrate the difference between a record of evidence and a conclusion about a person.
For your own worksheet, add the observation date, task version, sample identifier, and reviewer above the table. Store only the evidence needed for the decision. A reference to an authorized record may be sufficient. Avoid copying private supplier documents into a training plan.
Review the rows with the process owner and learner. Ask whether the evidence supports the proposed cause. Where it does not, leave the cause provisional. Schedule the next observation around the unresolved question.
Write Objectives After the Need Is Established
Suppose the second synthetic case confirms the classification gap. Access works and the governing instruction is clear. The process owner has resolved the routing conflict: incomplete packets remain on hold, with missing inputs recorded. Complete packets go to intake review. Neither state authorizes supplier approval. The coordinator still misclassifies an absent required attachment.
That finding supports a focused practice task. A tour of every screen would exceed the evidence gathered so far.
CDC's learning-objectives guidance describes the ABCD method: audience, behavior, condition, and degree. Use those elements to make the expected performance observable.
For this fictional brief, set three objectives:
- By the end of the session, the coordinator identifies every required attachment gap in two synthetic packets using checklist version three.
- By the end of the session, the coordinator prepares a draft containing all six required fields with the reference checklist available.
- By the end of the session, the coordinator places the incomplete sample on hold, records its missing attachment, and leaves supplier approval pending.
The sample count and completeness criteria are editorial choices for this exercise. The process owner must determine whether they fit the actual task. They are not universal thresholds or certification requirements.
Each objective points to evidence. The first produces an annotated checklist. The second produces a draft record. The third produces a routing decision and status. If an objective produces only “understanding,” rewrite it around the action you need to observe.
Turn the Findings Into a Bounded Training Brief
Keep the brief short enough that the trainer, process owner, and learner can check it together. Include what remains blocked alongside what the session will cover.
| Brief field | Fictional supplier-intake plan |
|---|---|
| Purpose | Practice attachment classification and preparation of a pending intake draft |
| Audience | Coordinators assigned to prepare intake records; approvers are outside the learner group |
| Prerequisites | Working draft access, governing checklist version three, complete synthetic sample pack |
| Existing knowledge | Learner has demonstrated navigation and required-field entry with the checklist |
| Practice task | Classify one complete packet for intake review and one incomplete packet for hold, then prepare their draft records |
| Support | Reference checklist, annotated example, and a designated process reviewer |
| Review evidence | Completed checklists, saved practice drafts, routing decisions, and observer notes |
| Exclusions | Supplier approval, purchasing, payment details, and production activation |
| Open condition | Process owner confirms the hold state and escalation contact before the session |
Choose delivery conditions the learner can use. Ask whether the checklist is readable, the sample interface is accessible, and the practice window permits participation. Confirm these conditions directly rather than guessing from a role title.
Include an example of the attachment distinction. Then let the learner classify a fresh sample with the same reference material. Record where the trainer prompts. Keep supported practice separate from a later independent attempt.
Use SOP documentation for the governing task steps. Keep the training brief focused on the decisions and actions the learner needs to practice. The procedure and the lesson serve different purposes.
Give Every Other Remedy an Owner
A training brief can be ready while the workflow remains blocked. Track both states accurately.
For the fictional company, the access owner confirms draft permissions. The request owner supplies missing packet inputs. The process owner reconciles contradictory routing instructions. The trainer prepares the classification exercise only after those answers are available.
Put these dependencies into the consulting project plan. Give each one a completion condition. “Access discussed” is weaker evidence than a successful draft-only practice attempt under the intended account role.
If access remains unavailable, label the observed skill result untested under the required conditions. A screen demonstration by the trainer can introduce the interface. It cannot establish that the coordinator completed the task.
If the process owner changes the rule, revise the practice sample and objectives before the session. Record which version the review used. Otherwise, a correct action under yesterday's instruction may appear incorrect under today's rubric.
Keep a separate decision for transferring responsibility. Operations handover addresses who accepts ongoing ownership, support, and maintenance. A training session alone does not settle that transfer.
Close the Analysis With a Decision and Its Limits
Write the recommendation around the evidence gathered. For the fictional workflow, it reads: practice the attachment-classification decision after access and routing instructions are corrected. Retain the checklist during practice. Review fresh sample outputs against the stated objectives.
List what the analysis has not tested. This example does not assess every supplier type, the approval role, or live operating performance. Those limits belong beside the recommendation.
Record the next review evidence and its owner. If the corrected workflow removes the observed gap, stop the training proposal there. If a learning need remains, build the bounded lesson described in the brief.
Teach the task the evidence identifies.
Sources
- CDC: Assess Training Needs: Conducting Needs Analysis. Gap investigation and training versus other remedies. Checked 2026.10.28.
- CDC: Design Training: Learning Objectives. Audience, behavior, condition, and degree. Checked 2026.10.28.