01
The problem
Jobs lived in chat. Delays lived in someone’s head. Product and ops were looking at different truths by lunchtime.
Project / 03
Lumen field ops
A field dashboard so product and ops could see jobs, delays, and who owned the next move.
- Client
- Lumen Labs
- Year
- 2024
- Category
- operations
- Stack
- WebMobile companionStatus feeds
02
You leave with
One board instead of three chat groups and a spreadsheet.
03Approach
A field dashboard so product and ops could see jobs, delays, and who owned the next move.
Name the statuses
We wrote down the real states a job passes through — including the ones nobody wanted on a slide.
One board
Web for the office, a companion view for the field. Same job, same owner, same delay reason.
Exceptions first
The home screen is what is stuck — not a gallery of everything that is fine.
Stay for the first month
After-sales was a weekly review of the board, not a ticket form.
- Shared board
- 1
- Same status
- Field + desk
- Included
- Handover
The build was focused, the communication was plain, and we shipped without extra noise.
01Selected work
Products built around how teams actually work.
Learning, retail, operations, and care — each one left with training and after-sales, not just a go-live date.
Have a product in mind?
Tell us the job your team needs done and we will map a scope.