You've launched... now what?

Welcome to Rework, podcast by thirty seven Signals about the better way to work and run your business. I'm your host, Kimberly Rhodes, with Jason Fried and David Heinemeier Hanssen, cofounders of thirty seven Signals. This week, we're chatting a little bit about the second step of a launch process. So we've recently launched a new product, Fizzy. Thought we'd talk about what happens next. Things are live. We've tweeted about it. Like, what's the next part of this phase of the launch process? So you guys jump right in. We had a big telling people about it. Now things are kind of back to normal and we're at a regular cadence. Like, what does the day to day look like at this point? Well, I think you first have to maintain enthusiasm for the platform, the product, wherever you is that you put out there. So one great way to do that is to share some examples of how we're using it. Every time we launch a new feature, share that. Because it's open source, we can highlight and celebrate other people who are contributing or merging in their pull requests and getting that thing out there into the world. So there's a lot of that that has to continue to happen. You have to continue to cheerlead and and promote without feeling like you're, you know, just spewing ads. Right? So these things have to be sort of realistic. So there's that. And then on the product side, there's, of course, a bunch of feedback that flows in. A bunch of stuff comes in that you knew was gonna come in. A bunch of stuff comes in that you didn't know was gonna come in. And I I think it's best to kind of wait for a little bit and not knee jerk and do anything, like, aggressive in the first few weeks. And And by that, I mean, like, don't make any big changes that people complain about something. Of course, if something's broken, you fix it. For the most part, people are getting used to something if it's new. So it's an old idea, brand new application, brand new execution of this idea. Some people are gonna come at and go, you know, bring their other expectations and go, why doesn't it work this way? Or can we lose this? Or can I rename that? Or I don't like this being open. Or why can I only open two things? And it's like, I hear all those things. Give it five minutes. Give it a few weeks. Give it a few months. See how you adjust to it. See how it feels. Whatever. So I think that's important. And then we still will have some ideas that we didn't get in for v one launch that we either held back, didn't feel great about, that we then can implement now which we've already begun to do and sort of refine at the edges without making any …