303. From features to benefits

A second pattern need not be a second set of spacing decisions. In Vexy Lines, a Fill Clone follows changes to its source fill's direction and spacing while allowing differences in attributes such as color. You can keep that relationship and still make the two fills look different.

There is a benefit here, and it does not require a promise about saving the reader's afternoon. The useful part is the relationship: change the source pattern, and the clone follows. Name what stays connected and what can vary. The reader can decide whether that is the part of the job they wanted to change.

This chapter develops benefits from mechanisms, chooses a useful point of entry for each audience, and turns the result into copy with enough detail to be believed. The positioning chapter helps decide which job the page should address. Here we follow that job closely.

Start with the change in the work

A feature describes what a product has or does. A capability describes what someone can do with it. A benefit explains why that capability matters in a particular task. These distinctions help you draft; readers do not need to see the labels.

Consider this fictional proof-review tool. Its supplied facts are:

• The reviewer chooses two PDF proofs.
• The app displays the chosen proofs side by side.
• A recorded comment is attached to one of those proofs and a page number.
• The app does not decide which proof should be approved.
• No measured time saving or accuracy improvement has been supplied.

A feature list might say that the tool has a two-document view and page comments. That is a useful start for a specification. For someone reviewing a correction, the consequential detail is that a comment identifies the proof and page it concerns. The writer can follow that detail into the work:

Feature: A recorded comment includes its proof and page number.

Capability: Reviewers can identify the document and page a comment concerns.

Benefit: The comment carries its location with it; the writer does not need to repeat those details in every comment's text.

Each step depends on the supplied behavior. We have not established live collaboration, automatic difference detection or a way to reopen the page by clicking the comment. Those would be useful features. They would also be new facts.

The worksheet is finished when it reveals something worth saying. Do not keep asking why until an ordinary convenience becomes a promise of a better life. Sometimes the benefit is that the next person knows which page you mean.

Let detail carry the appeal

Compare three introductions to the fictional review tool:

Abstract: Improve collaboration with powerful review capabilities.

Overstated: End approval confusion forever.

Developed: A comment can be precise and still leave out the place it belongs. Record it against a proof and page, and those details stay attached to the comment. “The heading is too dark” now has an address.

The developed version begins with a recognizable distinction. It follows the mechanism and ends with the practical consequence, expressed through a small comparison. The comparison refers to the attached location; it does not suggest that the comment is mailed, routed or automatically delivered.

The last phrase is optional. A more literal ending also works:

The comment identifies the proof and page it concerns.

Read both in their intended setting. The first may suit a product-page explanation; the second may suit a comparison table. A dry observation earns its space by sharpening the point. It need not accompany every feature.

Useful detail also gives a paragraph somewhere to go. A heading, a page number and the two visible proofs offer more to explain than a collection of adjectives about efficiency. You can show what the reviewer sees, how the comment relates to it, and what remains a matter of judgment.

Keep mechanism and consequence together

A benefit can lead when it answers the reader's immediate question. A mechanism can lead when readers need it to understand whether the benefit applies. Neither order belongs exclusively to one audience or register.

For the fictional tool, compare:

Benefit first: Keep each comment tied to the proof it concerns. The app records the chosen proof and page number with the comment.

Mechanism first: The app records the chosen proof and page number with each comment, so its location remains explicit.

The first gives someone considering the tool a reason to look. The second explains a behavior they may already be investigating. Both make the same claim.

Try moving the benefit back beside its mechanism during review. If the combination needs another fact to become true, find that fact or revise the benefit. “Make every approval correct” cannot follow from attaching a page number. More confident punctuation will not bridge that gap.

This review works in the other direction too. A paragraph that names six controls may be accurate yet leave the reader to discover why they appear together. Follow one consequential relationship far enough to make it useful, then return to the other controls where the page's purpose requires them.

One feature, different points of attention

Readers doing different jobs may care about different parts of the same behavior. You can change emphasis without inventing a personality for each reader.

For the fictional proof tool:

Reader's current task	Useful point of entry	Supported copy
Inspect two proofs	Both documents are visible	Put the chosen proofs beside each other for review.
Write a page comment	The location is recorded	Attach the comment to its proof and page.
Respond to a comment	Its location is explicit	Use the recorded proof and page number to identify what the comment concerns.
Approve a version	Judgment remains with the reviewer	Compare the proofs, then make the approval decision yourself.

These are task differences. They do not establish that one reader is anxious, another ambitious and a third short of time. If research supplies a relevant concern, use it with its actual scope. A job title alone supplies very little psychology.

Nor does a changed opening require a different product promise. The app has the same behavior in every row. Adapt the path to the fact, and keep the fact intact.

Show what becomes possible and what disappears

A benefit may introduce an action or remove a repeated one. A linked pattern can make a variation possible; it can also remove the need to repeat a supported pattern adjustment on the clone. Both descriptions may help, provided the link really covers the property being discussed.

Return to the Vexy Lines example:

Change the source fill's spacing and the clone follows. Give the clone a different color, and the two fills can retain their shared pattern relationship without looking identical.

The example distinguishes shared behavior from independent appearance. It does not claim that every attribute is linked, that every fill type supports cloning, or that the resulting artwork needs no further adjustment.

The documented clone types are Linear, Wave, Circle, Spiral and Handmade. Other fill types produce a simple copy. If the reader is choosing a fill for this workflow, that condition belongs beside the claim. A footnote after the purchase button is too late.

Removal claims deserve close reading. An app that records a comment's location removes one piece of repeated writing. It does not remove every misunderstanding about the comment. Describe the repetition that changes and let its importance come from the reader's work.

