How to Write a Social Persona Your Team Can Use.

A social persona is only useful if it can settle an argument about a caption. Most cannot.

The usual artefact runs to a dozen slides of adjectives, archetypes and reference brands, and none of it tells the person writing at four on a Friday whether the post in front of them is right or not.

A persona your team can actually use is a short working document with four jobs. What this brand would say. What it would never say. How it behaves when someone is angry. Who decides when two people disagree. Everything else is decoration.

What a usable social persona actually is

A social persona is a working document that tells a writer how this brand speaks and behaves in public, in enough detail that they can draft a post and check it themselves.

The test is a new freelancer. Hand them the persona and a brief on Monday morning. If they write three posts without asking anyone what the brand sounds like, and you would publish two of them, the document works.

That is a different job from a brand book. A brand book explains the brand to the people who buy from it. A persona instructs the people who write for it, which is why it belongs with the rest of the machinery for running social media as a system rather than a calendar and not in the deck it was born in.

Why three adjectives and a mood board fail

Open almost any brand persona and you find the same shape. A handful of personality traits, an archetype, a palette, a page of reference brands and a paragraph on voice and tone. Every field describes. None instruct.

The traits are the weakest part, because no brand has ever chosen the opposite ones. Nobody writes down that they want to sound timid, cold and forgettable. Confident, playful and human are not decisions, they are the defaults with a typeface applied.

A description you cannot disagree with cannot resolve a disagreement either. That is why the request to define the persona keeps coming back around. The artefact was produced, filed, and never opened again, so the problem it was meant to fix is still sitting there.

The only test that matters

Read the persona line by line and ask one question of each line. Which post would this have changed?

Not which post it describes. Which post it would have stopped, rewritten, or pushed through approvals faster. A line that cannot answer that is not a standard, it is a sentiment.

Most personas do not survive that test at full length, and that is the point. Two pages a team trusts beat twenty they skim.

Start with what the brand will never say

Positive instructions are hard to check. Prohibitions are easy, and they are where a brand’s actual judgement lives.

Write down what this brand does not do, specifically enough that a stranger could enforce it. A usable version reads closer to this:

• We do not use a trend sound unless someone on the team can explain the joke.
• We do not comment on national news events unless we are directly involved.
• We do not post a question we do not want the answer to.
• We do not open a caption with “we are excited to announce”.
• We do not make a customer the punchline, including a rude one.
• We do not use more than one emoji in a caption, and never one per line.

Six lines like that settle more arguments than a page of adjectives, because each one can be checked by someone who has never met the brand.

Show the good and the bad version of the same post

The most useful page in any persona document is a pair. One brief, two executions, and a sentence explaining why the second one is the brand.

Imagine a homeware brand launching a table lamp.

• Off persona: “Introducing the Ora lamp. The perfect addition to any space. Available now, link in bio.”
• On persona: “The shade is cut from a single sheet, so the seam sits round the back where you will never see it. Took us four goes. The Ora lamp is on the site now.”

The explanation line carries as much weight as the pair. On persona here means leading with a detail only someone who made the thing would know. That is a rule a writer can apply to the next product, and the one after that, which a mood board never is.

Two or three pairs is enough. Pick the formats you post most: a launch, a reply, and something with no news in it at all.

Set tone as a range, not a personality

Tone is not one setting. The same brand answers a refund request and announces a new hire in the same week, and those should not sound alike.

The format that survives contact with a real week is a default plus an exception.

• Formality: usually casual, formal whenever the subject is money, safety or somebody’s job.
• Humour: dry, never at anyone’s expense, off entirely when a customer is upset.
• Warmth: direct rather than gushing, and we never call the audience “guys” or “folks”.
• Energy: measured, so that genuine enthusiasm still reads as genuine on the rare occasion we use it.

Four dials is plenty. A team can hold four things in their head while writing. Twelve tone words is a document nobody consults.

Write down how the brand answers a complaint

This is the part almost every persona skips, and it is the part that gets tested in public every week.

Comments and replies are where a voice either exists or does not. A brand that sounds warm in a launch post and defensive underneath it does not have a voice problem, it has an undocumented one.

Answer these once, in writing:

• What do we apologise for, and what do we explain instead?
• What moves to DM, and what stays in the thread so other people can see the answer?
• What is the reply window during the day, and who covers evenings and weekends?
• What do we hide, what do we leave up and answer, and what do we never delete?
• What gets escalated, to whom, and inside what hour?

Whoever handles daily publishing and community management needs those answers before the first angry comment lands, not while it is climbing.

Name the person who decides

Two sensible people will read the same persona and disagree about the same caption. The document is not finished until it says who wins.

Name a person, not a committee and not a job title with three occupants. One arbiter, one deputy for when they are away, and a stated rule that the call gets made the same day.

This is the honest part of the exercise. A persona with no named arbiter is a quiet request that nobody ever disagree, which is not a system, it is a hope.

Put it where the writing happens

A persona in the brand deck is a document about the brand. A persona in the workflow is a control on what gets published.

So move it. The first screen of the brief template, pinned to the content board, and quoted in the reviewer’s checklist so that feedback cites a line instead of a feeling.

The persona and the approval process behind your content are the same tool at two moments, one before the draft exists and one after. Reviewers change once it is there. “Not quite us” becomes “this breaks the rule about opening with an announcement”, which a writer can act on in a minute.

Update it from posts that already shipped

The best source material for a persona is not a workshop. It is the last hundred posts and the edits they collected on the way out.

Every time a reviewer rewrites a line, a rule got applied that nobody has written down yet. Capture a few of those a month and the document grows into a real standard rather than an opinion recorded on one Tuesday.

Set a quarterly pass. Add the rules the edits revealed, cut the lines that never changed a post, and swap in a fresher good and bad pair from work that actually went out.

What good looks like

A usable persona is short, specific and slightly boring to read, in the way a good checklist is boring.

• It fits on two pages and a new writer gets through it in five minutes.
• Roughly half of it is prohibitions, written specifically enough to enforce.
• It carries at least one good and bad pair with the reason attached.
• It says how the brand behaves in the comments, not only in the feed.
• It names the arbiter and the deputy.
• It sits in the workflow, and it was last edited this quarter.

None of that requires a rebrand or an offsite. It requires somebody to write down the decisions the team is already making from memory, badly, on a Friday afternoon.

How NBK thinks about the persona document

NBK treats voice as an operations problem rather than a branding one. A brand that reads inconsistently usually has a consistent voice and an inconsistent process: several writers, no shared standard, and a reviewer working from taste.

So the persona sits with the rest of the operating system, next to the brief template, the approval lanes and the reporting rhythm. It gets written to be applied under time pressure by somebody who was not in the room when it was agreed.

That is the bar worth holding it to. If the document cannot survive four o’clock on a Friday, it is not finished.

Next step

Pull up the last month of posts and mark the ones you would not publish again. The reasons behind those marks are your persona, already decided, just not written down in one place.

If your social process is slowing good ideas down, or the same caption argument keeps repeating, NBK can help rebuild the workflow behind the content.