You Suck! And How to Handle Other Negative Feedback

Negative feedback hurts. It’s easy to take personally and get offended. It’s easy to dismiss too. But negative feedback is a lot better than no feedback at all. The worst thing for a startup -at any stage- is crickets.














Ugh. Silence is the ultimate form of “you suck” feedback. Better that people take the time to tell you to your face. And in many cases, negative feedback can be more valuable than positive feedback, which is often given because people want to be nice. As a founder, you don’t need nice, you need honest and meaningful. So customers that tell you that you suck could be your most valuable ones ever. And just because they’re negative, doesn’t mean they won’t help you along the way, and ultimately buy from you.

When receiving negative (or positive) feedback, it’s important to understand the context. For example, feedback at any point in time, without any sense of historical feedback, is a very small data point. You shouldn’t ignore it, but keep it in perspective.

You need to understand the “why” behind feedback as much as possible. So don’t be scared to ask for more information from people that have just told you that you suck. Oftentimes they’re quite willing to speak their mind further. You need to understand your customers as much as possible. It may be that you’re focused on the wrong target market. It may be that you released really early, and find out that with a bit more work on the product, you can go back to those same people and they’re willing to try again. Sure it’d be nice if those people loved your product right away, but the above scenario is still a good one: you received honest (bad) feedback, you figured out what to do, you’ve determined it’s worth doing (because it impacts a broader, valuable market), and you still have a chance of making a sale down the road.

Negative feedback is discouraging. But you have to remember that it’s part of the learning process. It doesn’t feel like that all the time, but if you’re digging into the feedback, understanding the context, and using the feedback to make decisions, it’s going to help steer you in the right direction.

Silence is the worst. Negative feedback is just part of the process. You’ll need thick skin (every startup founder needs thick skin and a healthy dose of delusion). Try your best to avoid the crazy up and down roller coaster that comes with good and bad feedback. Focus on learning. Focus on extracting the value from feedback, and moving forward.


One Customer Doesn’t Make a Market

These days, most entrepreneurs I talk to understand the importance of speaking with customers before building a full-blown product. They’re getting out of the building. And that’s great. A few years ago it wasn’t like that at all.

But unfortunately, I often speak with entrepreneurs that have only talked to one or two customers. That’s not nearly enough. The danger in speaking with too few customers is that you bet too much on too little data. If the first customer you speak to loves your idea and you put blinders on to go build the solution, you haven’t eliminated any real risk. You’ve just found one potential customer. Chances are you don’t even understand the problem well enough to solve it.

A customer that says, “That sounds cool,” or “That would be really useful,” is a lot different than one who says, “I’ve tried solving that problem in a few ways, and looked at five different solutions, none of which really addresses my problem.”

You need to find out if the customers you’re speaking to have ever tried to solve the problem on their own and/or if they’ve gone out and looked at other solutions. If they haven’t done that, there’s a very good chance the problem isn’t big or painful enough. Ask them straight up, “How have you tried to solve this problem before?” Don’t be shy about it.

Consulting companies that want to convert themselves into product companies run the risk of building a product off too few customers. They get hired to build something, and assume there are no alternative solutions that are good enough. They deliver the solution and then decide that there must be a whole bunch of other customers out there that need the same thing. Maybe. But maybe not.

In my experience you need to speak with at least 10-15 potential customers before you can see any significant patterns and get any real clarity. After 10 or so interviews you should have a good sense as to whether or not the problem you’re proposing to solve is important enough.

One customer doesn’t automatically represent a worthwhile market. It’s just one customer. And you need to know why they’re a customer (or a potential customer) before making the big assumption that they represent a full-blown market. If they became a customer because they didn’t know any better (never bothered looking for something else), or they’re your friends, or some other non-replicable and scalable reason, you could be in trouble.


Gaps in the Market

Startup founders often say to me, “We’re going ahead with this new startup … we’ve identified a gap in the market!” It’s a common refrain explaining why someone is starting a business, and how the startup is positioned against competition. There’s a gap in the market.

The question to ask at that point is simple: “Is there really a gap?”

Too often, startup founders haven’t done enough homework and really don’t understand the industry they’re going into. They use incomplete evidence and analysis to come to the fairly significant conclusion that there’s a gap in the market. Here are some examples I’ve seen in the past:

  1. Anecdotal evidence: “A friend of mine who works in the industry says this is a huge problem.” That’s anecdotal evidence and it’s not enough to really understand a market. The anecdotes may be right, but like most “stories” they’re embellished or altered away from pure fact.
  2. Backyard evidence: “Companies in this area are way behind the times and need a new, more innovative and less expensive solution.” Backyard evidence -if gathered correctly- can be a compelling first place to start, but be careful that there aren’t any regional specifics as to why there may be a better local market vs. everywhere else. Serving a local market (at least with a software/web startup) is extremely difficult and narrow minded. Don’t make the assumption that a local gap in the market will be reflected everywhere else as well.
  3. Me too evidence: “I see a bunch of startups jumping into the space (reading it on Techcrunch), I knew there was an opportunity there!” You can identify trends and certainly identify competition from the press, but I wouldn’t base my assessment of a market on what I see published online. Plus, there’s no way of knowing if all the other startups did their homework either.
  4. Past experience evidence: “I’ve been in this industry for 10 years, I know what’s going on.” This kind of domain knowledge can be extremely valuable. I’ve often counselled people to stay out of industries they haven’t participated in because they really won’t appreciate the intricacies of it. But past experience is powered by the bias of one person, so be careful about how you interpret it, especially when it’s someone else’s experience and not yours.

Knowing your market isn’t something you should take lightly. It can make or break you, simple as that.

Using super-biased, incomplete, casual, close-minded or anecdotal evidence as a determinant about whether or not you should start a company, and then how to position it in the market, your value proposition, and what you should build, is incredibly risky. Instead, take a rigorous, scientific approach to identifying market gaps. Talk to more people. Talk to people outside of your local area and comfort zone. Do more research on competition. Try and disprove yourself instead of seeking “evidence” that only proves your point. Hack something together, show it to prospects and get them to pay for it.

Even after you’ve identified a gap, you have to then understand why the gap exists. A gap alone doesn’t provide enough validation to jump into it. There could be lots of reasons why a gap isn’t being filled.

Don’t jump blindly into a startup and industry that you don’t understand, using a haphazard “gaps in the market” analysis … it’ll hurt.


Ben Yoskovitz
I'm VP Product at GoInstant.

I'm also a Founding Partner at Year One Labs, an early stage accelerator in Montreal. Previously I founded Standout Jobs (and sold it).

My bio »

or

Follow me on Twitter

Get updates and special content
When I publish new content, get it directly in your inbox. Subscribers will get special stuff as well not available on the blog (but I promise it will be infrequent + high quality.)
or

Subscribe via RSS Feed

Get the Lean Analytics Book!
Advertisement
Startup Resources
Find Stuff
My Photos