Turning “our process is messy” into things teams could fix

The situation

A dealership group whose customer lifecycle ran across disconnected teams and tools — sales, service, back-office systems, spreadsheets, and a series of handoffs between them.

What everyone thought the problem was

That the process was messy. Which was true, and not actionable. “Messy” cannot be assigned to anyone or sequenced into a plan.

What I found

Interviews across the operation, including senior operational leadership, followed by end-to-end journey mapping. The breakdowns were not evenly spread: they clustered at handoffs, where context was lost between teams that each had a correct view of their own segment and no view of the whole.

The decision

Build one shared end-to-end picture before proposing any fix, so that prioritisation could be argued from evidence rather than from whichever team was loudest.

What we made

A service blueprint covering the full lifecycle — customer actions, frontstage interactions, backstage work, and the system dependencies underneath — with the breakpoints identified and located.

What changed

The group had a first shared view of its own customer journey. Lost context and specific breakpoints became visible, and a vague complaint turned into a set of named issues that teams could sequence and own.

What this proves

Not every product problem is an interface problem. Some are operating-model problems wearing an interface costume.