L&D MOJO
Get your L&D MOJO back.
Machine-Orchestrated, Judgment-Owned
What Is MOJO?
L&D MOJO is an AI production pipeline for instructional design. A training request runs through a disciplined workflow: diagnosed, designed, produced, independently quality-audited, and documented, with you making every call that matters along the way.
It's one skill, installed as one file. Inside it, six instructional design specialists take a training request from root-cause diagnosis to publish-ready deliverables in hours instead of weeks, an independent Auditor checks every phase's work against its sources, and a built-in Coach teaches you the craft as the project moves. They work the way a well-run studio does: in parallel where possible, pausing for your direction where judgment matters. You experience it all as one natural conversation.
MOJO is not AI replacing your team. It's the opposite. The name says it plainly: Machine-Orchestrated, Judgment-Owned. The machine runs the production grind of formatting, first drafts, paperwork, and consistency checks. Your team owns every judgment: understanding the business, building stakeholder relationships, making creative calls, and deciding what "good" means in your organization. One instructional designer with MOJO works like a designer with a full production team behind them.
| You bring | MOJO produces |
|---|---|
| A training request, in plain language | A root-cause diagnosis that confirms training is even the right answer |
| Whatever source material you have (or none) | A design blueprint grounded in learning science, with the reasoning shown |
| Your judgment at three checkpoints | Publish-ready scripts, job aids, interactions, assessments, and a rollout plan |
| Your brand, if you have one | Deliverables that look like a design team made them |
The Philosophy
Every MOJO project runs on one principle:
You are the Content Director. MOJO is your production team.MOJO never decides whether training is the right answer, what ships, or what "good" looks like for your organization. You decide that. It brings you evidence, options, and a recommendation with its reasoning shown. Then it does exactly what you direct, at production speed.
This shows up in concrete ways:
- Checkpoints, not surprises. The pipeline pauses at three gates: after planning, after design, and before final handoff. Each presents what it found in four skimmable lines. Nothing proceeds without your go-ahead. Even in overnight mode, every decision is written down for your review.
- Reasoning, always. Every recommendation comes with its "why." Every judgment call carries a confidence tag. A decision log records what was decided, by whom, and on what basis for the life of the project.
- Honesty about gaps. MOJO never invents numbers, quotes, or facts. When it doesn't know something, it marks the spot and asks. You'll see flags like "needs your input" rather than confident-sounding fabrication.
What's Included
- mojo-ld.skill. The complete pipeline in one file: six instructional design specialists, the independent Auditor, the built-in Coach and its curriculum, the three-phase workflow, the three autonomy modes, the quality standards, and the governance rules that keep you in charge.
- A starter sample project. A realistic source-document set with a one-line prompt, built for a first win in about 30 minutes.
- This manual. Everything you need to run, direct, and customize MOJO.
- The project dashboard. Every project beyond a quick one-off generates a visual dashboard right in the project folder. See The Dashboard.
- Deliverable formats for 7+ authoring tools. Scripts arrive copy-paste-ready for your LMS, Articulate Rise, video tools like Vyond, Synthesia, and Camtasia, PowerPoint for facilitated sessions, and self-contained interactive HTML.
Install in 2 Minutes
Open Claude Cowork
MOJO runs inside Cowork, the desktop workspace in the Claude app. If you use Claude already, you have it.
Install the skill file
Open mojo-ld.skill and click Save skill. You can also add it under Settings → Capabilities. One file, one click, done.
Pick a project folder
Point Cowork at any folder on your computer. Every MOJO project keeps its files there, organized and yours: deliverables, decisions, and the dashboard.
Once installed, MOJO is available in every Cowork conversation. No accounts, no servers, no per-seat platform fees beyond your Claude subscription.
Your First Project
The fastest first win is the starter project in your download: copy the sample-project folder into your connected folder, open RUN-THIS-FIRST.txt, and use the one-line prompt inside. You'll see the whole pipeline, including a diagnosis with a twist, in about half an hour.
Or just say what you need, in your own words:
MOJO opens with a short, natural conversation rather than a form. It will ask:
- Have you done instructional design before? Answer honestly; there's no wrong answer. Experts get framework names and shorthand. Newcomers get plain language with the theory available on request. You can switch styles any time by saying so.
- Where does your project information live? Files in the folder, a connected tool, or just your description. You can start with nothing but an idea.
- How hands-on do you want to be? Step through it live, or hand it off and review when it's done. See Three Ways to Work.
Then it gets to work. A few minutes later you'll hit your first checkpoint, with a diagnosis in hand.
Your AI Team
MOJO staffs every project with nine roles. You never manage them individually. The pipeline coordinates them, running roles in parallel when the work allows, and scales them down on small projects so process never outweighs the work.
The crew: workflow, quality, and growth
These three run on every project:
The Orchestrator
Runs intake, sizes the project so process never outweighs the work, coordinates every role, keeps the project record straight, and renders your dashboard.
The Auditor
Independently checks every phase against MOJO's quality standards, including full accessibility review. No other agent can talk it into passing something. Reports honestly and never blocks. You decide what ships.
The Coach
Teaches the craft while you work, at whatever depth you want, and steps back as your competence shows. See Coach Mode.
The six L&D specialists
These carry the instructional design expertise:
The Diagnostician
Finds the real problem before anyone builds anything, including telling you when training isn't the answer and something cheaper will work better.
The Analyst
Builds a right-sized measurement plan, from a simple reaction check to full ROI analysis, and refuses to build measurement theater your project doesn't need.
The Executive Partner
Turns the analysis into briefs your leadership will actually read: the ask in the first sentence, evidence below the fold.
The Architect
Designs the learning experience with a named learning-science principle behind every choice: objectives, structure, practice, and scaffolding.
The Maker
Writes the actual content: scripts formatted for your exact authoring tool, job aids, interactions, and imagery. Copy-paste ready, never "adapt as needed."
The Translator
Translates any deliverable into any language with format preserved and zero creative liberties taken with your content.
How a Project Flows
Every project moves through three phases, each ending in a checkpoint where you're in the driver's seat:
Planning Gate 1
The Diagnostician finds the root cause and confirms training is the right intervention. The Analyst builds a right-sized measurement plan. The project gets sized so documentation stays proportionate.
Your call at Gate 1: the format (eLearning, live session, video, or job aid) and the authoring tool it should be built for.
Design Gate 2
You set creative direction in one conversation: look and feel, imagery style, gamification, and whether you want a companion workbook. Then the Architect designs the full learning experience while the Executive Partner drafts your stakeholder brief, in parallel. When you provided source documents, the design comes with a content coverage matrix: every objective mapped to the exact document and section that supports it, and every gap flagged as a question for your SME instead of an invented fact. Gaps become a ready-to-send SME interview guide on request.
Your call at Gate 2: approve the blueprint before anything gets built on top of it.
Production Gate 3
The Maker produces every deliverable, formatted for your chosen tool. A deployment plan comes with it, because content without a rollout plan is shelf-ware. The Auditor runs the final quality and accessibility review.
Your call at Gate 3: ship it, request fixes, or add bonus formats such as a scored assessment, an LMS-ready SCORM package, a translation, or a standalone web page.
Change your mind later? Tell MOJO. It reruns the affected piece rather than the whole project, flags anything downstream that's now stale, and logs the change.
Checkpoints, Not Homework
Every checkpoint uses the same four-line shape, designed to be read in fifteen seconds. You can always dig into the full detail, but you never have to in order to make the call:
What we found: The real gap is that reps can't find the return-policy exceptions fast enough on a live call. They pass the policy quiz at 94%. This is a "can't find it in the moment" problem, not a knowledge problem.
What this means for you: A searchable job aid will fix this faster and cheaper than a course would.
Your call: Build the quick-reference job aid (my recommendation), or do you still want the full eLearning module?
Options: Job aid it is / Do the full module / Show me the details / I have concerns
Notice what's happening there. The verdict comes with its evidence, and the recommendation is stated plainly rather than hidden behind neutral options. MOJO regularly recommends against building the bigger, more impressive-sounding thing, because the evidence points somewhere cheaper. That's the Diagnostician doing its job.
Three Ways to Work
| Mode | How it feels | Best for |
|---|---|---|
| Interactive (default) | MOJO pauses at every checkpoint and asks about creative direction before designing. You co-pilot the whole way. | New content types, projects where you have strong ideas, learning the system |
| Agentic (overnight) | You hand it off. MOJO runs all three phases end to end, makes the best-supported call at each decision point, and writes down every decision, its reasoning, and exactly what to double-check. You come back to finished work plus a one-page handoff summary that leads with anything deserving a second look. | Batch work, familiar content types, running projects while you focus elsewhere |
| Hyper Speed | Same deliverable quality and the same checkpoints, but the internal paperwork shrinks to a single planning doc and obvious calls get made in one line instead of a discussion. | Clear briefs with a known format, when you want speed but still want to be asked |
Autonomous never means unaccountable. In Agentic mode, every gate produces a written report: what was decided, why, what the quality check found, and a "check this first" pointer for the two-minute reviewer. The work runs without you. The record reads like you were there.
The Dashboard
Every project beyond a quick one-off generates a visual dashboard: one file in your project folder, no login, no server. Double-click it any time to see:
- The pipeline at a glance. All eight stages from intake to final packaging, each marked done, in progress, or needs-attention.
- Click any stage to see what happened there in plain language: what was produced (with links to every file), the decisions made with their reasoning and confidence levels, and any flags raised.
- The deliverables table. Every finished file, what it is, and a link. The permanent answer to "where's my stuff?"
- What you gave MOJO. A summary of your original ask and source material, so anyone joining the project later can orient in one minute.
- Waiting on you. One consolidated list of anything that needs your input, each linked to the exact spot.
The dashboard updates automatically at every phase and checkpoint. It's also built to be shown: clean enough to share with a stakeholder who asks "where are we on the training project?"
Sized to the project
The dashboard scales with the work. A quick one-off (a single job aid, a fast edit) skips it entirely; the few-line project log is the whole story. A small project gets a compact, single-view version. Multi-deliverable projects get the full interactive dashboard with clickable stages. Process never outweighs the work.
Where Everything Lands
Every project keeps the same clean structure, so you always know where to look:
| Location | What lives there |
|---|---|
input/ | Your source material, plus a one-page summary of what you provided |
output/dashboard.html | The visual project dashboard |
output/deliverables/ | Everything you ship: briefs, blueprints, scripts, job aids, interactions, images, web page, deployment plan |
output/process/ | The paper trail: diagnosis, measurement plan, audit results, checkpoint reports, decision log, change log |
Nothing is a black box. Six months from now, when someone asks "why did we build this as a job aid instead of a course?", the answer is in the decision log with the date, the evidence, and who made the call.
Built-In Quality
Quality in MOJO isn't a final-step review. It's enforced at every phase, on every deliverable, by standards baked into every role:
- Three named quality bars. Every project is checked for accuracy and truthfulness (the TRUST Standard), experience and retention (the Engagement Standard), and craft and outcomes (the Excellence Standard). The Auditor applies them, and the results appear at your checkpoints.
- Accessibility is non-negotiable. Every visual deliverable meets WCAG 2.1 AA: real contrast ratios, alt text, keyboard navigation, captions specced for video, and information never carried by color alone. This check runs on every project, no matter how small.
- Zero fabrication. When MOJO doesn't have a real source for a number, it writes "needs your input" instead of inventing one. Stakeholder documents never look more certain than the evidence allows.
- Confidence tags. Judgment calls are labeled HIGH, MEDIUM, or LOW confidence, so you know which conclusions rest on solid evidence and which deserve a skeptical read.
- Right-sized process. A one-page job aid doesn't generate a 40-page paper trail. Projects are tiered at intake, and documentation scales with the stakes.
The Learning Science
MOJO's specialists work from the same evidence base a well-trained L&D team does. It's applied automatically, cited in the reasoning, and explained in plain language whenever you want it:
| Where | Grounded in |
|---|---|
| Diagnosis | Mager & Pipe performance analysis, COM-B, Action Mapping, the 5 Moments of Need |
| Design | Cognitive Load Theory, Mayer's multimedia principles, Bloom's Taxonomy, scaffolding, spaced retrieval practice, adult learning principles |
| Measurement | Kirkpatrick and Phillips ROI, combined into a six-level model that's applied only as deep as your project justifies |
| Engagement | Self-Determination Theory and Flow Theory: gamification with guardrails, never points for the sake of points |
| Visuals | Professional visual design standards plus accessibility research (Mayer, Tufte, Gestalt principles, UDL) |
The difference from reading about these frameworks: MOJO actually applies them, on every project, and shows its work. Every design choice in the blueprint names the principle behind it.
Make It Yours
Your brand
Share your style guide, or answer a few quick questions and MOJO builds a lightweight brand profile with you. Either way, every deliverable in every project uses it: colors, fonts, tone, layout. Set it once, reuse it forever.
Your organization's context
Drop reference documents into any project (style guides, compliance requirements, product documentation, past courses) and MOJO works from them. Its zero-fabrication rule means your real material always beats its assumptions.
Your tools
MOJO formats output for the tool you actually use. Seven formats are built in. When your tool isn't one of them, tell MOJO what it needs and it will define and remember a format for it.
Your working style
Expert or plain-language explanations, hands-on or overnight autonomy, coaching on or off, personality or strictly business. All adjustable per project, mid-project, any time, just by saying so.
Bonus Formats
At the final checkpoint, or any time you ask, MOJO can extend a finished project with:
- An LMS-ready SCORM package. The whole course as a SCORM 1.2 zip that uploads straight to your LMS, with completion and score tracking working out of the box. MOJO tells you exactly how to verify it in your LMS or SCORM Cloud before you distribute it.
- A scored assessment, formatted for direct import into your LMS.
- A translation into any language: 100% fidelity, format preserved, nothing "improved" in transit.
- A standalone web page. The whole course as one polished, interactive, accessible page you can host anywhere or embed in your existing site, with plain-language hosting instructions included.
- A companion workbook. A fillable transfer tool where learners apply every concept to their own real situation, not a hypothetical.
And one bonus you don't have to ask for: every project closes with a time receipt. Three lines showing the industry-grounded traditional estimate for work of that size, the actual time your run took, and the hours you got back. It's the number you show whoever asks whether the tool was worth it, and a full per-phase efficiency report is available on request.
Coach Mode
MOJO can teach you instructional design while it works. Think of it as a working apprenticeship, at whatever intensity you choose:
- Off: just do the work. (Default for experienced practitioners.)
- Available: occasional short "here's why" notes at natural moments, with more depth on request. (Default when you're newer to the field.)
- Active: a working apprenticeship. MOJO explains its reasoning as it goes, asks what you would do before revealing its recommendation, and gradually hands you more of the thinking as your judgment develops.
Say "turn on coaching," "explain that more simply," or "why did you choose that?" at any point. The scaffolding fades as you grow, by design.
Scaffolding that fades
Good teaching steps back as competence grows, and the Coach is built that way. Within a project, when you start anticipating its explanations or making the calls correctly before it comments, it offers to step down a level. Nothing about you is tracked or logged between projects; the Coach reads how you're doing from the conversation you're actually having, and direct questions ("why did you choose that?") always get a real answer at any level.
FAQ
Is this going to replace instructional designers?
No, and it isn't trying to. MOJO automates the production layer: drafting, formatting, consistency checking, and paperwork. The judgment layer stays human. Knowing the business, reading stakeholders, deciding what "good" means, and making the creative call all route to you, because MOJO is built to ask rather than assume. Teams that use it well produce more designer-led projects, not fewer.
Do I need to be technical?
No. If you can describe what you need in plain language, MOJO handles the rest. Installation is opening one file and clicking Save.
What do I need to run it?
A Claude subscription with access to Cowork (the desktop app), and a folder on your computer for project files. That's the whole stack.
How big a project can it handle?
MOJO sizes every project at intake, from a single job aid it turns around in minutes to a multi-module course it runs as a full overnight production. The size sets how much process you get: small requests skip the paperwork and get straight to the deliverable, while bigger projects earn the full audit trail, dashboard, and gate reports. A quick request finishes in minutes; a full course build is an overnight job, and the depth is the point.
Where does my content live?
In your project folder, on your computer, in ordinary files you can open, move, and back up. MOJO doesn't run on a third-party server and doesn't hold your content.
What if MOJO gets something wrong?
Tell it. It reruns the affected piece, flags anything downstream that's now stale, and logs the correction. Because every claim is either sourced or flagged as needing your input, errors tend to surface at checkpoints rather than after launch.
Does it work with my authoring tool?
Scripts come formatted for generic LMS/SCORM, Articulate Rise, Vyond, Synthesia, Camtasia, PowerPoint, and self-contained HTML out of the box, and MOJO can package a finished course as a SCORM 1.2 zip that uploads straight to your LMS with completion and score tracking working. Different authoring tool? MOJO will define a format for it with you and remember it.
Can my whole team use it?
Each team member installs the skill file in their own Claude Cowork (the Team license covers up to 10 seats and includes a step-by-step team setup guide). Projects live in shared folders when you want shared visibility, a shared brand profile keeps ten people producing like one studio, and the dashboard makes handoffs between teammates clean.
Support
The MOJO Framework is built and maintained by Todd Stone Consulting, an AI Workflow & Strategy practice. Stop guessing. Start using AI that actually works.
- Product page and purchase: toddstoneconsulting.com/mojo/
- General questions and support: toddstoneconsulting.com
- Want MOJO tailored to your organization? Brand integration, custom tool formats, compliance requirements, and team training are consulting work we do every week. Reach out through the site.