I’d like to say a few words about our launch strategy. By just looking around at other new online communities it’s obvious that there are many ways to go. Launch everything at once. Private beta phase. Public beta. Launch a little, then a little more etc.
These are our thoughts
- We’re planning a private beta
- Then a public beta period (phase 1) which is the official launch
- Phase 2 launch, end of beta
- Phase 3, slower continuous development
It’s hard to wait with functionality to later phases when we know it will add a lot of value but there are a few good reasons.
First of all we don’t want to put all the eggs into one basket. Also I don’t think the users want an overwhelming amount of features to hit them at once. Better to let them discover the features one by one and give feedback on what works and what doesn’t. We can then take this feedback and compare to our own release plans. Hopefully they’re in sync, otherwise we will have the opportunity to adjust our plans for the next phase.
This strategy helps the development process. If we see a demand for a particular feature we can prioritize amongst what’s in the pipe line to our users. We want to respond to their needs and to show that we listen and care.
Nothing new under the sun here. I think this is how most other community drivers think. I just wanted to bring it out in the open so we can discuss it if you feel like it