An instructional designer exists to make learning happen by design rather than by\nluck — to take a performance gap (people can't do something they need to do) and\nengineer an experience that closes it, usually without ever meeting the learner. The\nwork lives where a subject-matter expert who knows everything meets a learner who\nknows nothing and has forty minutes and a screen. The designer decides what gets cut,\nwhat gets shown, in what order, and how anyone will know it worked.
\n","wordCount":83},{"heading":"Core Mission","id":"core-mission","markdown":"Produce the smallest, most usable learning experience that reliably moves a defined\naudience from \"can't\" to \"can\" on a behavior that matters to the organization, and\nprove it with evidence rather than smile sheets.","html":"Produce the smallest, most usable learning experience that reliably moves a defined\naudience from "can't" to "can" on a behavior that matters to the organization, and\nprove it with evidence rather than smile sheets.
\n","wordCount":34},{"heading":"Primary Responsibilities","id":"primary-responsibilities","markdown":"The visible deliverable is a course, a module, a job aid, a video; the actual work is\nanalysis and ruthless subtraction. An instructional designer runs needs and audience\nanalysis to confirm training is even the right fix (often it isn't); writes measurable\nlearning objectives that anchor everything downstream; designs assessments before\ncontent so the course teaches to the test that matters; storyboards and sequences\nmaterial to respect a tiny working memory; partners with SMEs to extract and prune\ntheir knowledge; builds in authoring tools and hands off to media and LMS teams;\npilots, gathers data, and revises; and evaluates whether the thing changed behavior on\nthe job, not just whether learners liked it. Underneath it is a constant fight against\nthe default failure: a content dump dressed up as a course.","html":"The visible deliverable is a course, a module, a job aid, a video; the actual work is\nanalysis and ruthless subtraction. An instructional designer runs needs and audience\nanalysis to confirm training is even the right fix (often it isn't); writes measurable\nlearning objectives that anchor everything downstream; designs assessments before\ncontent so the course teaches to the test that matters; storyboards and sequences\nmaterial to respect a tiny working memory; partners with SMEs to extract and prune\ntheir knowledge; builds in authoring tools and hands off to media and LMS teams;\npilots, gathers data, and revises; and evaluates whether the thing changed behavior on\nthe job, not just whether learners liked it. Underneath it is a constant fight against\nthe default failure: a content dump dressed up as a course.
\n","wordCount":131},{"heading":"Guiding Principles","id":"guiding-principles","markdown":"- **Training is the last resort, not the first.** Most performance gaps are caused by\n unclear expectations, missing tools, or broken incentives — none of which a course\n fixes. Diagnose before you build.\n- **Objectives are the contract.** If you can't write what the learner will be able to\n *do*, observably, you don't yet know what to build. Everything traces to the objective\n or it gets cut.\n- **Less content, more practice.** Coverage is the enemy of learning. People learn by\n doing the thing with feedback, not by being shown it.\n- **Design backward from the assessment.** Decide how you'll know they can do it, then\n build only what gets them there.\n- **Respect the working memory.** Attention is finite and novices overload instantly;\n every decorative element competes with the one that matters.\n- **Engagement serves learning or it's noise.** A delightful course that changes no\n behavior is expensive entertainment.\n- **The SME is a source, not the author.** Experts have forgotten what it's like not to\n know; your job is to translate their fluency into a beginner's path.","html":"Instructional designers rarely build alone. They extract from subject-matter experts\n(who own truth but not teachability), hand off to graphic designers, video producers,\nand developers (who own craft and production), coordinate with LMS administrators (who\nown delivery and data), and answer to a sponsor (who owns the performance problem and\nthe budget). The recurring friction lives at the SME handoff — the expert wants\neverything in, the designer fights for the learner — and at the sponsor handoff, where\n"make a training" hides an unexamined performance problem. The best designers manage\nSMEs like a journalist manages a source: extract, verify, prune, and protect the\naudience from the curse of knowledge.
\n","wordCount":109},{"heading":"Ethics","id":"ethics","markdown":"Instructional designers shape what people believe they know how to do, often in\nhigh-stakes settings — safety, compliance, medicine, finance. Duties: don't certify\ncompetence the assessment didn't actually verify; don't build training as cover for an\norganization's failure to fix a real problem (the \"we trained them\" liability shield);\nrespect learners' time by cutting everything that doesn't serve them; design for\naccessibility (WCAG, captions, screen-reader paths) so no learner is excluded; cite and\nlicense sources honestly; and tell the sponsor the truth when the answer is \"this isn't a\ntraining problem,\" even when they're paying you to build training. The gray zone —\ncompliance courses that exist to manage legal risk rather than change behavior — deserves\nto be named rather than quietly produced.","html":"Instructional designers shape what people believe they know how to do, often in\nhigh-stakes settings — safety, compliance, medicine, finance. Duties: don't certify\ncompetence the assessment didn't actually verify; don't build training as cover for an\norganization's failure to fix a real problem (the "we trained them" liability shield);\nrespect learners' time by cutting everything that doesn't serve them; design for\naccessibility (WCAG, captions, screen-reader paths) so no learner is excluded; cite and\nlicense sources honestly; and tell the sponsor the truth when the answer is "this isn't a\ntraining problem," even when they're paying you to build training. The gray zone —\ncompliance courses that exist to manage legal risk rather than change behavior — deserves\nto be named rather than quietly produced.
\n","wordCount":123},{"heading":"Scenarios","id":"scenarios","markdown":"**\"We need a course on the new expense system.\"** The requester wants a 60-minute module by\nmonth-end. The novice starts storyboarding. The expert runs a five-minute analysis: who's\nfailing at expenses, and why? The system isn't confusing — people just can't find the\napproval button, which moved. This isn't a skill gap; it's a UI discoverability gap with a\ntwo-minute fix: a tooltip and a one-page job aid showing the new location. The designer\nrecommends killing the course and ships the job aid. The hardest part is convincing a\nsponsor who already decided they wanted training.\n\n**A compliance module with a 100% pass rate and no behavior change.** Annual data-security\ntraining shows perfect completion and high satisfaction, yet phishing-click rates haven't\nmoved. Level 1 looks great; Level 3 is broken. The expert sees the design flaw: the course\ntells learners about phishing but never makes them *do* the discrimination task. The\nredesign replaces the lecture with a scenario simulation — learners triage real-looking\ninbox messages, get immediate feedback, and must hit a threshold on novel examples. The\nassessment now mirrors the job, and evaluation shifts to a tracked metric: simulated-phishing\nclick rate at 90 days. Learning is measured where it matters, not where it's easy.\n\n**Fuzzy request, impatient SME.** A startup wants onboarding training but can't say what\n\"good\" looks like; the SME is a brilliant engineer with no time who explains everything at\nonce. The expert abandons waterfall ADDIE for SAM: builds a rough one-screen prototype of the\nfirst task in a day, puts it in front of the SME and one new hire, and lets their reactions\nsurface the real objectives. Three rapid cycles later the scope is clear, the SME has\ncorrected the worst misconceptions by reacting rather than authoring, and nothing expensive\nwas built before the target was known.","html":""We need a course on the new expense system." The requester wants a 60-minute module by\nmonth-end. The novice starts storyboarding. The expert runs a five-minute analysis: who's\nfailing at expenses, and why? The system isn't confusing — people just can't find the\napproval button, which moved. This isn't a skill gap; it's a UI discoverability gap with a\ntwo-minute fix: a tooltip and a one-page job aid showing the new location. The designer\nrecommends killing the course and ships the job aid. The hardest part is convincing a\nsponsor who already decided they wanted training.
\nA compliance module with a 100% pass rate and no behavior change. Annual data-security\ntraining shows perfect completion and high satisfaction, yet phishing-click rates haven't\nmoved. Level 1 looks great; Level 3 is broken. The expert sees the design flaw: the course\ntells learners about phishing but never makes them do the discrimination task. The\nredesign replaces the lecture with a scenario simulation — learners triage real-looking\ninbox messages, get immediate feedback, and must hit a threshold on novel examples. The\nassessment now mirrors the job, and evaluation shifts to a tracked metric: simulated-phishing\nclick rate at 90 days. Learning is measured where it matters, not where it's easy.
\nFuzzy request, impatient SME. A startup wants onboarding training but can't say what\n"good" looks like; the SME is a brilliant engineer with no time who explains everything at\nonce. The expert abandons waterfall ADDIE for SAM: builds a rough one-screen prototype of the\nfirst task in a day, puts it in front of the SME and one new hire, and lets their reactions\nsurface the real objectives. Three rapid cycles later the scope is clear, the SME has\ncorrected the worst misconceptions by reacting rather than authoring, and nothing expensive\nwas built before the target was known.
\n","wordCount":311},{"heading":"Related Occupations","id":"related-occupations","markdown":"An instructional designer shares the learning focus of educators but works without a live\nroom, designing the experience rather than delivering it. Teachers teach the designed thing\nin real time and read a class the designer never meets. UX designers share the obsession\nwith reducing cognitive load and designing for a user's context — an e-learning screen is a\nUX problem. UX researchers supply the audience-analysis muscle the designer relies on.\nTechnical writers solve the adjacent problem of documenting how something works, often the\nbetter answer when the gap is reference, not skill.","html":"An instructional designer shares the learning focus of educators but works without a live\nroom, designing the experience rather than delivering it. Teachers teach the designed thing\nin real time and read a class the designer never meets. UX designers share the obsession\nwith reducing cognitive load and designing for a user's context — an e-learning screen is a\nUX problem. UX researchers supply the audience-analysis muscle the designer relies on.\nTechnical writers solve the adjacent problem of documenting how something works, often the\nbetter answer when the gap is reference, not skill.
\n","wordCount":94},{"heading":"References","id":"references","markdown":"- *Design for How People Learn* — Julie Dirksen\n- *Analyzing Performance Problems* — Mager & Pipe\n- *Multimedia Learning* — Richard Mayer\n- *The Conditions of Learning* — Robert Gagné\n- *Evaluating Training Programs* — Donald Kirkpatrick\n- *Leaving ADDIE for SAM* — Michael Allen","html":"