Le papa
Give customers, owners and technicians a clear path
A staging workflow for bookings, arrival queues and consent, with separate customer, owner and technician portals.
The business and its needs
Bookings need to connect with arrival and service, while each role sees the relevant work. This case introduces staging workflows, not live payment or public activation.
KDS’s contribution
-
Designed separate customer, owner and technician portals.
-
Connected bookings, arrival queues and consent.
-
Built simulated payment and content review flows, keeping testing separate from activation.
How the workflow connects
The workflow illustrates the design scenario, not actual client outcomes. Publishable historical screens are unavailable.
Illustrative scenario
- Example: bookings, consent and arrival handled separately
The system workflow
- Customer selects a service and booking
- Staging records simulated payment state and consent
- Owner and technician follow the service within their roles
A closer look
Le papa staging version with demonstration content and simulated payment (Sample data)
Delivery record
- Scope and required materials confirmed
- Not yet confirmed
- First usable version
- Not yet confirmed
- Public launch
- Not publicly launched
Delivery time is measured from confirmed scope and complete required materials. We leave durations unstated where the record is incomplete.
Improvements after delivery
Reworked the three role portals
Reorganised navigation and workflows around customer, owner and technician tasks, with acceptance still on staging.
