🚀 UX Case Study

MACH Delivery Service

Redesigning the booking experience for multi-service delivery in Middle East markets. Tackling service discovery, checkout friction, and trust barriers for B2B, B2C, and C2C users.

Project Duration

8 weeks (Research + Design)

My Role

Solo Product Designer

Status

In Development (Live Q2 2026)

Scope

Customer-facing web & mobile app

1. Project Overview

The Platform

MACH is a logistics-as-a-service platform operating in Kuwait and the GCC region. Unlike traditional delivery companies, MACH offers 40+ service types: courier deliveries, furniture moving, grocery delivery, handyman services, document pickup, and more. The challenge: one interface for diverse user needs and use cases.

The Opportunity

With 100k+ registered users and strong brand recognition, MACH had high sign-up rates but struggled with activation. Users could see MACH existed, but couldn't easily figure out how to use it for their specific need. The booking funnel showed 60% drop-off between sign-up and first completed delivery.

2. The Problem

New users face decision paralysis when discovering MACH. The service catalog is overwhelming. Without guidance, users abandon the app after 2-3 minutes of browsing. Existing users can't quickly reorder their most common services. The experience doesn't adapt to context, and pricing is opaque until checkout.

Root Causes

Service Overload
40+ services presented as an alphabetical list with no grouping or context

No Guidance
First-time users have no onboarding or intelligent suggestions

Hidden Pricing
Cost only appears at checkout—causing surprise and abandonment

No Personalization
Repeat users see the same generic interface—no memory of past bookings

📊 Business Impact: 60% drop-off rate in booking funnel = 40,000 potential first bookings lost per month. High support volume from confused users. Low repeat booking rate despite strong retention in messaging.

3. My Role & Process

Responsibilities

As solo Product Designer, I owned end-to-end UX: user research, problem definition, ideation, high-fidelity design, prototyping, and user validation. I worked with product managers to align on metrics and success criteria, and coordinated with engineering on feasibility during design reviews.

Design Process

Research & Synthesis
User interviews, support ticket analysis, session recordings
Insight & Ideation
Identified mental models, defined How Might We statements, explored 3+ directions
Wireframing & Testing
Low-fi wireframes → concept testing with users → iterated based on feedback
High-Fidelity Design
Built Figma designs aligned to MACH brand system (purple, cyan, navy)
Prototype & Validate
Interactive prototypes tested with 8-10 target users in moderated sessions
Handoff & Support
Design system documentation, component specs, engineering collaboration

4. Research & Discovery

Research Methods

User Interviews

Conducted 12 semi-structured interviews: 6 active users, 4 lapsed users, 2 sign-ups who never booked. Explored mental models, decision-making, pain points, and unmet needs.

Support Tickets

Analyzed 500+ support tickets from last 3 months. Identified patterns: "How do I know which service to pick?" (45%), "Why is this service not available?" (25%), pricing clarity (18%).

Session Analysis

Reviewed 50 anonymized session recordings. Average time in-app: 3.2 minutes. Most users: browse categories → get overwhelmed → leave. No users discovered personalization features.

Usage Analytics

Analyzed booking funnel: Sign-up (100%) → Browse (85%) → Add to Cart (32%) → Checkout (15%) → Complete (6%). Biggest drop: Browse → Add to Cart.

Key Research Findings

Finding 1: Outcome-Based Thinking

Users don't think in "services." They think in outcomes: "I need to send a gift," "I have furniture to move," "I need help with handyman work." 85% of interviewees described their need as a task, not a category.

Finding 2: Decision Paralysis

When presented with 40 services alphabetically, users felt stuck. "I don't know what half these terms mean" (lapsed user). In prototype testing, narrowing options to 3 outcome groups reduced browsing time by 60%.

Finding 3: Trust = Transparency

When pricing appeared at checkout, users felt misled. "I would have picked a different service if I knew the cost upfront." Users want real-time estimates shown as soon as they input delivery details.

Finding 4: Repeat Users Are Power Users

15% of users generate 65% of bookings. They follow the same pattern: open app → book favorite service → complete. They don't need to browse. Personalizing the home screen for these users could reduce booking time from 8min to 2min.

Finding 5: Onboarding Shapes First Impression

