LIXIL — American Standard, GROHE, DXV, LIXIL Insider
Scaling digital across brands, markets & 10K+ products
Building the digital foundation supporting multiple major brands, regional and multilingual experiences, ecommerce, and thousands of products — where every brand needed its own identity and the organization needed one scalable way to deliver it.
- Theme
- Multi-brand digital scale
- Portfolio
- 4 major digital brands & properties
- Catalog
- 10,000+ product SKUs
- Reach
- Regional and multilingual experiences
The chain every brand experience depended on
- Brands
- Digital platforms
- Product information
- Ecommerce
- Content
- Customer experience
The brands and properties it had to serve
- American Standard
- GROHE
- DXV
- LIXIL Insider
- Regional & multilingual experiences
Brand individuality and enterprise scalability, at the same time.
Managing digital experience across multiple brands creates a category of complexity a single website never encounters. It is not the same problem multiplied. It is a different problem.
Each brand in the portfolio had its own identity, its own audience, and its own reason to exist — which meant each one legitimately needed its own customer experience rather than a recolored version of someone else's. American Standard, GROHE, DXV, and LIXIL Insider were not variations on a theme. Treating them as interchangeable would have flattened exactly what made them valuable.
At the same time, the organization behind them needed the opposite thing: scalable technology, common processes, reliable product information, content operations that did not have to be reinvented per brand, governance that held, and capabilities that could be built once and used more than once. A catalog of more than 10,000 SKUs, sold through ecommerce, presented across regional and multilingual experiences, does not tolerate being handled four separate ways.
The central tension: Brand individuality plus enterprise scalability. Optimize only for individuality and every brand becomes its own bespoke operation the organization cannot afford to run. Optimize only for scale and the brands stop being distinct enough to matter.
Where I stopped managing websites and started managing an ecosystem.
This is the work where my thinking changed. Up to this point, the unit of work had been a site, a page, a campaign, a launch. Here the unit of work became the ecosystem — the set of platforms, data, content, and processes that determined what any individual brand experience could become.
My responsibilities spanned digital strategy, UX and customer experience, ecommerce, multi-brand website management, product catalog experiences, regional and multilingual experiences, content, SEO, digital operations, and the cross-functional technology coordination that held it together. In practice that meant working on the brand-facing experience and the shared foundation underneath it in the same week, and being accountable for whether those two things agreed with each other.
- Digital strategy across the brand portfolio
- UX and customer experience direction
- Ecommerce experience
- Multi-brand website management
- Product catalog and product information experiences
- Regional and multilingual experiences
- Content and content operations
- SEO
- Digital operations
- Cross-functional technology coordination
- Scalable capabilities usable across brands
Ownership, precisely: I led digital strategy, experience direction, and digital operations across these brand properties, and coordinated across the technology, ecommerce, marketing, product, and content teams who built and ran the underlying systems. Platform engineering and systems implementation were delivered by those teams and our partners; my contribution was the strategy, the experience decisions, and the connective work of making the parts operate as one ecosystem.
Four brands, one product catalog, many customer journeys.
The hardest thing about a multi-brand portfolio is that almost every requirement is legitimate. A brand team asking for a distinct experience is not being difficult; they are protecting the thing that differentiates them. A technology team resisting a fourth variation of the same capability is not being obstructive; they are protecting the organization's ability to maintain what it builds. Both are right, and the disagreement does not resolve itself.
Underneath that sat the product data problem. More than 10,000 SKUs had to be represented accurately across brand sites, catalog experiences, ecommerce, and search — each of which wanted the same information in a slightly different shape. Product information is where multi-brand digital either scales or quietly stops scaling, because everything customer-facing inherits its quality.
Regional and multilingual experiences added a further dimension. A market is not a translation. Different regions carried different product availability, different content needs, and different customer journeys, which meant the foundation had to flex by market without forking into unmaintainable variants.
And every one of these dimensions crossed a team boundary. No single group owned brand, product data, commerce, content, and market experience together. The customer met the sum of all of them.
Build capabilities, not four solutions to the same problem.
The approach that changed the economics was to stop treating each brand as a separate delivery project and start treating recurring needs as shared capabilities. When four brands need product catalog experiences, regional variation, content operations, or commerce integration, solving that four times is not four times the cost — it is four times the cost plus four times the maintenance, four times the governance, and four divergent answers to the same question a year later.
So the question I kept putting in front of teams was not how do we build this for this brand, but what is the capability here, and which parts of it genuinely need to differ by brand? That distinction — shared foundation versus deliberate difference — is what let brand teams keep the things that mattered to their identity while the organization stopped paying for accidental variation.
Product information sat at the center of it. Getting to a dependable, well-structured view of a 10,000+ SKU catalog was the prerequisite for everything downstream: catalog experiences that could be trusted, ecommerce that reflected reality, search and SEO that worked on real attributes, and content that did not have to restate product facts by hand for every brand and every market.
Innovation lived on top of that foundation rather than beside it. The American Standard 3D Room Designer is the clearest example: a net-new product experience that was only feasible because product data, configuration, and commerce were coherent enough underneath it to support a customer designing a real room out of real, purchasable products. Ambitious experiences are downstream of unglamorous foundations.
“Every brand deserves its own experience. No brand deserves its own version of everything.”
Making the shared foundation worth choosing.
A shared foundation cannot be imposed on brand teams; it has to be better than the alternative they would build themselves. Most of my leadership effort went into making that true and then making it visible — showing brand stakeholders what they gained in speed and reliability by working within the common approach, and taking seriously the cases where they genuinely needed something different.
That meant a lot of translation. Brand and marketing teams thought in identity, campaigns, and customer perception. Technology teams thought in platforms, data models, and maintainability. Ecommerce thought in conversion and catalog accuracy. Regional teams thought in market reality. Each frame was correct and none of them was sufficient alone, so the work was getting them to converge on decisions rather than trade positions.
I also held the line on sequence. Product information and content structure had to be trustworthy before the experiences depending on them could be improved, which is not the order anyone prefers — foundations are invisible and experiences are what get noticed. Protecting that sequence was one of the more valuable unpopular things I did.
Leadership principle: Standardization only holds when teams can see what it buys them. Governance that arrives as a rule gets worked around; governance that arrives as a faster path gets adopted.
What the foundation had to carry.
The measure of this work is not a single launch. It is the range of things one foundation had to support at once: four major digital brands and properties, a catalog of more than 10,000 SKUs, ecommerce, and regional and multilingual experiences serving different customer journeys — all of which had to remain distinct to customers while staying coherent to the organization.
Ecosystem thinking, established well before it was in the job title.
This is where enterprise digital leadership started for me. Not a website, not a redesign — a portfolio of brands, a large product catalog, commerce, content, multiple markets, and the operational reality of making all of it work with one organization behind it. The capability it demonstrates is holding brand strategy, customer experience, product data, commerce, content, and digital operations in view simultaneously, and making decisions that serve the individual brand and the wider system at the same time.
Digital scale does not come from making every experience identical. It comes from creating a strong shared foundation that allows brands and markets to meet different customer needs without rebuilding the organization behind them.