YIYANG LIUYL
Back to work

(04) — Case study · Service Agreements

Service Agreement Materials — itemize before activation, protect margin at renewal.

Office users couldn't itemize materials needed for Service Agreement Visits until after activation — blocking accurate pricing and forcing technicians into return trips. This case study traces the six-phase process behind the redesign, from problem framing through Maze usability testing to stakeholder sign-off.

Client

ServiceTitan

Role

Lead Designer

Year

2023

Team

Service Agreements

Hi-Fi Deliverables

Final designs, shipped across the visit takeover flow.

High-fidelity screens covering the full Scope of Work experience — Visit Details, Cost Estimates, Equipment, Services, and Materials — across quick-estimate and commercial-scale use cases.

Fig. 01 — Hi-fi screens across the visit takeover

Fig. 01.1 — Hi-fi screens across the visit takeover

Clickable Prototype

Try the flow, add a visit and itemize materials end-to-end.

Interact with the high-fidelity prototype below to walk through the Add Visit takeover — including the Scope of Work, Equipment, Services, and Materials sections.

Fig. 02 — Clickable prototype

Open in new tab ↗

End-to-end design process

Six phases, from problem framing to engineering handoff.

Tap any phase to explore the activities, decisions, constraints and deliverables that shaped the final design.

Design process · SA Materials

Materials in Scope of Work

Service Agreement · Office user & technician workflows

01Discovery

Problem framing & requirements

Office users can't itemize materials for SAVs until after activation — blocking accurate cost estimation and forcing technicians into return trips.

Office user personaTechnician personaCurrent-state gapJourney map

Core problem

No pre-activation material itemization exists today
Users locked out of cost data at the exact moment of pricing decisions
Technicians make return trips due to missing materials
02Strategy

Goals & success metrics

Define measurable customer benefits, product vision, and how this feature lays the foundation for future TitanIntelligence automation.

OKR definitionItem Requisitions feedPricebook alignmentTitanIntelligence foundation

Customer benefit metrics

↑ Increase % of visits completed on time
↓ Reduce number of return trips per visit
↓ Reduce delta between estimated and actual material cost
Protect margins against rising material costs
03Constraints

Constraints & technical feasibility

Map dependencies, hard technical limits, and competing user needs across quick-estimate and high-volume commercial customers.

Materials ↔ Equipment gapPricebook unit cost limitVisit takeover densityEquipment squad dependency

Key constraints

No formal Materials ↔ Installed Equipment association today — users work around with tags and custom fields
Unit cost editing blocked — data sourced from Pricebook only; only total cost is manually overrideable
Design must serve both quick-estimate and full-itemization users from one interface
04Design

Iterative design exploration

Multiple layout drafts stress-tested against real equipment names, commercial volumes, and the Equipment–Service–Materials information hierarchy.

Layout templatesLong equipment namesCommercial high-volumeProgressive disclosure

Variants tested

Equipment · Service · Materials layout templates — tab, accordion, and inline row approaches
Stress-tested truncation and wrapping with real-world verbose equipment names
Commercial use cases with large equipment datasets and multi-site agreements
05Research

Maze usability testing

Validated comprehension and task success. Surfaced a critical discoverability failure in the Pricebook cost alignment action.

Pricebook alignment not foundAffordance placementCopy clarityRenewal flow

Critical finding & response

"Update cost to align with Pricebook" action was not discoverable without prompting
Surface as inline alert, badge, or contextual button — not a buried menu action
Reword copy to make intent and benefit immediately clear
Make the affordance first-class in the renewal flow specifically
06Alignment

Stakeholder reviews & sign-off

Cross-functional review with Product, Engineering, SA domain SMEs, and Field/CS. Capture blocking concerns before development begins.

ProductEngineeringSA domain SMEsField / CSEng handoff spec

Next steps after sign-off

Engineering handoff spec with annotated design decisions
A2 component mapping for visit takeover flow
UX debt tickets for any legacy component swaps

Fig. 03 — Interactive process map

Reflection

What this project taught me, about designing for range and depth.

01 — Users

Balancing two distinct user needs

One of the core challenges was designing for two very different user groups: field users who needed quick estimates and commercial users who required detailed material breakdowns. Rather than optimizing for one at the expense of the other, we used progressive disclosure to support both workflows. Users see a lightweight summary by default, with full itemization available when needed. The result is an experience that adapts to different levels of complexity without forcing either group to change how they work.

02 — Systems

Designing beyond the immediate feature

This could have been approached as a simple request to add a materials section to the visit form. Instead, we treated it as a foundational systems problem. Material data was structured at the agreement level, creating a single source of truth that powers Item Requisitions, aligns with the Pricebook, and lays the groundwork for TitanIntelligence material recommendations. By designing the underlying infrastructure—not just the surface feature—we created a solution that scales with future workflows and capabilities.