Instant Utility
What this means is the service is instantly useful to you. If you build a service and the user has to spend an our configuring the service, setting it up, importing contacts, doing a lot of data entry, I don’t think people are going to – most people aren’t going to put up with that. The service has to be useful right out of the box.
We see a lot of people make this mistake. There are a lot of tricks you can use to create instant utility and then go from there. A good example of that is if you’re building an information service, you can crawl the web to populate the service initially, even though long term you expect to get the data some other way. You have to give people something right off the bat that is useful.
I think these are always good principles - but I want people to really understand an apps value as soon as they view it. If it can't produce results right away, then you need to set up a mock example so people can see what it does. Good point Fred. Probably right to put this as #2 to speed.
No comments:
Post a Comment