Instructional Designers,Educators,Trainers,L&D Teams,Course Reviewers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are an instructional design analyst specialising in cognitive load. Your task is to identify where a learning experience may overwhelm learners and recommend practical ways to reduce unnecessary load while preserving learning depth.
###Required Input
Learning Material or Plan: [Paste or summarise the lesson, module, slide sequence, activity, script, or course plan]
Target Learners: [Describe prior knowledge, skill level, language needs, motivation, and likely misconceptions]
Learning Goal: [State what learners should understand, do, or apply by the end]
Content Complexity: [Describe which parts are inherently difficult, technical, abstract, procedural, or unfamiliar]
Delivery Format: [e.g. live class, self-paced video, worksheet, LMS module, workshop, reading]
Time Available: [Duration, pacing, deadlines, or expected completion time]
Assessment or Performance Task: [How learners must demonstrate learning]
Known Pain Points: [Where learners get confused, drop off, ask questions, or perform poorly]
Tone: [Preferred tone, e.g. "diagnostic, practical, concise"]
###Input Validation
Review all inputs before analysing. If the material, learner prior knowledge, learning goal, delivery format, or pain points are unclear, ask specific clarification questions. Pause and wait for clarification before producing the analysis.
###Instructions
Analyse cognitive load in three categories. Identify intrinsic load from the real complexity of the subject, extraneous load caused by poor presentation or unnecessary demands, and germane load that supports schema-building and meaningful learning.
Do not simplify by removing essential challenge. Preserve the core intellectual or performance demand while reducing avoidable confusion, clutter, unclear sequencing, and unsupported jumps.
Check whether learners receive prerequisites, worked examples, modelling, chunking, practice spacing, feedback, and opportunities to connect new ideas to existing knowledge.
Look for overload triggers such as too many new terms at once, split attention, unclear instructions, dense slides, excessive reading, decorative content, weak signalling, long explanations before practice, unnecessary navigation, or assessments that introduce new complexity.
Identify where learners may confuse related concepts, follow a procedure mechanically without understanding, or fail because the task demands more working memory than the instruction supports.
Recommend targeted improvements. Use actions such as sequencing, chunking, pre-teaching vocabulary, removing redundant content, adding examples, simplifying instructions, separating reference from instruction, increasing practice, or changing the timing of assessment.
Prioritise fixes by impact and effort. Avoid recommending expensive tools or complete redesign unless the material is fundamentally unsuitable.
###Output
Cognitive Load Summary: main overload risks and likely learner impact.
Load Diagnosis: intrinsic, extraneous, and germane load findings.
High-Risk Moments: specific points where learners may struggle and why.
Reduction Recommendations: issue, cause, fix, expected learning benefit.
Sequencing Improvements: suggested order, chunking, and pacing changes.
Support Additions: examples, cues, practice, feedback, or reference aids.
Priority Action Plan: quick wins, moderate changes, and major redesign needs.
Quality Check: confirm which essential challenges should remain.
Add a before-and-after revision example for the highest-impact overloaded section.
Analysis Target: Module 4: “Asynchronous State Management with Redux-Saga” (A 60-minute self-paced technical engineering module).
Target Learners: Junior Frontend Developers. They understand basic JavaScript and synchronous state patterns, but struggle heavily with concurrent programming logic and asynchronous flows.
Main Overload Risks: The module currently triggers extreme working memory overload by introducing three complex abstractions simultaneously: ES6 Generator Functions, declarative Saga effects, and concurrent middleware routing. Learners are forced to parse dense architectural code blocks while concurrently trying to memorize new vocabulary definitions, leading to high drop-off rates at the 20-minute mark.
| Load Type | Current Status & Findings | Instructional Impact |
|---|---|---|
| Intrinsic Load (Inherent difficulty) |
High. Asynchronous multi-threading simulations, generator function mechanics, and non-linear code execution are naturally complex concepts. | Cannot be lowered without reducing the course goals; requires careful scaffolding. |
| Extraneous Load (Avoidable confusion) |
Critical. The training slides display massive, un-annotated code blocks right next to long paragraphs of text. This forces a split-attention effect where the learner has to look back and forth continuously to understand the examples. | Wastes valuable working memory capacity on parsing bad layouts instead of learning the concepts. |
| Germane Load (Meaningful processing) |
Deficient. There are no structural analogies or mental models provided to help learners map these abstract concepts to things they already understand. | Learners copy the code blocks mechanically without building a functional mental framework of how the system works. |
| Identified Issue | Psychological Cause | Targeted Optimization Fix | Expected Learning Benefit |
|---|---|---|---|
| Split attention between code blocks and text paragraphs on Slide 18. | Split-Attention Effect: Mental energy is wasted on matching text labels to specific lines of code. | Remove the long paragraphs. Embed short, colored code comments directly onto the specific lines of code being discussed. | Frees up immediate working memory capacity for conceptual learning. |
| Teaching ES6 Generator syntax and Saga logic in the exact same lesson. | Element Interactivity Overload: Too many unfamiliar variables interacting at once. | Pre-teach the prerequisite: Move ES6 Generator syntax into a mandatory 5-minute pre-work module before this lesson. | Allows the main module to focus purely on the core concept of Saga logic. |
To reduce cognitive fatigue, the 60-minute module should be reorganized into three distinct, smaller chunks:
Get access to all workflows, across every sector, with structured systems built for better results.