When did filling in a form become the price of being treated like a person? That question runs through a phrase that keeps appearing in design studios, government offices and hospital waiting rooms: people over papers. It sounds like a slogan, and sometimes it is one. But it carries a serious argument about how services get built, how rules get written, and who ends up paying when paperwork quietly takes priority over the person holding the pen.
The phrase has no single definition, so it helps to be precise. It is used in at least three overlapping ways. First, as a design principle: build things around what people actually need rather than around the documents that describe them. Second, as a critique of administrative burden: the forms, proofs and compliance steps that deter eligible people from getting help. Third, as a values statement in welfare, immigration and disability policy: treat lived experience as evidence, not noise. This article takes all three seriously, because in practice they reinforce each other. (Evidence-based practice)
What “people over papers” actually means
Strip away the rhetoric and the idea is simple. Paper is a proxy. A form is a stand-in for a person’s circumstances, a policy document is a stand-in for a decision, and a case file is a stand-in for a life. Proxies are useful. They let large organisations act at scale. But every proxy loses information, and the losses tend to fall hardest on people whose situations are complicated, unusual or simply poorly served by the categories on offer.
The human-centred design tradition has made this concrete. The international standard ISO 9241-210:2019 sets out principles and activities for designing interactive systems around the people who use them, including understanding the context of use and involving users throughout. That is the design version of people over papers: the specification document does not get the final word, the person using the thing does.
In public services, the same logic shows up in the UK Government Digital Service’s design principles, the first of which is to start with user needs. The accompanying guidance on defining user needs is blunt about method: teams are expected to describe needs in terms of what people are trying to do, and to back that up with evidence rather than assumption. That is a small procedural detail with large consequences, because it makes “we assumed” an unacceptable answer.
The hidden cost of administrative burden
Here is where the phrase stops being aspirational and starts being a complaint. Administrative burden is the cost that paperwork imposes on the people who have to deal with it, and researchers have spent more than a decade mapping it. The political scientists Pamela Herd and Donald Moynihan, in their 2018 book Administrative Burden, argue that these costs come in three flavours: learning costs (working out what you are entitled to and how to claim it), compliance costs (gathering documents, filling forms, attending appointments) and psychological costs (stress, stigma, the sense of being judged).
Their central finding is uncomfortable for anyone who assumes that a badly designed form is merely annoying. Burden is not spread evenly. It deters exactly the people most in need, and it does so quietly, because non-claimants do not appear in the statistics of a programme they never entered. A form that takes forty minutes to complete looks efficient on a spreadsheet. It looks very different to someone with no printer, no stable address and a shift that starts at six.
The United States has legislated about this for decades. The Paperwork Reduction Act, enacted in 1980 and substantially amended in 1995, created the Office of Information and Regulatory Affairs within the Office of Management and Budget to review federal information collections. OIRA publishes an annual Information Collection Budget estimating the paperwork hours federal agencies impose. Whatever the exact headline number in any given year, the exercise itself is revealing: governments now measure paperwork as a cost to be managed, in the same way they measure spending.
That measurement matters because it changes the conversation. Once burden is counted, it can be reduced deliberately. Remove a redundant proof, pre-fill a field from data the agency already holds, accept a photograph of a document instead of a certified copy, and the person on the other side of the counter gets an hour of their life back.
Designing for the person, not the process
The practical question is how an organisation actually shifts from paper-first to people-first. In practice, the teams that manage it tend to do a handful of things differently, and none of them are glamorous.
Start with the hardest case
The most common mistake is designing for the average user, then bolting on “edge cases” at the end. It works in reverse. If a service functions for someone with low digital confidence, limited English, a disability or an unstable income, it will almost certainly work for everyone else. The GOV.UK Service Standard makes this explicit by requiring teams to test with users including assisted digital users, the people who need help to use a service at all. Designing for them first tends to simplify the whole system rather than complicate it.
Reduce what you ask for
Every field on a form is a small demand on someone’s time and attention. The discipline is to ask, for each one, whether the organisation genuinely needs the answer, whether it already holds the information somewhere, and what happens if the field is left blank. A surprising amount of requested paperwork exists because it always has. That is not a reason. It is a habit.
Make the paper match the person
Accessibility is not a courtesy layered on top of a process; it is part of whether the process works. The NHS Accessible Information Standard, first published in 2015 and updated since, requires health and care providers in England to identify and meet people’s communication needs, including for people with disabilities or sensory impairments. The underlying legal principle is broader still: Article 9 of the UN Convention on the Rights of Persons with Disabilities, adopted in 2006, requires accessible information and communications. A letter nobody can read is not communication. It is paper.
Treat lived experience as evidence
The disability-rights slogan “nothing about us without us,” popularised in the 1990s and associated with James Charlton’s 1998 book of the same name, makes a claim that goes beyond consultation. Its origin is contested, but its argument is not: people with direct experience of a system should shape it, not merely be processed by it. In practice that means paying people for their time on advisory panels, recruiting them into design teams, and giving their objections the same weight as a legal opinion.
Where the phrase goes wrong
Balance matters here, because “people over papers” can be misused in at least two directions.
The first misuse is paper as scapegoat. Some documentation exists precisely to protect people: records of consent, audit trails, safety checks, evidence of eligibility. Ripping out paperwork without understanding what it guards is not human-centred, it is reckless. The goal is not zero documents. It is zero pointless documents, and a clear account of what each remaining one is for.
The second misuse is empathy as substitute for rigour. A team can feel deeply user-centred while shipping something that fails in practice, because nobody tested it with the people it was meant to serve. Warm intentions do not show up in an error rate. Evidence does. The design standard and the service standard both insist on the same thing: observe real people using the real thing, and change your mind when they struggle.
There is a third, quieter failure worth naming. When organisations talk about “people” they often mean articulate, connected people who turn up to workshops. The people most affected by administrative burden are frequently the least likely to be in the room. Reaching them takes deliberate effort, and it is the part most likely to be cut when a project runs late.
What actually works in practice
A few practical patterns recur across services that have genuinely reduced the paper-to-people ratio.
| Pattern | What it changes | Common mistake |
|---|---|---|
| Pre-filling from existing data | Removes fields the organisation already knows the answer to | Asking for the same document twice because two systems do not talk |
| Plain-language rewriting | Cuts learning costs dramatically | Testing comprehension on colleagues instead of real users |
| Multiple channels, one process | Lets people choose phone, post or online | Building a digital service and calling the paper route “legacy” |
| Named human contact | Reduces psychological cost and failed applications | Hiding the phone number to push people online |
| Measuring burden explicitly | Makes the cost visible to decision-makers | Counting forms processed instead of hours imposed |
The last row is the one leaders most often skip. If nobody measures how long a process takes from the applicant’s side, nobody is accountable for shortening it. A simple time-and-effort study, run with a handful of real applicants, will usually surface two or three fixes that cost almost nothing.
For teams thinking about this in a digital context, the same instinct applies to the tools themselves. Choosing equipment and software on measurable performance rather than marketing claims is its own small version of the principle, whether that means picking the best external SSD for 2026 based on real speed rather than marketing or checking whether external SSD TRIM support over USB actually works before trusting a spec sheet. The parallel is not exact, but the habit is: judge by what the person at the end experiences, not by what the document promises.
Why this matters beyond government
It would be a mistake to file people over papers under “public sector reform” and move on. The same tension runs through private customer service, where a support ticket can become more important than the customer, and through internal operations, where a process survives because it is documented rather than because it helps. Organisations serving large customer bases feel it acutely; the thinking behind a customer success platform built for SaaS companies with more than 500 customers is essentially about keeping a human relationship visible when the account data becomes overwhelming.
Education shows the same pattern. Students drowning in notes can mistake accumulation for learning, which is why comparisons of NotebookLM and ChatGPT for studying notes and papers tend to circle back to a simple question: does this help the person understand, or just produce more material? Even a mundane purchase carries the idea. A pour-over coffee maker is a small daily reminder that a slower, more deliberate process can beat a faster one that skips the human step.
The through-line is consistent. Paper, process and documentation are means. The person is the end. When the order flips, everyone pays, and the people who pay most are usually those with the least room to absorb the cost.
Conclusion
People over papers is not an argument against records, rules or rigour. It is an argument about priority. Documentation should serve the person holding it, not the other way around. That means designing with the hardest cases first, counting burden as a real cost, making information genuinely accessible, and treating lived experience as evidence rather than decoration. It also means being honest when paperwork exists for a good reason, and ruthless when it does not. The test is simple enough to apply to almost anything: if this form, letter or process disappeared tomorrow, who would be worse off? If the honest answer is nobody, the paper was never serving the person in the first place.
Frequently asked questions
What does “people over papers” mean?
It is a shorthand for prioritising human needs over documentation, process or administrative convenience. It appears in three main contexts: human-centred design, where user needs outrank specifications; public administration, where reducing paperwork burden is the goal; and disability and welfare policy, where lived experience is treated as valid evidence. The phrase has no single official definition. (WHO: Evidence-informed policy-making)
Is “people over papers” a law or a standard?
No. It is not a named legal standard. The ideas behind it are reflected in instruments such as ISO 9241-210:2019 on human-centred design, the UN Convention on the Rights of Persons with Disabilities, and national rules like the NHS Accessible Information Standard. In the United States, the Paperwork Reduction Act of 1980 addresses federal paperwork burden directly.
What is administrative burden?
Administrative burden is the cost that paperwork and process impose on the people dealing with them. Researchers typically divide it into learning costs, compliance costs and psychological costs. The key finding is that burden is not spread evenly: it deters the people most in need of a service, and those non-claimants are largely invisible in programme statistics.
Does reducing paperwork mean cutting safeguards?
Not if it is done properly. Much documentation exists to protect people, for example consent records, safety checks and audit trails. The sensible approach is to ask what each document is for and who would be harmed if it vanished. Pointless paper should go; protective records should stay and be made easier to complete.
How can an organisation tell if it is paper-first?
Look at where the effort sits. If staff measure their work in forms processed rather than outcomes achieved, if applicants are asked for information the organisation already holds, or if nobody has timed the process from the applicant’s side, the paperwork is probably in charge. A short effort study with a few real applicants usually settles the question.
Why does accessibility matter to this argument?
Because a document nobody can read or understand is not really communication. Accessibility standards exist so that information reaches people with disabilities, sensory impairments or limited digital access. Designing for those users first tends to simplify a service for everyone, which is why accessibility and burden reduction so often point in the same direction.
