Sludge and Ordeals¶
Sunstein. (2018). Sludge and Ordeals.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Friction Budgeting
- UX and product design — the home turf: one-click checkout removing friction versus "type DELETE to confirm" adding it, sized to which interactions deserve which side. Financial controls and approval workflows — auto-approving small expenses while gating large ones with signatures, justification memos, and waiting periods, the friction concentrated on high-impact actions. Consent and informed-choice processes — medical, research-subject, and sensitive-data consent forms adding deliberation cost so the choice is genuine, sized to the decision's weight without becoming theatrical. Trust-and-safety and content moderation — rate limits, cooldowns on dangerous actions, and "are you sure?" gates on irreversible deletions, the friction sized to harm potential. Software-engineering release discipline — code-review requirements, deployment gates, and kill-switch procedures, friction inserted to catch errors before they propagate. Public-safety and physical design — speed bumps, child-resistant caps, ergonomic guards, and lockboxes, physical friction allocated to actions with downside risk. Policy design — registration burdens, waiting periods, and permit processes, policy-level friction budgeting with deep contestation over where the budget should sit. Behavioural economics / choice architecture — the nudge/sludge tradition framing default choice and required-step counts as the same allocation variable under another vocabulary
This sourceThe account of sludge as administrative friction - quantifiable required paperwork and steps that can be reduced as a policy variable through automatic enrolment, simplified forms and reminders.
Supported in partVerified against the publisher's abstract
“Many of these hours are best categorized as "sludge," reducing access to important licenses, programs, and benefits.”
- UX and product design — the home turf: one-click checkout removing friction versus "type DELETE to confirm" adding it, sized to which interactions deserve which side. Financial controls and approval workflows — auto-approving small expenses while gating large ones with signatures, justification memos, and waiting periods, the friction concentrated on high-impact actions. Consent and informed-choice processes — medical, research-subject, and sensitive-data consent forms adding deliberation cost so the choice is genuine, sized to the decision's weight without becoming theatrical. Trust-and-safety and content moderation — rate limits, cooldowns on dangerous actions, and "are you sure?" gates on irreversible deletions, the friction sized to harm potential. Software-engineering release discipline — code-review requirements, deployment gates, and kill-switch procedures, friction inserted to catch errors before they propagate. Public-safety and physical design — speed bumps, child-resistant caps, ergonomic guards, and lockboxes, physical friction allocated to actions with downside risk. Policy design — registration burdens, waiting periods, and permit processes, policy-level friction budgeting with deep contestation over where the budget should sit. Behavioural economics / choice architecture — the nudge/sludge tradition framing default choice and required-step counts as the same allocation variable under another vocabulary
Verification¶
Does it exist? Not checked yet. This work's DOI is recorded above but has not been resolved against an external catalogue, so nothing here confirms the work exists.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:c0073dd1e7ba · see in the full table