Skip to content

bereach-ai/linkedin-prospecting-skills / skills/linkedin-personas

linkedin-personas

Verified

Builds 2 to 4 persona cards with the user and puts each lead in one. Use before writing to a new list, or when messages sound generic or repeat the job title.

FileKindSize
SKILL.mdskill md7.1 KB
references/artifacts.mdmarkdown9.1 KB
references/frameworks.mdmarkdown20.3 KB
references/persona-card.mdmarkdown4.9 KB
references/sources.mdmarkdown3.5 KB

references/frameworks.md

View on GitHub
# Reference frameworks for persona cards

How to use this library:
1. No framework here is proven better than another at getting replies. What is measured is the parts of a message: about them, their problem, short, one easy ask. A framework only decides which parts the card holds and in what order.
2. The default is the persona template, written in the user's voice. A framework fills a card field; it never overrides the facts the user gave (their trade, offer, price, proof) or the words replies used. That no framework is proven never excuses a message that fails the linkedin-messages checks.
3. Name a framework on the page (the "Étape N · Framework (Author)" band) only when the cards visibly apply it, so the user sees why a field is there and can push back on it; otherwise leave the name out.

## Summary

| Framework | Author | Feeds | Evidence |
|---|---|---|---|
| Goal-directed personas | Alan Cooper (1995 project, 1999 book) | Name, Goals; drops demographics | Practice |
| Provisional personas | Kim Goodwin (2001, 2002, 2009); Cooper, Reimann, Cronin (2007) | The `(guess)` mark, Found by | Practice |
| Few attributes match more people | Chapman et al. (2008) | Card length, empty fields | Measured |
| Anti-persona | Pruitt and Grudin (2003) | Not this persona | Practice |
| ICP then persona (macro, micro segmentation) | Wind and Cardozo (1974) | Name (company first), Found by, sorting leads | Practice |
| Buyer persona | Tony Zambito (2002) | The card as a buying view | Practice |
| 5 Rings of Buying Insight | Adele Revella (2015, 2016) | Why now, Goals, Objection, Who else decides, Proof | Practice |
| Pain is not priority | Adele Revella (2016) | Why now, Pain | Practice |
| Jobs to be Done | Clayton Christensen et al. (2016) | Who (the situation), Pain | Practice |
| Forces of progress (push, pull, anxiety, habit) | Bob Moesta and Chris Spiek | Why now, Pain, Objection, Today they use | Practice |
| Job stories | Alan Klement (2016), Intercom | Who, Why now | Practice |
| Business and personal motives | Jenni Romaniuk (2022) | Goals, What they do with it | Practice |
| Trigger events, window of dissatisfaction | Craig Elias with Tibor Shanto (SHiFT!, 2010) | Why now, Signal to look for | Practice |
| Critical event (SPICED) | Winning by Design | Why now window | Practice |
| Stages of awareness | Eugene Schwartz (1966) | Awareness | Practice |
| Buying center roles | Webster and Wind (1972) | Who else decides | Practice |
| Mobilizers and group relevance | CEB, The Challenger Customer (2015); Gartner (2025) | Who else decides, Offer | Survey |
| Value Proposition Canvas | Osterwalder, Pigneur, Bernarda, Smith (2014) | Pain to Proof link, Offer | Practice |
| Relevance over personal facts | Becc Holland; 30MPC with Gong | Never use personal traits | Vendor claim |
| Formal or informal address | Leung et al. (2023) | Address form | Measured |

## Which card field comes from which framework

