White Papers
P&G Never Advertises P&G. A Job Posting That Only Sells the Company Loses You the Person You Actually Wanted.
Why employer branding and role-level specificity are doing two different jobs — and a posting that only tells one story is only doing half its work.
172
studies in the Personnel Psychology meta-analysis separating person–job from person–org fit
21
studies confirming that honest, specific role previews reduce early turnover
2
jobs every posting must do — the company story and the role story — and most only tell one
01
The P&G principle
P&G doesn't advertise P&G when it wants to sell Ivory Soap — it advertises the soap. Not because the company's reputation doesn't matter, but because when the company expects the ad to actually pay off, it targets the specific thing it wants the customer to buy, and appeals directly to what that buyer gets from it. The company's name lends credibility. The product's value closes the sale.
What most postings do
Sell the company
Mission, values, culture — the brand. A candidate learns a lot about the organization and almost nothing about what the job will actually be like.
What P&G does
Sell the product
Target the specific thing you want the buyer to act on, and appeal directly to what they get from it. The brand lends credibility. The role closes the hire.
Recruiting mostly ignores this. Most job postings do the opposite of what P&G does: they sell the company — the mission, the values, the culture — and barely describe the role itself.
02
Why the gap matters: fit is not one thing
There’s a real reason that gap matters: fit isn’t one thing, it’s several. A 2005 meta-analysis of 172 studies in Personnel Psychology found that fit with the organization and fit with the specific job are separate, independently measurable constructs — liking a company and being right for a particular role are not the same trait, and neither one substitutes for the other.
Kristof-Brown, Zimmerman & Johnson, 2005 — Personnel Psychology
doi.org/10.1111/j.1744-6570.2005.00672.xThis isn't just an academic finding. Marcus Buckingham and Ashley Goodall — a former Gallup SVP and a Cisco executive, writing in the Harvard Business Review Press book Nine Lies About Work — reached the same conclusion from their own large-scale engagement research: people don't care which company they work for nearly as much as which team they're on. The emotional connection that actually predicts whether someone stays lives at the team level, not the brand level.
Buckingham & Goodall — Nine Lies About Work, Harvard Business Review Press
store.hbr.orgA posting built entirely around brand only speaks to one of those. It says nothing about whether this specific role, this specific management style, this specific day-to-day, is right for this specific person.
03
Two halves of the cost
The result is predictable. Candidates self-select based on the company they liked, not the job they'd be doing. They join excited about what they imagined the role would be — and find out, usually within the first few months, that the imagined version and the real one don't match. The people most likely to leave over that mismatch are often the strongest ones: capable enough to have other options, honest enough to act on the gap instead of tolerating it.
The visible half
The wrong people join and leave
Candidates self-select on company attraction, not job fit. The strongest ones — with other options — leave first when the role doesn't match what the posting implied.
The invisible half
The right people never apply
The candidates who would have been genuinely right never applied at all — because the posting never told them the nuance that would have made them recognize themselves in it. They didn't reject the job. They never knew it existed in the form that would have mattered to them.
That's a real cost, not an abstract one.
50–200%
of annual salary to replace one employee — direct recruiting costs plus months to full productivity
SHRM$1T
in annual U.S. losses from voluntary turnover — brand-driven mismatch a major, untracked contributor
GallupMultiply that across every mismatched hire a brand-heavy posting produces in a year, and the cost of skipping role-level specificity is large, real, and almost never traced back to the posting that caused it.
04
Why it persists
It persists because the alternative is genuinely harder. Finding what makes one specific role distinct takes real work — structured conversations with the actual hiring manager, not a template. A brand narrative gets written once and reused across hundreds of postings with almost no changes. It looks efficient. Its failure shows up as turnover six months later, on someone else’s dashboard, never connected back to the posting that started it.
There’s decades of research on exactly this trade-off: a meta-analysis of 21 studies found that giving candidates an honest, specific preview of a role — not just the appealing version — improves self-selection and reduces early turnover, because the people who wouldn’t actually fit opt out before they’re ever hired.
Premack & Wanous, 1985
doi.org/10.1037/0021-9010.70.4.706Brand messaging is close to the opposite of a realistic preview. It's accurate about the company and silent about the role.
05
Two jobs. One posting doing half.
Employer branding isn't the problem. Using it as a substitute for role-level specificity is. The company story and the role story are doing two different jobs, and a posting that only tells one of them is only doing half its work.
Job one
The company story
Mission, values, culture — lends credibility, builds trust in the brand. Most postings do this well.
Job two — the missing one
The role story
This specific manager, this specific team, this specific day-to-day — the nuance that makes the right person recognize themselves in it.
06
The actual answer
Every open role has a specific person who'd be right for it. A posting that only sells the company was never going to reach them — it wasn't written to. Any recruiter can do this by hand: ask what actually makes this role, this team, this management style, different, and write it down before writing anything else. That's the whole method, and it works whether or not you ever use JobWriter. But if this is the exact problem you're reading this to solve, say so plainly: this is exactly what JobWriter was built to do, every time, for HR, not a related idea. The actual answer.
See how JobWriter approaches this differently.
Role-specific behavioral targeting — built into every posting, by default.
Request a Demo