Transforming 100+ Sites into a Unified Platform

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, + ongoing enhancement support

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


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

The Challenge

Bridgestone's digital footprint had grown into more than 15+ NA sites, 36+ LATAM sites, 75+ EMEA sites, and 1,000+ separate URLs, each built independently by a different team. Nothing talked to each other. Navigation, content, even basic product info varied site to site, not because anyone planned it that way, but because a decade of independent builds does that.

They needed one platform that could hold B2C and B2B audiences without diluting either, cut the duplication, and actually scale as new regions and products got added.

The Reality

This was never going to be a straightforward redesign. A few things made it harder:

  • A fragmented ecosystem.
    Over 100 sites, each built in isolation, meant inconsistent navigation, content, and flows everywhere I looked.

  • Stakeholders pulling in different directions.
    B2C and B2B teams cared about different metrics and different wins. Getting to one coherent experience meant getting both rooms to agree on what "better" even meant.

  • Real technical limits.
    No clean-slate rebuild here, every solution had to work inside existing tech and data constraints, not around them.

  • A trust problem I inherited.
    Design and development had been misaligned before I got here, and it had already cost the team the client's confidence. Part of the job was earning that back.

Strategy &
Key Decisions

Turning 100+ fragmented sites into one coherent platform meant building something flexible enough to hold every audience's needs without collapsing into a generic mess. Here's what I prioritized:

  • One component system, built to be reused.
    A single, modular component set now powers dozens of sites: faster to build, easier to keep consistent.

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

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

  • Fixed the process, not just the product.
    I introduced requirement templates and a creative-specific QA step; the fastest way I knew to close the design/dev gap and rebuild trust with the client.

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

My Role

As Experience Lead, I stayed hands-on with research and wireframing throughout, while working closely with three designers, content strategy, product, and engineering. My work included:

  • Unblocked the team.
    Turning stakeholder feedback into clear direction the team could actually act on, and clearing blockers when they came up

  • Aligned design and engineering.
    Running development refinement sessions to keep design and engineering aligned on what was actually feasible

  • Bridged the data.
    Serving as the main point of contact with our analytics partner, folding real data into design decisions

  • Owned the client relationship.
    Presenting solutions directly to external stakeholders and managing their expectations

  • Synthesized at scale.
    Synthesizing feedback from a wide stakeholder group into one clear, consistent design direction

The Impact

The rebuild moved the needle in ways I could actually measure:

  • 90% YoY cost per site, driven by 85% pattern reuse across the platform

  • +93% increase in time spent on site

  • +71% increase in PLP page views, 27% increase in PDP page views

  • 470 pages and assets removed; a real cleanup, not just a redesign

  • 30% reduction in post-launch errors, thanks to the creative-specific QA process

What I'm proudest of: this isn't just a nicer-looking site. It's infrastructure that scales for new regions and new products without starting over.

Key Learnings

  • Bring developers in earlier.
    The sooner they're in refinement sessions, the sooner technical constraints surface, and the more accurate our estimates get.

  • Set expectations with stakeholders early, not during review.
    Naming technical limitations upfront saved us friction later, every time.

Discovery Highlights

Key Wireframes

Usability Testing

Next
Next

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