Illustrative scenario
A simpler form—for whom?
An agency replaces a paper form with an online application. Processing gets faster, but someone without reliable internet spends an afternoon trying to upload a document. The service looks more efficient from one side of the desk. What does it look like from the other?
01
Examine what a system rewards
A system teaches people what to do through what it rewards, what it makes easy, and what it makes exhausting. A service can be well intended while its procedures, incentives, or access requirements create preventable overload.
Examine basic services, health systems, and externalities together: what supports people’s capacity, what protects it, and what imposes avoidable stress.
02
Three ways a system can change a life
Raise baseline capacity
Basic services can make food, shelter, learning, and essential support less dependent on a person’s ability to navigate repeated crises.
Protect capacity
Health systems can support prevention, care, recovery, and dignity, including when an illness cannot be cured.
Reduce imposed stress
Externality management asks who carries the costs of a product, policy, or activity—and how those costs can be prevented or fairly addressed.
These levers work together. A system can provide support while continuing to create the conditions that exhaust it. Evaluate both sides.
Zach Charles, Sufferless (2026), Chapter 52, pp. 433–445. Website adaptation; proposed applications require testing in context.
03
Put existing power to a better purpose
The capacities that amplify a problem can sometimes help address it. An attention system could support learning rather than compulsion; a procurement system could reveal labor conditions rather than reward the lowest visible price.
Repurposing requires more than changing a mission statement. Change the incentives, make consequences visible, and give people affected by the system a route to challenge it. Apply the same questions to biotechnology, automation, energy, and materials—not only AI.
Zach Charles, Sufferless (2026), Chapters 52–53. Website adaptation; proposed applications require testing in context.
04
Design for feedback and correction
- Identify the burden and the conditions producing it.
- Examine consequences across the four domains and four tiers.
- Include people poorly served by an “average user” design.
- Compare alternatives and record uncertainty, costs, and possible transfers.
- Use staged trials, independent review, and a practical way to reverse course.
Resource allocation, service design, and regulation require different evidence. The book provides a design philosophy; a policy recommendation still needs local analysis.
05
Change the arrangement, change the burden
The following comparisons are illustrative design proposals. Their effects would need evaluation with the people affected.
Accessing support
An applicant repeatedly supplies the same information to different teams.
Reuse information appropriately, explain requirements once, and offer assisted access.
What to evaluate: Examine completion effort, privacy, error rates, exclusions, and staff workload.
Protecting attention
Employees are expected to respond continuously while completing focused work.
Agree on response windows, quiet working periods, and a separate route for urgent issues.
What to evaluate: Examine interruption burden, service responsiveness, autonomy, and who absorbs urgent tasks.
Making an informed purchase
A consumer must reconstruct a supply chain to assess a product.
Provide accessible, independently checked information at the decision point.
What to evaluate: Examine comprehension, verification costs, producer access, and misleading simplification.
06
Five design heuristics
- Reversibility
- Prefer changes that can be undone if harm emerges. Identify who can pause them.
- Visibility of harm
- Make burdens and exclusions observable. Do not interpret silence as evidence that a service works.
- Repairability
- Make correction possible after feedback, including the resources and time needed to do it.
- Incentive alignment
- Examine whether profit, prestige, or performance targets reward the outcome people actually need.
- Equity
- Examine the distribution of benefits and burdens; include people least able to absorb new demands.
Use these questions in a Sufferless Decision Brief. Set a review date and a condition for changing course before expanding a proposal.
Chapter 52, printed pp. 433–445. These explanations apply its heuristics without presenting proposed reforms as proven outcomes.
07
Worked example · Accessing a public service
A digital application may reduce paperwork for an agency while shifting work onto applicants with limited connectivity, literacy, time, or accessibility support. Compare completion effort, waiting time, error rates, staff workload, and access by group.
Test assisted and offline routes alongside the digital service. An apparent efficiency gain is incomplete if eligible people quietly lose access.
08
Who decides—and how can the decision change?
Responsibility should follow capacity and proximity. Explain when consequences justify a wider response, while preserving participation and proportionate safeguards.
Web application of Chapters 4 and 50: authority, proportionality, subsidiarity, and reversibility. These are proposed questions for decision-making, not a statement of legal authority.
09
Evidence, tradeoffs & review
Before an intervention is recommended, document the evidence for its expected benefits, plausible harms, affected groups, and short-, medium-, and long-term effects. Include lived experience and alternative explanations, and distinguish predictions from observed outcomes.
A favorable average cannot justify overriding autonomy or concealing a worse outcome for a vulnerable group. Define what would count as failure, who can request a pause, and how a trial could be reversed. The evidence approach explains how proposals should be tested and revised.
10
Help develop this application
Public-service teams, designers, and researchers can contribute cases where an institutional change relieved a burden—or moved it onto someone less able to carry it.
Discuss a research collaboration
Based on Zach Charles, Sufferless: The Science & Philosophy of Reducing Suffering (2026), Chapter 52, printed pp. 433–445. Proposed applications. See the evidence briefs for selected research and its limits.
Turn understanding into a next step
Prepare a decision brief.
Identify the people affected, compare alternatives, record uncertainty, and decide how to review what happens.
Open a worked decision brief