Designing for anticipation: Human-centered experience design in government services

Key takeaways:

• Government agencies inherit legacy systems and siloed teams, but the real friction comes from never mapping the citizen's actual journey. When you see where people get stuck and why they abandon services, the design opportunities become concrete and actionable.

• Citizens arrive with limited time and uncertainty, not an interest in your compliance requirements or system architecture. Design that acknowledges their reality and guides them forward, rather than forcing them into rigid processes, delivers measurable impact.

• Certain moments have outsized impact on whether citizens succeed or abandon your service: deciding to engage, understanding the path forward, encountering problems, deciding whether to continue, and completing their task. Design these moments to anticipate problems rather than react to them, and guide citizens forward instead of leaving them stuck.

• The real question is whether government can afford the cost of fragmentation: abandoned applications, wasted staff time, overwhelmed support lines, and eroding trust. What's needed is the commitment to shift from "What do our systems require?" to "What do citizens need?"

It's Monday morning, and a single mom sits at her kitchen table with her laptop, coffee getting cold. Her youngest just turned 6, which is old enough for the after-school program she's heard about, the one that would give her the breathing room she desperately needs between work and pickup.

She finds the government website that promises information about enrollment, eligibility, and next steps. At first, it feels promising, but that quickly turns to confusion.

The eligibility criteria are buried in dense paragraphs. Income thresholds appear in one section while documentation requirements are in another, all scattered across pages with no clear sequence. She clicks to apply, only to discover she needs forms she's never heard of and can’t find on the site. There’s no roadmap, no guidance.

Frustrated, she searches for a phone number to call, but finds nothing. She does see an email to contact, but it’s a generic inbox with responses expected to take 5 to 7 business days.

She closes her laptop. The program she qualifies for remains unclaimed, and her need goes unmet. It’s a need the government wants to fill, but the experience makes it nearly impossible for her to find the help that's meant for her.

This happens every day across government. But it doesn't have to.

Where experience design falls short in government

Inside the organization, the story looks different. Marketing teams launch campaigns; IT maintains systems; program leaders manage operations. Each function does what it's designed to do.

From the outside, nothing feels connected. To users, every interaction feels like starting over.

This results in invisible friction that's easy to miss internally but impossible to ignore externally. People disengage because the path forward is unclear, cumbersome, or impersonal. Government loses trust, momentum, and the opportunity to build meaningful relationships.

Why this happens

Government agencies face real constraints:

• Legacy systems that don't talk to one another

• Compliance requirements (FedRAMP, NIST, Section 508) layered on after the fact

• Siloed teams with rigid approval processes

• Fragmented data that prevents real understanding of user behavior

But the cost of fragmentation is far higher than the investment required to address it:

• Citizens disengage.

• Teams waste days on manual workarounds.

• Trust quietly deteriorates with every frustrating interaction.

Most organizations treat this as a technology problem, but it may be an experience design problem. That requires a fundamentally different approach.

Journey mapping that reveals friction

Most government organizations have documented their processes. What they haven't done is map their citizen journeys from the citizen's perspective.

There's a critical difference:

• Process mapping = "Here's how our systems work."

• Journey mapping = "Here's what citizens experience and where they get stuck."

A 4-step approach

1. Start with real user research. Don't assume you know what citizens need, but observe them. This might include conducting user interviews with people who've attempted your service, analyzing behavioral data, identifying personas that represent distinct user types and their unique needs, and mapping emotional states.

2. Map moments, not steps. Traditional process flows show linear paths, but real journeys are messy and non-linear. Identify the critical moments in the journey, such as when citizens decide to engage, where they get stuck, and when they feel confident moving forward.

3. Uncover hidden friction points. This is where many organizations miss the real problems by failing to look deeper than the obvious, such as identifying why citizens may be abandoning mid-journey, why they’re using workarounds instead of intended paths, and why they’re calling support instead of utilizing self-service. While the technology may be fine, the journey fragmentation is problematic.

4. Identify where internal process conflicts with user need. Look for places where your internal process doesn't match user expectations. For example, this is the difference between "Data validation happens after submission" and "Tell me immediately if something is wrong so I don't waste time."

Consider the single mom exploring after-school program enrollment. Journey mapping would have immediately surfaced what the current experience obscures: Her decision point came with urgency and limited patience; her confidence peaked the moment she landed on the website, and it plummeted the instant she encountered repeated form fields and fragmented guidance.

The friction points were everywhere because no one had mapped her journey. Internal processes (eligibility criteria spread across multiple pages, required documentation housed elsewhere) conflicted sharply with her expectations (clear guidance, one coherent path, respect for her time). By starting with her reality, journey mapping transforms these invisible friction points into concrete design opportunities.

The result is an experience that matches her needs, respects her constraints, and keeps her moving forward instead of closing her laptop.

Designing for real user needs rather than internal processes

Government organizations typically design around internal constraints: compliance requirements, system architecture, approval workflows, and organizational silos.

But citizens don't care about any of that. They care about whether they can do what they came to do, whether it makes sense, and if they can trust it.

