The SCARF model — overview
The 5 dimensions the brain treats as „social survival”.
- Memorize the 5 letters and what they stand for
- See how they apply to daily situations
David Rock, in 2008, synthesized dozens of studies into a practical model: SCARF. The 5 dimensions that, if threatened, trigger protection mode. And if satisfied, trigger exploration mode.
┌───┬─────────────────────────────────────────────┐
│ S │ STATUS — my place in the hierarchy │
│ C │ CERTAINTY — predictability of the future │
│ A │ AUTONOMY — control over decisions │
│ R │ RELATEDNESS — sense of belonging │
│ F │ FAIRNESS — perceived equity │
└───┴─────────────────────────────────────────────┘General rules
- The reaction is disproportionate to the stimulus. A small remark can generate a big wave. That's normal.
- Losses hurt more than gains please (loss aversion). „I'm taking 10% of your scope” hits harder than „I'm giving you +10%”.
- People differ on which dimension affects them most. Someone is sensitive to Status, someone else to Fairness. Notice which is yours and others'.
- Threat and reward are symmetric. The same dimension you can trigger as threat, you can activate as reward.
How we apply it in this course
The next 5 modules — one for each letter — give you, for each dimension: what activates it, what threatens it, BA-specific examples, and 3 „before/after” rephrasings.
Match: behaviors → SCARF dimension
For each IT behavior, pick which SCARF dimension is most likely affected. There aren't „single” answers — pick what feels strongest.
The PO rewrites your acceptance criteria in Jira, directly, without telling you. You see it when the story moves to „Ready”.
The „starting Monday we're reorganizing teams” announcement, Friday evening, no context.
In demo, the manager praises team A and skips your team, though you both shipped.
A junior dev corrects you in refinement, publicly, on a minor business detail („I don't think that's the actual rule”).
You're the only BA in a meeting with 8 engineers using internal jargon.
The stand-up turns into a status report to the PM, not a team sync.
What's the difference between SCARF and a list of „good communication practices”?