308. Story-driven marketing

In a fictional label project, two lettering drawings look persuasive on the screen. At label size, one is harder to read. The artist chooses the other and sends the approved artwork to the client. Nothing explodes, nobody works through the night, and the useful part of the story is still there: a change of scale changed a decision.

An actual customer story needs evidence of the work and permission to publish it. But the scene suggests where to look: at the drawing, the comparison and the judgment, before reaching for a crisis that the project may never have had.

A story lets the reader follow something as its meaning changes. The drawing that seemed finished becomes a candidate; the small label becomes the test. The software belongs in that sequence where it did something relevant. The person still gets credit for looking.

Keep the work in view

Begin with what someone was trying to make. Find the decisions that affected it, the conditions under which they worked and the result they could actually observe. These details give the account shape. A generic account of frustration followed by success could fit almost any product; a particular comparison gives the reader something to learn.

In the fictional scene, this summary goes too far:

The software rescued the project and transformed the artist’s workflow.

The events support something narrower and more interesting:

The artist compared the drawings at label size. One became harder to read, so the other went forward for approval.

The revision makes the choice intelligible. It does not yet explain a product’s contribution: no feature, command or software behavior has been supplied. Obtain that evidence if the contribution belongs in the account.

A product can be the subject of a sentence. A customer story need not hide its name or count how often it appears. Keep the actors distinct: the app displays a comparison, the artist judges it, the client approves the artwork. A different source may establish different actions. Follow it.

Name the kind of account

Choose the form that fits the material before polishing the opening.

Form	What the reader is being offered
Case study	An actual project, with checked facts and permission for the published material
Profile	A person’s work and perspective; no rescue plot is required
Demonstration	A result under stated input, settings and test conditions
Tutorial	An executable route to a stated result
Scenario	An explicitly invented example that illustrates a decision or method
Composite	A labelled combination of experiences or patterns, without pretending that invented particulars belong to one person

Keep the distinction visible before the invented particulars arrive. Giving a scenario a plausible customer name does not make it a testimonial. Calling a scenario fictional does not permit it to misdescribe a real product.

For an early pitch, record the proposed subject, the work, the product’s likely role, available evidence, missing evidence and publication permissions. The pitch can contain unanswered questions. Resolve them, omit the dependent claims or choose a form that accurately describes what is available.

Enter at a consequential moment

A scene earns its place when something in it affects what happens next. The reader needs enough orientation to understand that relation, not a complete biography before the first useful action.

Compare two openings for the lettering example:

Result first: The artist chose the lettering that remained legible at label size.

Decision first: At working size, both drawings were candidates. The artist reduced them to label size before choosing which to send for approval.

The first suits a compact account of the result. The second gives the comparison a little room and invites the reader to follow it. Neither needs a deadline, a failed export or a complaint about an earlier tool.

Situation, obstacle, attempt, change and result can help organize material. They are questions to ask of the source. Some answers may be absent: the first attempt worked, the customer was satisfied with the old method, the new tool served a different project. Preserve those circumstances. A profile can be absorbing because a person notices things carefully.

Use a title that identifies the work, the question or a supported result. Check its claims as closely as the body. A quoted outcome, project count or award does not become harmless decoration because it sits above the opening paragraph.

Follow an object through the account

A label, proof, source image or exported file can hold a story together. Introduce it where it matters, then return to it after a decision has changed its role. The recurrence should carry new information.

For the lettering scene, the route is simple:

1. Two drawings are candidates.
2. Both are inspected at the intended size.
3. One is selected for approval.
4. The approved artwork is sent to the client.

Those are the scene’s supplied events, not a universal four-part template. The artist’s criteria would enrich the account if an interview established them. An invented thought about “finally finding a voice” would change its kind.

Let a transition carry a shared object or question into the next paragraph:

The smaller view settled which drawing would go forward. Approval settled which artwork could be sent.

This is more connected than “Next came the approval stage,” because it explains what each stage decided. Use such a bridge where it helps. Repeating “the label” in every sentence merely makes the object conspicuous.

Interview for decisions, not a prescribed plot

Ask questions that allow an uncomplicated answer:

• What were you making, and who would use it?
• Which constraints affected the design?
• What did you inspect, compare or try?
• What made you keep one version and change another?
• Which part did the software perform?
• How did you judge the result?
• What would someone need to know before using this method?

A broad claim needs a follow-up: “Which step changed?” or “What did you observe?” A failed attempt may be revealing if one occurred. Do not make a complaint the price of appearing in the story.

Listen for small actions. A person who prints the specimen again, changes its size or sets two proofs beside each other may be explaining the central decision without naming it as a lesson. Ask what the action helped them see. Keep their answer’s scope and their uncertainty.

Agree on publication boundaries for names, quotations, images, project details and files. Permission to interview does not cover every supplied artifact. Let the subject check facts and proposed quotations; retain any restrictions that affect what may appear. An unpublished client detail remains unpublished even when it would improve the opening.

Keep the voices distinct

