Blog

Blog

When it comes to conducting user research, presenting UX work, or collaborating with other team members or stakeholders, we know that face-to-face interaction can have a lot of advantages: It’s easier for participants to build trust and rapport in person than remotely, and attendees are likely to pay attention and be cooperative for longer.

However, we can’t always conduct UX activities face to face. Sometimes, budget or time limitations, travel restrictions, or other unforeseen circumstances make in-person sessions impossible, unaffordable, or even unsafe. In these cases, remote sessions can offer immense value in maintaining the flow of insights and ideas.  

Additionally, remote UX sessions offer many benefits that in-person sessions do not, regardless of the circumstances:

  • Flexibility in project funds: Remote sessions lower travel expenses. This reduction might free up monetary resources for other valuable activities, such as recruiting additional research participants, doing extra rounds of research, or providing deeper analysis.
  • Increased inclusiveness: Location and space are no longer limitations with remote sessions. For user research, this means access to a more diverse group of participants to whom you might not have access locally. For UX workshops and presentations, it means nonlocal colleagues can easily attend and more people in general can participate. (However, it doesn’t mean that everyone should attend. Continue to limit attendance to relevant roles.)
  • Attendee convenience: Participants might be more willing and able to attend remote sessions that don’t require them to leave their office or home. They’ll save the commute time (whether that’s a couple of hours driving to a research facility or a few days traveling to a workshop in another city), and they can participate from the comfort of their own space. Especially with remote, unmoderated research or remote, asynchronous ideation, participants can complete tasks on their own schedule.

Given these advantages, remote UX work can be a useful solution to many project challenges. This article provides guidelines and resources for transitioning 3 types of common UX activities to the digital sphere:

  1. Conducting user research
  2. Facilitating and presenting
  3. Collaborating and brainstorming

Remote User Research

Generally, we recommend in-person usability testing and user interviews whenever possible. It’s simply easier to catch and read participant body language and recognize which breaks in dialogue are appropriate times to probe or ask followup questions. However, remote testing is preferable to no testing at all, and remote user research can accelerate insights on tight timelines and budgets.

Tips for Remote User Research

  • Practice using the technology: Even if you are familiar with the tool you’ll be using, do a practice run with a colleague or friend. Particularly for remote, unmoderated sessions, make sure instructions for signing in and completing tasks are clear. Plan initial pilot testing with a few users so you can adjust technology and other factors as needed, before launching the study.
  • Recruit additional users: With remote, unmoderated research, you can’t help if a handful of remote interviews or usability tests are rendered useless due to unsolvable surprise technology issues on the user’s end, such as firewalls. Recruit more users than you think you need in order to create a proactive safety net.
  • Plan for technology challenges: Technology mishaps will occur. Assume technology challenges will happen, and don’t panic when they do. Have a backup plan ready, such as a phone dial-in in addition to a web link for user interviews and, whenever possible, use a platform that doesn’t require participants to download anything to join the session.
  • Provide instructions: If the technology tool is complex or users will be setting it up and using it over an extended time, create documentation specific to the features you’ll ask them to use. For example, for our digital diary studies using shared Evernote notebooks, we provide detailed documentation for participants on how to set up and use the platform.
  • Adjust consent forms: If you’ll be recording the participant’s face, voice, or screen while conducting a remote session, update your consent form to ask for explicit permission for each of these items. If you plan on asking additional researchers to join the session or if you’ll share recordings among the team during postsession analysis, outline and ask for consent on these items, as well.

Tools for Remote User Research

Consider tools that match the needs of your study, and, as always, match appropriate research methods to your study goals. Remote research is certainly better than no research at all; however, invalid insights are not helpful in any situation.

  • Remote, unmoderated sessions: Tools such as Lookback, dscout, and Userbrain help capture qualitative insights from video recordings and think-aloud narration from users. Tools such as Koncept App and Maze capture quantitative metrics such as time spent and success rate. Many platforms have both qualitative and quantitative capabilities, such as UserZoom and UserTesting. (Be sure to check whether these tools work well with mobile applications, as needed.)
  • Remote, moderated sessions: Any video conferencing platform that has screensharing, call recording and the ability to schedule meetings in advance is likely to meet the needs of most teams. Zoom, GoToMeeting, and Google Hangouts Meet are frequently used. (Remember to consider platforms that do not require participants to download anything to join the meeting.)


Source: NN/g

