Active ExperimentTools

The Cognitive Load Budget

Can designers predict where an experience will become mentally expensive before users encounter it?

Last updated: August 2026
The Cognitive Load Budget

Hypothesis

"If cognitive load can be estimated during design, then the highest-friction moments in property owner onboarding should receive higher Cognitive Load Index scores—and redesigning those moments should reduce completion time, errors, hesitation, and perceived effort."

The Problem Space

Property owner onboarding often requires people to interpret unfamiliar terminology, make consequential financial and operational decisions, retrieve documents, move between systems, and remember what remains incomplete. The burden rarely comes from one difficult screen. It accumulates across the entire experience. Yet design teams often discuss cognitive load as a general concern without a practical way to identify where that burden is being created.

Current Approach

I’m developing a Cognitive Load Index that evaluates each onboarding task across six dimensions:

• Information — how much must be read and interpreted
• Decisions — how many meaningful choices must be made
• Memory — what the owner must remember or retrieve
• Ambiguity — how uncertain the expected response feels
• Context switching — how often the owner must leave the experience
• Recovery — how difficult it is to correct a mistake or resume later

Each dimension receives an initial score from 0–3. The combined score produces a predicted cognitive-load range for each task.

I will apply the framework to two versions of a property owner onboarding experience: a fragmented, conventional process and a guided, centralized redesign. Usability testing will then compare the predicted scores with observed completion time, errors, hesitation, clarification requests, context switching, and perceived effort.

The purpose is not to claim that cognitive load can be reduced to a perfect number. The experiment asks whether a transparent scoring model can help designers identify mentally expensive moments earlier and make more intentional decisions about where complexity belongs.

Iteration Timeline

December 2025

Initial Attention-Cost Model

The first model assigned fixed attention costs to interface elements such as fields, buttons, decisions, and context switches. This made cognitive load visible, but the values were arbitrary and treated every interaction as equally demanding.

January 2026

Context Changes the Cost

The same interaction can create very different levels of effort depending on the user, task, consequences, and environment. A banking field during owner onboarding, for example, carries more uncertainty and risk than a familiar field in account settings.

August 2026

From UI Elements to Task Demands

The framework shifted from pricing individual interface elements to evaluating complete tasks across six dimensions: information, decisions, memory, ambiguity, context switching, and recovery.

August 2026

Property Owner Onboarding Selected

Property owner onboarding was selected as the first test environment because it combines unfamiliar terminology, document retrieval, financial decisions, legal consequences, multiple systems, and several downstream users.

In Progress

Prediction and Validation

The next iteration will compare predicted Cognitive Load Index scores with observed completion time, errors, hesitation, clarification requests, context switching, and perceived effort.

Still evolving...

Current Insight

Complexity is not automatically harmful. Cognitive burden increases when people must interpret uncertainty, remember information across steps, leave the experience to retrieve something, or recover without clear guidance. The design opportunity is not to eliminate complexity, but to place it deliberately and help the system carry more of it.

Still Evolving

Open questions we're exploring:

  • Which Cognitive Load Index dimensions most closely correspond with observed user difficulty?
  • Should high-consequence decisions receive additional weight even when the interface itself is simple?
  • How should the model account for differences between first-time and experienced property owners?
  • Can a task receive a high predicted score while still feeling manageable because the system provides strong guidance?
  • Does reducing cognitive load for property owners create additional work or poorer information for the operational team?
  • How should emotional pressure be documented without presenting it as the same thing as cognitive load?

Artifacts & Resources

Framework

Cognitive Load Index

A six-dimension framework for identifying information, decision, memory, ambiguity, context-switching, and recovery demands within a user task.

Worksheet

Owner Onboarding Load Map

A task-by-task scoring worksheet for predicting where property owners are most likely to hesitate, make errors, request clarification, or leave the onboarding experience.

Prototype — Planned

Fragmented Onboarding Experience

A reconstructed baseline flow representing conventional owner onboarding across email, forms, document requests, agreements, and follow-up communication.

Prototype — Planned

Guided Onboarding Experience

A centralized onboarding flow using conditional logic, plain-language guidance, saved progress, document deferral, and visible completion status.

Research Plan — In Development

Prediction Validation Protocol

A usability-testing protocol comparing predicted load scores with task completion, errors, hesitation, context switching, clarification requests, and perceived effort.

Interactive Tool — Future Iteration

Cognitive Load Budget Calculator

A proposed calculator that will help designers score task demands, document assumptions, compare design versions, and revise predictions using testing evidence.

Related Experiments

Experiment Meta

Status

Active Experiment

Category

Tools

Last Updated

August 2026