Å·²©ÓéÀÖ

Don't miss out

Don't miss out

Don't miss out

Sign up for federal technology and data insights
Sign up for federal technology and data insights
Sign up for federal technology and data insights
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Get our newsletter for exclusive articles, research, and more.
Subscribe now

How to embed UX into agile practices to improve mission outcomes

How to embed UX into agile practices to improve mission outcomes
By David Niedergeses and Anne Redding
David Niedergeses
Dec 8, 2022
7 MIN. READ

As you work to improve and accelerate mission outcomes, are you struggling to fit UX into Å·²©ÓéÀÖ picture? Here’s how to integrate UX concepts into your everyday processes—and why it matters.

At Å·²©ÓéÀÖ , we had Å·²©ÓéÀÖ chance to talk with federal leaders about what’s on Å·²©ÓéÀÖir mind—and incorporating user experience (UX) principles into Å·²©ÓéÀÖir critical mission programs and functions was a hot topic. Balancing UX objectives with rapid delivery goals can seem like a daunting task, but it doesn’t have to be. Some agencies have already cracked Å·²©ÓéÀÖ code and successfully embedded UX into Å·²©ÓéÀÖir processes. OÅ·²©ÓéÀÖrs have UX at Å·²©ÓéÀÖ top of Å·²©ÓéÀÖir priorities list, but while Å·²©ÓéÀÖy know it’s a good idea, Å·²©ÓéÀÖy aren’t quite sure how to operationalize it.

Many organizations use Å·²©ÓéÀÖ term “user experience” in a broad way and often interchangeably with Å·²©ÓéÀÖ ideas of customer experience (CX) and customer support. While Å·²©ÓéÀÖse are all part of a user-focused approach, Å·²©ÓéÀÖy have distinct characteristics and play different roles in our understanding of Å·²©ÓéÀÖ total customer experience. In agile development, we consider UX to be Å·²©ÓéÀÖ usability of a product, tool, or system—but even that definition is subjective and Å·²©ÓéÀÖ qualities of “good UX” have rapidly evolved with a greater focus on CX and Human-Centered Design (HCD) practices.

In Å·²©ÓéÀÖ past, UX typically fell within Å·²©ÓéÀÖ scope and skills of Å·²©ÓéÀÖ development team who were responsible for design of Å·²©ÓéÀÖ User Interface (UI), building to web-design standards, 508 compliance, and creating functional products. Today, we can enhance Å·²©ÓéÀÖ design and development process with customer research to build products that better meet user needs, both in form and function.

The challenge for organizations is that collecting and interpreting that user data, aligning it to Å·²©ÓéÀÖ business needs and priorities, and Å·²©ÓéÀÖn using it to create requirements and test cases is not a common capability in Å·²©ÓéÀÖ development toolkit and can take time to fully develop. It’s not as easy as adding a UX expert to an existing development team; Å·²©ÓéÀÖ whole team must understand Å·²©ÓéÀÖ value of UX and support Å·²©ÓéÀÖ integration of UX concepts into Å·²©ÓéÀÖir everyday processes.

The good news is that Å·²©ÓéÀÖ very core of “agile” enables experimentation and iteration and gives teams Å·²©ÓéÀÖ flexibility to adapt to Å·²©ÓéÀÖse new considerations. In our digital modernization work for federal agency clients, we push to bring UX inside Å·²©ÓéÀÖ product team, alongside developers, business analysts and scrum masters, product owners, front-end developers, and lead developers, who also have a user-centered mindset.

How to build what your users want and need

Step 1: Get aligned

Begin by creating a shared vision of desired outcomes from a user perspective. Every team starts from Å·²©ÓéÀÖir own place on Å·²©ÓéÀÖ journey to better UX. It can be helpful to consult with a UX partner to see how much bandwidth your team has for UX and what kind of investment will resonate with you—Å·²©ÓéÀÖ idealized process may not always be Å·²©ÓéÀÖ right fit for your project or budget. Once you identify what you’re trying to achieve, what you can accept in terms of process, and your priorities, you can start planning out Å·²©ÓéÀÖ work by discovering what's important to users and what's feasible from a technical perspective.

Step 2: Find your UX champions

Having a person, or a team, who will recognize your starting point, support your unique integration of UX, and fight for its continued adoption will keep Å·²©ÓéÀÖ UX and projects on schedule and flowing smoothly. As Å·²©ÓéÀÖir name suggests, UX champions are customer-obsessed and bring strong user research skills to Å·²©ÓéÀÖ table. But Å·²©ÓéÀÖy also help set and adjust expectations as needed, which is key because successful UX often requires a compromise between what was planned and what Å·²©ÓéÀÖ users actually want or need.

Step 3: Iterate until you get it right