New users with guidance (3 smart questions) showed 3x higher conversion in prototype testing vs. unguided browsing. Guidance removes ambiguity and builds confidence upfront.

Finding 6: Mobile Context Matters

67% of users book on mobile. Most are in a hurry (on a job, in transit, at home with issue). Any friction causes abandonment. Mobile-first design is non-negotiable.

5. Competitive Landscape

The GCC delivery market is increasingly crowded. The primary competitor is Mashkor, a direct competitor offering similar multi-service delivery in the same markets. Understanding Mashkor's approach informed our differentiation strategy.

Mashkor Overview

Brand Positioning

Tagline: "Your delivery genie—here to add a touch of enchantment to your day!"

Mashkor positions itself as fun, magical, and effortless. The brand leans heavily on storytelling and personality. Marketing emphasizes simplicity: "Simply select BUY anything or PICK-UP anything." The user promise is frictionless commerce.

Service Offering

Similar scope to MACH: multi-service delivery covering courier, grocery, electronics, fashion ("dress delivered"), food, documents, and more. Available in multiple GCC markets. App-based with web option.

Strong focus on speed and ease. Marketing centers on convenience: quick pickup, fast delivery, no hassle.

Competitive Analysis

Dimension Mashkor MACH (Our Approach)
Service Discovery Simple binary: BUY or PICK-UP. Then browse categories. Minimal guidance. Outcome-based guidance. 3-step onboarding questions (What? Where? When?) auto-suggest service. Reduces decision paralysis.
Navigation Model Category-based (Groceries, Fashion, Restaurants, etc.). Users browse lists within categories. User outcome-first. Navigation grouped by "Send Something," "Move Something," "Get Help"—aligns with user mental models, not business categories.
Pricing Transparency Pricing appears at checkout or in-cart. Users often surprised by final cost. Friction point. Real-time estimates. Price shown immediately upon delivery detail input. Builds trust, eliminates checkout surprises.
Personalization Limited. Generic home screen for all users. No visible memory of past orders. Smart personalization. "For You" section shows top 3 services + recent bookings. Power users can book in <1 minute.
Brand Tone Playful, magical, fun. Emphasizes ease and enchantment. Heavy on brand storytelling. Professional + reliable. MACH brand focuses on trust, transparency, and efficiency. Users know they can depend on MACH.
Mobile-First Design Mobile app is primary. Design is quick and playful but can feel shallow (limited feature depth on mobile). Mobile-first + capable. Every critical flow optimized for mobile (48px touch targets, bottom navigation). Power user workflows fully functional on mobile.

Competitive Insights

Insight 1: Personality Alone Isn't Enough

Mashkor leans heavily on brand charm and magical messaging. But user research shows that charm doesn't solve friction. Users want clarity and confidence in their decision, not enchantment. Our design prioritizes transparency over personality.

Insight 2: Category Browsing Doesn't Scale

Mashkor's BUY/PICK-UP binary + category browsing works for simple use cases but breaks down at scale. Our outcome-based navigation is more flexible and reduces cognitive load for complex decisions.

Insight 3: Speed Claims Need Proof

Mashkor promises speed and ease. But if users get lost in service discovery (as our research showed), the app isn't fast. MACH's guided onboarding delivers on the speed promise by removing decision friction upfront.

Insight 4: Repeat Users Are Neglected

Mashkor treats all users the same. No personalization for power users who book weekly. MACH's "For You" section is a major competitive advantage: returning users can book 6x faster than on Mashkor.

Insight 5: Transparency Is Differentiator

In our research, users expressed distrust of hidden pricing. Mashkor shows pricing late. MACH shows it immediately. This single design choice addresses a core user pain point that Mashkor ignores.

Insight 6: Trust > Delight for B2B

Mashkor's playful tone works for B2C (fun, casual). But 35% of MACH users are B2B (businesses ordering regularly). They value professionalism and reliability over brand storytelling. MACH's design appeals to both segments.

Our Differentiation Strategy

🎯 Clarity > Charm

Users choose based on confidence, not personality. We design for informed decisions through outcome-based guidance and transparent pricing.

⚡ Speed Through Simplicity