| Card field | Framework(s) |
|---|---|
| Name (the company, then the role) | Wind and Cardozo (company first), Cooper goal-directed personas, Klement job stories |
| Short name | none, the user's answer |
| Found by | Wind and Cardozo (persona inside the ICP), Goodwin (a title is not a persona) |
| Why now (the push) | the user's hiring moment; Moesta and Spiek push; Revella ring 1 (check it is a priority), SPICED critical event (its window) |
| Signal to look for | Elias trigger events (at the user's hiring step or just before) |
| Pain | Moesta and Spiek push, Revella "pain is not priority" |
| Objection (the resistance) | Revella ring 3 (perceived barriers), Moesta and Spiek anxiety and habit |
| Proof that lands | Revella ring 5 (decision criteria), Value Proposition Canvas (pain relievers) |
| Offer they keep, What they do with it | Value Proposition Canvas (gain creators), Romaniuk business and personal motives, CEB group relevance |
| Goals | Cooper goals, Revella ring 2 (success factors), Romaniuk business and personal motives |
| What it costs | none, the user's answer |
| Today they use | Moesta and Spiek habit (the solution hired today) |
| Busy months | none, the user's answer, else the sector's public calendar |
| Their words | Revella (quote the buyer's own words) |
| Never say | Revella (the buyer's own words, by contrast) |
| Awareness | Schwartz stages of awareness |
| Who else decides | Revella ring 4 (buyer's journey), Webster and Wind, CEB Mobilizers |
| Not this persona | Pruitt and Grudin anti-persona |
| The `(guess)` mark, seen in N replies | Goodwin provisional personas, Strategyzer (fit is a hypothesis until customers confirm it) |
| Address form | Leung et al. 2023 |
| Short card, no personal traits | Chapman et al. 2008, Cooper, Holland |

## The persona itself

### Goal-directed personas (Alan Cooper, Sagent project 1995; The Inmates Are Running the Asylum, 1999)
- What it says: a persona is split from others by goals, tasks and skills, built to make a choice, not to describe a market. The 2004 second edition of The Inmates Are Running the Asylum has a section titled "It's a User Persona, Not a Buyer Persona".
- On LinkedIn: the card Name is the company in its situation, then the role, and Goals is one line; age, gender, hobbies, school and photo never appear.
- Example: "Water utility with an ageing meter fleet: its network manager", never "Marc, 47, cyclist".
- Use when / not when: always for the card's Name; not as a reason to invent a life story.
- Evidence: Practice, his own account, nothing measured.

### Provisional personas (Kim Goodwin, Cooper Journal, 2001 and 2002; Designing for the Digital Age, 2009; Cooper, Reimann, Cronin, About Face 3, 2007)
- What it says: personas are behaviour patterns, not job descriptions; with little research write a provisional persona (a few goals, no narrative) and say it is a guess.
- On LinkedIn: a line not in the user's words ends in `(guess)` and becomes "seen in N replies" only from 2 replies; one title can hold two personas, so Found by sorts, it never decides alone.
- Example: Pain "meters drift and nobody knows which ones (guess)" until two replies say it.
- Use when / not when: every card drafted before replies; not once replies have confirmed a line.
- Evidence: Practice, documented method, not measured.

### Few attributes match more people (Chapman, Love, Milham, ElRif, Alford, HFES 2008)
- What it says: at 9 or more attributes, the best descriptions matched no one in 5 of 6 real datasets.
- On LinkedIn: keep the card short; leave a field empty rather than add a detail that narrows who it fits.
- Example: drop "works in a 50k inhabitant town" unless it changes the message.
- Use when / not when: when tempted to add a field; it does not say whether personas help.
- Evidence: Measured, six real survey datasets.

### Anti-persona (Pruitt and Grudin, Microsoft, DUX 2003)
- What it says: name who you are not designing for, beside the personas.
- On LinkedIn: feeds "Not this persona" and the Who is who page (students, side projects, the user's own team are held, no message).
- Example: "Not this persona: meter installers (fit meters, do not choose the software)".
- Use when / not when: when lookalike titles reach the list; not as a way to remove someone silently.
- Evidence: Practice, industrial method, impact never measured.

### ICP then persona: macro and micro segmentation (Wind and Cardozo, Industrial Marketing Management, 1974)
- What it says: segment the organisations first (macro), then the people inside them (micro).
- On LinkedIn: the ICP says which companies (kind, size, place, in the search plan); the persona card says which person inside them and what to say. Found by lists titles inside the ICP's companies only.
- Example: ICP "water utilities, 20 to 500 staff"; persona "network manager" inside them.
- Use when / not when: before sorting leads; not to put company facts (size, sector) on the card twice.
- Evidence: Practice, a conceptual model widely followed.

### Buyer persona (Tony Zambito, 2002)
- What it says: coined "buyer persona": research-based archetypes of who buyers are, what they try to accomplish, what drives them, how they think and how they buy.
- On LinkedIn: the card describes how this role buys, not only who it is; what Claude writes from the user's knowledge is a role-based card, labelled a hypothesis. A role filter (titles, seniority) says who the buyer is; a buyer persona says how they decide (ITSMA, 2021: a role-based profile describes who the buyer is, a buyer persona the buying process; paraphrased). The card holds both halves.
- Example: "Buys after a regulator audit flags missing calibration records".
- Use when / not when: to frame the card around buying; not as proof the card is researched.
- Evidence: Practice, a definition, not a test.

## What makes them buy

### 5 Rings of Buying Insight (Adele Revella, Buyer Personas, 2015; The Buyer Persona Manifesto, 2016)
- What it says: five insights reveal the buying decision: priority initiatives, success factors, perceived barriers, buyer's journey, decision criteria. Built from 6 to 10 interviews of recent buyers, in their own words.
- On LinkedIn: ring 1 feeds Why now, ring 2 Goals, ring 3 Objection, ring 4 Who else decides, ring 5 Proof that lands. The user's won and lost deals (Step 2 questions) stand in for interviews; Their words are quoted, never paraphrased.
- Example: ring 3 "We tried a tool and the field teams never used it".
- Use when / not when: drafting every card.
- Evidence: Practice.

### Pain is not priority (Adele Revella, 2016)
- What it says: do not confuse what makes them invest time, budget or political capital now with pain points reverse engineered from your product.
- On LinkedIn: Why now stays the hiring moment the user gave; check that it is a priority they spend on now, not only a pain the product solves. Pain is the moment of work it causes.
- Example: Pain "drifting meters"; priority "the leak reduction target due this year".
- Use when / not when: checking every Why now and Pain pair; not to drop a real pain the user heard.
- Evidence: Practice, author's documented warning.

### Jobs to be Done (Clayton Christensen, Hall, Dillon, Duncan, Competing Against Luck and HBR, 2016)
- What it says: people "hire" a product to make progress in a circumstance; the circumstance, not the person, explains the choice.
- On LinkedIn: the card's Who is a role in a circumstance; Pain is the progress blocked.
- Example: "When a sector loses water we cannot locate, I need to know which meters to trust".
- Use when / not when: naming the persona and its Pain; not as a full research programme (no interviews here).
- Evidence: Practice, case-based, not measured.

### Forces of progress: push, pull, anxiety, habit (Bob Moesta and Chris Spiek; Demand-Side Sales 101, Moesta and Engle, 2020)
- What it says: a switch happens when the push of the current situation plus the pull of the new beat anxiety about the new plus the habit of the present.
- On LinkedIn: push feeds Why now and Pain; the resistance is anxiety (Objection "we tried", "not now") and habit (Today they use). A first message can name the push and lower one anxiety; it cannot create pull in one paragraph.
- Example: habit "calibration logged in spreadsheets"; anxiety "another tool the field teams will not open".
- Use when / not when: writing Pain and Objection; not to argue the reader out of habit in message one.
- Evidence: Practice, interview method, not measured.

### Job stories (Alan Klement, When Coffee and Kale Compete, 2016; Intercom)
- What it says: "When ..., I want to ..., so I can ...": the situation comes first and the demographic persona is dropped.
- On LinkedIn: a test for Who and Why now: if the card cannot be written as one job story, it is still a title.
- Example: "When the regulator asks for calibration records, I want them in one place, so I can answer in a day".
- Use when / not when: checking a card is a situation; not as message copy.
- Evidence: Practice, summaries only.

### Business and personal motives (Romaniuk's 'Why' entry point; Jenni Romaniuk, Category Entry Points in a B2B World, LinkedIn B2B Institute and Ehrenberg-Bass, 2022)
- What it says: a buying situation's motive can be the business's or the decision maker's own (their job performance).
- On LinkedIn: Goals holds both, and What they do with it says what the person gains personally.
- Example: business motive "fewer losses"; personal motive "a clean audit on their watch" (their job performance).
- Use when / not when: writing Goals; not to guess feelings in a message (hedging is flagged).
- Evidence: Practice, a framing inside a survey-method report.

## Why now

### Trigger events and the window of dissatisfaction (Craig Elias with Tibor Shanto, SHiFT!, 2010)
- What it says: events (a new executive, new funding, a change) move a buyer out of the status quo into a window where the current way no longer works; be first in.
- On LinkedIn: trigger events help place the Signal to look for at the user's hiring step, or the step just before it; they never replace the moment the user gave. The event must cause the Pain, never be recited back.
- Example: user's moment "a leak reduction plan is launched"; Signal "utility posts a tender for leak detection".
- Use when / not when: when choosing the Signal; not to invent a Why now earlier than the user's hiring step (`trop tôt`). His "74%" and "10 times more likely" figures are never quoted.
- Evidence: Practice; his numbers Untraced.

### Critical event, SPICED (Winning by Design)
- What it says: Situation, Pain, Impact, Critical Event, Decision; the critical event is a dated reason it must happen now.
- On LinkedIn: gives Why now its one window (6 months at most); the date belongs to the user's stated moment, never one Claude derives.
- Example: "Annual loss report due in March".
- Use when / not when: dating the moment the user gave; not as a discovery script in a first message.
- Evidence: Practice, company method.

### Stages of awareness (Eugene Schwartz, Breakthrough Advertising, 1966)
- What it says: start from what the reader already knows; one message cannot serve every state of awareness. The five popular stages: unaware, problem aware, solution aware, product aware, most aware.
- On LinkedIn: the card merges product aware and most aware into "knows you", because a cold LinkedIn reader is never "most aware", so it keeps 4 stages (does not see the problem, knows the problem, compares solutions, knows you), shown as "What they know already". A cold reader is "knows the problem" unless posts or replies show more; it decides whether the message opens on the situation, the problem or the result.
- Example: "Knows the problem": open on drifting meters, not on the software.
- Use when / not when: every card. Most aware and completely unaware are his terms; the three middle labels are later shorthand for his descriptions.
- Evidence: Practice; the three middle labels are not his.

## Who else decides

### Buying center roles (Webster and Wind, Journal of Marketing, 1972)
- What it says: users, buyers, influencers, deciders and gatekeepers share a purchase.
- On LinkedIn: Who else decides names the other roles at the table and what this persona can forward to them.
- Example: "Technical director decides: forward the audit checklist".
- Use when / not when: filling Who else decides; not as five personas to write to.
- Evidence: Practice, conceptual, never tested as a partition.

### Mobilizers and group relevance (Adamson, Dixon, Spenner, Toman, The Challenger Customer, CEB, 2015; Gartner, 2025)
- What it says: Mobilizers move buying groups; value positioned to one stakeholder did worse than what helps the group learn together (CEB); Gartner (632 buyers) found group-level relevance tied to more high-quality deals.
- On LinkedIn: the Offer is something the reader can take to their team, not flattery of the person; the seven stakeholder types are behaviour in a deal, so they never sort leads.
- Example: an Offer the user already gives (a one-page grid) framed as something the network manager can share with the director.
- Use when / not when: shaping Offer and Who else decides; not at a cold touch as proof of effect.
- Evidence: Survey, self-reported, inside active purchases.

## Proof and offer

### Value Proposition Canvas (Osterwalder, Pigneur, Bernarda, Smith, Value Proposition Design, 2014)
- What it says: a customer profile of jobs, pains and gains matched to pain relievers and gain creators; Strategyzer treats fit as a hypothesis until customers confirm it.
- On LinkedIn: each Pain points to one Proof the user can show; the Offer is a small gain they keep, one the user already offers; the card stays a claim until replies.
- Example: Pain "unknown drift" to Proof "a utility found its 12 worst meters in a week (your words)".
- Use when / not when: linking Pain to Proof; not to write a Proof the user did not give.
- Evidence: Practice, not measured.

## How to write to them

### Relevance over personal facts (Becc Holland, Flip the Script; 30MPC with Gong, cold email report, 85M+ emails)
- What it says: relevance is about the role and its context; personal facts (alma mater, hobbies) do not help; pitch words lower replies.
- On LinkedIn: the card holds no personal traits and the title finds the card, never the opener ("I saw you are...").
- Example: open on the audit, not on the reader's university.
- Use when / not when: every card and message; not a reason to skip a real, dated fact about their work.
- Evidence: Vendor claim, no method published.

### Formal or informal address (Leung, Lenoir, Puntoni, van Osselaer, Journal of Consumer Psychology, 2023)
- What it says: informal address fits warm brands, formal fits competent ones (five consumer studies). No study tests it on B2B replies.
- On LinkedIn: backs the card's default, vous (or Sie) where the language has a formal form when the Voice card has none; mirror their reply.
- Example: network managers at public utilities: vous.
- Use when / not when: every card in a language with a formal form; not as a measured reply lever.
- Evidence: Measured, on consumers, not B2B.

## Further reading

- Alan Cooper, The Inmates Are Running the Asylum, Sams, 1999.
- Alan Cooper, The Inmates Are Running the Asylum, 2nd edition, Sams, 2004.
- Alan Cooper, "The origin of personas", Cooper Journal, 2003 (republished 2008): https://web.archive.org/web/2013id_/http://www.cooper.com/journal/2008/05/the_origin_of_personas.html
- Alan Cooper, Robert Reimann, David Cronin, About Face 3: The Essentials of Interaction Design, Wiley, 2007.
- Kim Goodwin, Designing for the Digital Age: How to Create Human-Centered Products and Services, Wiley, 2009.
- John Pruitt and Jonathan Grudin, "Personas: Practice and Theory", DUX 2003: https://www.microsoft.com/en-us/research/wp-content/uploads/2017/03/pruitt-grudinold.pdf
- C. N. Chapman et al., "Quantitative Evaluation of Personas as Information", HFES 2008: https://quantuxbook.com/papers/REPRINT-HFES08-chapman-love-milham-elrif-alford.pdf
- Adele Revella, Buyer Personas, Wiley, 2015.
- Adele Revella, The Buyer Persona Manifesto, 2016: https://www.buyerpersona.com/wp-content/uploads/2018/05/Buyer-Persona-Manifesto-2016.pdf
- Clayton Christensen, Taddy Hall, Karen Dillon, David Duncan, Competing Against Luck, HarperBusiness, 2016.
- Bob Moesta and Greg Engle, Demand-Side Sales 101, Lioncrest, 2020.
- The four forces, Jobs-to-be-Done.org: https://jobstobedone.org/the-four-forces/
- Alan Klement, When Coffee and Kale Compete, 2016.
- Jenni Romaniuk, Category Entry Points in a B2B World, LinkedIn B2B Institute and Ehrenberg-Bass, 2022.
- Craig Elias with Tibor Shanto, SHiFT! Harness the Trigger Events That Turn Prospects Into Customers, 2010.
- Eugene Schwartz, Breakthrough Advertising, 1966.
- Y. Wind and R. N. Cardozo, "Industrial Market Segmentation", Industrial Marketing Management, 1974.
- Frederick Webster and Yoram Wind, "A General Model for Understanding Organizational Buying Behavior", Journal of Marketing, 1972.
- B. Adamson, M. Dixon, P. Spenner, N. Toman, The Challenger Customer, Portfolio, 2015: https://challengerinc.com/the-challenger-customer-profiles/
- Alexander Osterwalder et al., Value Proposition Design, Wiley, 2014: https://www.strategyzer.com/library/the-value-proposition-canvas
- 30 Minutes to President's Club with Gong, The Ultimate Cold Email Data Report: https://tactics.30mpc.com/hubfs/The%20Ultimate%20Cold%20Email%20Data%20Report-1.pdf
- E. Leung et al., "Consumer preference for formal address and informal address from warm brands and competent brands", Journal of Consumer Psychology, 2023, DOI 10.1002/jcpy.1322.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall