Why (and how) should I ask for feedback?

Doing a project on your own is always exciting, you’ve worked out everything in your head and all the pieces fit together nicely. You then spend the next month hard at work making strides on your project. When you finally emerge with a fully functioning product or piece of art, you come to the realization that everybody you’ve showed it to has no idea what they are looking at. One of the worst feelings in the world is creating something that nobody wants or appreciate. Getting target feedback is crucial in the success of a product. But what is the best way to integrate a feedback system into your work flow?

Here’s what I’ve learned from the last 3 years of my entrepreneurship journey:

1. Your ego is your worst enemy.

Thoughts like “It’s not ready yet” or “I don’t want to show it until it is perfect” are extremely dangerous. The more I’ve worked on different things over the years, the more I realized that no product is ever or will be perfect. Nobody likes failure, but unless you’ve achieved full mastery, chances are you are not going to hit the nail on the head the first few times. Jumping to conclusions about how something ought to be can become expensive and time-wasting. So get feedback whenever you can and don’t be afraid to be proven wrong.

The way I see it, rejections are little blessings in disguise. Put your ego aside and embrace them!

2. Integrate constant feedback into your workflow

At Wizdy, the first game (Wizdy Pets) took a team of four 2 years to complete. Our second game took a team of three 1 year to complete. Why did the first one take so long? We kept changing our game design based on the few feedback that we’ve gotten by talking to only a few doctors too late into the game. Every time we decided to change directions, it was months of work down the drain. One thing that helped immensely on the second project was integrating continuous feedback throughout the development of the project and spending a considerable amount of time in the design and prototyping phase. Even before we came up with the final design, we brought devices to kids with very similar games and observed their reactions while playing. Even during the prototyping phase, we went to play-test with kids from after-school programs at least once every two weeks. This made sure we were on the most optimal track in the general direction we had wanted to go and constantly made small design changes that have huge opportunity costs down the road.

3. Talk to strangers

I am guilty of being the problem here. If a friend came to me with a ridiculous idea for a project, chances are I am probably going to be supportive no matter how inane it may be. People tend to become much more considerate of the things they say to their friends as they age (which also makes some adult friendships tricky). The best place to get honest feedback is from people that you don’t know. This doesn’t necessarily mean to go out on the streets to flag people down, but interest group meetups are an excellent place to start. Again, I want to emphasize that if you really want a product to succeed, learn to embrace constructive criticism, even though sometimes they hurt.

Every project is different, and unfortunately there is no silver bullet to solve all problems. I hope that the points above helps to serve as a guideline on avoiding some of the pitfalls that my peers and I have wasted a lot of time trying to remedy.

With that, good luck and happy hustling!

One response to “Why (and how) should I ask for feedback?”

  1. Great post Sean, very helpful especially #1!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.