After two years of using the Shape-Up methodology from Basecamp, Customaite decided to move on. Initially, they were attracted to Shape-Up's longer development cycles and focus on value-based prioritization, hoping to improve project delivery. The structure promotes 6-week cycles followed by 2-week cooldowns, aiming to reduce scope creep and encourage teams to focus on impactful projects. However, Customaite faced challenges with the appetite concept, which sometimes led to expanding work unnecessarily. They struggled with the methodology's rigidity, especially since many of their projects were smaller than the standard cycle size. This often forced them to plan multiple smaller projects into one cycle, hindering their ability to adapt and reprioritize. The cooldown period, designed to allow teams to address non-urgent work, became problematic. While it was intended to facilitate technical improvements, it often turned into a catch-all for tasks that didn't fit the main project focus. Urgent bugs and administrative tasks frequently encroached upon this time, diluting its purpose. The team also found that waiting too long to tackle smaller issues created latency and fragmented initiatives across cycles. The emphasis on strict focus sometimes stifled necessary work, as senior engineers struggled to manage important tasks while adhering to the rigid structure. Ultimately, Customaite recognized that their experiment with Shape-Up was more about addressing symptoms than solving underlying issues. As the team evolved and gained clearer product direction, the long cycles became a hindrance. They concluded that shifting back to shorter Scrum sprints with domain-focused teams would better suit their needs. Despite the decision to abandon Shape-Up, the insights gained about cooldowns and value-based thinking remain valuable for future development practices.