Delivery · Order Experience

Mrsool

Mrsool

Redesigning Mrsool’s Order Flow Without Breaking Its DNA

Redesigning Mrsool’s Order Flow Without Breaking Its DNA

Peace Badejo, wearing sunglasses, looking to the left.
Peace Badejo, wearing sunglasses, looking to the left.
Peace Badejo, wearing sunglasses, looking to the left.

Mrsool’s order experience relied entirely on chat to communicate everything from confirmation and payment to preparation and delivery. While familiar to long-time users, this made it difficult for many users to quickly understand what was happening during an active order. Key system updates were buried inside conversations, leading to repeated questions and unnecessary back-and-forth. Couriers often became the source of clarity for system states, pulling their attention away from delivery and increasing friction during critical moments of the order journey.

Role and Scope

Lead Product Designer

  • Led end to end redesign of the buyer order flow across preparation, payment, delivery, and completion

  • Rearchitected a chat first experience into a layered, state driven interface

  • Defined order states, hierarchy, and system feedback without breaking legacy chat behavior

  • Collaborated with product, engineering, and operations to validate feasibility and rollout

  • Focused on reducing cognitive load for new and high frequency users

Key Outcomes

-28%

-28%

-28%

Friction

Friction

Less order related inbound chat messages during active orders

+40%

+40%

+40%

Clarity

Increased Order state recognition accuracy without opening chat

+15%

Efficiency Gain

Increased Courier time efficiency by reducing repetitive status clarification

From Chat-Heavy to Structured Progress

The original order experience was entirely chat-driven. Order status, payments, courier updates, and system notifications all lived inside the same conversation thread. This worked for power users, but created high cognitive load for new and returning users, especially during active orders.

The goal was to simplify the order experience without breaking Mrsool’s core identity: chat as the heart of the product.

Clear Order State, Instantly

A dedicated order status layer makes the current state immediately visible, so users understand what is happening without scanning the chat or interpreting system messages.

Chat Becomes the Background, Not the Interface

Chat remains part of the experience, but it moves to the background, allowing structured system information to lead while preserving Mrsool’s conversational core.

Same Space, More Clarity

Order status, courier details, and key updates are layered within the same screen, delivering clearer information without adding new screens or navigation.

Payment Clarity Within the Order Flow

Payment and billing updates were previously communicated mainly through chat, which led to repeated user questions and uncertainty during active orders.

Make payment status immediately understandable from the interface itself, while keeping chat available for reassurance and exceptions.

Payment as a Visible Order State

Payment is surfaced as a clear, dedicated layer within the order flow, allowing users to instantly understand whether the bill is issued, pending, or completed without relying on chat messages.

Action Appears Only When Needed

The “Pay now” action is shown only at the exact moment the user needs to act and disappears once payment is completed, removing confusion around whether further confirmation is required.

Chat Supports, It Doesn’t Explain

System updates such as billing and payment confirmation are visually elevated above the conversation, shifting chat from being the source of truth to a supportive communication layer.

One View, Fewer Questions

Users can track preparation and payment together in a single view, reducing cognitive load and minimizing unnecessary back-and-forth during the most sensitive stage of the order.

Delivery, Closure, and Continuity

Previously, delivery progress, arrival cues, order completion, and feedback all blended into the chat stream. Critical moments like “on the way,” “around the corner,” and “delivered” were easy to miss, and post-order actions were fragmented.

So, I wanted to make the final stages of the order feel calm, confident, and conclusive, while smoothly transitioning the user from active tracking to closure and re-engagement.

Clear delivery moments

Delivery states like On the way, Around the corner, and Delivered are visually prioritized so users instantly understand progress without relying on chat updates.

Tracking without distraction

Live location supports the experience in the background, giving reassurance without pulling users into a separate map-first flow.

Confident closure and next step

The order ends with a clear completion state, followed immediately by feedback and reorder actions that feel natural and timely.

Design Impact

Clearer without losing identity
Preserved Mrsool’s chat-first DNA while making order, payment, and delivery states instantly understandable.

Lower cognitive load
System states were separated from conversation, reducing scrolling, questions, and waiting for replies.

More confidence at key moments
Structured, layered states reduced uncertainty during payment, delivery, and completion.

More value, same space
Improved clarity without adding screens, flows, or UI surface area.

Stronger closure and reuse
Delivery, feedback, and reorder became a single continuous experience, supported by a scalable, reusable flow architecture.

Optional Deep Dive

This is a showcase for Mrsool order flow redesign project, the full Case Study Includes:
  • Analysis of chat driven order behavior and user confusion patterns.

  • Redesign of the end to end order journey across preparation, payment, delivery, and completion.

  • Definition of layered order states and system driven feedback.

  • Usability testing and iteration with new and frequent users.

  • Collaboration with product, engineering, and operations on feasibility and rollout.

Full Case study available upon request