AI / Design Communication & Image Prompting
Cognitive Load in a Form
Count how much a user has to remember and decide on one form
Here is my form design: [field list and grouping]. Review it for cognitive load: 1) Count how many pieces of information the user must hold at once, and point out where that exceeds 3; 2) Which fields can be deferred, merged, or filled in by the system; 3) Which choices require looking something up elsewhere before they can be answered; 4) When do validation errors appear, and would they wipe out what has already been entered; 5) Reclassify the fields as required / can be added later / can be removed. Finally, give a trimmed field order and say what replaces each removed field.
How to use
With fewer than 6 fields this can overcomplicate a simple form — count them yourself before asking.
Good for
- The form keeps growing and conversion is dropping but you do not know which field to cut — 'how many things must be held at once' and 'which choice requires looking something up' locate the real burden instead of cutting by feel.
- When you need to argue in review that a field can go — that requires saying what replaces it, or the cut reads as laziness.
Not for
- The form has three to five fields — forcing a cognitive-load analysis overcomplicates a simple form for very little gain.
- The fields are mandated by compliance or legal — only order and helper text are adjustable; deleting a field is not on the table.
Example
Input
Account-opening form: name, national ID, mobile number, verification code, occupation (40-item dropdown), monthly income bracket, referrer code (optional), accept terms
What you get
Counts the simultaneous burdens first: the 40-item occupation dropdown, the income bracket, and the referrer code all demand attention at once, past the three-item mark. Defers occupation and income until after the account exists, and has the referrer code auto-filled or collapsed. Specifies the error timing — validate the ID on blur without wiping entered values. Gives the reordered field sequence and notes that the removed occupation field is replaced by a later profiling prompt.
Common mistakes
- Treating 'many fields' as identical to 'heavy cognitive load' — the real problems are usually field order (asking the hardest question first) and where the answer comes from (needing to look something up), not the count.
- Asking only for fields to be deleted without asking what replaces them — the flow breaks, the field comes back, and you pay for a second rework.
Try tweaking it like this
- Replace 'count what must be remembered' with 'simulate the user's state of mind at the fourth field' — walking the flow surfaces the drop-off point better than counting does.
- Add 'give the mobile keyboard type and the number of input-method switches' — extends cognitive load into real typing cost and makes the review case stronger.