9. Feature request list
By getting a lot of feature requests,
I can be certain which features are
truly the most important ones for
the users, therefore for me to
deliver.
Telling the story about Artlook, the first startup, how it started and how I started my first PM role without even knowing.
We just didn’t care about users. Actually it was not in our minds at all. We only looked at other eComm sites, added our own ideas and gut feeling and tried to create the best eComm website we can think of.We didn’t stop for a second to check whether they like the website, the products, is it hard for them to navigate between pages, to complete the purchase. Nothing.
Suddenly i found myself in a new company, with a total different approach for users.Suddenly i have millions of users to “serve”.What I will add to it, is a short description of what is ahead of us: “after understanding the difference between the two situations, let’s discuss the pros and cons of each’
“And just for you to understand why UNDERSTANDING the differences and following the requirements of these situations is so important, let me tell you what happened when I didn’t…”First time i “got it in the face” was when we launched a new UI for our Blog Manager. I wanted the tool to be more clean, less option that the majority of the users don’t even use. I wanted to be more like Medium.com.1.5 days after releasing first version we broke the record of support tickets for one day… 200 complaints, by VERY angry users who shouted out loud - “where are our text tools???”Then i understood it’s very hard to change things dramatically without understand first what my users think of it.
A big advantage in working with mass of users is the ability to perform A/B tests and get significant answer very soon.And what is the result of that? I think it will be better to state (the somewhat obvious…) that by doing that you follow the market and not “guessing”
A big disadvantage is to change things in your product, especially removing things, that users already used to (instead of saying “that users already used to” I think it will be better to explain that it is because they are also used to it. That’s the reason for that)Even if it’s the stupidest feature ever, out of millions, you still have many which are using it.There are a lot of new feature that might actually change user's website designs, and they can’t do control it.In every change of existing feature you have to be sure all existing users won’t get hurt by this change. For every new feature that adds new fields in the database you need to run migration for millions of old sites.
I love this picture :) I will suggest using it differently; I think you can use it for a great ending saying something like “It doesn’t matter if you are a small startup in your parents’ living room… or having a fancy office in the Valley. Always, always, listen to your users. This is my advisory board…”This is my advisory board. Built out of users. They are the first ones i’m asking for feedback about new feature before we release them, they are the ones for consulting about new ideas and more.