Uniting 100+ Sites

Snapshot

Client | Bridgestone is the world's largest tire and rubber company, with ~50 production facilities and nearly 55,000 employees across North America, Latin America, and Europe, Serving both B2C and B2B audiences.

Company | iCrossing

Focus | Global B2B & B2C platform unification

Role | Experience Lead, Research

Team | 15 people across design, content strategy, product, and engineering

Timeline | 12 months to launch, plus ongoing enhancement support

Impact | +93% increase in time on site, 30% reduction in post-launch errors

Bridgestone’s digital ecosystem was fragmented, with siloed experiences for commercial, consumer, and corporate audiences.


This lack of integration weakened brand consistency and limited opportunities to cross-sell products and solutions.

Context

Bridgestone’s digital footprint had grown to 15+ NA sites, 36+ LATAM sites, 75+ EMEA sites, and 1,000+ URLs, each built by a different team with no coordination. Navigation, content, and even basic product info varied from site to site, which weakened brand consistency and limited cross-selling across the business.

Approach

The goal was a shift in model, not just consolidation: from product-centric, organized around what Bridgestone sold, to customer-in, organized around what audiences needed. That meant one platform that could serve both B2B and B2C audiences without watering down either, and scale as regions and products were added.

We built one reusable component set flexible enough to power dozens of sites consistently, rolled out in phases: Bridgestone and Firestone Commercial first, then Consumer, Motorcycle, Bandag, GCR, LATAM, and EMEA.

It's infrastructure that scales for new regions and new products without starting over.

Strategy

Here’s what I prioritized:

  • Fixed the process first. I introduced requirement templates and a creative-specific QA step, the fastest way I knew to close the design and dev gap.

  • One experience, audience-aware. Consumer and commercial journeys stayed distinct where it mattered and unified everywhere else.

  • Built for what’s next. The framework supports new regions and product launches without a rebuild every time.

Challenge

Design and development were misaligned before I arrived, and it had cost the team the client’s confidence. Earning that back was part of the job. B2B and B2C stakeholders also cared about different metrics and wins, so reaching one coherent experience meant getting both rooms to agree on what “better” meant.

To close the gap, I set up an internal and external review and approval process with a predictable cadence and timeline, and brought developers into the room early instead of only at approval checkpoints. That rebuilt the client’s confidence in how the team operated. For stakeholders, I ranked business units and features by ROI and customer value, which gave both rooms a shared, objective basis for what shipped first. Everything else was documented for a future state.

B2B and B2C stakeholders cared about different wins, so reaching one experience meant getting them to agree on what “better” meant.

Ownership

As Experience Lead, I directed a team of three designers alongside content strategy, product, and engineering, staying close to research and wireframing.

  • Turned feedback into direction. Synthesized input from a wide stakeholder group into one clear, consistent design direction the team could act on, and cleared blockers as they came up.

  • Aligned design and engineering. Ran development refinement sessions to keep both sides aligned on what was feasible.

  • Bridged the data. Partnered with our analytics partner to translate real data into design decisions across the team.

  • Owned the client relationship. Presented solutions directly to external stakeholders and managed their expectations.

Impact

Key North America metrics:

  • Efficiency. ~69% YoY reduction in cost per site (~$175K to $55K). 85% pattern reuse saved ~15% in design and authoring time.

  • Engagement. Time on site up 93%, nearly doubling YoY. PLP views up 71% and PDP views up 27%.

  • Cleanup. 470 pages and assets removed. Post-launch errors and rework down 30% thanks to the creative-specific QA process.

It’s not just about building sites more efficiently, it’s about delivering a seamless, trustworthy experience everywhere Bridgestone shows up.

Reflection

  • Developers needed to be in the room. Early on, only tech leads sat in on refinement sessions, not the developers doing the work. Once I brought developers in directly, they could react to real screens and flag constraints on the spot, and our estimates got noticeably more accurate.

  • Constraints should come before the meeting. One stakeholder team wanted something technical limitations wouldn’t allow, and we didn’t find out until we were mid-design-session. It derailed the agenda and cost us time. Naming constraints upfront would have kept things on track.

Discovery Process

Designs

Testing

Previous
Previous

Turning Trust Into a Health Habit

Next
Next

Commerce Built for a 3,000-Store Co-op