Journey maps are an artifact depicting the customer’s perspective of their experience engaging with an organization. Customer journey maps can act as a roadmap to identify opportunities and address both known and previously unknown customer pain points. Unfortunately, after the initial learning, journey maps often end up posted on a wall or filed away after achieving a checkmark for completing a required artifact.

What if journey maps evolve beyond a static snapshot of a customer’s experience?

What if a journey map is measurable, dynamic, and provides insight into customer experience over time?


Join us at the next HCD Community of Practice program as Noble Ackerson with iQIES shares recent work: Quantifying Behavior Along the Customer Journey.

The program will include:

  • Shared Definitions
  • Lean Analytics for Enterprise Health Products
  • iQIES Key Takeaways

Register today to join the discussion and to collaborate with a community of professionals. Attend via WebEx.

Remote UX Work

A remote working structure can present difficulties for any team, in any field. For those in the UX field, it can be especially challenging. As we have recently transitioned (although temporary) to a complete remote working environment, we'd like to take some pointers from a company with a successful 100% remote structure, NN/g. Here are some specific challenges and recommendations which they've provided.

Challenges of Remote UX Work

Working remotely is a challenge for any team, but it can be especially difficult in the field of UX. NN/g has provided some specific challenges and recommendations, based on their successful 100%-remote structure.

Ideation and Collaboration

UX design often requires collaboration to generate ideas. In-person ideation workshops are much easier than the remote equivalent. When ideation participants are in the same room together, they have a shared context — it’s easy to see what they’re sketching on a sheet of paper and what sticky notes they’re posting on the walls. Also, when people can see each other face to face, the flow of information and emotion is easier to assess. If you’ve ever been on a conference call and rolled your eyes at a coworker, or awkwardly started talking at the same time as someone else, you’ll know the difference.

In a previous role at a different company, we had chronic problems with ineffective remote meetings — often, one or two people would dominate the conversation, while the rest would lurk without contributing.

A simple fix can avoid some of those issues: share webcam video as well as audio as much as possible. Just by being able to see the other people in the meeting, you’ll:

  • Encourage empathy and bonding
  • Be able to see when someone is about to speak
  • Assess body language and expressions to better perceive your coworkers’ emotions

You’ll likely get more engagement from participants if they’re on video as well: it’s obvious when someone has mentally checked out of the meeting or is busy sending unrelated emails.

At NN/g we often use multiple tools to achieve a smooth remote ideation workshop. For example, we might share webcam feeds and audio using Zoom or GoToMeeting, while we share ideas visually using a collaborative product like Google Docs, Miro, or Mural.

This screenshot shows the results of a remote affinity-diagramming exercise. In a video-conferencing meeting we used Miro, a whiteboard application, to cluster the findings from our Life Online research project and generate ideas for future articles and projects.


We tailor the tools to fit the needs of a particular meeting. For example, creating a journey map remotely may require different digital products than an ideation workshop.

Other remote teams have found success by using document cameras: each person in the meeting shares her video and audio streams, as well as her document camera that captures what she’s writing or drawing.

Team Building

When you don’t see your coworkers every day, it’s easy to slip into feeling disconnected from them.

We’ve found that having a company Slack workspace alleviates this feeling. In addition to having project- and topic-specific channels, we also have:

  • #nng-pets: For sharing photos of our animal office mates
  • #the-office-today: For sharing photos of where you happen to be working that day (a coffee shop, out on your deck, by a pool, etc.)
  • #feedback: For requesting quick input on anything you’re currently working on (an idea, a graphic, or an excerpt of writing)


Source: NN/g

Content Audit

What is a Content Audit?

The word “audit” can strike fear into the most stoic of hearts. A Content Audit, however, is nothing to be feared. It is simply the process of taking an inventory of the content on your website. It is a large, detailed list of the information on your website and most often is in the form of a spreadsheet. This list will be the basis for the re-organization of your site.

There are three types of audits: Full, Partial and Sample. A Full audit is just as it sounds; a complete accounting of every page, file and media. A Partial audit’s parameters are less specific. However it will include every section of your site as well as a subset, which can be the top few levels of a hierarchical site or the last few months of articles written. A Sample audit is a compilation of example content.

Why Conduct a Content Audit?

We’ve all gone through our closets at some point in our lives to determine what we have, what we need, what we should keep and what we should throw away. We essentially performed an “audit” of our wardrobe and walked away with a newly reorganized closet, a feeling of accomplishment and a great excuse to go shopping. Auditing the content of the closet known as your website will provide you with a similar result for you and your users.

