← Blog

Punish Your Best Users, Not Your Worst: The Enforcement Rule Most Platforms Get Backwards

The same suspension that makes an invested user better makes an uninvested one worse. Build losable status before you enforce, or your penalties will backfire.

Based on the research ofXiaohui Zhang, Zaiyan Wei, Qianzhou Du, and Zhongju Zhang, "Social Media Moderation and Content Generation: Evidence from User Bans," MIS Quarterly 50(1), 2026

Platform Governance · Marketplace enforcement · August 2026

Studying user bans on a large question-and-answer community, Xiaohui Zhang, Zaiyan Wei, Qianzhou Du, and Zhongju Zhang found that a temporary suspension does not reliably calm bad behavior. After the ban lifts, sanctioned users post measurably more answers, and those answers are lower in quality. The authors trace this to psychological reactance: strip away someone's freedom and they rush to reclaim it, flooding the platform with quick, emotional, low-effort content. But the effect flips for users who hold earned platform recognition. Because status is an asset they can lose, the same ban threatens something they value, and they respond by posting less and raising quality. Status, not the sanction, decides whether enforcement helps or hurts. That single contingency should reshape how every platform designs penalties.

Ride-Hailing: Uber Learns That a Deactivation Threat Is Only as Strong as What the Driver Has to Lose

Uber runs a four-tier status ladder in Uber Pro, from Blue up through Gold, Platinum, and Diamond, with standing earned over a rolling three-month window from trip points and service quality. Diamond drivers earn 5% more on most trip fares through a Pro Perk, plus priority airport queueing, a Trip Radar advantage, and VIP support. Upper-tier drivers at Gold and above with at least 2,000 lifetime trips also unlock fully funded ASU Online tuition. Separately, Uber can deactivate any driver for low ratings or safety issues, with a documented review-and-reinstatement path.

Put those two systems side by side and you see the paper's mechanism in the field. A deactivation threat against a driver with no earned tier costs them only the marginal trip income, so the low-stake response is to appeal, churn, or return with minimum service effort. A Diamond driver facing the same review is threatened with the loss of a tangible, hard-won bundle of earnings and perks, which gives them a strong reason to fix service quality rather than push volume.

The implication is that a pure deactivation threat only reliably improves the drivers who already hold losable status. For the large pool of low-tenure drivers, suspend-and-reinstate produces churn and grudging compliance, not better service. Three options follow, each with a tradeoff:

- Make enforcement status-linked rather than binary: dock tier progress or freeze perks for quality lapses. This builds constructive correction among established drivers but does nothing to a first-week driver who holds no status. - Accelerate status accrual for new drivers through early micro-badges and faster first-tier eligibility, so more of the fleet has something to lose sooner. This gives enforcement teeth earlier but cheapens the status signal and raises reward cost per driver. - Keep hard deactivation but pair reinstatement with a measurable quality gate, such as verified safer-driving telemetry, instead of a time-served wait. Uber has already started weighing phone-sensor evidence of safer driving in reviews. This converts the ban into a quality incentive but adds monitoring overhead and disputes over sensor evidence.

Home-Sharing: Airbnb's Real Leverage Is the Badge, Not the Ban

Over roughly two years Airbnb removed more than 400,000 low-quality listings that failed its hosting standards, its largest-ever purge, and afterward reported a 15% drop in quality-related customer-service issues and an average listing rating above 4.75. In parallel it runs Superhost status, which demands a 4.8-plus rating, a cancellation rate below 1%, a 90% response rate, and at least 10 stays, reassessed quarterly and lost when the numbers slip. Superhosts get priority search placement and rewards.

This is the flip point made concrete. A marginal, low-review host who gets delisted has little sunk reputation to protect, so the reactance response is to relist under a fresh account or minimally patch the listing. A Superhost facing a quality warning is threatened with a badge that took a year of five-star stays to build, where offsetting a single one-star review requires roughly 19 five-star reviews. That host has far more to lose and invests in genuine repair.

So delisting cleans the catalog, but durable behavior change comes from hosts with reputation at stake. The leverage is the badge. Three moves, each with a cost:

- Tie the crackdown to status jeopardy for established hosts, warning then stripping Superhost rather than only hard-delisting marginal listings. This maximizes quality investment among your best hosts but does little to stop low-reputation hosts cycling in under new listings. - Raise entry friction through verification and a minimum track record before full visibility, so new hosts must accrue reputation before they can flood the catalog. This suppresses churn-and-burn supply but slows growth and can deter legitimate newcomers in thin markets. - Make status faster to earn and faster to lose, with a shorter reassessment window. This gives more hosts something to protect sooner but raises host anxiety and support load around status changes.

