Länsförsäkringar · Company onboarding
Digital onboarding
of companies
From manual handling to a clearer application journey.
I worked with process maps, stakeholder requirements and user research to shape a company onboarding flow that supported the bank’s customer knowledge needs.


The challenge
Redesign company onboarding to reduce manual handling and make the application clearer.
The outcome
A redesigned onboarding flow, shaped by process maps, stakeholder requirements and user research.
01 / Background
A digital application.
A manual process behind it.
The existing Become a Bank Customer flow relied heavily on manual handling. This created extra work for case managers and could lead to errors and inconsistencies.
The goal was a clearer, more automated onboarding experience for both companies and bank staff.
02 / My approach
Turn process documents
into an experience.
The project began with process maps and PowerPoint documents. I studied the material with the team to understand requirements and dependencies before translating it into an interactive flow.
I also helped stakeholders understand the role of UX alongside other design disciplines, keeping the customer experience part of the discussion.
03 / Question design
Match the question
to the way people answer.
These examples show how the questions, answer controls and follow-up fields work together. The original interface is shown alongside updated editorial notes.






04 / Working with constraints
Bring the customer
into the process.
The challenge was not only the screens. I needed to work from existing documentation, understand the operational process and help the team see how individual requirements would affect the application.
The design work connected the bank’s information needs with the experience of the person answering the questions.
Reflection
A clearer flow starts
with a clearer question.
The examples show how much of the experience sits in small decisions: whether an answer is single or multiple choice, when another field appears, and when a term needs an explanation.