It allows you to know exactly what information you have on your site, what information you need on your site, what pages you need to keep and what pages are duplicative and can be “thrown away”. In addition it provides you with the information to address potential user pain points as well as opportunities for added value to your user. When you have completed your audit, you will now possess the information platform to create a newly streamlined and re-organized information architecture for your site, a better understanding of your content and great reason to get innovative in the solutions you provide your users.

How to Conduct a Content Audit?

There are different ways that you can audit the content of your website and there are different pieces of data that you can include.

The main recommended categories are:

  • Navigation Title (main link to the content)
  • Page Name
  • URL (web address)
  • Comments (any notes you’d like to remember)
  • Content Hierarchy (how the content relates to each other).

Other suggested categories are:

  • Content Type (page, blog post, media, attachment, article, etc.)
  • Entry Points (how the user gets to that information)
  • Last Date Updated
  • Secure/Open (is the page open to all or secure?)

 In order to conduct a successful Content Audit , use the following steps:

  1. Start with a blank spreadsheet. List your categories in the first row and your main pages or section in the first column
  2. Choose one page and list the information according to the categories
  3. If there are sub-pages, create a separate row for each under the main page/section and gather the same information for those as well
  4. Repeat these steps until every page is listed.
  5. Using this spreadsheet, analyze to determine where the opportunities and pain points are.

Key Tip #3 for UX success from Agile Practitioners

Soft skills can hold the keys to success in Agile projects. The respondents identified healthy collaboration as a main factor in success. This finding is not surprising; after all, in the Agile Manifesto, individuals and interactions are valued over processes and tools. Good communication is essential in any software-development organization, whatever its process methodology. However, collaboration is even more important in Agile settings, where delivery times are short and time-boxed.

Some organizations chose design-thinking techniques such as ideation and brainstorming to encourage discussion and tear down silos that often block effective communication and teamwork.


“Collaboration has been critical.”

“Close collaboration with other roles in the team has [helped us] arrive at agreements sooner in the process.”

“Constant ongoing collaboration with all team members. We use sketching and whiteboard sessions; journey-experience maps help capture the omnichannel experience.”

“Share info together in cross-functional teams. Communicate more with developer and designers.”

“No putdowns and no dismissal of ideas in early stages.”

“Involve everyone on the team and welcome everyone's suggestions and ideas.”

“Keep the relationship between the business analyst, designer, and engineer close.”

“Meet regularly once a week to update and know the progress. Focus on things to help one another accomplish the work.”

“Daily standups, iteration demos, biweekly pulse meetings, and interaction with management.”


In modern software-development environments, UX is heavily involved in defining how online products and services are developed. As such, the role of UX has expanded to include communication. UX can be the catalyst for good collaboration by involving team members in activities such as usability testing, and field studies, but also group design ideation and brainstorming.

Source: NN/g

Quality Metrics

What are Quality Metrics?

Quality Metrics are the measurement by which you can determine if you are meeting your goal of providing your users with useful and pleasant experience. These metrics demonstrate what your values and priorities are and ideally on what is essential to your user.

Why Use Quality Metrics?

In your effort to provide excellent user experience, you will implement changes to your product or service. The only way to determine if these changes are effective is by measuring the results. Quality metrics provide you with the platform to measure the results of your previous process with your improved process. After which you can determine if the changes moved you closer to your goal and what further improvements are necessary. Ultimately Pearson's Law applies: "That which is measured improves. That which is measured and reported improves exponentially."

How to Create Quality Metrics

Quality Metrics are established during the planning phase. Before you can improve a process, you have to outline what is “improvement.” This outline will serve as the basis from which you create your metrics. You can use your Feedback Loop to collect and analyze the information based on your metrics. It is vital that you establish metrics based on the following guidelines:

  • Your metrics should be quantifiable: You are looking for results such as “85% of clients are satisfied” rather than “most clients are satisfied.”
  • Your metrics should be actionable: Be sure to create actionable metrics, such as customer satisfaction or ease of use.
  • Your metrics should be trackable over time: Construct your metrics in such a way that you can determine if the quality is improving.
  • Your metrics should be maintained and updated regularly: Be sure to test your metrics consistently and to adjust them as your product or service changes.
  • Your metrics are tied to your goals: Make sure your metrics focus on what is essential to your user and will drive the success of your product or service.


Service design is the process of understanding and refining an organization’s people, processes, systems, and policies to improve both the employee experience and, directly and indirectly, the customer’s experience.

