Designing around people
Human-centered design means building a service around the real needs, behavior and circumstances of the people who use it. It is what turns a system that merely works into one people actually use, which is the only point at which it delivers anything.
For government it is not optional. The 21st Century IDEA Act makes accessible, user-centered digital services a legal requirement, and a badly designed public service does real damage. It shuts out the people who need it most, pushes avoidable volume into a call center, and wears away trust. Good design does the opposite.
Varmoda applies this across its public benefits, constituent-facing and platform work, and the payoff is measurable: higher take-up, better outcomes, lower cost to serve, and a service that reaches everyone entitled to it.
What it actually means
Human-centered design puts the people who will use a service at the center of designing it, and keeps them there, from the first research to long after launch.
- Start from real need. Interviews, observation and testing with real people in their real situation, rather than what a team assumes they want.
- Involve people throughout. Not a review at the end, but a say all the way through.
- Design the whole journey. The end-to-end experience, not one screen in isolation.
- Work in cycles. Design, test, learn, refine. Nobody gets it fully right first time, and circumstances keep changing.
These echo the United States Web Design System principles and the international standard for human-centered design, ISO 9241-210.
The contrast that matters is simple. Feature-first design starts from what the system can do and hopes people adapt. Human-centered design starts from what people need and shapes the system to fit. The two produce very different products, and the difference becomes clear at adoption.
Why it matters in government
Public services reach everyone, often at the hardest moments of a person’s life: applying for benefits, following a claim, getting care. Design is not decoration here. It decides whether people can get what they are entitled to.
The stakes
A confusing form or an inaccessible site can deny someone a benefit they qualify for, push avoidable calls into a contact center, and damage trust in government itself. Good design lets people succeed on their own, first time.
It is the law, not a preference
The 21st Century IDEA Act requires accessible, mobile-friendly, user-centered digital services from federal agencies. OMB guidance on delivering a digital-first public experience reinforces it, and Section 508 of the Rehabilitation Act requires accessibility for people with disabilities.
The tools already exist
The United States Web Design System turns all of this into reusable, accessible, mobile-first components, built around five ideas: start with real user needs, earn trust, embrace accessibility, promote continuity, and listen.
How the process runs
The work runs as a cycle: find out what people actually need, frame the right problem, and test solutions with real people before committing to them.
| Phase | What happens |
|---|---|
| Discover | Interviews, observation and journey mapping, to understand real needs and real frustrations. |
| Define | Turn the research into the actual problem and clear requirements. |
| Ideate | Generate and prioritize ideas with users and stakeholders together. |
| Prototype | Build rough and then refined prototypes cheaply, before anything expensive is constructed. |
| Test | Put it in front of real users and measure whether it meets the need. |
| Iterate | Refine on the evidence, repeat, and keep going after launch. |
The discipline that makes this pay is testing cheaply and early. A flaw in a prototype costs a few hours. The same flaw in a launched system costs months of rework, and in a public service it costs real harm to people who depend on it.
Accessibility and inclusion
Human-centered means all humans. A design that works only for people who are able, connected and comfortable with technology is not human-centered, and for a public service it is not lawful either.
- Accessibility is the floor. Section 508 and the WCAG standards require services to work for people using a screen reader, people with low vision, and people with motor and cognitive differences. Varmoda designs this in from the start, where it is both better and cheaper than adding it at the end.
- Design for the full range. Public services have to work for people with low digital confidence, people on a phone with a patchy connection, people whose first language is not English, and people under real stress. The people who most need a service are usually the worst served by one designed around a confident power user.
- Equity on purpose. The process deliberately surfaces the users who normally get left out, which is how a benefit reaches everyone entitled to it rather than only the easy to serve.
- Plain language. Clear words, simple steps and forgiving design cut errors and support calls, and they respect the person on the other side of the screen.
Done properly, accessibility and inclusion are not constraints on good design. They are good design.
Design and delivery are one discipline
This is not a phase bolted onto the front of a project. It is how the whole thing gets built, from requirements through to adoption.
- Research becomes the requirements. What the research uncovers is what gets built, so the solution follows evidence rather than internal preference.
- Usability is a requirement. On a packaged platform or a custom build alike, if the new system is harder than the old way, people route around it with spreadsheets, workarounds and old habits, and the need goes unmet.
- It carries through delivery. The prototypes tested in design become the acceptance criteria in testing, and the people involved in research are the same people who adopt at go-live.
- Measured against people. Done means a person can complete their task, not that a feature exists in the build.
Separating design from delivery is exactly how systems ship that work on paper and fail in people’s hands.
The value it creates
| What the customer needs | How the design delivers it | Value created |
|---|---|---|
| People to use the service | Designed around real needs and behavior | Higher adoption |
| Better mission outcomes | Services that fit how people actually work | Faster completion, better results |
| Lower cost to serve | Clear, usable, forgiving design | Fewer support calls and fewer errors |
| Public trust | Services that respect people and work for them | Confidence in the service and the agency |
| Compliance | Accessibility and user-centered design built in | Meets Section 508 and the 21st Century IDEA Act |
| Equity | Designed for the full range of users | The service reaches everyone entitled to it |
The same economics sit under every row. The cheapest time to meet a need is in a prototype. The most expensive is after launch, in production, with real people affected. Human-centered design moves that work to the point where it costs least, which is why the investment is recovered well before go-live and continues to return afterwards.
How Varmoda delivers
Varmoda designs around people because that is what makes a public service work, and because its signature capability, public benefits delivery, is exactly where design decides whether people get what they are entitled to.
Varmoda’s teams apply this across benefits and claims, constituent-facing services, packaged platform implementations and modernization work. Requirements are grounded in real user research. Designs meet Section 508, WCAG and the United States Web Design System. And the work is tested with real users before anything expensive is built.
Design and delivery are run as one discipline, so what ships is adopted rather than merely delivered. Delivery is United States based and secure, for the sensitive public-service environments where this matters most.
War Mode here is a commitment: start with real needs, design for everyone, test early, and measure success by whether a person can actually get what they came for.