Reporting findings to the API Service team

Bringing focus to our findings: continued user research for the API Service

This is the final blog post in my short series about the [user research I led on for the API Service at the University of Edinburgh](https://website-programme-blog.is.ed.ac.uk/bringing-focus-to-our-findings-continued-user-research-for-the-api-service/).

This post covers the second half of the research, where we brought focus to the detailed picture developed in the first phase, and began to prioritise the issues to help the API Service team direct their ongoing work.

Crying over spilt milk: An empathy map example

Example empathy map

I have recently been involved in a project with the University of Edinburgh UX Service to conduct [user research for the API Service](https://duncanstephen.net/user-experience-research-for-the-university-of-edinburghs-api-service/).

In one of the workshops we ran, we wanted participants to work with empathy maps to give us an insight into their experiences.

This post on the University Website Programme blog outlines [how I introduced workshop participants to the concept of empathy maps](https://website-programme-blog.is.ed.ac.uk/crying-over-spilt-milk-an-empathy-map-example/), with an example around my own experience of buying milk.

Buying milk is a simple task that most of us carry out on a regular basis. But this example showed how using an empathy map can reveal a surprising amount of detail about the behaviours and feelings someone goes through when completing a task.

Presenting findings of our user research for the API Service

User experience research for the University of Edinburgh’s API Service

I have been leading some user research for a project at the University of Edinburgh to develop API Service. [This post on the University Website Programme blog outlines the steps we went through in the first phase of the research](https://website-programme-blog.is.ed.ac.uk/user-experience-research-for-the-api-service/). This included interviewing developers, running workshops, and developing personas and journey maps.

This has been a successful and rewarding project. It has been particularly interesting for me to do some UX work that wasn’t necessarily to do with a website. There will be a couple more blog posts about it to come.

The secret cost of research

A belter of an article on why it is difficult to persuade people to undertake user research:

Research is simply asking questions about how the world works. And asking questions about how the world works threatens established authority.

I especially love the section “Bad research is good theatre”:

Focus groups look like how people imagine research looks. In a special room, controlled. But just because you have a 2-way mirror doesn’t make it anything more than a tea party. Actual ethnographic research happens where the people you’re studying do the thing you want to learn about. It’s often unsatisfyingly messy and low tech.

Fake research makes people money, and it makes people in charge feel good, but it’s useless and potentially dangerous to a design project.

So how do you get decision-makers to see the light? Understand them as people, like a good UXer should!

The 9 rules of design research

One of the hardest things about design or user research is convincing people that it actually needs to take place. That is especially maddening when working for an research organisation.

(Researchers themselves are sometimes the most reluctant to undertake user research before spending serious amounts of money on ineffective websites.)

So this snippet, among a series of useful rules of thumb, made me cheer. 🙌

If you’ve ever worked with a leader who was resistant to doing qualitative research as part of a million dollar project, ask yourself whether they would skip doing their own research before buying a $50,000 car.