Making sense of customer research at MURAL

If your company is willing to hear what customers have to say, you’ll probably be overwhelmed by the amount of feedback you’ll get. Luckily, we get a ton of feedback at MURAL.

Agustin Soler
Jun 26, 2018 · 6 min read

Organizing and synthesizing feedback and research is critical for us.

In the last post, I mentioned that each product team at MURAL has an “Icebox” of ideas, opportunities, and observations from which Product Managers find patterns and spot trends about what seems to be the most important underlying themes we should focus on.

An Icebox mural of a product team looks something like this:

MURAL icebox

Product Managers organize the different iceboxes during the quarter and use them when deciding what to build next.

Where do ideas come from?

Credit: https://ericveldkamp.wordpress.com/2016/04/21/availability-heuristic/

We’ve come up with a simple process in which we take customer input, synthesize it, and end up with a draft prioritization to be used during the planning phase.

  1. Get input from different sources
  2. Understand
  3. Debrief
  4. Centralize
  5. Synthesize

1. Get input from different sources

  • Contextual inquiries: We do customer visits, in which we observe and interview customers on-site while working. Understanding the context of usage is critical. Observing a live collaborative session is revealing.
  • Interviews: We also do tons of customer interviews via Zoom. Most of our product team is in Buenos Aires, Argentina, but that doesn’t stop us from running interviews each week. Sometimes we just want to talk to someone who sent us interesting feedback. Other times, we proactively contact customers using Intercom or via Customer Success to co-create or get early feedback.
Interviewing customers at MURAL
  • Usability tests: We’ve done around 50 usability tests in the last year. Each time we do one, we find new things to work on. We do usability test of our product and also of our competition.
Usability test reports

Each Usability test has a debrief, and it’s later shared in Slack….

Usability test debrief
  • NPS surveys: Every 3 months we ask 1/3 of our active users the NPS question. We’ve been using it as a benchmark against ourselves. But, the most important part of the question, is the open response. When we get an answer to the Why? question, it is posted directly to Slack. If there’s a response that seems interesting to one of the PMs, we contact the customer and dig deeper.
NPS channel in Slack

We also organize the different NPS responses from our detractors into categories.

Numbers are fake, but the report is the one we use
  • Internal Stakeholders’ feedback and ideas: This is obvious. Everyone at MURAL has ideas on what we should be doing. We use our own product, so we constantly have suggestions and ideas. These are also captured. A designer might be using MURAL while doing a design studio, and a new idea might be captured. Product Managers have tons of ideas they want to try out. They are all captured.
  • Sales and Customer Success feedback: Sales and Customer Success reps have daily conversations with customers. Their feedback is critical for us. We have a weekly sync with sales and another one with CS, but they are constantly sending us feedback from the different touch points they have with users and buyers.
CS session with a customer
  • Customer Support tickets: Support tickets are a great source of customer feedback, and are great opportunity to have conversations with customers. A support ticket might escalate into an interview that provides us with plenty of insights.

2. Understand

Just to give you an example: When someone from our customer support team receives a ticket via Zendesk, they’ll first try to understand whether what they are reporting is a bug or not. If it’s not a bug, but rather a suggestion, request or idea, customer support always asks for more context to understand why customers are saying what they are saying.

Why do you need to do this?

Could you tell us more about this idea?

What were you doing that made you ask for this?

…are common questions we might ask.

Digging deeper

3. Debrief

Product Managers read that channel on a daily basis, but we don’t act upon the feedback we get immediately. Maybe we’ll be able to use it for what we’re designing this Q, maybe not; but having all the information centralized in this channel helps us make that decision more effectively (and avoid that availability heuristic).

Getting feedback via Slack is already great. However, Slack acts like a feed for PMs. We need other ways to process and make sense of every input.

4. Centralize

Product Feedback spreadsheet.

It contains every piece of feedback we get from our multiple sources. Each source is represented by a tab in the spreadsheet.

MURAL PMs read this spreadsheet weekly, pick out the different pieces of feedback relevant to their area, and take them to their respective icebox murals to synthesize the information.

5. Synthesize

PMs can synthesize the information, affinity cluster the data, and thus see patterns that start to emerge. The more our PMs go through the process, the more habitual it becomes to notice current patterns. With these patterns, we can put together a cogent, insightful list of priorities for when we’re deciding what to build next.

Icebox WIP

These artefacts enable communication among product team members and with external stakeholders. They give us clarity and direction.

Visualising the whole process

This is what we currently do, and there’s probably a lot of room for improvement. If you have suggestions or want to share how you handle customer feedback at your company, please let us know!

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade