3 ms·
> I think the best advice for me was "Add sample data to avoid an empty nest." I respectfully disagree with that view and I say that as someone who has impleme
by capkutay 7y ago
> I think the best advice for me was "Add sample data to avoid an empty nest."
I respectfully disagree with that view and I say that as someone who has implemented a product with sample data during the onboarding process.
Users don't care about your data. They care about their data. The easier you make it for the user to input their own data and get some value out of it...even if its something trivial...the faster they'll be able to relate their problem to your products ability to solve it.
- pbhjpbhj 7y agoI've been thankful of sample data before - eg auditioning online image editors, I didn't want to hunt around and upload something but just wanted to get right in to editing to get a feel for the apps and whether they're so what I needed. In general though: most onboarding I've disliked, too slow, but some with "click here to do this, or elsewhere to end the tutorial" have been good.
- DanHulton 7y agoI don't know that we have much to disagree about. Absolutely users will get more value from seeing their data, but there are situations where it can take a while to get "their data" visible, like if you're waiting for people to answer a form that they created with your software. Instead of having them wait a day, it can help prove the value of your service to show them what data will look like, once it starts coming in.