Radical Candor

Work keeps producing moments where something should be said and isn't. The same problem shows up three times in a colleague's screen designs, and each time raising it feels like it would make things awkward, so it passes. At Pagedeck, Mia saw the same broken flow in Noa's specs twice and let both go. She said something the third time, and her voice was louder than usual.

Holding back twice and coming in hard on the third attempt helps nobody. The person on the receiving end hears something for the first time at high volume, and the person speaking is carrying the weight of the two times they stayed quiet. Letting the first two pass looked like consideration. What it actually did was take two chances to fix the problem away from the other person.

The failure in the other direction is just as common: everything gets said, and what the listener remembers is the tone rather than the content. Someone who hears only "this needs redoing" walks away without knowing what to redo or how, and keeps the feeling from the room instead. Next time they won't show that person a draft first.

Radical candor organizes those two failures into two axes. One is how much you care about the person. The other is how directly you name the problem. High on both is radical candor. High on caring but unable to say anything becomes the kind of consideration that blocks someone's growth. Direct with no evident care becomes an attack where the content never lands. Low on both leaves nothing but pleasant noise. The point of the framework is that this isn't a choice between the two — there is a fourth position where both are present at once, and that position is the one being named.

Break one conversation into five steps.

1. Decide whether to say it. The test is simple: say it if the other person cannot fix the thing without knowing about it. Skip it if it's a matter of taste, or if they already know and are adjusting.
2. Pick the setting and the timing. Never in front of a group, and inside a day of the thing happening. After a week the other person no longer remembers the moment, and a conversation about a moment nobody remembers goes nowhere.
3. Start with what happened. An observation, not a verdict about character. Not "collaboration has been rough" but "in that meeting you cut Theo off three times."
4. Attach the effect it had. "He didn't say anything for the rest of the meeting." Without this line the other person has no reason to accept that it was a problem at all.
5. Close with a request and then listen. Say in one sentence what you'd like done differently, and hear the reply. Skip this step and the whole thing was a notification.

There is a procedure for the receiving side too, and it starts with asking. A manager who says "tell me if I'm missing something" gets materially different results from a manager who waits in silence, because silence produces silence. The place that request gets repeated is the one-on-one — the recurring private conversation between manager and employee, commonly 30 minutes every other week.

This works best where a relationship already exists. Caring about someone can't be manufactured in the moment; it is demonstrated by the time that came before it. Be direct with someone in their second week and they have no way to verify that the caring axis is there, so they read it as an attack. With new people, build that side first and slow the other one down.

Three situations call for something else. The first is anywhere a group is watching, because the same words said publicly leave the shape of the exchange behind rather than its content. The second is when feelings are already running high, because you start at step 4 instead of step 3 and the other person begins disputing the facts. The third is speaking sharply up a large gap in authority. For someone to talk to a founder this way, they need to be sure first that saying it carries no cost — a condition called psychological safety, the sense that raising mistakes or disagreements won't be held against you.

The limits are clear too. This is a disposition, not a system. Even a team that speaks honestly every week still has to gather those conversations into a document when the period closes, and that document is the performance review, which turns a period's results and capabilities into a judgment. In the opposite case, an organization with an elaborate process and none of this disposition produces evaluations where every sentence is inoffensive. Neither one substitutes for the other.

"This might be uncomfortable to hear, but going without knowing it seems worse."

Saying why you're raising something before you raise it.

"You cut Theo off three times in that meeting. He didn't speak again afterward."

A sentence built from the fact and the effect, with no judgment about character in it.

"Say it to me the same way when it's the other direction."

The receiving side opening the door for the next conversation.

Mia and Noa changed how they work after that episode. They now sit down over specs at the draft stage rather than at the end. Commenting on something finished is criticism; commenting on a draft is building it together, and the same sentence reads differently depending on which one it is.

The timing wasn't the only change. Mia stopped saying "this flow feels off" and started saying "if you hit back here, everything you typed disappears." Same point, but there is nothing in the second version to argue with.

The most common reading is that the whole thing is just being blunt. The word candor is in the name, so that's how it scans. But candor is only one of the two axes. Direct with the caring axis missing means the content never lands, and from then on that person shows you nothing before it's finished. In organizations where this misreading settles in, speaking harshly to each other gets described as the culture — right up until people start leaving one by one and it becomes clear it wasn't one.

The mirror-image mistake is believing that softening things is consideration. Holding back makes the immediate moment easier, so it feels kind. But the other person never learns there was a problem, repeats it, and hears about it for the first time in a review six months later. What they receive at that point isn't the result of kindness. It's the result of losing six months of chances to fix it.