Direct speech can make a decision vivid because it lets a person state what mattered to them. Use actual, authorized words in a customer account. Do not write a polished exchange and attribute it to an interview that never happened.

A paraphrase can be better than a long quotation. Identify whose account it is, retain its meaning and preserve relevant qualifications. A customer’s “I found this easier on this project” cannot become a measured speed claim or a promise about everyone’s work.

Distinguish what the subject said, what you observed and what you infer. These can coexist in a developed paragraph:

• The subject describes why they made the comparison.
• An image shows the two versions at the stated size.
• The writer explains how that comparison relates to the reader’s task.

Each part has a different basis. An image cannot disclose an unrecorded motive; a confident recollection cannot replace a timing measurement. The distinctions usually need accurate verbs and attribution, not a warning label on every line.

Put evidence where it helps the reader look

Choose material that supports the actual account: a specimen, a glyph or master comparison, a source image, a rendered result, a relevant setting or an exported file. There is no standard package that every story must contain.

Place evidence beside the claim it clarifies. Explain what to inspect in a caption. If the scale, input, settings or version differs between two images, identify the difference rather than allowing it to masquerade as an improvement. Keep the before image fair.

A finished artifact shows a result. It does not by itself establish which tool caused it, how long the work took or what would have happened otherwise. Use measurements with their method and conditions. Where only a qualitative result is known, describe that result well.

Production claims need particular care. An SVG screenshot does not prove that a machine accepts the file. A completed print or engraving establishes an outcome under its own conditions. Keep the device, material and workflow scope attached to any conclusion that depends on them.

Provide text alternatives for essential visual information, credit the work and retain permission records. If the article uses a featured typeface or artwork, identify it without making the body difficult to read. The specimen should help the story’s reader as well as honor its subject.

Leave useful questions in plain view

A story can explain a workflow or a decision that a feature list cannot. It need not surround every factual answer. Someone asking which formats are supported may need a list and its conditions before they need a customer’s experience.

Give price, compatibility and license answers where the decision requires them. Check the current offer. Do not borrow a historical trial duration from a case study and let it become today’s promise.

Treat unsuitable use cases respectfully. A person who needs an unsupported format has a legitimate reason to choose something else. State the limit and any supported alternative. An honest account may help them decide to leave.

Keep a tutorial executable

A tutorial can accompany a story or stand on its own. State the goal, input, version, prerequisites and expected result. Put actions in ordered steps and inspect the result at useful points. See chapter 205.

A clean sample can isolate an operation; a difficult one can teach preparation. Explain why you chose it. Include predictable mistakes and supported recovery where they help learning, without staging a failure for the product to resolve. State license and production requirements before the learner invests work that depends on them.

Let the surrounding account carry perspective and warmth. The step itself should tell the reader what to do. A memorable scene cannot rescue an ambiguous instruction.

End where the work has arrived

Return to the object if the return adds meaning. At the beginning, the fictional label held a design question. At the end, approved artwork goes to the client. That is an ending at the scale of this story.

A next step may be useful: compare two versions at their intended size, inspect a sample, read the procedure. Connect it to the demonstrated work and state its requirements. A profile does not have to become a download request in its final sentence.

Keep the result bounded. Do not add future commercial success, universal approval or a transformed career because the actual ending feels quiet. Quiet may be the right way to let the decision remain in view.

Review the story and its purpose

Read first for continuity. Can a reader follow the work, understand the choices and distinguish each person’s contribution from the app’s behavior? Then check the evidence, permissions, comparisons, links and proposed action.

Wait, but an accurate sequence can still be lifeless. Look for the detail that changes the reader’s understanding: the scale of the label, the repeated test, the criterion that ruled out a tempting version. Give that detail room. Cut the paragraph that merely announces how inspiring the project was.

Evaluate the publication against its purpose. Task completion may matter for a tutorial; resolution of a recurring question may matter for an explanation. Visits and trial starts describe different events and do not by themselves prove a sale’s cause. Content performance also cannot substantiate a customer result inside the article.

Practice a change of judgment

Use this fictional account: a designer prepares two poster layouts, prints both at the intended size and finds that the smaller caption in one is hard to read. The designer chooses the other layout. No software feature, timing measurement, client response or sales result is supplied.

Write a short account that begins before the comparison and ends with the choice. Keep one object in view across the passage. Then write a result-first version for a compact summary. Preserve the same events in both.

One possible pair:

Following the comparison: Two poster layouts were ready for comparison. The designer printed both at their intended size, where the smaller caption in one proved hard to read. The other layout was chosen.

Result first: The designer rejected one poster layout because its smaller caption was hard to read at the intended size, and chose the other. Printing both candidates had exposed the problem.

The first version lets the print change the reader’s understanding alongside the designer’s. The second states the result and explains its basis. The caption returns in both accounts with a different role: first a detail to inspect, then the reason for the decision. Neither gives the software credit for making it.

On the second pass, find the sentence where the reader learns why the choice changed. Give it an appropriate pace. Remove any added thought, crisis or future success; replace general praise with an observed action. The story should leave the reader with a decision they can understand.