Enterprise Web Transformation

What problem or opportunity existed?

Brother's digital presence had grown the way most enterprise estates do — one justified decision at a time. Across business units, regions, and product lines, 19 websites had accumulated, together holding roughly 5,000 pages, and around them sat a wider digital estate of microsites, platforms, and supporting systems. Each had its own history, its own content conventions, and its own reasons for existing.

For customers, the result was a fractured journey: the same brand behaving differently depending on where they landed, with product information that did not reliably agree with itself. For internal teams, it meant duplicated effort, unclear ownership, and a publishing process where the cost of any change multiplied across every property in the estate.

The opportunity was not to redesign a website. It was to replace a fragmented estate with a coherent enterprise ecosystem — and to do it without losing the search equity, commercial performance, or business-unit needs the old estate was carrying.

What I owned, led, and influenced.

I helped lead the digital experience and web operations side of the program. I owned the experience direction — the mobile-first strategy, the navigation and information architecture, and the UX standards the new ecosystem would be built against. I also led the content rationalization approach that took roughly 5,000 pages down to about 600, and shaped the governance and operating model that would keep the new estate coherent after launch.

I worked in close partnership with technology, commerce, marketing, product, and regional business stakeholders, and translated between them — turning business requirements into experience decisions, and experience decisions into things engineering and content teams could actually execute.

Teams, systems, and constraints involved.

The technical surface alone spanned CMS, eCommerce, PIM, DAM, enterprise search, analytics, and SEO tooling — each with its own data model, its own owner, and its own opinion about where the source of truth lived. Getting product data, content, and commerce to agree was a prerequisite to any experience work, not a consequence of it.

Layered on top of that were organizational realities: multiple business units with legitimate differences, regional requirements for a US launch that had to extend cleanly into future markets, and a content migration touching thousands of pages with real SEO consequences attached to every redirect decision.

The genuinely hard part was sequencing. Consolidation, replatforming, content rationalization, and operating-model change all had dependencies on one another, and none of them could wait politely for the others to finish.

The strategy, experience, or operating model introduced.

I pushed the program toward a mobile-first experience strategy and a single, consistent architecture — one navigation model, one content structure, one set of UX patterns that every business unit worked within rather than around.

The content rationalization was the decision that made the rest possible. Rather than migrating what existed, we established criteria for what deserved to exist: what customers actually used, what search demand supported, and what the business genuinely needed. That reframing is what turned roughly 5,000 pages into about 600 without losing what mattered.

I also introduced the governance layer — clear ownership, publishing standards, and decision rights — so the consolidated ecosystem would not quietly re-fragment as soon as teams resumed normal operations.

Aligning teams and moving the initiative forward.

Most of the leadership work was alignment. I spent significant time making the case that consolidation was a business decision rather than an aesthetic one, and building a shared understanding of what the new ecosystem was for. Where business units had competing needs, I worked to distinguish genuine requirements from inherited habit — usually by returning to customer evidence rather than debating preference.

I established forums and decision frameworks so choices got made at the right level and stayed made. And I kept the program honest about sequencing: what had to be true before the next thing could start, and what could safely be deferred to a post-launch phase.

The impact that resulted.

Brother launched the US experience on a new enterprise web ecosystem, bringing 19 websites, alongside the supporting microsites and digital systems around them, into a single coherent platform and reducing roughly 5,000 pages to approximately 600. That launch established the enterprise foundation — a reusable structure rather than a one-off build.

The broader transformation remains in progress by design: remaining sites and future markets can migrate onto the same foundation over time, benefiting from the architecture, patterns, and governance already proven in market rather than needing a rebuild to get there.

Beyond the launch itself, the durable outcome was operational: a governed ecosystem with clear ownership and standards, and a web operations model capable of running and evolving it.

The leadership capabilities shown.

Orchestrating an enterprise ecosystem — not redesigning a website. This is the work of holding experience strategy, platform architecture, content, search, governance, and organizational change in view simultaneously, and sequencing them so a transformation of this size can actually land.

• Enterprise Transformation
• Web Operations
• UX Leadership
• Global Strategy
• Governance
• Change Management
• Program Leadership