Alena Essina
Data import
Data import as a trust-building onboarding experience.
Redesigning a critical onboarding flow to reduce early churn.
Redesigning a critical onboarding flow to reduce early churn.
Role:
Lead Product Designer (hands-on)
Product:
Tribe (B2B and B2C CRM platform)
Why it could be interesting for you:
This project shows how I work as a hands-on Lead Product Designer: aligning UX decisions with business risk, challenging assumptions with research, and designing systems that scale trust, not just screens.
What?
The problem
Import is one of the first actions new users perform.
The existing all-in-one page was optimised for speed, but new users:
The existing all-in-one page was optimised for speed, but new users:
- didn’t understand required fields or Tribe-specific mappings
- missed errors and didn’t know how to fix them
- lost confidence early, contributing to churn
So what?
The real problem
The surface problem looked like usability and errors. The deeper problem was trust.
New users were being asked to make decisions and using unfamiliar concepts without understanding consequences.
New users were being asked to make decisions and using unfamiliar concepts without understanding consequences.
Strategic tension
Research and support data were pointing in the opposite direction.
The real tension:
The real tension:
- Speed vs. comprehension
- Power vs. guidance
- Experienced users vs. first-time users
Key insights that changed direction
From user interviews, usability tests and qualitative feedback were get following insights:
This led to a critical reframing:
The import flow needed to guide and teach, not just execute.
- Users didn’t know what was required until it was too late Required fields and rules were technically present—but cognitively invisible.
- Error management was poor Error messages were hardly visible, if users saw that something was wrong, it was no explanation what to do next.
- Tribe-specific relation ID mapping concept was hidden and unclear Users couldn’t evaluate correctness because they didn’t understand the model.
- Speed without understanding increased anxiety Users preferred a slower experience if it meant feeling in control.
- One screen for all actions brought confusion and unclarity Spending significant time without understanding what should be done, users asked Customer Support for help not being able to perform action by themselves
This led to a critical reframing:
The import flow needed to guide and teach, not just execute.
Field mapping before/after
Now what?
Design strategy — a guided experience on purpose
I made a deliberate strategic decision: Increase interaction steps if it increases clarity and confidence.
I challenged the assumption that fewer clicks = better UX. Research showed new users preferred clarity over speed, so I intentionally increased steps to improve understanding and confidence.
Key principles:
This wasn’t just a redesign—it was a change in philosophy for onboarding experiences.
I challenged the assumption that fewer clicks = better UX. Research showed new users preferred clarity over speed, so I intentionally increased steps to improve understanding and confidence.
Key principles:
- Progressive disclosure over information overload
- Explicit guidance before irreversible actions
- Errors as part of the flow, not exceptions
- Clear cause → effect visibility
This wasn’t just a redesign—it was a change in philosophy for onboarding experiences.
What I designed
I owned:
- Problem framing and success criteria
- UX strategy for first-time import
- End-to-end flow redesign
- Stakeholder alignment around a counter-intuitive direction
I also worked hands-on:
- Mapping flows and states
- Designing interaction patterns
- Defining error handling and recovery
This was a high-impact, high-risk decision, because it intentionally challenged an established product assumption.
Impact
First-import completion rate — 62% → 84%
Import-related support tickets — down ~40%
Time to first successful import — ~22 min → ~7 min
Early-stage activation / 30-day retention — directional uplift
Strong qualitative feedback around clarity and confidence
Import-related support tickets — down ~40%
Time to first successful import — ~22 min → ~7 min
Early-stage activation / 30-day retention — directional uplift
Strong qualitative feedback around clarity and confidence
Gallery
