Improving the Ride Booking Experience on Careem
A step-by-step teardown of Careem's cab-rides flow, from download and sign-up through ride completion and rating
Phase 01 · Product teardown
Improving the Ride Booking Experience on Careem
✳The problem they went after
Careem is the dominant super-app in MENA, bundling rides, food delivery, grocery, and payments. This teardown narrows to cab rides and asks where the flow actually breaks. Location detection is inaccurate enough to confuse drivers and add delay, the destination search bar accepts invalid characters that corrupt results, and Samsung Pay is missing despite Android's large regional base.
✳What they actually did
The walkthrough runs the full journey and marks friction at each step, including repeated driver cancellations and a post-ride rating prompt aggressive enough to sour the ending. From there it maps Careem's position against Uber, Bolt, and Blacklane, then reverse-engineers three core features: one-step sign-up, the Careem Pay wallet, and the all-in-one app model, explaining the user value and business value of each. Segmentation covers daily commuters, corporate travellers, and tourists.
✳What you can take from it
Worth stealing
- Full journey walked from download to post-ride rating
- Three features reverse-engineered for user and business value
- Segments split into commuters, corporate travellers, tourists
- Competitive map against Uber, Bolt, and Blacklane
Read this if
First-time teardown writers who want a clear structure to copy
The transferable bitWorth studying for how cleanly it separates the three jobs of a teardown: catalogue the friction, explain why the existing features exist, and describe who is affected. The reverse-engineering section is the part most people skip, and it is what turns a list of complaints into an argument about what Careem is optimising for.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
Phase 02 · Journey mapping
Fixing Ride Reliability and Trust Issues on Careem
✳The problem they went after
Careem runs rides, food delivery, pharmacy, and payments across MENA, and rides is the dominant vertical. That vertical carries recurring friction: pickup location detection that gets the spot wrong, driver cancellations, thin payment options, and a post-ride rating prompt pushy enough to undermine the feedback it is trying to collect.
✳What they actually did
The analysis maps download, sign-up, destination search, driver assignment, and payment as one continuous sequence, then marks where confusion turns into drop-off or dissatisfaction. Findings include no Apple App Store promotion on the website, permissions demanded before a user can explore anything, and no way to share live tracking. Those issues are then read against Careem's mission and benchmarked on Uber, Bolt, and Blacklane, with one-step sign-up, Careem Pay, and the all-in-one model reverse-engineered.
✳What you can take from it
Worth stealing
- Friction catalogued in journey order, not severity order
- Website discovery treated as part of the funnel
- Permission gates flagged as an exploration blocker
- Live-tracking sharing named as a trust gap
Read this if
PMs building a journey map that has to point at real drop-off
The transferable bitFriction is listed in journey order rather than severity order. Sequencing shows how an early problem, like permissions demanded before exploration, compounds into later drop-off, and it makes the case for fixing the entry point before touching anything about driver reliability.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
Phase 03 · Friction prioritisation
Improving Ride Booking Trust and Reliability on Careem
✳The problem they went after
App store reviews and user research on Careem's rides vertical keep landing on the same three themes: customer support, driver reliability, and payment integration. Underneath them sit specific gaps, including location detection that fails in dense urban areas, no visibility into which car types are available right now, and driver cancellations frequent enough to become the expectation.
✳What they actually did
The write-up separates annoyances from things that cost Careem money. Missing live-tracking sharing and absent Samsung Pay support are treated as satisfaction losses for particular segments, while driver assignment reliability and pickup accuracy are argued as churn drivers. Those sit against what Careem already does well, namely localised services, Arabic language support, and cultural compliance across MENA markets, and the chosen improvements are the ones that defend that position against Uber and Bolt.
✳What you can take from it
Worth stealing
- App store reviews mined as a research input
- Complaints sorted into churn drivers versus satisfaction dips
- Localisation treated as the moat worth defending
- Car-type availability named as a missing signal
Read this if
Anyone deciding which usability complaints are worth a roadmap slot
The transferable bitFixes are anchored to an existing moat. Instead of weighting every complaint equally, the analysis asks which failures undercut the local advantage Careem is built on, which gives a defensible reason to put pickup accuracy and driver reliability ahead of payment breadth.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
Phase 04 · Business and users
Full Product Analysis and User Segmentation for Careem Rides
✳The problem they went after
Careem's cab-rides vertical serves millions across the Middle East from a strong market position, and still leaks satisfaction. Pickup location detection misses, drivers cancel with no alternative offered, payment integrations are limited, and the rating prompt intrudes. Each is small alone; together they wear down loyalty on the vertical Careem can least afford to weaken.
✳What they actually did
The analysis covers the whole chain, from website discovery and app download through sign-up, destination search, scheduling, car selection, driver assignment, tracking, payment, and rating, marking what works alongside what does not. It then steps back into company context: the mission, and revenue from subscriptions, surge pricing, delivery commissions, and Careem Pay fees. Differentiation through Arabic language support and local regulatory compliance is mapped, and segmentation covers both riders and captains.
✳What you can take from it
Worth stealing
- Revenue streams named: subscriptions, surge, commissions, Careem Pay
- Both riders and captains segmented
- Website discovery counted as journey step one
- Every step assessed for what works, not just faults
Read this if
PMs who want a teardown that connects UX gaps to revenue
The transferable bitCaptains get their own segment alongside riders, which changes what counts as a fix; cancellations stop being a rider annoyance and become a question about captain incentives. Segmenting both sides of a network is worth the extra work. Tying journey steps to named revenue streams keeps the recommendations connected to how the business earns.
✳The submission itself
Open the PDF →Reading on a phone? The embedded viewer is cramped — open the PDF in a new tab instead.
