The client already had a strong brand and a clear ambition for a more connected customer journey. The harder problem was that the journey crossed several organisations that did not operate as one system.

OEM, importer and dealer processes had developed separately. Customer data, retail routines, service activity and local execution sat in different systems and management structures. A better website or app could improve the visible interface without resolving what happened behind it.

The engagement therefore treated omnichannel retail as an operating-model problem rather than a digital front-end project.

A customer journey map becomes useful only when each important event has an owner, a system path and a management response behind it.

The work therefore linked journey design to CRM and data points, dealer workflows and the processes used to manage sales, service and aftersales performance. Training and enablement were included because a new process is not operational when the network cannot execute it consistently.

This shifted the discussion away from touchpoint design on its own. The relevant question became whether the organisation could carry the intended experience through the actual retail system.

The programme included loyalty and membership concepts, EV charging behaviour, apps, showroom visualisation and service-tablet use cases. The point was not to declare all of them part of the future model.

Ideas were grouped into measures, modules and pilots, then connected to roadmap and business-case work. That created a way to separate concepts worth scaling from concepts that needed more evidence.

The original programme also used structured gate reviews to test effectiveness and commercial viability as work progressed.

The engagement was staged rather than launched as one large transformation package.

• Define scope, guardrails and governance.
• Develop the initial hypothesis and topic portfolio.
• Turn topics into measures and modules, then sequence them in a two-to-five-year roadmap.
• Build business cases for the modules that required investment.
• Use post-project KPI reviews to test whether the selected measures were working and remained scalable.

This sequencing made the transition traceable. Strategy, customer experience, process design and investment decisions were connected rather than handed from one workstream to the next.

• An integrated view of sales, service, ownership and loyalty journeys across digital and physical channels.
• Standardised retail processes across OEM, importer and dealer interfaces.
• Shared performance logic and dashboards covering relevant retail and aftersales activity.
• Pilots for selected loyalty, mobility and digital-retail concepts.
• A two-to-five-year roadmap connecting measures and modules to business-case work.
• A repeatable governance model using KPIs and gate reviews across markets.

Omnichannel retail is easy to reduce to a technology or customer-experience programme. The operating difficulty is usually elsewhere.

A customer can move from digital research to test drive, purchase, delivery, service and loyalty activity without caring which legal entity or system owns each step. The organisation cannot ignore those boundaries. It has to decide who owns the event, which data moves, what the dealer sees, which KPI applies and how exceptions are resolved.

That is why the strongest part of this case is not the individual digital concepts. It is the attempt to connect journey design, retail process, data, dealer execution and governance before scaling the programme across markets.