How do I map a customer problem to the right product and journey?
By Trayan Hristov · Founder, Thrivelia · 19 November 2026
Before I draw a customer journey, I want someone to finish this sentence: “They came to us because…” If the answer is “they viewed the collection”, we’ve described their browser. We still don’t know what they needed. The same tap on a tile sample could come from a homeowner choosing a kitchen floor or an installer checking a specification for a client.
Start with the problem and list the decisions in order
Take an illustrative flooring retailer. A homeowner wants a kitchen that looks right in the evening light and can be installed before the builder leaves. First they need a finish they like. Then they need a product suitable for the application, the right quantity and a reliable delivery date. If the product team cannot confirm suitability, pass the question to somebody qualified. No reminder or bundle fixes missing information.
The product path is the sequence of items or services that solve those problems. It might be a sample, a comparison, a quote and the right accessories for an approved installation. The journey path is the experience that moves the project through those decisions: where it happens, what triggers it, who owns the next step and when to stop. An accessory can be a sensible next product six weeks from now and a terrible recommendation today.
Observable state | Question still open | Next experience and stop rule |
Sample delivered, finish undecided | Does the colour work in my room? | Offer a side-by-side comparison in different light. Stop once a finish is chosen. |
Finish chosen, quantity unknown | How much do I need? | Open the room calculator or offer a quote. Suppress sample reminders. |
Quote accepted, installer awaits delivery | Will the materials arrive together? | Operations confirms stock and logistics. Pause cross-sell during an open issue. |
Installation confirmed | What does this surface need now? | Send product-specific care. Offer another room only if the customer signals a new project. |
Resolve the handoff before writing the copy
Give the project a stable reference. Two samples and an installer’s order can belong to one room. Allow a person to link a quote to that room without silently assuming everyone at the address is the same buyer. The showroom, website and trade team need to agree what counts as a new project. Use an unknown state when a match is uncertain.
Now map the exception paths. A sample lost in the post goes to fulfilment. A discontinued shade goes to merchandising with a substitution that has been checked. A homeowner who finished elsewhere can opt out of project reminders. Give every unresolved state an owner and an expiry. This is where many journey diagrams stop being useful if you leave the room too soon.
Test one decision before rebuilding the whole journey
I’d start with delivered sample to accepted, paid project. Define the window from actual lead times. Compare eligible projects assigned to the new decision aid with the current experience. Count unique projects, net contribution and cancellations. Check showroom and phone orders before interpreting a drop in web conversion. Work through the sample-to-project calculation, then see how the DUSK example changes once fabric is decided but access is still open.
Run the exercise
Use the Journey brief tab with one person from operations and one from CRM. Agree who can end the journey when the project is resolved. Download the editable workbook or browse the other retention workshops.

.png)



Comments