Executive Narrative · Enterprise Digital Transformation
Dominion Automotive
Enterprise Digital Transformation — Rebuilding the Systems Customers Actually Experience
How Dominion Enterprises modernized a fragmented automotive retail technology portfolio — aligning executives, product, engineering, and marketing around a shared customer-first platform model without disrupting the operating business.
ThesisLarge organizations do not become customer-first through redesigns alone. They do it by rebuilding the systems customers actually experience.
Large organizations do not become customer-first through redesigns alone.
They do it by rebuilding the systems customers actually experience — and by aligning the people who own those systems around decisions the business can execute.
The mandate was not to ship prettier surfaces. It was to modernize a portfolio the operating business still depended on — without breaking it.
Chapter 01
Business Context
A major automotive retail technology portfolio at the intersection of consumer marketplaces and dealer SaaS.
Dominion Enterprises' Automotive Division operated one of North America's largest automotive retail technology platforms — consumer marketplaces, dealer software, and brand experience under one corporate roof.
As Head of Product Design & Creative Director, Marketing, Social & Brand Experience (2015 – 2023), the work sat with executive leadership, product management, engineering, marketing, and analytics. The business needed better acquisition, engagement, conversion, and long-term customer value while millions of users continued to depend on the portfolio every day.
This mattered because growth had already produced the enterprise condition that stalls transformation: fragmented journeys, disconnected products, and legacy systems that made consistency expensive.
Enterprise product ecosystem
Not a collection of redesigns. A platform model connecting consumer journeys, dealer operations, shared design systems, and AI-assisted product bets under one modernization thesis.
Chapter 02
Inflection Point
Why the organization could not keep operating the same way.
Years of growth had created fragmented user experiences, disconnected products, and legacy technology that limited innovation. Continuing as a collection of local redesigns would not produce one coherent customer journey.
Consumer marketplaces asked high-intent buyers to navigate purchase decisions across surfaces that did not share hierarchy, language, or conversion logic. Dealer SaaS carried dense operational work that became costly when information architecture failed. Marketing promised experiences the product did not always deliver — and digital trust eroded in the gap.
The inflection was organizational as much as technical. Without a shared platform thesis, every division could justify its own patterns and exceptions. Incoherence had become normal. That is the moment incremental modernization becomes a leadership mandate — not a craft preference.
Enterprise friction compounds quietly — across business units, handoffs, and legacy constraints — until customers feel it as one incoherent journey.
- Fragmented customer journeys across marketplace and dealer surfaces
- Legacy infrastructure that made shared patterns slow and contested
- Business units optimizing locally without a platform thesis
- Digital trust at risk when promise and product diverged
Chapter 03
Dominion Design System
The operating language that turned fragmented products into one coherent portfolio.
After the fractured-to-unified mandate was clear, the work became systems work: shared patterns, atomic design, governance, and documentation that product and engineering teams could actually ship against.
The design system was not a component library theater. It was how Dominion made coherence transferable — brand integrity, consistent experience, faster development, streamlined workflows, and data-driven decisions treated as operating requirements.
Unified Product Ecosystem
The system mapped discovery through delivery — tokens, components, templates, and pages — so marketplace and dealer surfaces could share one operating language.
Unified Product Ecosystem
Strategic Pillars
Business Impact
Chapter 04
Executive Decisions
What was invested in, refused, reconciled, and sequenced.
The durable work was decision-making under ambiguity: which problems deserved investment, which complexity had to be removed, how conflicting priorities could be reconciled, and where customer value had to outweigh organizational habit.
01Invest in coherence before spectacle
The organization could have funded a visible platform replacement — or continued local redesigns that never produced one journey.
Alternatives considered
- Announce a full platform rebuild and freeze legacy evolution
- Continue product-by-product redesign without shared systems
- Outsource a greenfield platform and migrate later
Tradeoff
Less ‘new platform’ theater. More continuity for revenue-critical systems while coherence improved.
Why
Enterprise modernization fails when the operating business cannot absorb disruption.
Result
Shared design systems and cross-functional delivery practices became the spine of modernization.
02Prove the future with AI product bets — then ask for scale
Dealers needed better ways to predict intent, run marketing, and evaluate inventory — problems legacy tools were not designed to answer.
Alternatives considered
- Wait for platform purity before shipping new capability
- Bolt AI features onto unchanged legacy workflows
- Buy point solutions without an experience thesis
Tradeoff
More product risk on new surfaces. Clearer proof that modern experience could change dealer decisions.
Why
Working proof points change investment conversations. Slideware does not.
Result
Activator and Car Score became modernization proof points for predictive marketing and vehicle intelligence.
03Reconcile product and brand under one customer-first vision
Customers experienced Dominion as one company even when internal teams optimized as separate channels.
Alternatives considered
- Keep product and brand experience organizations permanently separate
- Treat marketing as a campaign layer on unchanged product journeys
Tradeoff
Harder cross-functional coordination. Higher integrity between promise and product.
Why
Digital trust collapses when marketing and product speak different languages.
Result
Product, marketing, social, and brand experiences were aligned under a shared customer-first vision.
04Make governance part of product direction
Without critique rituals, documentation, and handoff standards, shared patterns would fragment again under local pressure.
Alternatives considered
- Ship shared components without operating practices
- Defer governance until after the portfolio ‘stabilized’
Tradeoff
More process discipline short term. Less silent rework over time.
Why
Long-term scalability had to inform short-term decisions. Unowned systems do not stay coherent.
Result
Shared standards, documentation, critique rituals, and handoff practices reduced rework across teams.
01
Temptation
Win the room with a complete platform replacement narrative
Rejected
Big-bang rebuild theater the operating business could not absorb
Prioritized instead
Incremental coherence through shared systems and targeted AI product investments
Strategic consequence
Modernization could proceed while marketplaces and dealer tools continued to operate.
02
Temptation
Treat every local exception as inevitable enterprise complexity
Rejected
Complexity preserved by habit rather than customer or business need
Prioritized instead
Shared patterns, clearer journeys, and decisions that removed avoidable friction
Strategic consequence
The portfolio could move toward one operating language instead of accumulating permanent special cases.
Chapter 05
Organizational Alignment
Who had to align, where priorities conflicted, and how momentum was built.
No single function owned the full customer journey. Alignment required executives, product, engineering, marketing, analytics, and creative to share prioritization — not just review decks.
Research, usability testing, journey mapping, and analytics became the foundation for that shared judgment. Stakeholder workshops created a decision space where local roadmaps could be challenged against portfolio outcomes.
Governance kept alignment alive after workshops ended: critique rituals, documentation, and delivery practices that made quality transferable. Momentum came from proving the model — first through shared systems, then through AI product bets that made the future tangible.
Where priorities conflicted
- Business continuity versus modernization speed
- Local product optimization versus shared patterns
- Campaign urgency versus product integrity
- Legacy investment versus AI product bets
How alignment was created
- Evidence-led prioritization across divisions
- Cross-functional delivery rhythms
- Explicit governance for shared systems
- Executive partnership on transformation thesis
Chapter 06
Car Score
Vehicle intelligence for inventory decisions — a primary product application of the system.
Car Score
AI-assisted vehicle intelligence combining pricing, market demand, vehicle condition, merchandising quality, competitive analysis, and predictive scoring to help dealers make faster inventory decisions.
Shown in light theme only — a focused product reading of condition, pricing, demand, and competitive signals, not a theme comparison.
CarScore Platform Overview
Vehicle Condition Report
Pricing & Demand
Condition Detail
Market Comparison
Risk Signals
Decision System
Chapter 07
Activator
Predictive dealer marketing — a product proof of the platform model.
Activator
AI-powered automotive platform for predicting buying intent, automating marketing, and turning customer data into actionable insights — predictive AI, customer journeys, real-time analytics, and intelligent campaign management.
Activator applied the shared design system to a new AI-assisted surface — intent prediction, journey intelligence, real-time performance, and campaign automation for automotive teams.
Activator Platform Overview
Real-Time Command Center
Predictive AI
Campaign Performance
Chapter 08
Business Impact
Organizational clarity, platform coherence, and proof points — without fabricated percentages.
Published outcomes are organizational and platform-level. Presentation graphics contain illustrative figures; those numbers are not treated as verified KPIs here.
Impact showed up as portfolio leadership, research-driven customer outcomes, scalable design systems, experience unification across product and brand, multidisciplinary team capacity, executive partnership on transformation, and AI proof points — Activator and Car Score — that made the modernization thesis tangible.
Portfolio leadership
Led UX strategy across enterprise SaaS platforms and automotive marketplaces.
Customer outcomes
Improved customer acquisition, engagement, conversion, and retention through research-driven design.
Operating systems
Established scalable design systems and cross-functional delivery practices.
Experience unification
Unified product, marketing, social, and brand experiences under a shared customer-first vision.
Organizational capacity
Built multidisciplinary product, UX, creative, and marketing teams.
Executive confidence
Partnered with executive leadership on product vision and digital transformation initiatives.
What This Demonstrates
Dominion is evidence of transformation leadership under enterprise constraint: modernizing a legacy-dependent portfolio without breaking the business that depended on it.
It shows how customer understanding, strategic sequencing, cross-functional alignment, and governance become an operating model — and how AI-assisted product bets can prove that model before larger investment is asked.
Alberto González is someone trusted to modernize organizations — not simply design products.