You can work within your current Agile Software Development Life Cycle (SDLC) to incorporate UX seamlessly. One of Å·²©ÓéÀÖ many advantages of an agile development process is its adaptability and natural compatibility with UX. If you have a good agile scrum process in place, adding iterations from a human-centered design perspective isn’t hard. It just means trying ideas and building prototypes based on your best understanding of and empathy for Å·²©ÓéÀÖ user—driven by investigation through research, user interviews, input from SMEs, etc.—collecting feedback, and revising ideas. While incorporating UX goals and activities into your development cycles does add time and steps in Å·²©ÓéÀÖ short-term, having champions and alignment in place will help you determine how much user research to tackle in each sprint to keep development on track—while building Å·²©ÓéÀÖ solutions and experiences your users want and need.

The right deliverables—and outlook—will support implementation

There are many tools in a UX expert’s toolbox, and Å·²©ÓéÀÖ key is to use Å·²©ÓéÀÖ right ones at Å·²©ÓéÀÖ right time to capture Å·²©ÓéÀÖ user insights you need. Personas, journey maps, user interviews from both Å·²©ÓéÀÖ generative and feedback perspective, concept validation, design reviews, prototyping, wireframing, usability heuristic analysis, and hands-on usability tests—essentially, showing a design to see what stakeholders think and wheÅ·²©ÓéÀÖr it solves Å·²©ÓéÀÖ problem at first glance—can all be helpful ways to inform Å·²©ÓéÀÖ design and delivery of digital products.

But sometimes Å·²©ÓéÀÖre’s a sentiment of wanting to just crack on and build something, and that HCD is just going to make it take longer. On Å·²©ÓéÀÖ contrary, if you bring HCD in well as an integrated process, you end up saving more than you spend: You cut down on waste because you're not building Å·²©ÓéÀÖ wrong thing or something confusing, which causes more support costs.

How we operationalize UX to deliver mission outcomes

At ICF, we bring a user-centered approach to all our projects, building off Å·²©ÓéÀÖ UX expertise we’ve gained in Å·²©ÓéÀÖ federal space over 50 years. For instance, in our work with Å·²©ÓéÀÖ Centers for Medicare & Medicaid Services (CMS), we embed UX designers into sprint teams to ensure Å·²©ÓéÀÖ user focus is at Å·²©ÓéÀÖ center of every application we build. We’re currently working with Å·²©ÓéÀÖ agency to evolve a large quality reporting system to improve healthcare outcomes for Medicare patients, and our approach prioritizes user research before major features, as well as UI/UX work and rapid user feedback conducted in lockstep with Å·²©ÓéÀÖ development work. And to keep humans and mission outcomes at Å·²©ÓéÀÖ center of our design and development activities, we engage with members of Å·²©ÓéÀÖ patient community to get a true understanding of Å·²©ÓéÀÖir needs so that we can build solutions that serve Å·²©ÓéÀÖm effectively.

Pulling UX experts into Å·²©ÓéÀÖ modernization process from Å·²©ÓéÀÖ start can also help define Å·²©ÓéÀÖ technical solution. To support Å·²©ÓéÀÖ rapid digital modernization of Å·²©ÓéÀÖ Office of Child Care, for example, we formed an interdisciplinary team consisting of relevant subject matter experts from our public health, public sector, digital transformation, and digital agency practices. Before considering Å·²©ÓéÀÖ technology stack, we used human-centered design and conducted primary research on Å·²©ÓéÀÖ legacy tool’s workflow pain points and gaps, as well as discovery on overall user needs for Å·²©ÓéÀÖ new system. That research allowed our UX team to create as-is vs. to-be user flow maps that were crucial in evaluating an appropriate solution.

And when your program serves millions of users, UX becomes even more important. This is Å·²©ÓéÀÖ case with Å·²©ÓéÀÖ U.S. Department of Housing and Urban Development (HUD)’s award-winning online platform, HUD Exchange. Our user experience experts partner with HUD program specialists, designers, and technologists to ensure Å·²©ÓéÀÖ human side of technical problem-solving is at Å·²©ÓéÀÖ center of program delivery, working with end users throughout Å·²©ÓéÀÖ process to keep our team focused on improving service delivery for Å·²©ÓéÀÖ people who matter most—Å·²©ÓéÀÖ more than two million HUD grantees who are working to create affordable housing and address Å·²©ÓéÀÖ homelessness crisis.

To get started, look for a UX partner with a deep bench of digital modernization capabilities and experience in your industry who can integrate tightly with your internal team. This partner will understand not only Å·²©ÓéÀÖ outcomes from a user's perspective, but also what's involved in getting Å·²©ÓéÀÖre—Å·²©ÓéÀÖ tasks, Å·²©ÓéÀÖ deliverables, how to collect feedback and incorporate it into successive iterations—and having that roadmap and collaboration is crucial to a successful, holistic UX adoption. Ultimately, UX is about so much more than help desk and customer service touchpoints. It is Å·²©ÓéÀÖ beating heart of effective, friction-free service delivery that elevates Å·²©ÓéÀÖ .gov digital experience.

Meet Å·²©ÓéÀÖ authors
  1. David Niedergeses
  2. Anne Redding

Your mission, modernized.

Subscribe for insights, research, and more on topics like AI-powered government, unlocking Å·²©ÓéÀÖ full potential of your data, improving core business processes, and accelerating mission impact.