Jason Fried, Co-founder and CEO of 37signals, discusses building and shipping the new HEY Calendar product. Topics include why they built a calendar, their approach to new product development, deciding on scope before launch, the role of Shape Up, working on one feature at a time vs. in parallel, early project cycles, starting a new project with design, decision-making and finding confidence, achieving clarity in project goals, and the current state of Hey Calendar development.
The development of the Hey Calendar started with design and experimentation, exploring different UI concepts and aiming for novelty.
The team focused on creating surface area and trying out different features, embracing imperfection but having confidence in the overall direction.
After the launch of the Hey Calendar, the team plans to dedicate the next six weeks to bug fixing and addressing customer feedback, following the shape-up method for continuous product development.
Deep dives
Early stages of the project
The development of the Hey Calendar started with design and experimentation. Sketches were drawn and UI ideas were explored to find a direction for the product. The focus was on creating novelty and trying out unusual concepts. The team spent weeks working on the design, making iterations, and sharing ideas. There was no code at this stage, just the exploration of different UI concepts.
Iterative design process
The team aimed to build confidence in a direction during the first cycle of development. The goal was not to finalize everything but to pick a direction and start moving forward, knowing that changes and improvements would be made along the way. They embraced the fact that parts of the design would be right and parts would be wrong, and they were open to iterating based on feedback and insights gained throughout the process.
Progress and decision-making
The development process included making decisions based on the best ideas explored during the early stages. The team focused on creating surface area and trying out different features. They didn't limit themselves to one design version, but rather aimed to pick the best approach and iterate from there. There was an understanding that not everything would be perfect, but confidence in the overall direction was important.
Timeline and project scalability
The Hay Calendar project started in early February, with initial designs and experimentation. The development process involved multiple iterations, and as the project progressed, more team members joined. The project was scoped to fit within a six to eight-week cycle, ensuring that progress was made without spending too much time on any one aspect. Surface area was prioritized over perfection in the early stages, allowing for quick exploration and idea generation.
Post-launch plans
After the launch of the Hay Calendar, the team plans to dedicate the next six weeks to bug fixing and addressing customer feedback. They anticipate dealing with performance issues, missed features, and improvements highlighted by users. The development process will shift to a more structured approach, following the shape-up method for continuous product development and maintenance.
37signals have talked a lot about how they build new features for existing products using Shape Up, where they carefully hammer the scope to avoid letting anything ever drag on for more than six weeks. But there's not a lot of information out there about how they approach new product development, where it can take over a year to actually get the first version out the door.
In this episode, Adam goes deep with Jason Fried about building and shipping their new HEY Calendar product, and whether or not Shape Up was part of that process.
Timestamps
(00:00) - Building the HEY Calendar with Jason Fried
(01:04) - Why build a calendar
(04:12) - How 37signals approach new product development
(07:30) - Deciding on scope before launch
(13:13) - Was there a six-week version of the HEY Calendar?
(15:38) - Deciding how much time to spend on a new product
(17:46) - Was the HEY Calendar built using Shape Up?
(22:20) - Working on one feature at a time vs. in parallel
(28:47) - What cycles look like at the early beginnings of a product
(38:49) - How a project starts
(45:46) - Increasing surface area vs. finishing things
(47:57) - The development process for HEY Calendar going forward