You've launched... now what?

Key takeaways

Understand and manage the post-launch phase with enthusiasm and real engagement.
Scaling down the team post-launch is essential for ongoing improvement.
Let feedback accumulate before making immediate changes to the product.
Avoid allowing early numbers to overly influence business decisions.
Return to structured work cycles for better management and productivity.
Focus on long-term strategies instead of quick financial returns.

Summary

The Launch Aftermath

The hosts discuss the immediate post-launch period, emphasizing the importance of maintaining enthusiasm for the newly launched product, Fizzy. They suggest sharing real user examples and recognizing contributors to sustain motivation and engagement. The conversation also covers the need to balance between promoting the product and avoiding excessive advertising.

Managing Team Size Post-Launch

Following a major launch, it’s crucial to adjust team dynamics. The hosts explain how they scale down from a large launch team back to a more manageable size, typically consisting of two developers and a designer, while ensuring ongoing product improvements and feature enhancements.

Communication and Feedback Loops

The episode emphasizes the necessity of setting up communication avenues to collect user feedback without rushing into changes. It urges to let users acclimatize to the new product before implementing drastic changes, allowing for a more measured approach to updates.

Navigating Early Numbers

When discussing early metrics and user sign-ups, Jason and David assert the importance of not allowing these numbers to dictate immediate business strategies. They focus on understanding trends rather than reacting impulsively to fluctuations in user engagement.

Balancing Work Cycles

Post-launch, the company will return to its regular work cycles, which typically last six weeks. The hosts explain how these cycles help maintain balance, providing time for reflection and organized planning rather than continuous reactive work.

Long-Term Vision vs. Short-Term Gains

Towards the end of the episode, there’s a discussion about prioritizing long-term vision over immediate financial gains. The hosts argue that compromising the product's integrity for quick monetization can be detrimental.

Show notes

The confetti’s settled. The product is out in the world. So… what happens next? Jason Fried and David Heinemeier Hansson share what the days after a launch actually look like at 37signals. They discuss not letting early numbers steer the ship, making space for rest after the push, and remembering that shipping is just the start, not the finish line.

Key Takeaways

00:10 – What happens shortly after launch
02:09 – Dialing the team back
05:10 – Product touch ups and enhancements
06:16 – Returning to a familiar work rhythm
07:16 – Balancing the product push with real breaks
10:39 – Not letting early signups call the shots
20:32 – Sticking with what works for your team
22:00 – Putting the product ahead of quick money moves
27:26 – Why launch buzz doesn’t last forever

Links and Resources

The Great Falls of Boeing, Intel, and Apple from David Heinemeier Hansson's HEY World
Fizzy is a modern spin on kanban. Try it for free at fizzy.do
Record a video question for the podcast
Sign up for a 30-day free trial at Basecamp.com
Books by 37signals
HEY World | HEY
The REWORK podcast
The Rework Podcast on YouTube
The 37signals Dev Blog
37signals on YouTube
@37signals on X