Let the reader supply the feeling

Relief, satisfaction and pleasure can follow a useful result. Writing those feelings into a promise does not make them happen.

For the fictional tool, this sentence gives the reader something to recognize:

The next comment still needs an explanation. It already has a page number.

Its small shift in pace lets the unchanged work and the useful change sit beside each other. It may suggest relief without instructing the reader to feel relieved. In a longer example, keep the same document or comment in view as its role changes; the continuity helps readers see what the tool contributes.

Warmth can also come from interest. Explain why two nearly identical proofs are worth comparing, or how a small correction affects the task, when the source provides those particulars. Do not assume every benefit must begin with distress. A reader may simply want to try an interesting variation.

Give proof the right job

A measured result, a demonstration and a customer's account provide different kinds of evidence. State what each establishes.

A measurement needs its method and scope. Name the tested version, inputs, comparison and relevant conditions. Use the precision the evidence supports. If a result is surprising, explain it; do not substitute a more plausible invented number. Conflicting measurements need examination before they become one convenient headline.

A demonstration makes a behavior inspectable. Show the inputs, action and result that support the claim. A demonstration of two proofs on screen establishes that view for the demonstrated case. It does not establish how much faster every reviewer will finish.

A customer's account records that customer's experience. Keep the wording, permission and context required for its use. An account of a successful export cannot establish compatibility with every machine. An award or attractive studio photograph supplies even less information about that question.

Specificity helps readers check a claim; specificity alone is not proof. An invented value with three decimal places remains invented. A real control name can also sit inside an unsupported sentence.

When no measurement exists, describe the supported behavior directly. A precise qualitative benefit is complete without a percentage attached.

Make constraints part of the choice

Suppose the fictional proof tool has a demo that displays comparisons but cannot save them. That is an additional supplied fact for this example. The invitation can say:

Try two proofs side by side in the demo. Comparisons cannot be saved there.

The reader can decide whether an unsaved comparison is a useful trial. Do not promise that the demo will settle every question about the paid product, or imply that viewing the screen verifies an export workflow it cannot exercise.

The same care applies to source quality, supported formats, license eligibility and required review. Explain how a person can work within a constraint when the facts support a useful route. Some constraints simply limit the offer. They do not all need to become selling points.

For production claims, keep each boundary visible. Exporting a format, opening it in another app and obtaining a suitable machine result are separate claims. Evidence for the first does not establish the other two.

Change the placement for the surface

The fictional tool's comment-location behavior can appear in several forms:

Surface	Example
Product-page heading	Keep comments tied to their proof and page
Explanatory body	The app records a proof and page number with each comment, so readers can identify its location.
Feature comparison	Comments attached to a proof and page number
Release note, if this is the supplied change	Recorded comments now include their proof and page number.

The release-note example needs evidence that the behavior is new. The other examples do not imply a release date. Surface changes can quietly introduce new claims, especially words such as now, again and still.

For a procedure, supply the actual controls and sequence from the relevant product version. The packet above does not name them, so it cannot support click-by-click instructions. For a warning or error, lead with the condition and action the reader needs. Benefit writing must not delay either.

Develop the voice in a second pass

First write the literal relationship. Then give it a readable movement.

Using the fictional packet, a serviceable draft is:

The app displays two proofs together. It records comments with a proof and page number. Reviewers make approval decisions.

A developed version can hold the work in view:

Put the two proofs beside each other and inspect the pages that need attention. When you record a comment, its proof and page number go with it, so the location need not become a second explanation. Deciding what to approve remains your work.

The paragraph follows a reviewer's attention from the visible documents to a particular comment and then to a decision. The middle sentence has room to explain a relationship. The last settles the boundary. This is one useful rhythm, not a compulsory pattern.

Now compare the revision with the packet. It should not acquire automatic marking, saved comparison history or measured speed. Then read for positive qualities: can the reader picture the task, follow the thought and find the useful change? A draft can pass a claim check and still need a better paragraph.

For another version, begin with the comment rather than the two proofs. Keep its location as the recurring detail. End as soon as the consequence is clear. Compare the versions for this page's purpose; do not choose by sentence length or the number of times they say you.

Practice the transfer

Use this new fictional packet rather than rephrasing the worked example:

• A layout app can show three user-selected color variants of the same layout together.
• Editing the color in one variant does not change the other two.
• No copying, exporting or color-accuracy behavior has been supplied.

Write a feature sentence, a capability sentence and a short benefit paragraph. Choose a concrete point of attention: perhaps the same shape seen in three colors. Give the paragraph a development, then an ending. Do not add a deadline, customer quotation or claim about what the reader will feel.

One possible paragraph is:

Set the three color variants beside each other and look at the layout as a whole. A color has neighbors here; the comparison shows it in the place where you intend to use it. Adjust one variant's color while the other two keep theirs.

The paragraph moves from the whole layout to the relationship between colors, then to an action. It describes inspection without claiming that the app chooses a palette or predicts a printed result. The writer's interest comes from looking at the arrangement, not from inventing a troubled customer.

Next, revise for someone who wants to compare variants and for someone who wants to adjust one. The source facts should remain the same. Finally, remove the fact about independent editing and revise again. Any benefit that depended on that independence must change too.

Check the result in two readings:

1. Evidence: Each outcome follows from a supplied behavior. Conditions, uncertainty and remaining human decisions keep their scope.
2. Craft: The paragraph notices something useful, develops a connected thought and uses a cadence suited to that thought. Its ending adds a consequence or leaves the relevant detail in focus.

Keep the version that helps this reader see the change. That is enough work for a benefit to do.