SCARF

The problem it solves

Managers usually judge a decision on whether it's right, and the people it lands on respond to things the decision never mentioned. A restructure argued on cost and focus arrives as a question about whose standing survived it, and a daily check-in set up to reduce delivery risk arrives as a verdict on who can be left to finish work alone.

What follows tends to get read as a temperament problem in whoever had the reaction, which is the convenient reading, because it puts the trouble in one person rather than in the design of the announcement. The person who wrote the announcement is also the worst-placed person to see what it cost, having had three weeks with the decision and the reasoning that produced it, while everybody else gets the conclusion in a paragraph on a Tuesday.

The cost that stays hidden longest is capacity. People who feel badly treated rarely stop working, so the bill arrives as slower thinking, shorter tempers, work that is technically finished and light on judgement, and a fortnight in which the hard problem doesn't get solved by anyone. None of that reaches a decision log, which is part of why a change looks cheaper in hindsight than it was at the time.

The idea

SCARF names five social dimensions that the brain appears to treat as consequential, and Rock's argument is that they behave more like survival needs than like preferences. Each one has a characteristic way of being set off and a characteristic way of being paid, and the management examples are ordinary enough that most of them happen by accident.

The second claim is the one that does the work, which is that the two sides of each domain aren't symmetric. A threat arrives faster, reaches further into the rest of the day and lasts longer than a reward of the same apparent size, and the model's reading is that it draws on the same attention the work needs. So a manager who spends a little standing to get a decision through has bought the decision and sold some of next week's thinking, at a rate nobody quoted.

Enlarge: The two responses aren't the same size or the same length, which is the part a list of five domains leaves out.

A horizontal line runs across the drawing with a single tick on it, labelled the moment it lands. Above the line a small curve rises and falls back quickly, labelled the reward response. Below the line a deeper curve drops further and is still below the line at the right-hand edge, labelled the threat response, bigger and still running tomorrow, and drawing on the attention the work needed.

The two responses aren't the same size or the same length, which is the part a list of five domains leaves out.Close

The two responses aren't the same size or the same length, which is the part a list of five domains leaves out.

Take a project that's running late and a manager who starts reviewing the work daily. The intervention gets weighed on delivery risk, which is a real risk, and it also spends autonomy and usually a little standing, so what arrives is a slightly better plan and a senior engineer who stops raising problems early. The grounding stops where the two become commensurable, because nothing in the model says how much delivery certainty is worth against how much autonomy, and the decision to step in is often still the right one.

Certainty is the domain most often mishandled during a change, because the instinct is to supply reassurance when what people can use is predictability. A promise that nobody's role is at risk is usually made by somebody who can't guarantee it, and it spends credibility on the day it turns out to have been conditional. A date for when the next decision lands, who is making it, and how people will hear about it cost the speaker nothing they don't already have.

Enlarge: Both ends supply less predictability than the middle does, and reassurance about the outcome is the common mistake.

Both ends supply less predictability than the middle does, and reassurance about the outcome is the common mistake.Close

Both ends supply less predictability than the middle does, and reassurance about the outcome is the common mistake.

Fairness behaves differently from the rest, in that it answers to how a decision was reached at least as much as to what was decided. An unwelcome outcome with a visible process and a standard that reaches everybody tends to survive. A good outcome that arrives without either gets read as favour, and it teaches people to work out who to be close to rather than what to be good at, which is a lesson that outlives whoever taught it.

How to use it

Before announcing a change, go through the five domains and write down which of them it actually moves for the people it lands on, rather than for you. Most changes move two or three, and the ones nobody thought about are usually where the money goes.

Supply predictability rather than comfort. Say when the next decision lands, who makes it and how people will hear, then hold to those dates, because a date that slips in silence undoes more than publishing it bought.

When the thing being delivered is critical feedback, keep the judgement and change the sequence. Ask for their own read first, say what standard is being applied and who else it applies to, and leave the remedy at least partly theirs, so the information survives the conversation instead of being softened out of it.

When you do have to intervene on delivery, price the intervention before you make it. Name which reviews start, at what threshold, for how long, and what would let them stop, so an open-ended loss of control becomes a bounded one.

Then go back and check the reading. Say in advance which domain you expect a change to hit and what you would see if you were right, and look a fortnight later, because a prediction that survives is worth more than an explanation that fits.

One thing to avoid: telling somebody their reaction is a threat response. Explaining a person's reaction back to them adds being diagnosed to whatever they were already dealing with, and it turns the model into a way of declining an objection rather than a way of hearing one.

Where it breaks down

Every concept here has one. It is the section most summaries leave out.

The brain evidence is thinner than the framing implies. The claim that social threat runs on the machinery of physical pain rests on regional overlap in brain scans, and Iannetti and colleagues argue that the overlapping activity isn't specific to pain, so what the two share is more likely salience or unpleasantness in general. Reading an experience off which region lit up is a known unsafe inference. What survives is the ordinary observation that people work worse when they feel badly treated, which was visible long before anybody owned a scanner.

Five broad domains explain anything after the event. Once a change has gone badly you can find the domain it threatened, the account will feel like a diagnosis, and a frame that fits every outcome has been tested by none of them. The repair is to use it forwards, and that is the step the training around it rarely insists on.

The rankings are measurement dressed as insight. The Institute sells a SCARF assessment, and its 2025 update reports, on more than fifteen thousand responses to that assessment collected across 2024 and 2025, that fairness and autonomy have overtaken certainty and relatedness, with certainty falling from the top of the list to the bottom of it. The announcement doesn't say who completed them or where they were, an average over fifteen thousand self-selected responses is silent about the person in front of you, and asking somebody to rank their own social drivers is self-report about responses the model itself describes as fast and largely automatic.

It turns a material grievance into a communications problem. Where the real complaint is pay, workload or a decision somebody got wrong, lowering the social cost of it makes an unwelcome answer easier to live with and changes nothing about the answer. That is the use most worth refusing, because the model is genuinely good at making things land, and something landing is a different matter from it being right.

The status advice shades into manufactured recognition. The suggestions for raising status without a promotion, more praise and more visibility, work while they are real and curdle the moment people can see they are standing in for the thing they wanted. Status is also the domain that makes accurate critical feedback expensive, and the lesson managers take from that is usually the wrong one, which is to say less.

There's no evidence that using it produces better outcomes. Nobody has run the comparison between managers who design their conversations this way and competent managers who don't, the literature is mostly conceptual, and the most confident writing about it comes from the organisation that teaches it. Lindebaum and Zundel's objection to the wider field applies here, which is that a neuroscientific frame supplies authority rather than evidence.

The experiments behind it are narrow. The studies the five domains were assembled from run mostly on small Western university samples in laboratory conditions, and norms about status and fairness vary enough between cultures and between organisations that treating the five as universal is an assumption rather than a finding.

In one line

Work out what a decision costs people in standing, predictability, control, belonging and fairness before you announce it, because they'll answer that bill rather than your argument.