Why Good Work Gets Ignored

Most small businesses and community organisations do not lose clients because their work is poor. They lose them because the client cannot picture what is being sold. A pension adviser explains tax wrappers. A bookkeeper lists reconciliation cycles. A community energy group talks about governance structures. Every word is accurate, and none of it sticks.

The problem is not complexity itself. People happily follow complicated stories about hospital dramas or police investigations. The problem is abstraction. Stories give the brain something to hold: a person, a place, a moment when something changed. Your service already contains all three. You simply have not pointed at them yet.

Start With the Person, Not the Process

Technical writers are trained to explain systems. Storytellers are trained to follow a person through a system. That single shift solves most clarity problems.

Compare these two openings from a fictional home insulation firm:

• Process version: "We conduct a thermal survey, assess cavity suitability and install injected insulation to current building regulations."
• Story version: "Margaret's house in Levenshulme was cold by four o'clock every afternoon. The heating was on, the bills were high, and the front room still needed a blanket."

The second version sells the same service, but the reader now has a stake. They know who is cold, where, and when. When you later explain cavity suitability, it arrives as relief rather than as homework.

A useful rule: one protagonist per story. If you are describing a service to families, keep one family in view. If you serve three very different audiences, write three short stories rather than one sprawling case study that features everybody and moves nobody.

Use a Three-Part Spine You Can Reuse

You do not need a literary structure. You need something short enough to repeat in a proposal, a website page and a five-minute talk at a community meeting. Try this spine:

• The situation: who they are and what ordinary life looked like before.
• The snag: the moment it stopped working, the thing they could not solve alone.
• The turn: what changed, who did what, and what is different now.

Notice that the snag comes before the solution. This matters. If you introduce your service before the reader understands the difficulty, you sound like a sales pitch. If you let the difficulty breathe for a sentence or two, your service arrives as the answer to a question they are already asking.

The turn should be specific. "We sorted everything out" means nothing. "By the Friday, the accounts were filed, the penalty was cancelled and Priya slept properly for the first time in a fortnight" gives the reader something to want.

Turn Jargon Into Concrete Detail

Jargon is usually a shortcut for people inside the work. Clients are outside it. Translate, do not simply simplify.

• Instead of "bespoke solutions", describe the thing you actually made: a two-page plan, a fortnightly visit, a single phone number.
• Instead of "robust compliance framework", describe what happens on a Tuesday morning when someone checks the file.
• Instead of "holistic support", name the first conversation, the second conversation and who leads each one.

Numbers help when they are attached to a person. "We reduced processing time by 40 per cent" is fine. "The forms used to take Anwar three evenings; now they take forty minutes on a Sunday" is memorable. Use both, side by side, if your sector expects figures.

Sensory detail is optional, but one concrete image per story does a great deal of work. A waiting room chair, a stack of unopened envelopes, a photocopier that jams on the same tray every week. Readers trust specifics.

Where to Use Stories in Practice

You do not need a marketing budget. Narrative fits into places you already write.

• Homepage: open with a short client story rather than a mission statement. Two or three sentences is enough.
• Proposals and quotes: include a "what happens next" paragraph written as a sequence of events, with names of stages and who is responsible.
• Onboarding: a short welcome story about a client who was nervous at this exact point reduces panic emails.
• Talks and funding bids: lead with one person's experience, then widen out to the numbers.
• Case studies: keep the three-part spine. Situation, snag, turn. Then a short list of practical outcomes.

Community groups often have the strongest material and use the least of it. A single meeting where a decision was made, or a volunteer's first week, tells a funder more about your culture than a page of outcomes.

Keep It Honest and Keep It Yours

Three safeguards. First, get consent before naming anyone, and be willing to change identifying details. Second, do not invent the ending. Readers forgive an unfinished story far more readily than a fabricated one, and a "we are still working on this" ending is often more persuasive than a neat bow.

Third, build a small story bank. Keep a note of moments as they happen: a comment from a client, a problem you solved on a wet Wednesday, a question someone asked twice. Half an hour a month is plenty. After a year, you will have twenty stories and no excuse for starting any document with "We are a dynamic provider of..."

Try it on one page this week. Pick a real client, write the situation in two sentences, the snag in two more, and the turn in three. Read it aloud. If you can picture the person while you read, so can everyone else.