Ask so what until you reach the reader's life

Turn any feature into a benefit by asking so what until the answer matters to the reader.

Open your own product page, or the last post where you described what you sell, and read the list of what you offer. Most small-business pages are a list of what the business has. A tuition centre might list small classes, experienced teachers, air-conditioned classrooms and free parking. Each item is true, and each one leaves the reader to work out why it matters. Most readers will not do that work. They skim, see the same items every competitor lists, and leave.

The fix is to keep asking yourself "so what?" about each item until you reach something the reader cares about. Digital marketing foundations lesson 4.2, "Match what you offer to jobs, pains and gains", made the same point from the strategy side. The so-what chain turns it into sentences you can put on a page.

Features, benefits and why benefits take more work

A feature is what the product has or does. A benefit is what changes for the reader because of that feature. Features are easy to write because you know them by heart. Benefits are harder because they happen in the customer's life, and you have to find out what they are. That extra work is also what makes benefits persuade.

Take Priya, who runs a tuition business for schoolchildren (Priya and her figures are an invented example). Her features include a curriculum aligned to the school syllabus, a weekly progress note, and the one she is proudest of: small classes of six students. A parent reading her page wants their child to stop losing marks on the same kind of question. A class of six is one reason that might happen, and the page has to make that connection for the parent.

Running a feature through the so-what chain

The so-what chain works like this. Ask "so what?" of a feature and answer honestly and plainly. Then ask "so what?" of that answer. Keep going until the answer is something the reader would say about their own life. Each step should be plain and true. The chain does not make the product sound grander. It moves the description from the seller's side of the counter to the reader's side.

Priya's chain for her small classes runs like this:

Small classes of six. So the tutor can see every child's working during the lesson. So mistakes are caught in class while they are fresh, rather than on the exam paper. So the child stops losing marks on the same kind of question, and the parent stops finding out about the problem only when results arrive.

The same method works for any product. Mei Ling, a home baker in Punggol, bakes her cakes the morning of delivery. So the sponge is still soft at the party. So nobody leaves a half-eaten slice on the plate. Farah sells workwear with a hidden button placket. So the blouse does not gap when you move. So you can raise your hand in a meeting without checking your buttons. Each of these chains ends in a moment the customer can see.

Knowing where to stop the chain

Stop when the answer is in the reader's words and about the reader's life. If you keep going past that point, the chain drifts into big abstract claims. Priya could push on: the child gains confidence, then reaches their full potential in life. That last step is vague, every competitor says it, and a parent cannot picture it.

Stopping too early has two signs. The first is an answer that still describes the product, such as "the tutor can give more attention". The second is an answer that uses words a customer would not say, such as "learning outcomes improve". If you see either one, ask "so what?" again.

The chain can also carry you into promising something you cannot deliver. If Priya's chain ended at "your child gets an A", she would be promising a result no tuition centre can guarantee, and saying it could mislead parents. Benefits must be true, so stop the chain at the last step you can honestly stand behind. Lesson 3.3 sets out what the rules say about promising results.

When you have a final answer, check it against the voice-of-customer file you built in lesson 1.4. If a customer phrase says nearly the same thing, use the customer's version, because it will almost always be more specific than yours. Priya's final answer matched what two parents in her file had said: "she keeps making the same careless mistakes" and "I only find out when the results come back".

Writing the benefit first with the feature as proof

Once you have the benefit, put it first and keep the feature in second place as the reason to believe it. Compare two lines for Priya's page. The first is the bare feature: "Small classes of six students." The second leads with the benefit: "Catch careless mistakes before the exam does. With six students per class, your tutor checks every child's working in every lesson."

The first line is a fact the parent has to interpret. The second gives the parent what they want, then shows how it happens, and it is the one Priya should use. If she left out the feature, the benefit would be one more promise on one more website. Lesson 3.2 covers how to attach proof to a claim.

This order works for headlines, bullet points on a landing page, the first line of an ad, and a product description on Shopee. There is one exception. Readers comparing products closely near the end of their decision sometimes want features listed plainly so they can check them side by side, so a specification table on a product page still has a place. Even then, the line above the table should say what those features mean for the reader.

For the activity, pick five features you would normally list on your website or in a post. Run each one through the chain out loud or on paper, and when you reach the reader's life, check the wording against your voice-of-customer file before you write it down.

Pick five features of your product. For each one, keep asking so what until you reach a benefit in the reader's own words.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).