Make priorities visible.
A restrained interface uses hierarchy, spacing, and a small accent palette to distinguish the important action from supporting information. The concept keeps the overview calm even when the work is busy.
RelayOps
Less friction. More forward motion.
Connect dispatch teams and field workers without adding another layer of complexity.
[1] The starting point
A question worth
exploring.
Dispatch work involves moving information as well as people. This concept explores how a shared product language could help an office team and a person in the field understand the same situation without seeing the same screen.
The direction separates overview from action. A desktop workspace makes status and priorities easier to scan, while the mobile experience focuses on the immediate task and the information needed to move it forward.
The direction
One product language across the dashboard, mobile workflows, and the story that brings it to market.
[2] On the drawing board
Before it looks finished.
The thinking takes shape.
Sketches, structure, and a possible way forward. A closer look at the ideas behind this concept.
01 / Mapping the flow
Find the flow before the finish.
An exploratory wireframe board separates the office overview from the field task. The arrows connect a shared workflow, while the screens give each person a different level of detail.
Illustrated concept study · Task flows / wireframes / interface
02 / Building the experience
Two contexts. One product language.
A component and layout study for dispatch and mobile. Shared statuses, a calm overview, and a focused task card make the relationship between the two screens visible.
- Overview for the office
- Focus for the field
- Consistent status patterns
[3] The development notebook
The paths. The pieces.
The reasons behind them.
A look beneath the finished surface: proposed journeys, small visual systems, and the questions that would guide the next iteration.
01 / Structure before styling
One job. Two very different contexts.
A dispatcher needs to see the whole day. A person in the field needs to know what happens next. This proposed handoff maps how a task moves between those two views without losing its context.
01
See what needs attention
Surface the exception first. The map supplies location, while the task list explains what needs a decision.
02
Give the task an owner
Keep the route, availability, and assignment together. Show the impact of a choice before asking for confirmation.
03
Support the person doing it
Give the field view one primary action. Keep support close by for the moments when the real world does not follow the plan.
Low-fidelity concept wireframes · Illustrative content · Proposed journey
02 / A system in the details
Build the small pieces. Connect the whole day.
A status vocabulary, a task card, and an activity trail form a small interface kit. Each state has a written label and a distinct symbol, so colour is never the only way to understand the work.
Status is shared language
Unassigned, in progress, and complete should mean the same thing on the office dashboard and the field screen. A task changes state; its identity stays consistent.
Design the interruption too
The proposed system keeps a visible place for issues and reassignment. A polished happy path is only one part of an operational product.
[4] Inside the thinking
The idea is in
the decisions.
Design around the situation.
The dashboard supports coordination. The mobile direction supports action in the field. Shared terminology connects them, while the layout responds to what each person needs to do.
Create a language that can grow.
Consistent status patterns and reusable interface components form the proposed foundation. New workflows could build on familiar behaviour rather than introducing a different system each time.
Keep exploring
A different world.
Another perspective.
Forma House
Art direction / Digital design