The Human-Centered Design (HCD) Center of Excellence (CoE) teaches a simple approach to service design that results in 3 outputs:

  1. Persona – Identify, define, and prioritize the customer types impacted by ISG’s products, services, and policies;
  2. Journey Map (customer viewpoint) – Research, document, and validate the persona’s experience (journey) with the organization over time and touchpoints; and
  3. Service Blueprint (business viewpoint) – Document how the organization currently supports the customer journeys and use these artifacts to identify opportunities to improve the customer experience by creating new or improving upon existing products, services, and policies.

Personas: What and why

Today we focus on personas, artifacts that are a fictitious, specific, and concrete representations of a target customer group for a product, experience, or policy. Personas provide an actionable narrative that leverages both qualitative and qualitative research. First and foremost, a well-crafted persona allows the business to gain greater empathy for the customers who will benefit from the initiative.

Personas are artifacts created early in a project when teams are gaining a better understanding of the problem they are looking to solve and the people (customers) who are impacted by a new or improved product or service. The recommendation is that employees spend 2 hours every six weeks observing their customers as they use their products and services; this cannot always happen. HCD, as a philosophy, argues that understanding informs solutions, but many times businesses rush to a solution and make risky assumptions in a one-size-fits-all approach.

Rather than making business decisions based only on what is viable or feasible to the organization, a well-crafted persona allows organizations to inform their decisions based on what is desirable to their customers. For personas to be useful artifacts, please do not treat them as an unchangeable fact. Instead, personas tell the story of a customer type based on what the organization knows now, which could be subject to change the more they learn about and involve their customers in the process. Further, useful personas should not be customer stories or pretty pictures that collect dust on a shelf somewhere. Smart teams may create trading cards or full-size cardboard cutouts, whatever it takes to channel the customer perspective across levels within an organization making business decisions that impact these key stakeholders.

Learn more

In part 2, we will define and discuss the value of journey maps. HCQIS is committed to helping our team members learn more about HCD to help us better support customers. Here are three ways you can learn more today:



A head shot of Rob Fay

ROB FAY
Rob currently leads the CCSQ Human-Centered Design Center of Excellence (HCD CoE). The HCD CoE is an organization that impacts the way the CCSQ delivers policy, products and services to its customers. Through the provision of education, support and resources, he promotes the continued implementation and usage of HCD best practices and seeks to fulfill the charge of OMB Circular A-11 Section 280 (i.e., “Managing Customer Experience and Service Delivery”). For over 20 years Rob has focused on making products and services delightful and easy to use by leading research and design initiatives at government agencies like CMS, NIH, and USPTO and commercial organizations including Blackboard and Allegis Group. Rob holds a Master of Information Management and a Master of Science in Marriage & Family Therapy from the University of Maryland, College Park.



Measuring and improving the user experience of your product or service requires a plan and an understanding of who your users are. Whether your goal is to introduce guidance and processes for measuring user experience, or trying to scale UX in your organization, a well-devised plan will improve your chances of success. In addition, it can play a critical role in convincing stakeholders to invest in UX and make it an essential part of your product development process.

Key Areas to Consider When Creating a User Experience Measurement Plan

  • Create a Communication Process
  • UX Key Performance Indicators (KPIs)
  • Benchmarking Results
  • Continuous Improvement
  • UX Measurement Plan Summary


More Information on the Key Areas of Consideration ➟

Tip #2. Conduct UX activities ahead of the sprint.

Many people reported challenges in trying to fit both design and development for the same feature into a single sprint. Two weeks is usually not enough time to conduct research, create wireframes and designs, AND do the development work for the selected user stories.

The most common advice for overcoming this challenge was to stagger the UX/UI and the development work stream so that research and design are completed before the sprint begins. For example, UX creates the screens in sprint 1. Then development takes the completed designs and codes them in sprint 2.

“I worked one sprint ahead as a UX/UI lead. I would work with the scrum master and product owners to prioritize projects in the backlog and fulfill the UX/UI requirements a sprint before production. My time had to count differently toward the sprint, omitted from velocity, but very efficient.”

“Research and design should stay at least one sprint ahead. Give yourself time to do thorough user research and test your designs.”

“Make sure to design as much upfront so you can prototype and test concepts before development needs to start.”

“Spend investigative time during sprints in anticipation of needs for the upcoming sprints.”

“Have mockups ready for sprint planning.”

