Designing reassurance in a high-intent moment

Reimagined critical moments after user action — transforming confirmation and expectation flows into experiences that build trust, clarity, and direction.

MY ROLE

UX Designer

TEAM

PM · 2 Engineers

TOOLS

Figma

DURATION

3 months · Shipped ✓

INDUSTRY

Consumer facing (Web + Mobile)

SCOPE

Two surfaces, one page

PART A - POST FORM SUCCESS PAGE

PROBLEM

The form worked. That was the trap.

Users completed a meaningful, personal action — and were met with a generic confirmation: a checkmark, a vague promise, and a link elsewhere.
‍
There was no emotional continuity.
No clarity on what happens next.

This wasn’t an acquisition problem.It was the moment where trust is either built — or quietly lost.

"I submitted the form and immediately thought — what did I just do? It just said 'missionaries will contact you soon.' I didn't feel reassured. I felt more anxious."

– Reconstructed from user research

REFRAME

What users needed wasn't more information.
It was reassurance.

Early on I assumed personalization was the answer — show people their own data back, make them feel seen. What I found was the opposite. A screen full of accurate, well-organized information made the experience feel transactional. That reframe changed every decision that followed.

5

Iterations, each built around an explicit hypothesis

8w

From first principles to approved and shipped

1

Central question: how much is
too much ?

CURRENT STATE

Three screens. Zero momentum.

A working form, a generic confirmation, and a 'prepare page' that felt like homework. The submission created a full stop at exactly the wrong moment.

DESIGN PRINCIPLES

4 things every version
had to do.

Before touching a screen, I needed to know what "better" actually meant. These four principles became the filter — not aspirational statements, but tests I ran every version against.

PART B - 'WHAT TO EXPECT' COMPONENT

Where the experience broke

This is what we started with. The brief was “make it more engaging.”
The real problem was structural — not visual.

EXPLORATING STRUCTURE & MEANING

Three label directions. None of them survived as-is

To help users understand what to expect, I explored three structural directions — across interaction, layout, and visual language. What testing revealed was that no single treatment was enough — but each exposed what mattered.

TRANSITION TO OUTCOME

From explaining → to showing

Instead of structuring the experience with UI, I reframed it to a video-first carousel, supported by lightweight descriptions —where motion carried the meaning, and text simply grounded it.

OUTCOME

What previously required multiple elements was now understood in seconds of video —
reducing friction and building confidence at the exact moment it mattered most.