Clarity First
Progressive disclosure intake experience reducing cognitive load during enrollment.
the idea
Applications drop people into high-stakes forms without preparation.
People arrive under stress and are immediately asked to interpret requirements and hand over sensitive information.
People arrive under stress and are immediately asked to interpret requirements and hand over sensitive information.
The core issue isn't complexity.
It's the lack of orientation before interaction begins.
The Principle
Sequencing is a product decision.
Helping people understand what's about to happen is often as important as simplifying what happens next.
The System
A pre-application orientation layer designed to reduce uncertainty before form entry.
.png)
01 — Orientation
Explains what the application is, what it involves, and what is required.
02 — Expectation Setting
Surfaces time, steps, and required materials upfront.
03 — Staged Intake
Breaks information into sequential steps to reduce cognitive load.
04 — Guided Entry
Transitions users into form completion with contextual support.
Explains what the application is, what it involves, and what is required.
02 — Expectation Setting
Surfaces time, steps, and required materials upfront.
03 — Staged Intake
Breaks information into sequential steps to reduce cognitive load.
04 — Guided Entry
Transitions users into form completion with contextual support.
Key Design Decisions
Four choices that shaped the system.
01 — Orientation as Readiness, Not Instruction
Context comes first, not a how-to.
Context comes first, not a how-to.
.png)
.png)
02 — Scope made visible early
Time and requirements shown before commitment.
Time and requirements shown before commitment.
03 — Sequential Disclosure
One decision at a time, not all at once.
One decision at a time, not all at once.
04 — Entry as transition
Onboarding eases users in rather than dropping them into a form.
Onboarding eases users in rather than dropping them into a form.
.png)
testing the concept
Tested with 3 interviews on expectations, confidence, perceived workload, and trust.
What design Improved
- Confusion about what happens next
- Pacing and step-by-step overwhelm
- Uncertainty about time and effort required
What remained
- Doubts about eligibility
- Questions about why information is collected
- Trust in the institution itself
The finding
Orientation improved readiness. It didn't resolve trust and it was never going to.
Procedural uncertainty reduced
Institutional uncertainty surfaced
Orientation ≠ trust
Institutional uncertainty surfaced
Orientation ≠ trust
"If these three screens weren't here and the application started immediately, I'd feel lost. I'd dread going into it because I wouldn't know how long it would take or what I needed."
Reflection
Reducing cognitive load isn't just about simplifying interfaces.
Uncertainty isn't one problem. The prototype reduced procedural uncertainty: people better understood what would happen, what they'd need, and how much effort was involved. But it couldn't resolve institutional uncertainty around eligibility, data collection, or trust.
Future iterations would explore greater transparency around why information is collected and how eligibility decisions are made.
The biggest takeaway: helping people build a mental model comes before asking them to act.