Cognitive Overload
Users were confronted with long forms containing inputs that were not yet relevant, increasing effort and making the flow harder to read.
Case Study // Insurance Underwriting
Reducing Cognitive Load in Complex Underwriting Workflows
How we helped a cloud-based insurance platform simplify a decision-heavy underwriting journey by sequencing conditional inputs, surfacing dependencies at the right moment, and making the workflow easier to navigate.
Underwriting workflow designConditional logicPrototype-led validation
Client
Leading Insurance Platform
Industry
Insurance / Enterprise Software
Duration
~3 months
Team Size
8 (cross-functional)
Underwriting Logic
Progressive Reveal
02Guided Flow
The Challenge
01Complex underwriting workflows were creating cognitive overload
Underwriters had to work through large, interdependent forms with little guidance on which questions mattered at each point in the journey.
The platform surfaced eligibility, risk, and dependency-heavy inputs too early, leaving users to interpret field relationships and underwriting rules for themselves.
Hidden Dependencies
Important field dependencies were buried in the interface rather than made explicit, so users had to carry too much workflow logic in their heads.
Inefficient Workflows
Without a clearer sequence through the journey, underwriters spent time navigating unnecessary inputs and second-guessing what came next.
Our Approach
02Reframing the underwriting flow around decision points and dependencies
Rather than treating the work as a visual redesign, we started with the structure of the underwriting journey: what decisions users were making, which inputs triggered new requirements, and when information needed to appear.
Because the rules were highly conditional, static wireframes could only go so far. We used a functional prototype to test sequencing, progressive disclosure, and interaction patterns against realistic underwriting scenarios.
Phase 01
Map Workflow Logic
We mapped the underlying structure of the underwriting journey, identifying key decision points, input dependencies, and conditional branches.
- Breakdown of form logic and field relationships
- Identification of conditional pathways
- Alignment on what information is required and when
Phase 02
Design Conditional Disclosure
We introduced a response model in which the interface reveals only the inputs and guidance required for the decision at hand.
- Progressive disclosure of fields
- Clear parent-child field relationships
- Removal of redundant or premature inputs
Phase 03
Prototype Real Workflows
Instead of relying on abstract artefacts, we built a working prototype to test the flow in conditions closer to real underwriting use.
- Interactive prototype reflecting real workflows
- Rapid iteration based on usage feedback
- Validation of logic, not just layout
Phase 04
Refine for Delivery
We iterated on the experience to balance usability with regulatory, operational, and engineering constraints before handoff.
- Simplified decision pathways
- Improved flow and sequencing
- Shared alignment across product, design, and engineering
Outcomes
03A clearer underwriting flow with less visible complexity
By the point of handoff, the prototype showed a more deliberate sequence through the underwriting journey, with less information exposed upfront and clearer logic built into the flow.
Outcome
Less Information Up Front
The redesigned flow reduced how much users had to process at any one moment, helping them focus on the decision in front of them.
Outcome
Dependencies Made Explicit
Inputs appeared in response to relevant answers, making relationships between fields clearer instead of leaving users to infer them.
Outcome
Clearer Progression Through The Journey
The experience guided users through the underwriting process in a more deliberate order, rather than presenting a flat form with hidden logic.
Outcome
Higher Confidence Before Build
Working in a functional prototype helped stakeholders align on the interaction model before committing engineering effort.
Key Learnings
04What the engagement reinforced
Structure shapes usability
In rule-heavy enterprise workflows, usability depends as much on how information is sequenced and revealed as it does on visual design.
Validate in context
For complex enterprise products, working prototypes provide more reliable signals than static wireframes alone.
Guide users through complexity
In decision-heavy workflows, the interface should reveal the next relevant step rather than expose the full rule set upfront.
Next Step
Need to simplify a complex enterprise workflow?
We help teams redesign decision-heavy journeys, align on the right interaction model, and reduce delivery risk before engineering build-out.