The problem this shows
The messy version is usually not a writing problem.
A requester asks for training before the team knows what needs to change.
Example
Bad Training Request to Better Scoped Request
Turn a broad training ask into a clearer request with audience, behavior, workflow, evidence, and constraints.
What you should take away
Look for the decision the artifact needs to support.
Before accepting the next request, ask: who needs to do what differently, where in the workflow, and how will we know it changed?
Aha moment
The shift is small, but it changes the conversation.
The request gets easier when we stop asking what to build and start asking what decision or behavior the work needs to support.
Put the original request at the top of a shared doc. Under it, add four lines: audience, behavior, workflow moment, evidence. Do not discuss format until those four lines have something real in them.
Use a one-page Word doc or Google Doc as the intake gate. Add a table with audience, behavior, workflow moment, evidence, owner, and due date. Keep the request there until the table is usable.
Ask the requester to show you one real example of the work going wrong. A ticket, call note, screenshot, or manager observation will usually beat another paragraph of explanation.
Paste the request and ask AI to classify the likely issue as training, workflow, documentation, manager support, tool friction, or measurement. Then have a person confirm the category.
Before and after
What changes when the work becomes clearer.
Use this as a pattern. The exact wording will change, but the move is the same: name the audience, workflow, owner, evidence, or decision more clearly.
The request names the asset, but not the audience, behavior, decision point, workflow step, or evidence that would show whether training helped.
Audience: frontline managers. Behavior: identify the issue type and choose the escalation path. Workflow: first 10 minutes after a customer issue is reported. Evidence: fewer misrouted escalations and faster first response.
Why this is better
The artifact starts carrying more of the operating logic.
- The work is framed around a behavior, not a course format.
- The workflow moment is visible.
- The evidence standard gives the team a way to say what good would look like.
- The request is small enough to scope before production starts.
Use this with
Open the related resource when you want to apply it.
Field test
Try it before you rebuild the whole system.
Run this on one incoming request this week. If the requester cannot name the behavior or evidence, redirect the conversation before a course gets promised.