Creator Platforms: YouTube's Demonetization Only Bites the Creators Worth Keeping

In July 2025 YouTube tightened its Partner Program, renaming "repetitious" content to "inauthentic" and later expanding guidance to demonetize "mass-produced," "unsatisfying or off-putting," and AI-persona content, while still paying content that adds original commentary, editing, storytelling, or educational value. The behavioral split matches the paper exactly. Low-stake clip farms and compilation channels respond to demonetization the reactance way, spinning up new channels and flooding the platform with high-volume, low-effort uploads. A high-stake creator responds constructively. The owner of HPad, an 18-year appliance-testing channel with more than 225,000 subscribers, publicly reported losing at least $15,000 over three months when his classification shifted to "unsatisfying or off-putting." For a creator with that much invested brand equity, the rational move is to raise production quality, not to churn.

So demonetization suppresses payouts but not necessarily the low-quality flood, because uninvested accounts simply respawn and re-upload (see the exhibit). It becomes a quality-raising incentive only where channel identity and audience are the asset at risk. Three options:

- Attach enforcement to the creator's persistent identity and reputation, not just the individual video, and make standing recoverable through demonstrated quality. This motivates established creators but is evaded by bad actors minting fresh channels. - Gate monetization and reach behind an originality and track-record threshold at entry, so new channels earn standing before they scale volume. This throttles spam supply but slows discovery for legitimate newcomers and invites backlash. - Pair demonetization with a transparent reclassification-and-appeal path that spells out what changed and what fixes restore monetization. This turns the sanction into a quality roadmap but is costly at scale and exposes ranking criteria to gaming.

App Stores: Google Play Pays for the Arms Race a Blunt Ban Sets Off

Google Play terminates developer accounts for accumulated policy strikes. On termination, all of a developer's apps are removed, they cannot publish new apps, and any linked accounts are permanently banned too, a rule built specifically to stop banned developers from opening fresh accounts. The scale of that fight is now public: in 2024 Google banned 158,000 developer accounts and blocked 2.36 million policy-violating apps from publishing, up from 2.28 million the year before, with more than 92% of its harmful-app reviews now AI-assisted. Those are the numbers of an expensive, permanent detection war, and the linked-account clause is the tell.

A low-stake spam or clone developer does exactly what reactance predicts, opening new accounts and re-publishing high-volume, low-quality apps to reclaim distribution. A developer with a genuine hit app and years of ratings holds a far larger sunk asset, so the constructive path in Google's own flow, fix the violations and appeal, is the rational one. Nate Shoffner's widely cited account of a Google Play termination shows the pattern from the ground: the ban cited linkage to a previously terminated account, confirming that Google spends real effort chasing respawns rather than reforming invested developers.

Account bans alone therefore invite whack-a-mole and force the platform to fund that arms race indefinitely. Enforcement turns constructive only where the developer holds a losable, hard-to-recreate asset. Three options, each with a tradeoff:

- Invest in identity and linkage detection so low-stake developers cannot cheaply respawn. This directly attacks the churn-and-flood response but locks you into an ongoing arms race and risks false-positive bans of innocent linked accounts. - Build graduated, status-preserving enforcement for established developers, using app-level strikes and guided remediation instead of nuking the whole account. This motivates good-faith developers to fix rather than flee but adds review overhead and can be gamed by bad actors hiding behind one legitimate app. - Raise entry stakes with verification or a bond before high-volume publishing. This makes respawning expensive and throttles spam supply but adds friction that suppresses legitimate indie onboarding.

The Rule: Enforcement Design Is Downstream of Status Design

Across all four platforms the pattern holds. A sanction only moves behavior in the direction you want when the target has accumulated visible, losable stake. Absent that stake, enforcement triggers reactance and hands you more volume, lower quality, and account churn. So build the thing users are afraid to lose first, whether tiered reputation, badges, monetization eligibility, or earnings perks, then aim enforcement at that asset rather than at raw access. Two moves recur everywhere: gate low-stake accounts at entry, because they will churn-and-burn no matter what you do afterward, and correct high-stake accounts by putting their status at risk rather than issuing a blunt ban. The blunt ban is your weakest tool against exactly the users who produce the most low-quality volume, and the status threat is your strongest tool for exactly the users worth keeping. Design the stake before you need the stick.