Qualitative Data Isn’t Just Bad Quantitative Data
Qualitative and quantitative data serve distinct purposes and work best when considered together.
Qualitative and quantitative data serve distinct purposes and work best when considered together.
In my last post, I talked about ways that research consent can be more nuanced than “yes” or “no”. This second and final part explores scenarios in which consent can get complicated and trust may be endangered.
This will be the first in a short series on ways to protect end-user identities when collecting feedback or testing products. As many of us become more proficient in cybersecurity best practices, it’s crucial that we don’t forget some of the low-tech ways that we can keep identities secure and maintain trust.
“Humanity-centered design” goes beyond “human-centered design” to look at the bigger picture surrounding applications. Here’s how that can change your approach.
The need for public-sector user experience (UX) professionals is continuing to grow. Here’s why the government UX field is thriving, while the private sector is trending downward.
While low-code and no-code tools can provide benefits, agencies should be judicious in how they use them and understand the limitations of what they can provide.
Experimenting with multiple wording options to see which one performs better can help you communicate in ways that match how your target audience is thinking.
It’s usually good to use plain language and avoid jargon. But sometimes, incorrect, outdated, or obscure terms can help you “meet people where they’re at”!
Where interactions suffer is when the quality of data doesn’t match documentation requirements. Improving the citizen experience can resolve these issues.
In the past decade, the concept of user experience (UX) in government IT has gained widespread acceptance and moved into the mainstream.