On bias interruption, social regulation, and why some of the best product decisions add friction rather than remove it
Reduce friction. Remove steps. Compress decision time. Make action easier. Most product teams absorb that rule so deeply that friction becomes synonymous with bad design.
That rule is useful often enough to be dangerous. The problem is not that reducing friction is wrong. It is that friction is not one thing. Some friction is waste. Some friction is cognitive load. Some friction is bureaucracy. And some friction is social regulation.
When teams flatten those categories, they end up removing the very pauses that help people behave with more care, accountability, and context.
Nextdoor's racial profiling problem is a clean case. People were posting about "suspicious" neighbors using race as the primary descriptor. The interface made it very easy to convert a vague suspicion into a public warning. That was efficient product design in one narrow sense. It was also socially dangerous design.
The company eventually introduced what it called thoughtful friction. Instead of allowing an easy post built around race alone, the product required more specific physical descriptions. That added effort. But it also interrupted a cognitive shortcut, made the act more reflective, and materially reduced the harmful behavior; Nextdoor says those changes led to a 75% decrease in racial profiling on the app.
The lesson is bigger than the case. Some forms of bad behavior travel through the interface precisely because the interface has made them too easy to perform before ordinary social checks can kick in.
In face-to-face life, many harmful acts contain natural pauses. You have to say the thing out loud. You have to face another person. You have to manage the social cost of being seen doing it. Digital products often remove those mediating frictions. That is part of why they feel so efficient. It is also part of why they can amplify bias, pile-ons, panic, harassment, and impulsive behavior.
Thoughtful friction is one way of putting some social reasoning back into the loop. Not enough friction to make the product miserable. Enough friction to force the user to become more specific, more accountable, or more aware of the consequences of the act.
Good friction does not punish ordinary use. It interrupts the behaviors where speed itself is part of the problem.
This does not only apply to neighborhood platforms. Thoughtful friction matters in privacy settings, irreversible deletes, marketplace commitments, financial transfers, content sharing, and any moment where the cost of a bad action is high and the act is easy to do in a thin emotional state.
It can also matter in collaboration products. When a system makes it effortless to assign work, critique publicly, or escalate without context, some added reflection can improve the social quality of the interaction. The point is not to slow everything down. It is to distinguish which actions benefit from speed and which benefit from pause.
That distinction is a sociological one as much as a UX one, because the question is not only what the user can do, but what kind of shared environment repeated action will create.
The best friction is specific, contextual, and purposeful. It should teach something or interrupt something. It should be aimed at a known failure mode. It should not read as arbitrary bureaucracy. Ask what the user is likely to skip past when acting quickly, and what single prompt, requirement, or delay would cause them to engage more responsibly.
That is why thoughtful friction belongs next to Community Health Is Product Health. If community quality is part of the product, then the right amount of social regulation is part of good design. The goal is not maximum smoothness. The goal is a system that remains livable as it scales.