1
Service Ecosystem
Clean4Wheels is a subscription-based doorstep car care platform where every successful booking depends on seamless coordination between customers, managers, and on-ground valets. As the business expanded, its digital experience struggled to keep pace with increasingly complex operational workflows.
1
2
3
4
5
6
Retention
Initiates the service
request
Verification
Customer initiates a
service booking
Manager oversees the
operational workflow
Valet
Valet receives task and
executes service
Manager
Booking
Proof collection and
service quality check
Customer
Final stage ensuring
customer loyalty
"By viewing the product as a connected service ecosystem instead of an isolated booking experience, I was able to identify opportunities that improved operational efficiency while simultaneously strengthening customer trust."
2
Business Context
Clean4Wheels had an established offline operation. The challenge was that the software no longer reflected how the business had grown. Disconnected workflows began affecting every stakeholder differently.
Core Realisation
3
Discovery & Research
Since the platform was live and direct customer interviews were not feasible, I combined stakeholder knowledge, product evaluation, workflow analysis, and secondary research to uncover friction across customer and operational experiences.
3.1 · Stakeholder Discovery
The Business Behind the Product
Founder
Business objectives, customer pain points, operational priorities
CTO
System architecture, implementation constraints, product limitations
Operations Team
Daily workflow challenges, coordination issues, reporting practices
01
Customer issues concentrated after payment, not before booking
01
Managers lacked centralised visibility into field operations
01
Valets depended on manual reporting for task updates
02
Customers had no reliable proof services were completed
02
Trust issues stemmed from limited visibility, not poor quality
3.2 · Existing Product Audit
3.3 · Heuristic Evaluation
Visibility of System Status
Limited feedback after booking confirmation
Needs Work
Match Between System & Real World
Scheduling terminology lacked clarity
Partial
Recognition Rather Than Recall
Users repeatedly entered known information
Needs Work
Consistency & Standards
Inconsistent form patterns across booking steps
Partial
Error Prevention
Limited validation and recovery during booking
Needs Work
3.4 · Competitive Benchmark
Feature
(Before)
Opportunity
Guided Booking Flow
✓
✓
✓
✗
Simplify journey
Service Package Comparison
✗
✓
✓
✓
Improve decision-making
Saved Addresses & Vehicle
✓
✓
✓
✗
Reduce repetitive input
Real- time Slot Availability
✓
✓
✓
◑
Increase scheduling confidence
Service Tracking
✓
◑
◑
✗
Introduce progress visibility
Photo Proof of Completion
✗
✗
◑
✗
Build trust via verification
★
Progressive disclosure reduces complexity
Competitors guiding users step-by-step have measurably lower abandonment at the booking stage.
Visible updates build post-payment confidence
Service tracking exists in only one competitor and it's the highest-rated feature in reviews.
Operational transparency drives retention
The gap isn't just a feature gap. It's a trust gap and no competitor has addressed it directly.
4
Research Synthesis
Across five research methods, a consistent pattern emerged, the operational blindspot was the underlying cause of every major problem.
INSIGHT 03
The competitive matrix, stakeholder interviews, and workflow analysis all pointed to the same gap: there was no mechanism connecting service delivery to customer confidence.
STAKEHOLDER
AUDIT
BENCHMARK
INSIGHT 01
Friction concentrated in post-payment, not booking itself.
Design a post-booking service lifecycle experience.
STAKEHOLDER
INSIGHT 02
Managers couldn't see what was happening in the field at any given time.
Build a real-time operational visibility layer for managers.
WORKFLOW
INSIGHT 04
Valets had no structured way to log attendance or report completion.
Create structured task and verification workflows for field teams.
WORKFLOW
OPS
INSIGHT 05
No product in the market offers proof that a service was completed.
Establish verification as a first-class product feature.
BENCHMARK
INSIGHT 06
Retention relied on service quality — but trust broke at the visibility layer.
Close the loop: connect service execution to customer awareness.
STAKEHOLDER
HEURISTIC
5
Booking Redesign
The booking journey was optimised for collecting information rather than helping users make confident decisions. I reframed it as a six-decision journey.
6
Service Verification
I redesigned the post-booking experience as an observable service lifecycle, a nine-node loop that closes every transaction and transforms operational transparency into a customer-facing feature.
For customers
Real-time status from booking to verified completion. No more guessing what happened after payment.
For valets
Structured task lifecycle with photo upload at completion. Accountability without unnecessary friction.
For managers
Instant visibility into every active service. No more chasing updates through informal channels.
7
Cleaner Platform
Rather than treating valets and managers as administrative users, I considered them primary product stakeholders whose daily efficiency directly influenced customer satisfaction.
Workforce Visibility
Photo verification and location confirmation established accountability, replacing ad-hoc WhatsApp coordination.
Structured Daily Operations
Daily assignments, booking status, and service updates consolidated into a single workflow.
Performance Transparency
Operational dashboards surfaced attendance trends, task completion history, and service metrics.
8
Design System
Rather than designing one-off screens, I developed a unified visual language with reusable components, defined tokens, and consistent patterns that scale across all three platforms.
9
Key Learnings
"The most significant decisions on this project weren't about what to design, they were about what the brief wasn't saying."
01.
Scope expansion requires stakeholder confidence, not just research.
Reframing a website redesign into a full service ecosystem redesign required demonstrating business value through early research evidence. Stakeholders supported expansion when reasoning was grounded in operational data, not assumptions.
02.
Service design thinking unlocks product opportunities.
Mapping stakeholder journeys across three roles revealed system-level patterns that individual user research alone would have missed. The operational gap came from thinking about the valet experience, not just the customer experience.
03.
Trust is designed in the spaces between transactions.
The biggest trust improvements weren't in the booking flow, they were in the moments after a customer finished placing an order. Designing for what happens between transactions turned out to be more valuable than optimising the transactions themselves.
