Promise: one employee, one real question, one quote that makes the company look like somewhere a person could work.
Evidence. Demand-ranked #2: 138 of 958 companies built this format, across 629 campaigns. Interviews and employee portraits are the single most broadly re-created format in the dataset. Read that as: almost every mature marketing team eventually discovers that a face outperforms a logo, and then builds a repeatable process for it.
Use it when
- You need to look hireable (before, during or after a hiring push).
- A person on your team has genuine expertise your audience wants and your brand account cannot credibly claim.
- Your feed has drifted into product, product, product and engagement is flat.
- You want content that the subject and their whole network will reshare, which is the cheapest reach you can buy.
Do not use it when
- The person does not want to be posted. A reluctant portrait reads as reluctant, always. Never negotiate this one.
- You want leads this week. This is not a lead format. Reaching for a portrait when the pipeline is empty is the most common misuse.
- The only interesting thing about the person is their job title.
- You cannot get one specific, concrete, slightly-risky sentence out of them. Without that sentence there is no post, only a bio.
Intent and value
Primary intent: Sharing ("excite people to share"). The reshare by the subject and their network is the mechanism, not a bonus. Value axes: identification (primary),knowledge (secondary, if the person teaches something). If you switch the intent to Hot lead (adding "we are hiring, apply here"), reach drops and you have built recipe #3 instead. Pick one.
Campaign shape
4-day burst, 2-3 pieces: the portrait itself (day 1), a pull-quote graphic or short clip (day 3), and optionally the subject's own first-person version on their personal account (day 4). Do not run these on the same day; they cannibalize each other.
The brief (fill before writing)
- Who: name, role, how long here.
- The one question: the single question you will actually ask. Not a list. One.
- The sentence: the one quote you expect or hope to get, in their words, that a stranger would repeat.
- The concrete detail: one specific object, number, place or moment (the whiteboard, the 4am callout, the 300-page spec).
- The mild risk: what this person is willing to say that a corporate account would not.
- Who it is for: the reader who should think "these are my people".
- The photo: what it shows. Working, not posing. Say where and when it is taken.
- What we will not say: the boundary the subject sets before the interview. Write it down and honor it.
Structure
- Headline patterns. Best fit: "Name: quote"("Marta: 'I stopped answering support tickets at 9pm and our churn fell.'"). Alternate: question ("What does a support lead do at 4am?"). Avoid the plain factual pattern here; "Meet our new Head of Design" is the version nobody reads.
- Intro pattern. Scene-setting. Open on the concrete detail from brief field 4, one sentence, no context. Context is the second paragraph, never the first.
- Body beats.
- The concrete moment (1-2 sentences, present tense).
- Who this is and why they were the person in that moment (1 sentence, this is your only bio sentence).
- The one question, asked in the text.
- Their answer, in their words, as a real quote. Longest block on the page. Do not clean it up into corporate English; keep one imperfect phrase.
- The thing the answer implies about how the company works (1-2 sentences, and this is the only place the brand speaks).
- Ending pattern. Tease a sequel ("Marta is writing up the tags she uses; we will post it next week"), not act-now. An act-now CTA on a portrait converts the post from Sharing to Hot lead and the subject's network stops resharing it.
Voice
Tonality pair: personal + storytelling. Address form: informal, direct-you. Complexity: layperson. Alternative pair:personal + ironic, which works when the subject is genuinely funny and fails badly when they are not - if you are unsure, they are not.
Channel variants
- LinkedIn. The home network for this recipe; the dataset's highest engagement rate (median 4%) lives here and portraits are what it rewards. 120-200 words, the quote as its own line with white space around it, one photo. Tag the subject so their network is reachable. No link in the post body.
- Instagram. Photo carries it. Slide 1 is the face plus the quote in large type; slides 2-4 are the story. Caption repeats the quote in the first line because that is all that shows before "more".
- Facebook. Longer is fine here and older audiences read portraits. Same text as LinkedIn plus 2-3 more sentences of context. Strong fit for local businesses whose customers know the person by sight.
- X. Skip the full portrait. Post the single quote plus the photo, and nothing else. The dataset's median of 3 favorites per post tells you not to spend production budget here.
- TikTok. Only if you can get 20-40 seconds of the person actually answering the question on camera. The unpolished answer is the asset. A scripted-to-camera version of the same words performs worse than not posting.
Worked examples
Ledgerloop (B2B SaaS) - demonstrates the pull-quote as headline plus a mild, specific risk.
Priya: "We stopped calling it 'accounts receivable'. Nobody was late on purpose."
There is a whiteboard behind Priya's desk with 41 agency names on it and a number next to each one. It is a list of people who owe our customers money.
Priya runs support at Ledgerloop and spent last quarter reading every overdue-invoice thread our customers forwarded us.
I asked her what surprised her.
"Almost nobody was late on purpose. They were late because the invoice went to the wrong person and nobody followed up for nineteen days. We were building tools to chase deadbeats and the actual problem was that the email went to a designer's inbox and she went on holiday. So we stopped calling it accounts receivable. It is a routing problem."
That is why the next release does not have a bigger dunning engine in it. It has a "who actually opened this" column.
Priya is writing up the four questions she now asks every customer about their invoicing setup. Next week.
Halstead Roofing (local service) - demonstrates scene-setting plus identification for a non-office business.
What a roofer does at 4am
It is 4:10am and Danny is standing in a stranger's kitchen holding a bucket, waiting for the rain to slow down enough to get on a roof safely.
Danny has been with us eleven years and takes the emergency calls.
I asked him what people get wrong about emergency calls.
"Everyone thinks the job is fixing the roof. At four in the morning you can't fix a roof, it's dark and it's wet and I'm not going up there. The job is stopping the water getting into the ceiling and telling the family honestly that we'll be back at eight. Half of them have been up since midnight thinking the house is ruined. It isn't. Nine times out of ten it's a two-hour job in daylight."
That is why we answer the phone at night even though we cannot do the repair until morning. The call is the service.
Danny is putting together the three things to do before we arrive. We will post it before the autumn storms.
Tidepool (consumer app) - demonstrates the format when the subject is technical and the audience is not.
Sam: "Your watch doesn't know you're asleep. It's guessing, and so are we."
Sam has a spreadsheet with 1,900 nights in it. All his own.
He builds the sleep-staging model at Tidepool and has worn three trackers at once for over five years.
I asked him the question we get in every single support email: why does the app say I slept badly when I feel fine?
"Because your watch doesn't know you're asleep. It's guessing from movement and heart rate, and so are we. On a good night we're close. On a night you had two glasses of wine and fell asleep on the sofa, we are confidently wrong. I'd rather we told you that. So now when the model isn't sure, the app says it isn't sure instead of inventing a number."
That is the change in 4.2. Fewer confident numbers, more honest ones.
Sam is publishing what the app actually measures versus what it infers. Next month.
Quality checklist (all must be yes)
- Is there exactly one named person, not a team?
- Does the first sentence contain a concrete object, number, place or time?
- Is there a real quote of 25 words or more, in their voice, with at least one phrase you would not have written yourself?
- Is the bio exactly one sentence?
- Does the brand speak in only one place, after the quote?
- Is there no "we are hiring" and no application link in the post body?
- Did the subject read it and approve it before posting?
- Does the photo show them doing something rather than facing the camera?
- Would this post still make sense if you deleted the company name?
- Is there a stated next thing, so the sequel is promised rather than hoped for?
What good looks like
This is a Sharing post, so judge it on reshares first and reactions second. On LinkedIn, a portrait should beat your account's own median engagement rate; against the dataset median of 4%, a working portrait is your best post of the month, not an average one. OnInstagram, faces normally outperform: if the portrait lands at the corporate median of 51 likes it did not work for you. OnFacebook, expect reach at or above your page median of around 1,400 and reactions well above the median of 10, because the subject's own network arrives. On X, expect the usual 3 favorites and do not draw conclusions from it. If three consecutive portraits do not beat your own account's median, the problem is the quotes, not the format: you are getting job descriptions instead of sentences.
Failure modes
- The press release portrait. "We are delighted to welcome..." Fix: delete every sentence before the concrete detail and start there.
- The sanitized quote. Someone in comms smoothed the answer into corporate English and it now says nothing. Fix: restore one imperfect phrase; that phrase is the proof a human said it.
- The bolted-on CTA. A hiring link at the bottom turns Sharing into Hot lead and kills the reshare. Fix: move the hiring ask to a separate post three days later (recipe #3).
- The reluctant subject. Reads as stiff no matter how well written. Fix: pick someone else. There is always someone else.
Repurpose
- The quote alone as a pull-quote graphic, 2-3 days later, on the same networks.
- The subject posts the same story in first person on their own account, linking nothing. Their version usually outperforms yours.
- Three portraits with the same question become a "we asked five people the same thing" roundup (recipe #17, The Ranked List, or #25, The Recap).
- The promised sequel becomes recipe #5, The Practical Tip, written by the subject.