Dynamic Intake

Redesigning online claim submissions

I designed a webtop and mobile interface to consolidate several existing channels into single funnel for existing online services platform.

View designs

Objective

1) Encourage adoption of this new platform
2) Decrease time to claim decision and effort to adjudicate claims
3) Develop the first, mobile first, native app within WSIB

My Role

As the UX Designer I was in charge of:
1) Evaluating current processes against market competitors.
2) Running and designing workshops to further understand hypothesis and assumptions.
3) Analyzing user testing results and iterating through various wireframes and prototypes.

Project challenges vs research methods

There were several challenges unique to this project which meant I had to take a different approach to research.

Challenge 1

Technology constraints

Complex automation rulesets in existing systems prevented any major changes.

Challenge 2

Process & Scope

Restrictions in changing and removing required fields due to business processes and scope.

Challenge 3

Limited data access

Limited access to users and their data due to privacy concerns.

Research methods

Here were the 3 types of workshops we decided to run to understand the problem space.

Telephone recordings & SME Interviews

Common themes and pain points were identified from different internal stakeholders

Analysis on past data

Past claim data provided me a initial base for card sorting and pin pointed me to problematic areas in the form

Question wording and comprehention

Running interviews allowed us to understand when questions were too complex and unclear

Research themes

Here is the summary of an internal usability audit, internal stakeholder interviews, and, and external user interviews.

Theme 1

Unclear Language in questions

Caused users to guess what was the right answer which created a lot of discomfort on a legal binding document.

Theme 2

Choices were confusing and hard to find

Options felt all the same to the users, creating additional  cognitive load on top of choice overload.

Theme 3

Repeating sections between documents

Multiple repeating sections asking for the same information in different forms caused users to start to lose trust.

Theme 4

Lack of flexibility

Submission process forced users to complete the form in one go and in a specific order.

Usability testing highlights

Here were the following key steps we took before we could ideate and implement the final design

1. Length of form

It took 30 minutes just to finish the introduction

Resolution

Consult business in further simplification of form, creation of an initial onboarding flow that can be done within minutes.

2. Users were lost

Two individual questions caused the highest task failure rates

Resolution

Conduct additional card sorting exercises to understand how external WSIB users would navigate and find items.

3. Lack of clarity of the overall process

Users didn't understand what happened after submission

Resolution

Create a brand new 3 step wizard status indicator, as well as improving the final confirmation screen to explain next steps.

Final solution highlights

Here are some of the key highlights of my final design

Removed barriers to completion

• Providing explanations and expectations of what information WSIB is looking for and why

Reduced cognitive load

• Getting to the bottom of what the business required, reducing choice overload and simplifying the necessary steps needed.

Using the power of defaults

• Encouraging users to create an account through different behavioral nudges.

Next steps

Key recommended steps to complete the project for a successful launch.

Incorporate behavioral insights

Develop clear understanding of key goals to create nudges to optimize the user flow.

Reevaluate mental models

The root cause of navigation problems was the misalignment of mental models of internal WSIB vs external users.

Develop key components

The form was designed to be modular, by going ahead and scaling slowly module by module, we can create more room for testing and iterations.

Key Learnings

Here were some of the key learnings I had from completing this project

1. Breaking down a project into scrums is critical

• Allow for full validation and understanding of critical hypothesis and design decisions.
• Increase ability to bounce back from failure and usability testing results.
• More visual progress and results for key stakeholders.

2. Getting buy in from IT is key

• IT can be the strongest champion and advocate for UX if aligned.
• Once aligned, it allows for prioritization of critical UX features and feels like the team is "speaking the same language".