There is always a sense of euphoria after a “launch” of any sort. Especially if you have been working on your product / service for many months and are not particularly sure how it will be received. Then you get a chance to go “public” with your features / product or company. It tends to be exhilarating, but brings its own set of things to do after the launch.
There are 3 major buckets of items that you will encounter the day after the launch.
They fall into the “do now”, “do later” and “do never” bucket.
First the “Do Now” bucket. I would put thanking people that supported you on the top of the list. Send personal emails to the reporter, initial users, advisors and mentors with a list of links (combine all coverage instead of sending multiple messages) that indicate the coverage your received for the launch. Even if all you did was launch it on HN, it helps to take a screen shot, or even provide a link to the comments. If you have a team, I’d highly recommend you collate all the links, and put them into a document to share and discuss when you meet. It helps to set context to something you have all been working on. Even if the feedback on the launch is negative or “meh”, I’d still recommend you put it together.
I’d also immediately put together a spreadsheet with the major items of feedback and perspectives, and put them into feature requests, comments, questions and general feedback. Some of them you can action and others likely not. Either ways, it is quicker and more helpful to capture all the feedback just after the launch rather than go back and revisit it later.
Finally I’d spend quite a bit of time providing customer support – helping answer user questions, addressing their issues (without coding new features immediately) and also documenting the bugs they encounter – maybe you might want to even fix the blockers or P zeros (priority zeros).
Second, for your “Do later” bucket. I’d write a blog post to collect your thoughts, and write about your experience overall – what were the highlights when you got your start, what the low lights were, what your journey was and how you made critical decisions. In that blog post I’d also add the links to the launch coverage.
I would also spend some time after day 1 on your traffic analytics – where did you users come from, where they spent time and finally what they did. These will help you prioritize the key elements of your go forward plan and help you target the right press or channels going forward.
This is also a good time (do later, not immediately) to check all your social channels – Quora, FB, Twitter etc. to capture your feedback. I dont put these in the do now bucket, because while you might get some feedback that needs immediate attention, they tend to be a big drain and time sink. You will end up responding to some of the feedback, but most of the response from your side will be emotional – either happy, because your launch was well received, or sad because you were panned.
Finally the “Do never” bucket. You will get a lot of email from potential recruiters – who have “a rock star ninja” who wants to join your team and mentioned your company by name, or potential partners who “want to set up time over coffee to talk about potential ways to partner” or other principals and associates at investment firms who “followed” your launch or were tracking you on angel list or tried your product and would like to setup some time to learn more.
These waste the most amount of your time. I’d highly recommend you push them all out by a few weeks and use it as a technique to buy some time and gauge their interest after 3-4 weeks. While I have learned that there’s some truth to the “strike when the iron’s hot”, these are rarely hot irons, but more “flat coal”.
I’d love your feedback. What’s been on your do now, do later and do never bucket after launch?