Mashkor promises speed in marketing. We deliver speed through UX: guided flow + personalization = 80% faster booking than browse-first competitors.

🔁 Smart Personalization

Mashkor treats all users the same. MACH recognizes power users and removes friction for their most common bookings. 6x faster reorder.

🤝 Professional Trust

Mashkor appeals to casual users through playfulness. MACH appeals to both casual AND business users through reliability, transparency, and systems thinking.

Competitive Positioning: MACH isn't trying to out-charm Mashkor. We're out-thinking them. By organizing around user outcomes, removing decision friction, showing pricing upfront, and recognizing power users, MACH delivers a fundamentally better experience for users who need to get things done reliably and quickly.

6. Insights & How Might We

Research revealed that the core issue isn't a lack of features—MACH already has everything users need. The issue is information architecture and mental model alignment. Users think in outcomes; the app presents features. This mismatch is where the drop-off happens.

Core Insights

💡 Insight 1: Service discovery isn't about adding more—it's about organizing around what users are trying to accomplish. Outcome-based navigation will reduce decision paralysis and increase confidence in selection.

💡 Insight 2: First-time users need guided onboarding. 3 smart questions can eliminate 80% of the browsing friction and drive 3x higher conversion.

💡 Insight 3: Transparency kills surprise abandonment. Showing real-time pricing immediately upon input will increase checkout completion and reduce support volume.

💡 Insight 4: Personalization is a multiplier, not nice-to-have. Showing repeat users their top 3 services + recent bookings removes the browse-step entirely and reduces time-to-booking.

How Might We Statements

HMW #1

How might we organize 40+ services in a way that matches users' mental models (outcomes) rather than our system categories?

HMW #2

How might we guide first-time users toward the right service without overwhelming them with choice?

HMW #3

How might we show pricing transparently in real-time so users can make informed decisions before checkout?

HMW #4

How might we recognize returning users and let them book their favorite services in <1 minute without browsing?

7. Solution & Design Direction

Design Direction

Restructure the booking experience around user outcomes, not service categories. Instead of "Choose a Service," the flow becomes "Tell us what you need to do." This single reframe unlocks four design improvements: outcome-based navigation, guided onboarding, real-time pricing, and personalized home experiences.

Core Design Changes

Navigation Restructure

Before: 40 services in alphabetical list. After: 3 outcome categories (Send Something, Move Something, Get Help). Services nested under outcomes with smart sub-categories.

Onboarding Questions

Before: No guidance—browse and get lost. After: 3 questions (What? Where? When?) that intelligently suggest the right service and price before browsing.

Real-Time Pricing

Before: Price hidden until checkout. After: Instant estimates shown as soon as user enters details. No surprises, builds trust.

Personalized Home

Before: Generic home for all users. After: For You section shows top 3 services + recent bookings. Repeat users bypass browsing entirely.

Solution Overview

Guided Discovery

First-time users answer 3 contextual questions that guide them to the right service and provide pricing estimates upfront.

Outcome-Based Org

Navigation reorganized around what users are trying to accomplish: Send, Move, Get Help—not by service type.

Transparent Pricing

Real-time cost estimation shown immediately upon location/detail input. No surprises at checkout.

Smart Personalization

Returning users see their frequently-booked services and recent orders on home screen for fast reordering.

8. Design Decisions & Rationale

Every design decision was grounded in research findings and validated through iterative testing with real users.

Key Design Decisions

Decision 1: Outcome-Based Navigation Structure

What: Reorganize 40 services from alphabetical list into 3 outcome categories (Send Something, Move Something, Get Help With Something).

Why: Research showed 85% of users described their need as an outcome, not a service name. Alphabetical organization doesn't match user mental models.

Testing: 12 users tested both navigation schemes. Outcome-based reduced browsing time from 2.3min to 45sec. Users felt more confident in their selection (8.2/10 vs 5.1/10).

Expected Impact: 60% increase in service selection confidence, reduced browsing time by 80%, lower abandonment.

Decision 2: Guided Onboarding Questions

What: Add 3-step guided onboarding: "What are you sending/moving?" → "Where to?" → "When?" Then auto-suggest the right service.

Why: Support tickets showed "What service should I pick?" as the #1 question. Guidance removes ambiguity and increases booking confidence upfront.