Working ahead of the development stream gives designers time to think through and test assumptions with real users. Staying ahead allows the entire team to review mockups and identify potential issues before the design of that feature is ready for the sprint.

The size and complexity of the project affects how far ahead of development UX designers should work. Most practitioners report designing ahead by 1 to 2 sprints.

This is a coordinated effort that requires communication among team members. Just because designs are completed (or mostly done) before the development sprint does not mean that the UX designer simply hands off the designs to the developers and moves on. While UX designers should constantly plan ahead, they must also support the current sprint, advise the team, and make adjustments as necessary.

Moreover, all team members, including project managers, product owners, and engineers, should work closely with the UX designer throughout the process so that when the design is “ready,” everyone is in sync. The back- and front-end developers need to understand and support the designs, interactions, and user flows.


In 2016, NN/g asked Agile practitioners at the UX Conference to share tips or techniques that have contributed to the success of their Agile projects. They received 125 responses from professionals in USA and Singapore. The respondents worked in various-size companies and held different job responsibilities, ranging from UX designers and developers to product owners and project managers. From this, these Top 10 Key Tips for Successful Agile Projects were developed. Here is the first of the most popular techniques reported by Agile professionals:

Tip #1. Allow time for release planning and story mapping.

Respondents reported that spending time at the start of projects to properly plan for releases is worth the investment:

“Place more effort in planning, design, and specification.”

“Be involved at the earliest stage.”

“Spend more time in the planning phase and then focus on refinements and tweaks. Get buy-in before starting the project.”

“Block out business time early, get sign off on everything.”

“Do proper and extensive planning in the beginning of the sprint. Allow sufficient time to deal with inevitable blockers.”

Collaborating with stakeholders from the beginning allows teams to develop a shared understanding and a common vision for their projects. This shared vision guides team members throughout the project, helping them prioritize user stories and make the right trade-offs along the way.

Some teams employ story mapping during release planning to help stakeholders collaborate with other team members in creating the product backlog. This activity often uncovers new opportunities and helps teams group and prioritize user stories.

UX involvement in release planning keeps the focus on the broader context, identifies knowledge gaps that require future research, and gathers information (e.g., by running appropriate user studies) to inform team decisions before the project begins. When teams allocate time for discovery work and research at the beginning, they reduce wasted effort later on.

“Include the discovery process before Agile kicks off for chartering, persona development, and story mapping.”


Source: NN/g

