X-StudioCase StudyX-Studio × Kite · 2025
Kite is field operations software that assumes the user is on a roof rather than at a desk. One shared operational layer for dispatchers, managers and technicians, in the form each of them actually needs.
What we did
Studio concept. Kite is an X-Studio exploration rather than client work. It is published to show how the studio approaches complex operational software, not to report a deployment.
01 · The project
Construction, solar installation, maintenance, infrastructure and service companies coordinate people, equipment, jobs, schedules and information every day. Almost none of that work happens at a desk.
Kite is a concept for field operations software that starts from the opposite assumption: the product has to work wherever the work happens. It creates a shared operational layer between the office and the site.
This was the most technical exploration in the set, and the one where usability is measured by how quickly real work can move forward.
02 · The opportunity
Field operations are fragmented by nature. Everyone needs the same source of truth, but a dispatcher and a technician need it in forms that have almost nothing in common.
Is looking at a dashboard and needs to know what is at risk today.
Is standing on a job site with one hand free and needs the next action.
Is moving schedules and needs to see who is available right now.
Is tracking equipment across sites and needs location with status.
The product has to work wherever the work happens.
03 · Product principles
The office and the field share the same underlying data without being forced into the same interface.
On site. In progress. Blocked. Complete. Operational software earns its keep by making important states impossible to miss.
Limited connectivity, dirty hands, bright sunlight, noise and very little time. The mobile experience is built for all five.
A dashboard is only useful when it helps somebody decide what happens next. Every view ends in something you can do.
04 · The backbone
05 · The core experience
Progress, schedule, open jobs, team status, equipment, issues and reports without opening a second tool.
The status model is the backbone of the product, and every job carries its own lifecycle.
Who is working, current assignment, availability and job status. Built to support coordination, not surveillance.
Availability, assignment, maintenance, location and issues, tied to the projects that depend on them.
06 · The field interaction
Before starting, the technician sees location, scheduled time, equipment, the required checklist and any relevant notes. During the job they can check equipment, upload photos, add notes, report an issue and work through the checklist.
The closing action is deliberately the most prominent element on the screen. Complete job is a single, unambiguous target, because the last thing a person wants at the end of a job is a form.
07 · The map
The map can show active jobs, team members, equipment, project sites and issues. It never shows geography alone: every pin is paired with a status and something you can act on, so the map answers a question rather than illustrating one.
08 · Responsive design
Where the day is planned and the week is understood.
Where the work is actually done.
09 · Visual direction
Compact, high legibility, with a strong numerical hierarchy.
A dark operational interface where status colour is reserved for meaning.
Dense where it has to be, structured by clear grids and strong grouping.
Movement reports live change: status, availability, progress, completion.
10 · The takeaway
Kite let us explore a different side of product design, where the measure of quality is not how clean a screen looks but how fast a crew can get to the next job. Connecting operational teams should not add operational complexity, and most software in this category does exactly that.
