William Bruno
03 · Case study

CDM Smith

Role

Senior Experience Designer

Scope

IA + 67-component system

Studio

Verndale · 2024–2025

Status

Live at cdmsmith.com

Six regions, five growth areas, five audiences. One platform.

Context

CDM Smith is a $1.8B+ global engineering firm with twenty years of accreted content across six regions and no shared component library.

Challenge

No editorial governance meant every region rebuilt the same pages differently, and nothing could scale.

Solution

I led the full redesign from information architecture and content audit through a 67-component design system built for Sitecore XM Cloud.

Impact

Live at cdmsmith.com. A coherent visual language and governed system the regional teams can actually maintain.

01 · The problem

Twenty years of growth, none of it navigable.

A firm with a stated goal of reaching $2B by 2027, whose site couldn’t show it. The redesign had to bring order to all of it without making a billion-dollar firm feel like a brochure.

Pre-Design ran 58 days of discovery with recorded country-manager interviews across Australia, Latin America, the Middle East, and Poland. Design ran four sprints, May to August 2025, with Build overlapping to compress the timeline.

Redesigned cdmsmith.com on a MacBook
The redesigned platform on desktop.
Redesigned cdmsmith.com on an iPhone
The same structure, scaled to mobile.
02 · The restructure

From seven ungoverned sections to six governed ones.

The information architecture was rebuilt decision by decision: unify three expertise silos, restructure a twenty-page About section, promote markets, consolidate resources, and give every page a permanent numbered address. Step through the five calls below.

About Us restructure, before and after IA panels
20 flat pages became 6 parent sections with clear scope, giving editors a governance model they can maintain.
03 · Governance

Six regions in one IA, not six microsites.

Australia, Europe, Germany, Global, Middle East, Poland. Each with different practices, leadership, and growth strategies. One template family with distinct regional codes honors them all without fragmenting.

Every template maps to one of four jobs: Built to Inform, Built for Exploration, Built for Conversion, Built for Discovery.

CDM Smith design details exploration
Design details from the visual exploration.
Redesigned homepage with expertise-led navigation
The homepage: expertise-led, photography-anchored.
04 · The surfaces

A system that shows up on every screen.

Mega-menu navigation, stat cards, practice and priority cards. The same primitives, recombined across thirteen templates.

Mega-menu navigation
The mega-menu.
Stat card component
Stat cards.
Practices, priorities, and technologies cards
Practice cards.
05 · The system

A design guide and component library, built to last.

Beyond the screens: a type ramp, color tokens, a spacing scale, responsive grids, and 67 components, so six regions and an internal team can maintain one consistent system long after launch.

CDM Smith component library board
The component library.
CDM Smith graphics and components in context
Graphics & components in context.
06 · The tension

Critique that survived the design.

We presented mood boards. The client came back hard: the designs didn’t read as a digital leader or an innovative firm. Round two wasn’t iteration, it was a reframe.

Innovation cues moved into interactivity and animation. The system had to feel as innovative as the firm wants to be perceived.

13
Templates

organized into four jobs-to-be-done categories.

67
Components

fully documented for engineering handoff.

6
Regions

Australia, Europe, Germany, Global, Middle East, Poland.

Live
In production

shipped on Sitecore XM Cloud at cdmsmith.com.

The calls that shaped it

Templates organized by job, not by content type.

Inform, Exploration, Conversion, Discovery. Every template maps to a business outcome it has to support.

Six regions in one IA, not six microsites.

Country-manager interviews surfaced the differences. One template family and distinct regional codes honor them.

Workflow and governance moved into design scope.

The legacy CMS let any author publish unreviewed. Content workflow and versioning came into scope, not the fix-later pile.