Better journeys, better results:
– 40 % errors

Better journeys, better results: – 40 % errors

This case study doesn’t include visuals due to confidentiality — but there’s plenty to explore. I’ve done my best to walk you through the thinking, decisions, and outcomes in a clear and engaging way. 💡

Role: UX/UI Designer
Timeline: 12 moths
Project Type: Luxury Business Branding Platform
Scope: High-end visual identity, brand storytelling, interactive digital presence
and immersive user experiences
Goal: Redesigning the agent tool to reduce errors and improve help speed for drivers in need
Tools Used: Figma, Axure, User Testing, Documentation
Impact: Task success rate: 62 % → 83 %, Error rate: –40 %

Role: UX/UI Designer
Project Type: Luxury Business Branding Platform
Scope: High-end visual identity, brand storytelling, interactive digital presence
and immersive user experiences
Tools Used: Figma, Axure, Maze, HotJar, Google Analytics

🚗 Waiting for help shouldn’t feel like waiting for a miracle

The original experience? Clunky. Vague. Full of question marks. Drivers were left wondering: What now? Who’s coming? When? That’s not support — that’s silence. So we rebuilt it. Clear steps. Real-time updates. Zero guesswork.

The Mission: Turn chaos into calm

Stressful moment. High stakes. Spinning wheels (literally). We wanted to flip that into something simple, human, and clear — powered by predictive UX and real-world data, not guesswork.

We focused on what actually matters when things go sideways:

⚡ Lightening the mental load when users are already maxed out

⚡ Rewriting robotic flows so they sound like someone who actually cares

⚡ Anticipating needs before fingers even hit the screen

⚡ Transforming the wait into a moment that feels handled — not forgotten


What came out of it?

A redesigned experience that doesn’t just look good in a prototype — It works in roadside rain, low battery, and “I’ve had a day” energy. Fast. Calm. Human. Great UX isn’t always about momentum. Sometimes, it’s about saying: you’re okay — stay right there.

🟥 Before vs. After 🟩

🟥 User breaks down → opens app → hits a vague form → no idea what’s happening → stress builds → ends up calling anyway.

🟥 “Request assistance”? Too vague. Assistance how, when, from who?

🟥 No timeline. No feedback. Just: “We’re working on it...” 🙄

🟥 Cold. Confusing. Emotionally tone-deaf.

🟩 User breaks down → app gives a clear next step → real-time guidance kicks in → updates reduce stress → user stays calm, informed, in control.

🟩 Microcopy builds trust by explaining why we ask for info

🟩 Fuzzy time estimates (“18–24 min”) set real expectations

🟩 Experience shifted from “follow instructions” to “we’ve got you”

The transformation? From Where is my help? to Help is already on the way.

Outcomes:

  1. Fewer users are exiting mid-request

  2. Users mentioning clarity and “felt like someone was actually helping” in feedback

  3. Internal teams reusing new copy standards in other emergency flows

  4. A stronger link between content design and emotional UX

What were we solving for?

We weren’t just streamlining a process—we were redesigning how support is felt.

Top issues identified in user research:

  1. Confusion about next steps

  2. No visibility on what’s happening behind the scenes

  3. Cold tone and unclear copy

  4. Lack of updates during the wait

Our UX goals:

  1. Reduce abandonment during help requests

  2. Increase perceived support and clarity

  3. Encourage self-service over hotline calls

  4. Build trust through transparency, not over-explanation

Voice Shift: from system prompts to reassurance

We rewrote the interface to sound less like a manual and more like a human.

Old copy

“Submit request”

“Your request is being processed”

“ETA: 23 minutes”


new


New copy

“Send for help”

“We’re notifying roadside assistance near you”

“Your technician is usually on site in 20–25 minutes”

“In the meantime, stay safe. Turn on your hazard lights.”

Old copy

“Submit request”

“Your request is being processed

“ETA: 23 minutes”




new





New copy

“Send for help”

“We’re notifying roadside assistance near you”

“Your technician is usually on site in 20–25 minutes”

“In the meantime, stay safe. Turn on your hazard lights.”

Old copy

“Submit request”

“Your request is being processed”


“ETA: 23 minutes”


new


New copy

“Send for help”

“We’re notifying roadside assistance near you”

“Your technician is usually on site in 20–25 minutes”

“In the meantime, stay safe.

Turn on your hazard lights.”

Why new copy works:

✔️ Reassuring tone reduces anxiety
✔️ Plain language builds confidence
✔️ Contextual tips turn waiting into preparation

What This Taught Me

“UX writing is not just about clarity. It’s about confidence - especially when the user is under pressure.”

This project sharpened my instincts around:

❤️ Designing for emotion, not just action

❤️ Using timing and tone to guide calmly, not command

❤️ Seeing copy as a UX safety net, not a label on a button

What were we solving for?

We weren’t just streamlining a process we were redesigning how support is felt.

Top issues identified in user research:

  1. Confusion about next steps

  2. No visibility on what’s happening behind the scenes

  3. Cold tone and unclear copy

  4. Lack of updates during the wait

Our UX goals:

  1. Reduce abandonment during help requests

  2. Increase perceived support and clarity

  3. Encourage self-service over hotline calls

  4. Build trust through transparency, not over-explanation

Outcomes:

  1. Fewer users are exiting mid-request

  2. Users mentioning clarity and “felt like someone was actually helping” in feedback

  3. Internal teams reusing new copy standards in other emergency flows

  4. A stronger link between content design and emotional UX

What This Taught Me

“UX writing is not just about clarity. It’s about confidence - especially when the user is under pressure.” This project sharpened my instincts around:

❤️ Designing for emotion, not just action

❤️ Using timing and tone to guide calmly, not command

❤️ Seeing copy as a UX safety net, not a label on a button

Santander

Zen.com

BMW

Ferrero

Wedel

Sector 3.0

Samsung

WWF

The 3E System

Procter & Gamble

Credit Agricole

Santander

Zen.com

BMW

Ferrero

Wedel

Sector 3.0

Samsung

WWF

The 3E System

Procter & Gamble

Credit Agricole

Santander

Zen.com

BMW

Ferrero

Wedel

Sector 3.0

Samsung

WWF

The 3E System

Procter & Gamble

Credit Agricole

© 2025 Made with ❤️ by Katarzyna Bobrowska

© 2025 Made with ❤️ by Katarzyna Bobrowska

© 2025 Made with ❤️ by Katarzyna Bobrowska

Create a free website with Framer, the website builder loved by startups, designers and agencies.