One booking looks different to the people involved. A Rider prepares a journey, a Driver manages work, and an Operator coordinates bookings and company administration.
One product, different jobs
FieldOps Taxi is our in-house platform in development. It brings focused Rider and Driver apps, an Operator web workspace and shared backend work into one connected product.
The useful design question is what each person needs when responsibility moves between them. Designing a screen for one role is only part of that job. The next person needs enough context to understand the request and take the appropriate next step.
Start with one handoff
Start with one handoff. Write down who begins it, what information they provide, who receives it and what that person needs to decide. Then ask what happens when information is missing or a request changes. Those questions help define the rules between the interfaces before more controls are added.
Give each surface a purpose
Give each surface a clear purpose too. The Taxi marketing website introduces the product and its roles. The Operator web app is the workspace for booking queues, company administration and support. Rider and Driver have their own mobile interfaces. Keeping those purposes clear helps people understand where they are and what they can do there.
Follow the actual behaviour
The platform remains in development. Its separate role previews show parts of the work; they do not establish a completed live journey. The same principle applies when reviewing a connected product: follow the selected handoff through the actual behaviour, as well as looking at each screen.
Explore the FieldOps Taxi project, or tell us about a process that crosses people and systems.