Meet users where they are, not where your systems expect them to be.

Citizens arrive with uncertainty, limited mental energy, and assumptions shaped by their worst experiences with government. Instead of forcing them into rigid processes, effective design acknowledges their uncertainty and guides them forward. This means:

• Simplifying language

• Limiting options to what's relevant

• Sequencing information based on user need (not organizational convenience)

• Never asking for the same information twice

A federal recruitment case study demonstrated this by intelligently architecting content—showing the right information to the right person at the right moment—they achieved 93% leaner content while maintaining mission impact.

Human-centered design adapts to users by creating journeys that surface relevant content based on behavior and context, offering clear next steps without rigid constraints, remembering where users left off, and anticipating follow-up questions. Equally important is making the implicit explicit. Government assumes user knowledge that citizens often lack, so answer the questions they're silently asking: Why are you asking for this? How will you use it? Why does it matter? Citizens want to understand the "why" behind every ask.

Now imagine that same single mom again. Instead of generic welcome screens and scattered eligibility criteria, she lands on a page that acknowledges her reality: "We help working parents find affordable, reliable after-school care. Let's find the right fit."

Questions about income and documentation appear only when relevant, in plain language, with explanations of why they matter. She never has to re-enter information because the system remembers where she left off. By the time she's ready to apply, she's confident. The experience met her exactly where she was and guided her forward.

Personalization that feels intuitive

Citizens expect personalization but fear surveillance. The difference lies in transparency: "Based on your role as an educator, here are relevant resources" feels intuitive, while invisible tracking feels invasive. Personalization succeeds when users understand the logic behind it.

Several principles guide ethical personalization:

1. Be transparent about what data you're collecting and why ("We'll remember your preferences for next time").

2. Personalize moments that matter (initial entry points, recommendations, timely reminders) rather than everything.

3. Give users control through opt-in choices and preference management.

4. Use data to reduce friction, not create it. Good personalization surfaces the most relevant options first while keeping others accessible; bad personalization hides choices based on predicted need.

A federal recruitment agency demonstrated this in action: By using transparent, relevant, user-controlled personalization, 1 in 4 searches now rank in the top 3 positions. They surfaced real-time content recommendations based on behavior, adapted journeys by applicant type, proactively suggested next steps, and tailored follow-up content to interests. Users accepted the personalization because they understood it, controlled it, and benefited from it.

Critical moments, better outcomes

Not all interactions are equally important. Some moments have disproportionate impact on citizen trust and action. That single mom sitting at her kitchen table with limited time before work, exploring after-school program enrollment, was a moment that matters. It's a moment of intent and decision. Government organizations that design for these moments transform outcomes.

1. Moment of intent. When citizens decide to engage, acknowledge their need and position your service as a guide. Instead of "Welcome to our system," try "We help working parents find affordable, reliable after-school care. Let's find the right fit."

2. Moment of clarity. When citizens understand what they need to accomplish, make the path crystal clear. Show the recommended path based on their stated need, with other options available, but not all options at once.

3. Moment of friction. When citizens encounter a problem, provide immediate, context-sensitive help. Instead of a generic error, offer: "This field requires a date in MM/DD/YYYY format. Example: 03/15/2025."

4. Moment of decision. When citizens decide whether to proceed or abandon, reduce uncertainty through transparency. Use progress indicators ("Step 1 of 3, takes about 5 minutes"), save options, and offer reassurance ("Your information is secure").

5. Moment of completion. Confirm success and set expectations for next steps. "Your application was submitted. You'll hear from us by March 30. Watch for an email confirmation."

The most powerful pattern is anticipatory, not reactive. Prevent problems before citizens hit them through real-time eligibility checks, proactive error prevention, predictive next steps, and preemptive follow-up. This transforms the experience from "navigating obstacles" to "being guided."

Putting it all together

Government organizations often ask, "Isn't this just a nice-to-have?" But the real question is, "Can you afford not to?"

Fragmented experiences have measurable costs: citizens abandon applications for services they qualify for, staff waste days on manual workarounds, support calls spike as confused citizens reach out, and trust erodes with each frustrating interaction.

The federal recruitment case study demonstrates the alternative: 93% leaner content, teams empowered to publish daily instead of waiting months, 2 years faster to federal clearance, 1 in 4 searches now hitting top 3 positions, search discoverability that increased organic reach by 376%, and zero production failures. These are transformational improvements.

They require a fundamental mindset shift, from "What do our systems require?" to "What do citizens need?" From "Speed or compliance, choose one" to "Speed and compliance, built together." From "Design is aesthetics" to "Design is outcomes."

That single mom deserves an experience that understands her constraints, anticipates her questions, and guides her forward with clarity and trust. She deserves to feel like the government is working with her.

This is about the mission, about whether government can meet citizens where they are and deliver genuine help.

The methodology is clear, and the tools exist. The case studies prove it works.

What's missing is the commitment to put citizens at the center of design. When you do, everything changes.

• Experience Design
• Digital Personalization at Scale
• Personalization
• experience design consulting