Königsweg für die Einführung einer neuen Software
Sonntag, 24 August 2008 14:58 - Geschrieben von René Lindhorst
Ein sehr lesenswerter Beitrag von Aaron Swartz darüber, wie man eine neue Software (Webanwendung) idealerweise einführen sollte (”Hollywood Launch” vs. “Gmail Launch”):
I’ll call this technique the Gmail Launch, since it’s based on what Gmail did. Gmail is probably one of the biggest Web 2.0 success stories, so there’s an argument in its favor right there. Here’s how it works:
- Have users from day one. [...]
- Try to get lots of feedback from these new invitees, figuring out what doesn’t make sense, what needs to be fixed, and what things don’t work on their bizarre use case combination. [...]
- Automate the process, giving everyone some invite codes to share. [...]
- Iterate: give out invite codes, fix bugs, make sure things are stable. [...]
- Take off the invite code requirement, so that people can use the product just by visiting its front page. [...]
- If all this works [...] then you can start building buzz and getting press and blog attention. [...]
- Start marketing. [...]
