Fixing the UX Case Study: Reviewing Pratiksha's Reliable Business ride experience in OLA
2.2K views · 2026-03-16
Product DesignInteraction & UX
AI UX Design Mentorship - Apply now → https://forms.gle/pcyMv4EhJ2WtKQz48
In this episode, a scan review of Pratiksha’s portfolio and an OLA business-ride booking case study, noting the product thinking is strong but the case study is overly templated, text-heavy, and should link a prototype instead of the full Figma file. Recommend rewriting the case study using a clearer storytelling format, reducing obvious explanations, and improving scannability, spacing, hierarchy, and visual consistency. Pratiksha presents a redesigned OLA flow aimed at professionals needing business features like ride purpose, fair breakdown, GST invoices, and punctuality signals; the reviewer probes business goals, research proof, friction from added steps, and emphasises designing the primary “happy path” for repeat users with auto-populated data.
00:00 Text Heavy UI Fixes
00:33 Portfolio Scan Review Setup
01:44 Picking the Hero Project
04:02 Case Study Scan Critique
07:19 Cut the Fluff Copy
09:54 Prototype Walkthrough Video
13:48 Interview Questions Business Goals
17:53 Scrutiny on Data Friction
20:20 Repeat Use Happy Path
21:48 FTUE vs Scalable Design
23:32 Retention Goal Rationale
25:36 Next Version Ideas
26:12 Retention Through Predictability
30:37 Constraints and Systems Thinking
32:12 Hiring Feedback and UI Skills
35:12 Scorecard and Wrap Up
In this episode, a scan review of Pratiksha’s portfolio and an OLA business-ride booking case study, noting the product thinking is strong but the case study is overly templated, text-heavy, and should link a prototype instead of the full Figma file. Recommend rewriting the case study using a clearer storytelling format, reducing obvious explanations, and improving scannability, spacing, hierarchy, and visual consistency. Pratiksha presents a redesigned OLA flow aimed at professionals needing business features like ride purpose, fair breakdown, GST invoices, and punctuality signals; the reviewer probes business goals, research proof, friction from added steps, and emphasises designing the primary “happy path” for repeat users with auto-populated data.
00:00 Text Heavy UI Fixes
00:33 Portfolio Scan Review Setup
01:44 Picking the Hero Project
04:02 Case Study Scan Critique
07:19 Cut the Fluff Copy
09:54 Prototype Walkthrough Video
13:48 Interview Questions Business Goals
17:53 Scrutiny on Data Friction
20:20 Repeat Use Happy Path
21:48 FTUE vs Scalable Design
23:32 Retention Goal Rationale
25:36 Next Version Ideas
26:12 Retention Through Predictability
30:37 Constraints and Systems Thinking
32:12 Hiring Feedback and UI Skills
35:12 Scorecard and Wrap Up