Singular narrative creation template

In the first edition, I spoke about why one person’s story beats any other narrative. You can read the first edition here. Today, I want to make it usable.

So here’s a simple template you can copy-paste the next time you want to write a case study, a LinkedIn post, a pitch opener, a change memo, or even an internal email.

The core idea

A singular narrative is about one person in one moment with a meaningful shift.

Everything else is supporting material.

The singular narrative creation template

Step 0: Pick the right “one person”

Choose someone who represents your audience, not your company.

Name (real or anonymised):

Role + context (in 1 line):

What they care about (1 line):

What’s at stake if things don’t change (1 line):

If your character feels like a label (a customer, a farmer, a manager), you haven’t picked a person yet.

#1 The hook scene (3 to 5 lines)

Start inside a moment, not with the background.

When/where is this happening?

What are they doing right now?

What small detail makes it vivid? (object/phrase/sound/screen/gesture)

What is the emotional weather? (stress, confusion, fatigue, hope, embarrassment)

#2 The friction (2 to 4 lines)

This is not the industry challenge. This is what your person is living through.

What is broken/slow/risky/confusing?

What workaround have they created? (shadow system, juggling, late nights, manual steps)

What is the hidden cost? (time, mistakes, anxiety, rework, reputation, missed growth)

Best friction is specific, slightly painful, and relatable.

#3 The turning point (1 to 3 lines)

The moment where things begin to shift.

What changed? (tool/process/decision/habit/clarity)

Why did they finally try it? (trigger: deadline, failure, peer story, small pilot)

What was their initial hesitation?

Turning points feel real when you include doubt.

#4 The shift (3 to 5 lines)

Show the change in behaviour and emotion, not just metrics.

What is now easier/faster/calmer/safer?

What stopped happening? (the midnight panic, the rework loop, the version chaos)

One measurable outcome (optional)

One human outcome (mandatory): (relief, confidence, time back, pride)

#5 The quote (1 line)

Give your character one line that carries the meaning.

Their line in their voice:

Examples:

• I stopped reconciling and started deciding.
• I didn’t realise how tired I was until it stopped.
• The work didn’t change. The weight changed.

The quote is the spine. Everything else hangs on it.

#6 The wider lens (2 to 4 lines)

Only now do you zoom out.

What bigger truth does this reveal?

Who else is likely facing this?

What should leaders/teams do next?

This is where your business lesson lives.

A one-page copy-paste version

[Person] is a [role] who [context].

On [a specific day/moment], they were [doing something ordinary] when [friction showed up].

The telltale detail was [object/phrase].

For months, they had been [workaround], which cost them [hidden cost].

Then [turning point] happened, and they tried [change] even though they worried [doubt].

Within [timeframe], [measurable shift] changed, but more importantly, [human shift] changed.

They said, “[quote].”

If you’re in [industry/team] and this feels familiar, start by [one actionable next step].

Examples

Example 1: Finance / Month-end close

Vikram, a finance manager, used to dread the last two days of every month.

On the 30th, his laptop would have three spreadsheets open, each claiming to be “final.”

His telltale detail?

A folder named Final_Final2_revised.

He spent more time reconciling than analysing.

Then they tested a single-source-of-truth workflow for a single entity. He was skeptical about maintaining another tool.

But by the next close, the rework dropped, approvals moved in one direction, and he stopped messaging people at midnight.

He said, “I didn’t become faster. I became surer.”

If month-end feels like a recurring emergency, start with one process you can make single-threaded.

Example 2: Hiring/talent acquisition

Shreya, a recruiter, could tell in 20 seconds whether a role would become a nightmare.

Not because candidates were bad, but because feedback came late and contradictory.

Her detail was the line: “Let’s revisit after a few more profiles.”

She kept candidates warm with polite messages while internally chasing five stakeholders.

Then she introduced a simple rule: one hiring manager owns the decision, everyone else advises within 48 hours.

Shortlists improved, drop-offs reduced, but the real shift was her energy.

She said, “I stopped following up and started moving forward.”

If hiring feels slow, fix decision ownership before you fix sourcing.

Example 3: Product team/roadmap chaos

Neha, a product lead, had a calendar that looked like a crime scene, with back-to-back alignment calls.

Her detail was a sticky note: “Ask again: what are we actually shipping?”

Requirements changed through whispers: DMs, hallway chats, and last-minute calls.

Then she implemented a single weekly decision forum: one doc, one owner, one decision log.

The output didn’t have more features. There were fewer reversals.

She said, “We didn’t get aligned. We are accountable.”

If roadmaps feel unstable, fix decision logging before you fix prioritisation.

If you want to communicate impact, don’t start with “we.”

Start with one person who makes your audience say, “That’s me.”