DHS (Department of Homeland Security) Usability Testing Kit — So Easy, Anyone Can Do It DHSUsability-2 (2).png Reading Time 2 mins Usability testing is a way to learn how easy or difficult it is for people to use something by observing them actually using it.  In this highly accessible session, you’ll learn how to use the kit’s guidelines and templates to test the usability of your services and solutions.…
Human-Centered AI: 5 HCD Principles for Developing AI  human-centered_AI.png Reading Time 6 mins Introduction  In recent years, Artificial Intelligence (AI) has transcended the realms of science fiction to become an integral part of our daily lives. From recommending the next song on your playlist to predicting global financial markets, AI's capabilities are vast, varied, and truly transformative. As with any disruptive technology, the potential of AI is unparalleled,…
How Collaboration Improves U.S. Health Care interprofessional-collaboration-735x400-1.jpgReading Time 6 mins In the face of escalating healthcare costs and inconsistent quality, the call for increased competition in the United States healthcare system has been prominent. Proponents argue that competition could incentivize hospitals to deliver superior care at reduced costs. However,…
Working with the Public to Improve Digital Forms: A GSA Case Study GSA.pngReading Time: 2 min The American public spends approximately 11.5 billion hours per year filling out federal government forms. Form complexity can result in lack of submission or completion, and errors on forms can cause processing delays and affect whether the form is accepted — which can have far-reaching consequences. Join the CCSQ HCD Community of Practice on Thursday, September 28,…
How to Design the Best Meeting Ever affinity-diagram-landscape.pngReading Time 8 mins I have a confession to make: I'm not a big fan of meetings. Now don't get me wrong. I understand why we have meetings. Meetings can be used to provide new information. Meetings can be used to make new decisions. Meetings can be used to align expectations. Meetings can be used to "meet" new coworkers. Meetings can be long. Meetings can be short. Meetings can include many people.…
Six Methods for Sustained Collaboration 784784p888EDNmain906Landburg_img.jpgReading Time 8 mins Wondering about the real importance of collaboration in organizations? Just ask any leader, and you'll receive an enthusiastic confirmation. Yet, when it comes to the actual outcomes of their collaboration strategies, the answers might differ. A high-ranking executive from a major pharmaceutical company recently revealed, “We've tried various changes,…
Why all the Healthcare Supply Chain Shortages?  Rocky_Mount_Facility_post-July_2023_tornado_opt.png https://www.pfizer.com/news/press-release/press-release-detail/pfizer-announces-post-tornado-relief-plans-rocky-mount?cid=em_PfizerNewsroomAlert&ttype=emReading Time 6 mins  The COVID-19 pandemic exposed vulnerabilities in the US health system supply chains, leading to persistent and elevated supply shortages, economic uncertainty, and growing inflation. Between 2021 and 2022,…
Creative Sprinting
Creative Sprinting baton-600.pngReading Time 6 mins The dictionary definition of sprint is "to race or move at full speed, especially for a short distance, as in running, rowing, etc." Agile methodologies use this term frequently, but organizations such as Scaled Agile Inc. instead use the more generic term iteration https://scaledagileframework.com/iterations/ to refer to "a standard,…
What is an Empathy Map to a Persona?  screen-shot-2017-12-14-at-55525-pm.png Reading Time 4 mins When creating new services or products you can ensure you genuinely meet the end-user's needs with Personas, https://qnetconfluence.cms.gov/display/HCD/Personas but another informative method is Empathy Maps https://qnetconfluence.cms.gov/display/HCD/Empathy+Maps that can build into personas. Personas help you create detailed profiles of your target users,…
Personas, Customer Segmentation and Target Groups – How do they work together? Reading Time 6 minTarget-Audience-4.jpg This is a short and insightful article about what are the differences between Personas, Customer Segmentation and Target Groups, and how these three tasks work together.  Most of us know and use personas, a fictional representation or archetype of a specific user. It is created to help development teams understand and empathize with the needs, behaviors, motivations,…
User Personas Need to Evolve 1_vquNcmrSEK10scjbN7ncWQ.jpg Reading Time 6 Mins UX designers often create user personas that are aesthetically pleasing but contain irrelevant details, diminishing their usefulness for teams. Furthermore, these personas often lack important contextual information and user behaviors that highlight the challenges and frustrations faced by users. Without these critical details, personas become mere deliverables,…
Generating AI Personas – Competitive Analysis  2023-06-28 08_53_37-digital face - Google Search.png Reading Time 8 mins Personas https://qnetconfluence.cms.gov/display/HCD/Personas are an integral part of the HCD UX development process to understand the idiosyncrasies and emotional state of our consumers and users to help build empathy for their challenges and lifestyle while reinforcing the very reason UX exists as a discipline.…
Large health insurers and other companies are especially keen on doctors’ groups that care for patients in private Medicare plans.  609f963c02f45d00046b1be4.png https://www.cvshealth.com/news/company-news/cvs-health-reports-first-quarter-2023-results.htmlone-medical-630x394.png https://press.aboutamazon.…
IRS Banner with IRS Logo (1).pngContinuously Improve Your Website by Using Customer Feedback and Web Analytics: An IRS Case Study Read Time: 2 min All Americans experience challenges while filing tax returns and using the Internal Revenue Service (IRS) Free File platform is no exception.   Join the CCSQ HCD Community of Practice on Thursday, June 29, for Continuously Improve Your Website by Using Customer Feedback and Web Analytics: An IRS Case Study.…
2023 Government UX Summit
2023 Government UX Summit 2023-GOVT-UX-SUMMIT.png https://qnetconfluence.cms.gov/display/HCD/2023/06/09/2023+Government+UX+Summit Read Time: 1 min On June 14, 2023, Digital.gov http://Digital.gov will host the 2023 Government UX Summit https://digital.gov/event/2023/06/14/2023-government-ux-summit/ (10-4pm ET).…

Human Centered Design: A Non-Linear Process

Human Centered Design (HCD) is the process we use to understand the people for whom we are writing policies and creating programs and services. CCSQ has outlined a six-step process to help us better support customer journeys.

• Initiate – Create a shared understanding of the problem.
• Immerse – Empathize by talking to and observing customers.
• Synthesize – Combine existing data and new learning to identify themes, patterns, and discover insights.
• Ideate – Generate many ideas without considering constraints.
• Prototype – Test a subset of viable, feasible, and desirable ideas with customers to get feedback.
• Implement – Continue to iterate, refine, and enhance.

The goal is to gain a deep understanding of customer needs and goals throughout the process so the business can successfully create innovative solutions that solve the right problems.

