Design for the worst moment of someone's day.
The strategic insight that shaped every decision: SERVPRO's users are not browsing. They are in distress. A pipe has burst. There's smoke damage. Mold has been found behind the walls. The person arriving at SERVPRO.com has a problem that feels overwhelming, and they need to feel — immediately — that they've reached the right place and that help is close.
That single insight reframed the entire design brief. This wasn't a website redesign. It was a trust system for people in crisis.
Positioning decision
The site needed to communicate two things in the first three seconds of arrival: we handle exactly your problem and your local team is right here. National credibility and local proximity had to coexist — and neither could be subordinated to the other.
Information architecture strategy
With 23 services and 1,900 locations, the IA challenge was genuinely complex. The strategic decision was to build the navigation around user urgency rather than SERVPRO's internal service taxonomy. Users in a crisis don't think in category labels — they think in situations. The architecture was designed to match the way distressed users actually describe their problems, not the way SERVPRO organizes its operations internally.
Local trust as a UX problem
The most consequential strategic decision was identifying local trust and emergency accessibility as the same problem. A national brand inspires general confidence. A local franchise phone number — displayed immediately, automatically matched to the user's location — closes the gap between "I trust this company" and "I'm calling right now." That reframe drove the technical architecture decision to implement IP-based location detection with ZIP code override, which in turn shaped the entire header and contact experience across the site.
Multi-team creative framework
Before any design work began, I established a shared creative framework across all three teams — defining the UX principles that would govern decisions, the approval workflow that would prevent fragmentation, and the division of creative ownership between design strategy (my team), content architecture (agency partner), and technical execution (development). Without that alignment, three teams working simultaneously on an enterprise site would have produced three different products.