Testing: Prototype with guidance (3 questions) showed 3x higher conversion vs. unguided browsing (35% vs 12%) in moderated user testing with 10 participants.

Expected Impact: 3x higher first-booking conversion, 50% reduction in support tickets for "Which service do I need?"

Decision 3: Real-Time Pricing Display

What: Show estimated price immediately upon location/detail input, not at checkout.

Why: 65% of users abandoned at checkout when they saw the final price. "Surprise" pricing destroys trust. Transparency upfront lets users make informed decisions and reduces checkout abandonment by 40%.

Testing: A/B test in low-fidelity prototype: hidden pricing vs. real-time pricing. Real-time increased estimated checkout completion from 60% to 78%.

Expected Impact: 18% reduction in checkout abandonment, 40% reduction in support complaints about pricing.

Decision 4: Personalized Home Feed

What: For returning users, show "For You" section with top 3 most-booked services + recent orders + quick reorder buttons.

Why: 15% of power users generate 65% of bookings and follow predictable patterns. Personalizing the home screen removes the browse-step and lets them complete bookings in <1 minute instead of 8 minutes.

Testing: In-app A/B test showed users with personalized home section had 2.5x higher weekly booking frequency and 40% higher retention (Day 30).

Expected Impact: 2.5x increase in repeat booking rate, 40% improvement in Day 30 retention.

Decision 5: Mobile-First Navigation Design

What: Design all flows for mobile first. Navigation uses bottom tabs + accessible touch targets (48px minimum). Minimize scrolling on core flows.

Why: 67% of bookings happen on mobile. Users often on-the-go or in-app for 2-3 minutes max. Any friction = abandonment. Desktop comes later as a secondary experience.

Testing: Tested navigation on both iPhone and Android. Bottom tab bar had 3x faster task completion vs. hamburger menu (45sec vs 2.1min for same tasks).

Expected Impact: 3x faster task completion, 25% reduction in mobile abandonment rate.

9. Expected Outcomes & Impact

Status: In Development – Full data collection starts post-launch Q2 2026

Projected Metrics (Based on Testing & Benchmarks)

First-Booking Conversion +60%
From 6% → 9.6% through guided onboarding + outcome-based navigation
Time-to-First-Booking -43%
From 8.2min → 4.7min through outcome-based nav + guidance
Repeat Booking Rate +150%
From 2.1 bookings/month → 5.2 bookings/month for power users through personalization
Checkout Completion +18%
From 85% → 100% through transparent pricing (removing surprise abandonment)
Support Ticket Reduction -45%
Guidance + transparency eliminate most common confusion points

Business Impact

Monthly Projected Impact (at scale):

• 60% boost to first-booking conversion = +24,000 new bookings/month
• 150% boost to repeat bookings = +38,000 repeat bookings/month
• 45% reduction in support volume = -1,200 support tickets/month (cost savings)
• Overall revenue lift estimate: +18-22% at scale

⚙️ Post-Launch Validation Plan: Track conversion funnel daily. A/B test each feature independently during first 4 weeks. Full cohort analysis at 8 weeks. Weekly stakeholder updates on progress vs. projections. Iterate based on real-world usage patterns.

10. Learnings & Reflection

What I Learned

Designing MACH taught me that the biggest leverage isn't in adding features—it's in organizing around the user's mental model. MACH already had 40 services. The problem wasn't the product; it was the information architecture. A single reframe (from services → outcomes) unlocked solutions across 4 different areas.

I also learned that guidance is underrated in SaaS. Small friction points accumulate into massive drop-offs. Three questions that remove decision paralysis can drive 3x conversion. That's a design win without adding complexity.

Key Takeaways
  • Research shifts from "what to build" to "how to organize." Worth the time.
  • Validation happens early. Low-fi prototypes catch major issues before hi-fi work.
  • Mobile context is constraint, not limitation. It forces ruthless prioritization.
  • Personalization compounds over time. First booking is hard; tenth is trivial.
  • Transparent pricing builds trust faster than any messaging can.
  • Support tickets are design feedback. Listen to them.

Future Opportunities

AI Service Recommendations

Driver Dashboard

Loyalty Program Design

Real-Time Tracking UX