Customer feedback
Control the layout
“I’d love to drag that over and basically customize it.”
The participant wanted to change the number of drivers shown and the space given to that information.
Platform investment / Lytx
Lighthouse: Making the case for customizable dashboards
Lighthouse makes the case for customizable dashboards on the main Lytx platform, using customer needs to define the proposed investment.
The proposal connects a configurable workspace to the tasks a fleet manager needs to complete. The UX team’s concepts show how dashboard information could lead into review and coaching.
- My contribution
- Owned ideation, business justification, and research materials.
- Scope
- Main-platform dashboards and reusable modules.
- Evidence
- Customer feedback and UX team design concepts.
01 / Investment case
Customers were assembling their own views
Customer feedback described fixed layouts that did not match individual responsibilities. Research also recorded customers moving between product tabs or preparing custom reports outside the platform.
That evidence gave the business case a specific problem to address: let customers choose the information they need and act on it in the same workspace.
Existing reporting effort
Prepare a report for the job
“I spend probably five to eight hours customizing it.”
This describes effort in an existing workflow. The research does not establish time saved by Lighthouse.
The business case also used win/loss data as commercial context. It did not isolate dashboards as a cause of lost deals. The competitive review compared customization, sharing, and data coverage available at the time.
02 / Experience
Useful defaults, with room to customize
The proposal gives new users an All in One starting view. Dedicated Safety, Fleet, and Admin dashboards offer a narrower focus. Experienced users could build their own dashboards from the same module library.
Edit mode exposes the choices directly: name the dashboard, select a group, choose KPIs and widgets, then arrange and save the layout. Shared views and administrator-set defaults were part of the proposed scope.
03 / Information to action
Review fatigue evidence and arrange coaching
The concepts use a fatigue alert to show what happens after a manager notices a problem. Review opens the supporting evidence, with options to contact a coach or create a coaching session.
AI-assisted pattern detection is part of the proposed experience. These screens demonstrate the intended workflow, without establishing detection accuracy or coaching outcomes.
A / Review
Inspect the pattern
The review brings events from multiple days together with video stills, route context, and a timeline. The manager can examine the evidence before deciding how to follow up.
B / Coordinate
Contact a coach with context
When a conversation is needed, the contact view keeps the fatigue topic attached to the exchange. Driver information and recent behavior data appear beside it.
C / Assign
Select examples for coaching
The session view lets a manager select relevant events and review coaching history. The design offers self-coaching or an assigned coach before the session is created.
04 / Investment sequence
Build the shared foundation first
The proposal starts with a common front-end codebase and an API-fed widget architecture. New and refreshed pages would use those modules, so work on one page could extend the library available to dashboards.
Defaults provide a starting experience while customization adds control for established users. The plan then extends to sharing and administrator permissions. Reduced engineering effort and faster onboarding were reasons to invest, with benefits still to be measured.
- Common UI foundation
- Page structure and a shared front-end codebase.
- Reusable module library
- API-fed widgets available to new and refreshed pages.
- Dashboard configurations
- Default views, custom layouts and shared team views using those modules.
Original estimated delivery plan
The proposal grouped the work into four estimated quarters. This is the original planning sequence. The current delivery target is recorded below.
Q1 / Foundation
Common codebase, page structure, widget architecture, and data connections.
Proposed staffing: UX Engineering and one sprint team.
Q2 / Defaults and AI exploration
Default modules, notifications, and dashboard templates. Proposed AI prioritization and task automation.
Proposed staffing: UX Engineering, two sprint teams, and Labs.
Q3 / Reuse and customization
Extend module reuse across pages and let advanced users compose dashboards from the library.
Proposed staffing: UX Engineering and two sprint teams.
Q4 / Sharing and administration
Share custom dashboards and let administrators set default views for users.
Proposed staffing: UX Engineering and one sprint team.
05 / Current status
In development for Q1 2027
Development recently started, with delivery targeted for the end of Q1 2027. The customer and business evidence on this page explains the investment case. The screens and phased plan document the proposal.
Delivery and measured outcomes remain pending.
The earlier Next-generation Lytx UI case study covers my navigation design work. Lighthouse addresses the dashboard investment separately.