augmented skill · Stage 05

Cognitive-load metric interpretation

Cognitive-load metric interpretation is the discipline of clicks-to-goal as diagnostic, not verdict. It helps a designer shape information into a structure people can understand and navigate while keeping the final judgment traceable and human-owned.

This skill supports reliable work in Experience Architecture and prevents speed from being mistaken for quality.

Stage outcome

Structure the shortlisted concept into navigable, cognitively sound information hierarchy

01

Frames cognitive-load metric interpretation against a clear goal, relevant evidence, and the stage quality gate.

02

Directs AI with scoped inputs, reviews uncertainty, and redirects weak or unsupported output.

03

Documents the decision, trade-off, correction, or override so another designer can follow the reasoning.

Apply this skill before the Stage 05 gate is approved. The accountable designer must be able to explain how it changed the work, what evidence was considered, and why the result is safe to advance.

Common failure patterns

  • Accepting a structure that is mechanically efficient but cognitively or culturally unintuitive.
  • Accepting fluent or high-confidence output without testing its evidence, assumptions, exclusions, and downstream effects.
  • Recording the final artefact while omitting the rejected option, correction, trade-off, or override that explains the decision.

Use it on the work you already have.

Take one current experience architecture artifact. Apply cognitive-load metric interpretation for five minutes, then record one AI contribution, one human correction, and the evidence that justified the final decision.

  • A reviewed sitemap, taxonomy, content model, or simplification record showing the skill in use.
  • A short rationale linking the decision to evidence, risk, and intended outcome.
  • An example of an AI suggestion that was corrected, rejected, or deliberately accepted.

Leadership assessment questions

01

Can the designer demonstrate cognitive-load metric interpretation on a real experience architecture decision?

02

What observable evidence distinguishes competent performance from confident explanation?

03

Which anchor skill depends on this capability, and how would a gap surface in delivery?

01 · Prompting

Can use cognitive-load metric interpretation with a defined task, suitable inputs, and a basic validation check.

02 · Directing

Can diagnose weak output, redirect the work, combine sources, and explain the resulting trade-off.

03 · Orchestrating

Can decide when not to delegate, own the human checkpoint, and remain accountable for the outcome.