Refining before release

What It Covers

Jason Fried explains 37signals' approach to finalizing Fizzy, their new product, covering authentication decisions, onboarding design, team structure changes, and why they reject roadmaps in favor of real-time customer learning.

Key Questions Answered

• •Authentication simplification: 37signals switched from their traditional Launchpad system with passwords and two-factor authentication to magic link authentication via email, reflecting changed user expectations and reducing complexity for both company and customers at launch.
• •Onboarding timing strategy: Product interface videos and walkthroughs must wait until final design decisions are made, even if this creates last-minute scrambles, because material changes like button repositions invalidate early documentation and waste production effort.
• •Feature withholding based on data: The FizzyAsk AI search feature exists internally but won't launch publicly because new users lack sufficient data to make it useful. Features should only ship when customers can actually benefit from them, not to showcase capabilities.
• •Roadmap rejection philosophy: Companies should sell products based on current capabilities, not future promises. Roadmaps create false obligations to outdated ideas and prevent teams from responding to real usage patterns and emerging customer needs discovered post-launch.