Name the action.
“People need to understand the system” leaves a lot open to interpretation. “A manager needs to review and approve a request” gives us a concrete task to design around. We can see the steps, identify the decisions and ask where people are getting stuck.
Listen to the people doing the work.
A subject expert knows the process. The people using it can tell us what happens in practice: the unfamiliar terms, the exception that comes up every Friday, or the step they always need to check. Both perspectives belong in the brief.
Choose the format after the question.
A short walkthrough may support a clear sequence. A scenario can give people a decision to practise. A job aid can put a useful reminder beside the task. The format earns its place by serving the need.
Make success observable.
Ask what someone should be able to do after the experience. That answer helps shape the learning, the practice and the feedback we collect after launch. A clearer question makes the whole project easier to steer.
Have a learning challenge in mind?
Talk it through with us