Your Baby is Ugly!
That’s the title of the article I just published on UXmatters, in which I give advice on how to soften the blow of delivering bad news to clients. Let’s face it, when we perform an expert evaluation, usability testing, or user research on an existing product – most of what we find is problems with the current product. Clients don’t pay us to tell them how great their products are. If they’ve hired us, it’s to find problems that can be fixed. But there are ways to make it easier to deliver bad news. In this article I provide the following advice:
- Get the stakeholders to admit that it’s ugly first
- Get everyone to buy into your research methods upfront
- Encourage stakeholders to observe the research
- Blame the bad news on the participants
- Back up your findings with metrics
- Present recordings and quotations
- Don’t beat your audience over the head
- Emphasize your expertise
- Back up your findings with examples of best practices
- Show your stakeholders they’re not alone
- Position it as providing recommendations, not pointing out problems
- Mention the positive aspects too
- Deliver your findings in person
- Prioritize the problems they should solve
- Provide a plan for addressing the problems
You can find more details about this advice in my latest article, Your Baby is Ugly.
As a user researcher, I often deliver bad news to clients – a long list of problems with their application or product and an intimidating list of recommended changes. It’s easy for me to think that the client should immediately set about making all these recommended changes. And when some of those changes aren’t made, I shake my head and can’t understand why they just don’t get it.
It’s not often that I’ve put myself in the client’s shoes to think about what they’re going through when they get the news. I’ve never been in the position of being the owner of an application or product who has to listen to a long list of problems that need to be fixed. So how can I empathize with what the client goes through?
I am, however, a homeowner who bought an older house after getting a home inspector to inspect the house. His inspection gave us a long list of problems to fix. It was intimidating and depressing to see how much work would be needed even after the high cost of buying the house.
What prevented us from giving up on the house, was that he prioritized the list of problems to show which items were critical to fix before purchasing the house, what would need to be done within the next year, which things could wait a few years, and what were optional but recommended fixes. That made his recommended changes seem more doable. We knew what fixes it would be reasonable to ask the seller to make, which items to focus on first after buying the house, and what we could wait on.
With user research findings and recommendations, it’s important to give your audience a sense of the severity of the problems and the priority of what should be addressed first. Like a home buyer, few clients have the time and money to fix all the problems right away. Receiving a large list of problems and recommended fixes can lead to a defeated feeling and a desire to ignore the problem or just give up. Instead, give them a sense that the problems are manageable and that it’s possible to focus on fixing a few items first and then gradually address additional problems over time.
I just got back from the IA Summit 2012 in New Orleans, where I presented User Research is Unnatural (But That’s Okay). Yes, that may seem like a strange topic for a user researcher to present, but I think it’s very important to remember how strange and unnatural user research can seem for participants. The point of my presentation is that by remaining aware of the awkward and uncomfortable aspects of user research, we can take steps to minimize or eliminate those problems to get better research results.
See my slides on Slideshare: User Research is Unnatural (But That’s Okay)
This was my first time attending the IA Summit, and it was a great conference with some excellent speakers and intriguing topics. As a user researcher who more often attends UPA and CHI conferences, it was interesting to attend a more design-oriented conference. I’m already looking forward to next year’s IA Summit, which will be in Baltimore.