--- name: design-training description: Work out what to build before building it, for training or for any problem OrchestrateXR content could help with. Use when someone describes a problem, asks for training, a course, a scenario or a role-play, wants help writing a brief's Outcomes, Audience or Requirements, or asks whether training will fix something. Covers finding what people need to do differently, finding out why they don't do it already, saying plainly when part of the problem isn't one training can fix, writing objectives at the right level of thinking, choosing between Experiences, Characters, Threads and Courses, planning practice, feedback and scoring, and keeping the thinking in a Project so it outlasts the conversation. --- # Design training Start from what people need to do differently, never from the content someone wants to cover. Two bodies of work shape this guide: - **Benjamin Bloom**: objectives written at a level of thinking, with practice and scoring at that same level, and mastery reached through practice, feedback, correction and another try. See `references/bloom.md`. - **Julie Dirksen, *Talk to the Elephant***: the gap between knowing and doing. People are riders on elephants: the rider plans and reasons, and the elephant (feelings, habits, comfort, what everyone around them does) usually decides. Most training talks only to the rider. See `references/elephant.md`. Use these to think, not to lecture. Don't name a framework to the person unless they do. Ask the questions it raises in plain words. Work through the steps as a conversation, a few questions at a time, never as a form. A step the person has already answered needs no question. ## Keep the thinking in a Project Design work that lives only in a conversation is lost when the conversation ends, and the people the work answers to never see it. A Project keeps it: its brief holds the problem, the behaviors, the barriers and the objectives, next to the people it answers to, the source material behind it and the content it produces. Writing it down is part of designing it. - If the work already has a Project, find it with `list-projects-tool` and write into it as you go. - Otherwise, once you understand the problem (step 1), offer in a sentence to start a Project to hold it. If they agree, create it with `create-project-tool` following `plan-a-project`, and draft each section of the brief as the conversation answers it rather than all at the end. - If they'd rather not, carry on. Step 8 says what to give them instead. ## 1. Take the problem as they state it - Whatever they bring is the problem, whether it is a training need, a sales target, a fundraising goal or a product launch. Never call it out of scope or ask them to restate it as a training need. - If they haven't said what it is, ask in one short, open question, without offering examples. - Then ask what result they're after and how they'd know it moved: a number, where it stands today, and where they want it. ## 2. Find what people would do differently Ask what someone would be doing if this were solved, specifically enough that you could film it: who does what, in which situation. "Nurses recognize sepsis" is not filmable. "When a patient's vitals meet two sepsis criteria, the nurse escalates to the rapid-response team within 15 minutes" is. - Turn "understand", "be aware of", "appreciate" and attitudes into the actions that would show them. - If several behaviors come up, ask which few would move the result most, and plan for those first. ## 3. Find out why they don't do it already This is the step most requests skip, and it decides whether training will help. For each behavior, ask what gets in the way. Look in three places: - **Can they?** Do they know how, have they practiced it, can they do it under pressure? - **Does the situation let them?** Time, tools, the process, where they are when it matters, and what colleagues and leaders actually do. - **Do they want to, in the moment?** Do they see what it gets them, believe it works, feel confident, or does habit, fear or comfort pull the other way? `references/elephant.md` has the questions to ask for each. ## 4. Say what training can't fix Push back the way a trusted colleague would, never as a gatekeeper. - **When a barrier is in the situation**, such as no time, a broken tool, a process that rewards the opposite, or leaders who don't do it themselves, training alone won't move it. Say so once, plainly, naming that part. Then suggest what the organization could change, such as making the behavior easier, putting a prompt where the moment happens, or having leaders model it, and keep working on the parts training can move. - **When people already know what to do** and still don't do it, more information won't help. Say so, and design for practice, for seeing the value, and for habit instead. - **Ask, don't rule.** "What happens to someone who does this tomorrow?" tends to surface the real barrier faster than a verdict. - **Never refuse, and never make agreement a condition.** If they want to go ahead anyway, build the best version of what they asked for, and record the concern in the brief (step 8) so it isn't lost. - Don't blame the learners. If people aren't doing something, find out what makes it hard. ## 5. Write the objectives For each behavior, write one objective: who, an action you could observe, the situation, and how well. For example: "Given a deteriorating patient in the simulated ward, the nurse names two sepsis criteria and escalates within the scenario's 15-minute window." - **Pick the level of thinking the job needs.** Bloom's levels, from least to most demanding, are remember, understand, apply, analyze, evaluate and create. Most workplace results need apply, analyze or evaluate. If an objective reads as "remember", ask whether remembering is really the job. - **Feelings and values have levels too**, from noticing something to acting on a value without being asked. Values aren't taught by being told. They grow through practice, seeing others act on them, and seeing the payoff. - The levels are a guide, not a strict ladder. `references/bloom.md` has the verbs for each level and the caveats. ## 6. Choose what to build Match the practice to the objective's level and to the barrier, not to the content: - **Facts and terms someone looks up**: a Guide, read at the moment of need. Don't build practice for what people can look up. - **Applying a procedure in a place**: an Experience, with scenes of the real setting, hotspots for the steps, and questions at the decisions that matter. - **Judgment and talking with people**, such as de-escalation, feedback, sales or interviews: a Character to practice with, scored by a Report Type, with Goals for what the learner should achieve. When the Character has to cover set ground, such as an interviewer's topics, give it an Objective Set as its agenda. Guardrails on its Persona keep it in role and flag the moment a learner pulls it out. A Thread puts several Characters in order when the situation unfolds over more than one person. - **The feeling of the moment**, when pressure or emotion is the barrier: 360° scenes of the real place, and Characters who push back the way people do. - **Building up to mastery over time**: a Course that orders the items, locks each one until the one before is done, allows retries and adds a debrief. Put practice as close as possible to where the behavior happens, and make the scenario the one people actually face. ## 7. Plan practice, feedback and scoring From Bloom's mastery learning: practice, get feedback, correct, try again, until the standard is met. - **Score the objective itself.** A recall question can't show that someone can de-escalate. In a conversation, write one Measurable per behavior (`build-conversation`). In an Experience, put questions at the decisions and show the correct answer after each response (`build-experience`). - **Make feedback immediate and specific**: right after the attempt, about what they did, and what to do instead. - **Allow another try.** Retries in a Course, and a debrief after the items that matter (`assemble-course`). - **Set a demanding standard.** Mastery means most learners reach the objective, not that most pass a low bar. - **Check whether the result moved**, not only whether people finished. Compare learners' results (`review-results`) with the measure in the brief's Outcomes. ## 8. Write it into the brief When the work is in a Project, the brief is where this thinking lands. Draft each section from the conversation, show the person, and save it with `plan-a-project`. - **Outcomes**: the problem in their words, the measure with where it stands today and where they want it, then each behavior and its objective. - **Audience**: who the learners are, what they already know and do, what gets in the way today (from step 3), what they care about, and where and on what devices they'll practice. - **Requirements**: what must be covered, the limits (budget, devices, deadlines, policy), and anything outside the training the organization has agreed to change. If there are concerns from step 4 the person chose to set aside, add a section titled "Outside the training" that records them. If they chose not to keep it in a Project, give the same summary in the conversation before building.