A visual language
for field service
I created a new icon library for ServiceMax.
Then, I applied its visual rules to the scheduling and map views in ServiceBoard.
Role: Senior Visual Designer
Scope: Icon system, visual direction, and ServiceBoard UI
Products: ServiceMax and ServiceBoard
The dispatcher’s workspace
Dispatchers use ServiceBoard to assign work orders to technicians and crews. The scheduler shows them which jobs are waiting, who’s available, and what’s already booked. When ServiceMax updated its brand, my task was to make that workspace easier to scan.
Starting with the logo
I turned the logo’s sharp angles and unique gaps into simple rules. These rules cover line weight, proportions, and shape construction. Familiar metaphors and simple forms guided the icon explorations.
The library had to stay clear at small sizes and allow for future updates. The goal was to convey clear meaning in all languages. The library also needed consistent rules for expanding the family.
Icon construction rules
I created the icon library on a shared grid. The calendar illustrates how I applied the rules to an outline icon. I used a 2 px stroke with square ends, left 2 px gaps where the lines break, and rounded the outer corners with a 2 px radius. The square ends and gaps reflect the cuts in the ServiceMax wordmark.
Icon audit
ServiceMax helps dispatchers coordinate technicians, jobs and appointments. Dispatchers must compare detailed info across a busy schedule. They also need to keep work orders and resource availability in mind.
The visual refresh followed an update to the company’s identity. The brief asked for clearer information, a better hierarchy and easy navigation. I created a new icon library and visual standards. Then, I used them for screen design and UI component design.
Cloud or exchange arrows?
Should we keep the cloud metaphor for syncing, or would arrows be a simpler choice? I explored both approaches while keeping status feedback visible.
Icon explorations
Selected explorations for calendar, synchronization, messaging, and PDF icons.
A library built for the work at hand
The library covers key topics in field service. These include calendars, crews, maps, equipment, work orders, and their connections. I created the standards and designed the new assets. This brought together mixed styles into a unified visual family.
Navigation symbols, utility icons, and service metaphors all follow a similar method. Filled and outline treatments preserve the identity of a symbol as its state changes.
Bringing the system into the interface
My main responsibility was the visual design of screens and UI components. I collaborated with UX designers on parts of the structure and behavior. Then, I developed the treatment for schedules, job cards, and supporting views.
The examples below show what a dispatcher does: compare assignments, check job details, find available people or teams.
The job list and resource timeline stay side by side. Repeated rows, clear typography, and familiar symbols help dispatchers compare details.
Earlier interface reference
Archived scheduler context with jobs, resources and appointments.
New visual direction
Refined cards, navigation symbols and a consistent visual hierarchy.
Keep the selected job in context
The map view keeps the list visible while a detail panel presents the selected work order. The visual language is consistent across views. However, the list's treatment shows different behavior.
Cards for assignment. Rows for inspection
The scheduling view focuses on assignments. The map view highlights selection and inspection. Visual cues show these different tasks.
I developed a new icon library and applied the visual direction to key product areas. Some proposed screens and components were not shipped before the later Salesforce transition.
Scheduling: assignment
1 A raised card suggests dragging. 2 The adjacent resource row provides assignment context.
Maps: inspection
1 The highlighted row shows which work order is open. 2 Details open alongside the list.
Consistency lives in the details.
The contribution was both a new set of assets and the visual logic connecting them. The icon library was used in the product. The team implemented some screens and components, but others remained in design.
After I left, the company moved toward a Salesforce-based interface. This case shows my role in creating an icon language. I also integrated it into the visual design of field-service tools.
A visual system becomes useful when its rules hold up in the interface.