I've got to stop and capture all of what has happened in my brain over the last few days and write it down right now.
Last week, I strategized and launched a pretty large social network in four days, with the help of a really amazing team. In some days, I've done jobs like this before, in that I've launched a hyper-local social network last year in a couple of hours, but in many way, I entered uncharted waters this week.
A lot of people are going to ask me if this kind of effort can be replicated, and I can safely say that with the right team, it can be. That said, here's what you'll want to have lined up along with that team, before you tell a client that you're going to do it. To paraphrase Admiral David Farragut: Damn the torpedoes, full speed ahead, yo.
1. Delegate:
Make sure that overall initiative strategy and network development are handled by two separate entities working in tandem. If front end CSS and back-end integration can be developed in tandem to any degree, do it.
2. Lock Modules:
No matter what platform you're using (Ning, etc.) outline the modules you'll launch with; all other items are secondary.
3. Double Analytics = Double Happiness:
I don't care how good your platform's analytics are. Install 2 different types of analytics so that you can A/B them. Why would you choose between Rush tickets and Yes tickets, when you can have them both?
4. Think Globally, But Don't Get Up From Your Damn Desk:
If you don't have people working in 3 different time zones, plan for a lot of sleepless nights. The optimal config would be Tokyo-Chicago-Estonia, but three team members separated by 4-6 hours will do. Work like you're trying to get Baby Jessica out the well, aight?
5. Sleep, A little:
Warren Zevon may have been right about the whole "sleep when I'm dead" thing, but that guy never built a social network. 5 hours per night is a minimum if you don't want to be useless on conference calls.
6. Exercise, A Lot:
Block out 30-45 minutes per day.
7. Water:
6-8 bottles per day, no joke.
8. Scotch:
6-8 bottles per day may be a bit much. It will help make the non-project email tolerable.
9. Email:
It's a total time-suck, so try to avoid it at all costs. Move all project-related communication off email and onto Basecamp or something similar.
10. Copy:
Nail all static site copy in the first 24 hours. Make third-rev changes post-launch.
11. Press Releases:
Read every rev of every release.
12. Community Guidelines:
Write them pre-launch, and get that community manager working pre-launch.
13. Two Monitors: Normally I don't give big props to Jason Calacanis, but if you try this without two monitors, I can promise that you will fail.
There are certainly about 27 other points I could place at the end of this list, but you'll have to get in touch with me to find out what they are. Anybody who can place the graphic at the top of this post gets a coffee, on me.
Link to original post