A common myth about HCD is that we need to follow the six steps as prescribed. In fact, HCD is not a linear process. It is a framework, so there may be times when steps overlap, when steps are taken out of order, or when steps must be revisited in order to achieve successful results.

Getting started

In order to create a shared understanding of the problem among business stakeholders, it is critical to first validate the presenting problem with your customers. While the focus of the immerse phase is to gain empathy for the customer, this should happen throughout the process, even from the very beginning. Alternately, you may find yourself in the prototype phase and through testing an idea with customers, you generate a new level of empathy and understanding for your customer.

By familiarizing yourself with the six-steps and the methodologies, you will be prepared to engage in all six-steps regardless of the context or flow of work.

Learn more

HCQIS is committed to helping our team members learn more about HCD to help us better support customers. Here are three ways you can learn more today.
• Read more about HCD on the HCD Center of Excellence Confluence page.
• Join the HCD Community of Practice.
• Signup for an upcoming HCD Training Workshop.

World Usability Day is One Week Away!

World Usability Day is coming next week! Register below to join us in an open house style event on November 14th from 10 am - 1 pm. ISG is hosting this event to create an opportunity for the HCD community of practice and others with an interest in usability to come together and share knowledge; to showcase some of the work and learning across the CCSQ lines of business; and to highlight some of the human-centered design work that takes place throughout the agency. 

You don’t want to miss this event! 

.

The Program

Come hear lessons learned on applying human-centered design in government highlighting stories from the HHS Ignite Accelerator and the Indian Health Service Health IT Modernization project. 

Don't miss a talk on the past and current state of human-centered design at CMS. We'll also be featuring a panel discussion on future-proofing technology, mental models and services within Civic Tech. 

Our agenda features case studies, exhibits, a panel of UX experts from across the Health IT services community and several speakers including: 

Margeaux Akazawa

Internal Innovation Programs Director

Office of the Chief Technology Officer, HHS 

Adam Heller
Director, Division of Services and
Infrastructure Fulfillment (DSIF), ISG, CMS 

Kayenda Johnson
Human-Centered Design Specialist, CMS 

Maia Z. Laing
Senior Business Consultant
Office of the Chief Technology Officer, HHS 

Eric Smallwood
Human Centered Design Lead
HQR, Bellese Technologies

WHEN AND WHERE:

Thursday, November 14, 10 AM - 1 PM

Tantus Building - QCF
2270 Rolling Run Drive, Suite 100
Woodlawn, MD 21244

Join Us Upcoming for a World Usability Day Event!

The Human-Centered Design Community of Practice is relaunching on November 14th with a World Usability Day Event!

World Usability Day is a single worldwide day of events around the world that brings together communities of professional, industrial, educational, citizen and governmental groups for our common objective: to ensure that technology helps people live to their full potential and helps create a better world for all citizens everywhere.

The 14th annual World Usability Day event will be celebrated globally with programs and conferences being organized in over 40 countries around the world. This year’s theme is “Design for the Future We Want."

Why is ISG hosting a World Usability Day? 

As usability professionals, our work is moving us closer to a certain future. Whether the progress towards it is intentionally or unintentionally created, or whether that future is tomorrow, next month, or several years down the line – we are all heading towards endpoints of our own creation. This begs the question – What kind of future are we designing for? Our event will be an opportunity:

  • For the Human-Centered Design Community of Practice to come together and share knowledge,
  • To showcase some of the work and learning across the lines of business,
  • And to highlight some of the human-centered design work that takes place throughout the agency.

Save the Date!

Interested in becoming a part of this day? Email us at hcd@hcqis.org!


Human-Centered Design… Why Bother?

The bottom line at CMS is “Patients First”. This core concept innately reflects the central message of Human-Centered Design (HCD). After all, patients are human. We’ve already explored what HCD is. We’ve talked about how it can be accomplished, where it can be implemented and what methodology can be used. The question that remains is why. Why does HCD matter to you as a part of ISG or CCSQ? The simple answer is because… people matter.

People Matter

Now this answer might seem too simplistic, but let’s delve into it. One of the goals of CCSQ is to analyze the data provided by the HCQIS Systems and pay health care providers based on the quality of service they provide to patients. However, in order to receive feedback, people must provide it. People play a big role in the entire process because they provide this information on which you base your assessments. In addition, they provide this information through avenues you create. These avenues must be understandable, convenient, and easy to use.

