Casey
Since we started beta testing almost two months ago an argument has been building within the Wokai team about whether to channel our energy into enhancing the frontend, public features of the site, and to begin developing new features, such as our user-generated China microfinance resource, OR to hold back and complete admin systems in our current site that the user never sees, but must be finished before version 1.0 of the site can be considered complete.
We've received amazing feedback from the initial community of contributors on ways that the site and user experience can be enhanced. In all of our heads, we also have this huge vision of what the site could become and all of the features that we need to add to take it there.
Leslie, Wokai's Marketing Director, and I are in one camp, advocating that we shouldn't start marketing Wokai on a mass scale until we've implemented our laundry list of ideas and have a site that we love.
On the other side of the argument is, Larry Sun, Wokai's Product and Technology Director, who says we should make sure that all of the features that are currently on the site work perfectly by the end of the year, then focus for the next three months on completing the backend admin systems.
Larry keeps telling us, "what we need to do now is just build a user base, analyze user traffic over the next few months, and then in the second or third quarter of 2009, start making frontend enhancements." On the other end of the argument, Leslie and I see the homepage and cringe, thinking "what a horrible use of space...it's not interactive enough...none of the best features of the site come through to the user that spends 2 seconds on our site then leaves because it's not worth their time...". We're sitting frantically mapping out the content and contributors that we want in the information resource part of the site.
Given the fact that Larry has over six years of experience at Google and Microsoft, he's winning now....
Wokai's current, homepage:
I'm sure this is the age-old dilemna that anyone who has built a website has run wrestled with.
Would any of you that have found a happy balance between working on future developments and stabalizing core features, please share what you've learned along the way?
Recent Comments