6 ms·
My projects are mostly based on features that are missing or misimplemented in the existing products. This is your first problem. First, features do not sell
by patio11 16y ago
My projects are mostly based on features that are missing or misimplemented in the existing products.
This is your first problem. First, features do not sell software. If there were a Ten Commandments of customer acquisition in the Internet age that would be #2 right after "Google is your god, you shall have no others." People use software and use websites because of the benefit that you credibly propose to bring to their lives through use of the software. Ironically, your users are even telling you this, which is fantastic because most of the time they don't have accurate insight into why your site doesn't do it for them. (Incidentally, "I don't know what problem you're solving" really means "I don't know what problem THAT I ACTUALLY HAVE will get better instantly if I sign up for this.")
StackOverflow is incredibly more complicated than Facebook is. You need an accurate mental model of how the game works in order to play it. (Seeing answers is easier, of course.) There is a reason Joel and company try to seed new Stack Overflow sites with people who have used one of the pre-existing ones. (That also helps solve the chicken and egg problem, which I suspect your sites are likely suffering from in a severe fashion.)
Early adopters are a quirky bunch. One of their problems is that other people are cooler than they are because those people have technology that they haven't used yet. Another of their problems is that the software they previously liked is now lame because even their mother uses it. Most people do not have these problems.
Talk to people. Find out what their pains, fears, frustrations are. This is not hard -- most people love to talk about what they hate about their life, jobs, etc. Identify problems which are tractable with software. Develop the smallest possible thing that shows the vision of a solution. See if it 'clicks' with people. If it clicks, you know you have a viable idea for a product. If not, development is generally expensive guessing.
P.S. Translation from user into English: "It's too complicated" => "I am insufficiently invested in this to do the work that it looks like it is going to take to extract the unknown amount of value I may get out." There are a number of solutions: simplification, hiding the complexity, easing the users into the complexity, and demonstrating higher value. Your user can play effing bridge, she is clearly capable of understanding complex systems when the spirit moves her.
- scrrr 16y agoGood comment, but what makes you believe StackOverflow is "incredibly more complicated" than Facebook?
- patio11 16y agoLast time I used Facebook there wasn't a system of badges, karma, minimum karma levels required to access core features, and a community wiki for my wall posts. These are all highly nonobvious. Embedded assumption #475 in Stack Overflow users: it is obvious that replying to a question is not Answering it.
- davidu 16y agoI use StackOverflow. I've posted questions and I've read lots of responses. I have no idea what the badges, karma, etc. are. For me, it works quite well. In fact, the only mildly confusing thing for me was that I had to use some OpenID thing to login the first time. Think about that. Their value prop to someone coming in through Google or posting a question is simple and the barrier to entry is very low.
- GFischer 16y agoI've also posted questions and read responses on SO, but I believe I still haven't figured out how to "use" StackOverflow. My first experiences with the site weren't too good: I tried to upvote a comment (I mean, there's a big fat arrow to the left of the comment!), and then I tried to answer the question and I believe it didn't let me either...
- Document 16y agoI don't see a private message option (http://news.ycombinator.com/item?id=30088 http://news.ycombinator.com/item?id=30088, http://news.ycombinator.com/item?id=75407 http://news.ycombinator.com/item?id=75407), so I'm replying to your most recent comment to ask: Did you ever find the story you mentioned at http://news.ycombinator.com/item?id=1386010 http://news.ycombinator.com/item?id=1386010?
- GFischer 16y agoI didn't really look for it. If you want to I'll try finding it :) (it should be on my PC somewhere, I don't usually delete those things) Edit: I'll put my e-mail on my profile, sorry people for the offtopic.
- ryandvm 16y ago> features do not sell software I've always thought that, but Joel Spolsky did an excellent talk where he made the exact opposite point. Skip to 25:00: http://www.joelonsoftware.com/items/2010/08/19.html http://www.joelonsoftware.com/items/2010/08/19.html
- jasonkester 16y agoI think you misread the grandparent if you think Joel's point counters Patrick's. Yes, your software needs to have features. That's a given, and it's not what we're talking about here.
- jashmenn 16y agoI'd be interested in hearing the other 8 commandments of customer acquisition in the Internet age, if you care to take a stab at them.
- wglb 16y agoCheck out his blog at http://www.kalzumeus.com/ http://www.kalzumeus.com/. He doesn't have a list of the 10, but it is very useful reading.
- loumf 16y agoFeatures absolutely do sell software if the demand already exists. If you are entering an existing market, where the product category is known -- your set of features (not # of features) is a big part of what will drive sales. StackOverflow, for example, was sold on features. Look at the early pitches -- it's a reddit+wiki replacement for Experts Exchange. Developers already knew that PHPBB and EE sucked for Q&A. They added voting and editing of old answers, and the demand flowed to them.
- joshklein 16y agoBut is it "voting and editing of old answers" what sells the service, or is it "finally, Q&A that doesn't atrophy over time, so it's worth investing your effort in making a great community"? The difference isn't features vs lack of features; it is features vs BENEFITS. This is the thing "business people" bring to the hackerverse.
- hasenj 16y agobusiness people bring "more features please so we can make the sale". It's the designers who deserve the credit here, not the business people. Plus, not all hackers are feature-centric. There are many hackers who understand design.
- andrewtbham 16y agoexperts exchanges was ripe to be taken down because they tried to charge money for access.
- dfrankow 16y ago> the demand flowed to them. Their combined blog readership was huge. They capitalized on that audience, not just the features.
- Travis 16y agoInteresting point. But those "features" existed (albeit in a mediocre form). So maybe "implementation of features" or "quality of features" sells a product...? Speaking just for myself: I don't use SO (or reddit) because of the features they offer. I use them because of the communities involved. I think that's the point here -- there are loads of sites that can compete on features (reddit, meet digg...) but lack something else. It's that "something else" that drives success (partially; I'm not suggesting it's entirely based on some esoteric quality, but that the specific quality can be different for different applications).
- TheSOB88 16y agoFound this sentence confusing: "One of their problems is that other people are cooler than they are because those people have technology that they haven't used yet." You're saying early adopters want try to be impressive by using new technology? That one of early adopters' "problems" (that you are trying to provide a solution to) is jealousy?
- patio11 16y agoYes, absolutely: they are envious of what other people have, that makes them want it, but only as long as other people can't have it, too. They want to be the people in the secret tree house, on the inside, looking out at the unwashed masses who they are intellectually and morally superior to. Apply practically built an entire company on this notion.
- ovi256 16y agoI think you meant Apple :D I concur, dear Sir, I concur. Sent from my iMac.