$npx -y skills add Owl-Listener/inclusive-design-skills --skill cognitive-load-assessmentAssess and reduce cognitive load in interfaces, flows, and content. Use when designing or reviewing any multi-step process, complex form, dashboard, decision flow, or information-dense screen. Triggers on: cognitive load, too complex, overwhelmed, too many steps, decision fatigue
| 1 | # Cognitive Load Assessment |
| 2 | |
| 3 | Assess cognitive load across three dimensions and provide actionable |
| 4 | recommendations to reduce unnecessary burden on users. |
| 5 | |
| 6 | ## The Three Types of Cognitive Load |
| 7 | |
| 8 | **Intrinsic load** — complexity inherent in the task itself. |
| 9 | A tax return is intrinsically complex. You cannot simplify the tax code. |
| 10 | Focus: break into manageable steps, provide context, explain terms. |
| 11 | |
| 12 | **Extraneous load** — complexity added by the design, not the task. |
| 13 | Confusing navigation, unclear labels, inconsistent patterns, visual clutter. |
| 14 | Focus: eliminate ruthlessly. Every instance is a fixable design failure. |
| 15 | |
| 16 | **Germane load** — effort invested in the actual task. |
| 17 | This is the load you WANT. The user engaging with their real goal. |
| 18 | Focus: maximise this by removing the other two. |
| 19 | |
| 20 | ## Assessment Framework |
| 21 | |
| 22 | For each screen or step, evaluate: |
| 23 | |
| 24 | | Dimension | Low (good) | Medium (review) | High (redesign) | |
| 25 | |-----------|-----------|-----------------|-----------------| |
| 26 | | Decisions required | 0–1 | 2–3 | 4+ | |
| 27 | | Items to remember | None | 1–2 | 3+ | |
| 28 | | New concepts to learn | None | 1 | 2+ | |
| 29 | | Steps to complete | 1–2 | 3–5 | 6+ | |
| 30 | | Reading complexity | Plain language | Some jargon | Dense/technical | |
| 31 | | Visual complexity | Clean, focused | Moderate | Cluttered | |
| 32 | |
| 33 | **If any dimension rates High, that screen needs redesign before launch.** |
| 34 | |
| 35 | ## How to Assess |
| 36 | |
| 37 | 1. Walk through the flow as a user who is tired, stressed, and unfamiliar |
| 38 | 2. At each screen, count: decisions, things to remember, new concepts |
| 39 | 3. Note where you pause, re-read, or feel uncertain — those are load spikes |
| 40 | 4. Map the load type: is the difficulty intrinsic or extraneous? |
| 41 | 5. Recommend specific reductions for each extraneous load source |
| 42 | |
| 43 | ## Reduction Strategies |
| 44 | |
| 45 | - **Progressive disclosure:** show only what the current step needs |
| 46 | - **Smart defaults:** pre-select the most common option |
| 47 | - **Chunking:** group into sets of 3–5 related items |
| 48 | - **Recognition over recall:** show options, don't make users remember |
| 49 | - **Persistent context:** show key selections throughout a flow |
| 50 | - **One primary action per screen:** de-emphasise secondary actions |
| 51 | |
| 52 | ## Output Format |
| 53 | |
| 54 | Present the assessment as a screen-by-screen table showing load ratings, |
| 55 | followed by prioritised recommendations sorted by impact. |