e-stebdalreturns, without the back-and-forth.
Merchants were running returns over WhatsApp and spreadsheets. I mapped the whole reverse journey — request, pickup, inspection, refund — and designed one dashboard that lets a small team process a return in three clicks instead of eleven messages.
- Client
- e-stebdal · Seed Stage
- Year
- 2025 – 2026
- Role
- Lead Product Designer & Brand Designer
- Team
- 3 engineers, 1 product manager
- Methods
- Interviews, Journey mapping, Usability

Overview
Every return touched four people and three tools. Nobody could say where a parcel was, and refunds waited on whoever remembered to check the spreadsheet.
The objective
Give operations teams one place to see, approve and close a return, and give their customers a status they can check themselves.
01 Discovery
A return is five handovers, and each one was a message.
Where time went
Shadowing the support team showed that most of a return was not work, it was waiting: for a photo, for a courier slot, for someone in finance to confirm the refund.
What merchants asked for
Nobody asked for more features. They asked to stop chasing. Every merchant described the same wish in different words: "I just want to know what is stuck."
One queue, sorted by what is stuck.
The dashboard opens on the returns that need a decision, not on a list of everything. Each row shows the one thing blocking it and the button that unblocks it.
Statuses are written the way merchants talk — "waiting for pickup", not "RTO_PENDING" — so a new team member can use it on day one.

The Impact
3
clicks to close a return, down from 11 messages
-40%
support tickets about refunds
2 days
faster average refund
Founder
"We finally stopped running the company from a group chat. The team picked it up in an afternoon."
Next
Donia & Omar
Engagement experience in print.