Touchpoint

A touchpoint is any interaction between a person and an organisation: a search result, an advertisement, the product itself, an invoice, a support call, a delivery driver, a letter.

The term comes from service design and marketing, and its value is that it forces attention beyond the screen.

Why counting them changes the conversation

Most product teams own one or two touchpoints and assume they own the experience. Mapping the full set usually shows the product is a minority of the contact, and that the moments deciding whether someone stays are elsewhere: the onboarding email that never arrived, the invoice nobody could read, the cancellation that required a phone call.

This is the distinction between user experience and customer experience made concrete.

Owned, earned and shared

Some touchpoints are controlled directly. Some are not: a review site, a forum thread, a colleague’s opinion. Those shape expectations before the product is ever opened, which is why a first-run experience that contradicts what people were told lands badly.

In practice

List every touchpoint in a journey and mark who owns each. The gaps, where the answer is nobody or several departments, are where experiences reliably break, and they are almost never inside the product.