If you create a form to fill out, but have not included customer feedback before releasing it, there is a greater likelihood that the customer will be confused with what the questions mean or even how to submit it. This confusion could result in either you never receiving the information or the responses not providing the answers you are looking for. The quality of the feedback received is based on how “User-friendly” or “Human-Centered” the avenues you created are.

Learn about HCD

Sign up to gain an understanding of the Human-Centered Design process through hands on training or browse the Microlearning videos section.

Return on Investment (ROI)

Developing a human-centered approach to garnering feedback will increase your return on investment (ROI). Research shows that every dollar invested in HCD generates $100 dollars in return. This is an ROI of 9,900 percent! Even without an immediate dollar correlation from CCSQ, you can measure the ROI in actionable information directly translated into dollars. Using a more user-friendly process will exponentially increase the amount of relevant and applicable information received. The more actionable the information, the less resources are spent on attempting to garner that information. As a result, you save costs and are able to focus more on what matters most: helping people.

Continuous Improvement

On a conceptual level, even the CCSQ approach to continuous improvement is analogous to an HCD concept known as a feedback loop. The HCD Feedback loop consists of three steps which function in a continuous cycle to improve the user experience: Ask, Analyze, and Apply. Although these steps are specific to the HCD process, the concepts can also be applied to the CCSQ Continuous Improvement process as well. It’s visible in the diagrams below, just how similar the two concepts are and how integral the HCD mindset is to CMS culture.

Step

The CCSQ Continuous Improvement Process

The HCD Feedback Loop

 

Ask

Ask For Feedback:  Patient provides feedback on Provider Services to CCSQ

Ask:  Ask for feedback and observe the user experience.

Analyze

Analyze Data:  Feedback is Analyzed by CCSQ

Analyze: Analyze the feedback you’ve received.

Apply

Apply Analysis:  Payment is issued to Provider based on the feedback. Provider improves quality of service based on feedback-based payment

Apply: Apply the knowledge you’ve gained.

START AGAIN!  Continuous Improvement means creating customer feedback loops throughout the process so that solutions are improved without assumptions. 

Getting Started

With HCD aligning so intricately with the fabric of CMS, it’s an easy jump into the HCD paradigm of thinking and methods. For assistance in further understanding the HCD mindset as well as applying its methods and leveraging its results, the HCD Center of Excellence (CoE) offers: regular trainings, a Community of Practice, as well as Confluence resources including micro-learning videos, method cards, and other sources of information. To view this cornucopia of information regarding HCD, please visit the Confluence Space : https://qnetconfluence.cms.gov/display/HCD

This is an “open” space which is accessible to anyone on the CMS or HCQIS network. It is not required that you have HCQIS Atlassian credentials or that you log into Confluence. You can also contact the HCD CoE team at HCD@hcqis.org, if you have any questions or comments, or need support.


Why Human-Centered Design?

Many times through sheer habit or lack of options, we continue to do things in the same manner we’ve always done. When we adopt that notion, knowingly or unknowingly, we often ignore the possibility of a more effective method.

What Is Wrong With This Picture?

In the image of the tea set, you may not even realize initially that you will have a very difficult time drinking from that cup. If you’ve had this set in your house for years, you might never recognize the need for a better design. Only when presented with a tea set with a round cup, would you realize you could actually drink from a cup without uncomfortable maneuvering or ruining your clothes.


What is the Solution?

Human-Centered Design (HCD) is both the philosophy and process that leads to the development of that new tea set.  It is a purposeful process which focuses on the customer’s needs, characteristics, and goals. HCD, through clear messaging, user participation, and customer-based solutioning, helps to make the product, service, or website understandable, beneficial, and relevant to the customer experience.

This is the reason for the creation of the HCD Center of Excellence (CoE). The HCD CoE provides you with the tools to invite your customer to the table, make your message clear to the customer, and develop a solution that best meets their needs.

Invite Your User:

Planning a wedding without the input of the bride is an idea that is unfathomable. Along the same lines designing a customer service without the input of the customer, especially when it comes to something as personal and vital as healthcare, should be equally as unthinkable a concept. The flaws in the design of that tea set could have been recognized prior to the manufacturing, if user interviews or contextual inquiries had been conducted. That is the essence of HCD. It is the invitation you extend to the user, customer, provider, or patient, to join you in developing a solution that best suits their needs.


“The most dangerous phrase in our language is ‘we’ve always done it this way’”. – US Navy Rear Admiral Grace Hooper, Computer Programmer