Talking to the audience in their language

Customers should not need to translate the product before deciding whether to care. Translation is work, and most adverts have not earned homework privileges.

“A thousand songs in your pocket” took unfamiliar machinery and converted it into a familiar pleasure. No lecture on storage, compression or transfer speed. Those facts could prove the promise later; first the audience received a life-sized unit of value.

Cloud storage becomes files available everywhere. Faster machinery becomes another day’s output each month. Security becomes fewer panicked calls after someone clicks the wrong thing. A lower-latency network becomes a video call that stops making colleagues speak like haunted ventriloquists. Internal capability is converted into time, money, completed work or avoided grief.

Too many product teams call this dumbing down because jargon is where their expertise feels safest. The audience’s confusion gets recast as proof that the product is sophisticated. Very convenient.

Technical buyers still need architecture, controls and performance numbers. Give them depth, evidence and a route into the machinery. Just stop opening with the engine diagram when the person asked where the car goes. Plain language and technical seriousness are perfectly capable of sharing a page.

Listen to how customers describe the problem to a colleague. Borrow their nouns. Use a consequence they can picture. Then let the specification earn belief after the benefit earns attention. Test whether a stranger can explain the promise without repeating the category name. If the audience must perform the translation, expect some of them to leave the phrasebook unopened.

Behavioural principles

Behavioural ideas at play in this post

Short, plain-English explanations of the principles behind this post, with links to related books and examples in the archive.