Microconf LogoMicroconf Recap

📡 Christian is actively writing this recap (if you listen closely, you can hear him furiously typing at the front of the room). Keep this page open for live updates.

How to read your customers' mind and develop a best-in-class product

Hanne Vervaeck

Marketing geek @thrivethemes, I love funnels, CRO, taking screenshots and listening to podcasts.

Hanne Vervaeck

Part 1: Why giving your customers what they ask for is a bad idea (and will throw you off track)

Flow chart for triaging feature requests.

If Henry Ford had asked his customers what they wanted, they would've asked for faster horses.

There are four types of feature requests that will throw you off track:

1. The Special SnowFlake Request

An example Special Snowflake request

Would less than 1% of your users be interested in this feature? Are the people asking for the feature early adopters?

2. The Centaur Request

Customers will sometimes ask you for features that aren't core to your business, like making a Paypal competitor.

When you get these requests, integrate with a trusted service that solves your customer's problems.

3. The Wash-a-Pig Request

Customers will often ask you for nice-to-have features, like Grammarly integration. If the feature wouldn't make a difference in the buy/not buy decision, and isn't something people would talk about in product reviews, it's a Wash-a-Pig request.

4. Faster Horses

Faster Horse requests have a bigger-picture problem to be solved.

The Faster Horse request is the hardest one to recognize because it makes sense. To identify Faster Horse requests, evaluate if the feature request could be satisfied by solving a bigger problem.

For example, a customer asking Henry Ford for a faster horse is actually asking for a faster way to get places.

Part 2: What you Should do Instead (including the Magic Wand Formula)

Instead of implementing every feature customers ask for, do things that don't scale.

Particularly, one-on-one customer development calls:

  1. send your customers an invitation to talk, or a link to a form
  2. send your customers a calendly link
  3. ?
  4. send followup emails
  5. record the call with a podcasting app or Skype

On the call, shut up and listen. A great open-ended question to ask is "if you had a magic wand to solve this problem, what would that look like?" This takes customers out of the limited mindset of thinking practically.

After the development call:

  • write down your gut feeling
  • have the call transcribed (rev.com charges $1/minute, which is practically nothing)
  • (have someone) listen to the call with the transcription and highlight the important information

Part 3: How to Avoid Overwhelm & Become a Mind Reader

Thrive Themes evaluates new features by looking at how much it would increase revenue, customer value, strategic value, efficency, and innovativeness.

From those customer interviews, you'll extract ideas for features. Organize those features in a spreadsheet to evaluate which features are the best to implement next. Weight features against eachother by what is important for you. Thrive themes values impact on revenue, customer value, strategic value, efficency, and innovativeness.

Questions

How do you get accurate rankings?

They're estimates - go based on your gut.

How do you manage a public roadmap with customer expectations?

We don't have a public roadmap. Our users don't know the exact features they want, and we prefer to capture their problems.

How do you respond to customer requests?

If it's a special snowflake request, we just thank them. If it's a faster horse request, we say we're working on the problem.

How many feature requests do you get each month?

Hundreds!

Have you ever launched a feature that you regretted?

Yes! Bad features generate a lot of support requests. Because our product is a wordpress plugin, it's difficult sometimes to see if a particular feature is getting used.

Why do you look at effort after the fact when evaluating features instead of including it in the score?

We wanted to make sure we didn't eliminate features just because they were hard to build.

Free "Microconf Recap" eBook

I'm sending out a beautiful PDF eBook of notes from every MicroConf Starter and Growth talk – both Speaker and Attendee. Want a copy?

What your friends call you