My first draft for H2 was a scatter plot of ride time vs. customer rating. That chart has nothing to do with whether premium vehicles generate higher booking values or ratings — it doesn't even use those variables. Catching that and switching to dual box plots (booking value distribution and customer rating distribution, both split by vehicle type) was where the real analytical work happened. The wrong chart looked analytical. The right chart actually tested the claim. That distinction — does this visualization answer the hypothesis or does it just look like it does — is the main thing this project sharpened.
Project / Fall 2025
Uber India Ride Analytics
Fall 2025
Data Visualization · Tableau
Tableau
Data Visualization
Hypothesis-Driven Analysis
Business Analytics
Dashboard Design
What I Built
Interactive Tableau dashboard testing three business hypotheses against Uber India ride data — two confirmed, one rejected.
Built an interactive Tableau dashboard testing three business hypotheses against Uber India ride data. Two confirmed, one rejected — and the rejected one (premium vehicles don't outperform) was where the real analytical work happened.
Framed around three testable business hypotheses: whether driver wait time drives cancellations, whether premium vehicles generate higher booking values and ratings, and whether digital payments dominate revenue. All three produced definitive answers — two confirmed, one rejected. The final dashboard was published to Tableau Public with vehicle-type and payment-method filters. The most important finding came from the rejected hypothesis: premium vehicles didn't outperform. UberXL had the lowest typical booking values of any tier, and customer ratings were effectively flat across all vehicle types. The visualization that surfaced this also went through the most revision — and catching that wrong chart was where the real analytical work happened.
Final Tableau dashboard. All three hypothesis charts consolidated under vehicle-type filters, with KPIs across the top: total booking value (revenue), average ride time, average time-to-pickup, cancellation rate, and average customer and driver ratings.
Ride Value Visualized
Rs51.8M in bookings across the analyzed rides
Business Questions Framed
3 decision-oriented views built from one ride dataset
Operational Risk Isolated
Cancellation threshold identified at the trip level (15.1 min)
POST-PROJECT REFLECTION
What I Took Away
What I learned. Ranges anywhere from technical skills, to general lessons.
My goal is to always learn from an experience, no matter how big or small.
The minimum observed rating was 3.93 across every vehicle type and category, so starting the axis at 3 was technically accurate and made differences more visible. I corrected it to start at 0 anyway. A reader who doesn't notice the axis origin will read the chart as showing dramatic rating differences across vehicle types. It doesn't. Deliberately or not, that kind of scaling misleads — and I'd rather lose a visual effect than imply a finding that isn't there.







