Thank you for your comment Moritz. Here's a breakdown of your points: 1. Agile vs. Six Sigma: While they aren't directly related, both are implementations of a process. Agile focuses its processes on iterative development and flexibility, while Six Sigma emphasizes its process on defect reduction and marginal improvements. 2. Cloud Uptime: You mentioned cloud software not reaching "five nines" (99.999%). Many do, although it's an aspirational goal for most providers. The linked paper below offers interesting insights on measuring cloud reliability. Nines are not Enough, Meaningful Metrics for Clouds. research.google/pubs/nines-are-not-enough-meaningful-metrics-for-clouds/ 3. Agile Adoption: Agile remains the dominant methodology in software development, with research indicating a 71% adoption rate among software development teams (January 2024). www.businesswire.com/news/home/20240116199385/en/17th-State-of-Agile-Report-71-Use-Agile-in-their-SDLC-Small-Organizations-Report-Strong-Business-Benefits-Medium-and-Larger-Sized-Companies-Continue-to-Experience-Barriers-in-Successfully-Scaling-Agile You are right to think that new (process-centric) approaches are emerging and that Agile isn't a one-size-fits-all solution. 4. "Do it (GTM) at scale": I completely agree with your point about GTM lacking a strong process-centric approach. This is an area I'm actively seeking solutions for. Implementing repeatable processes, measuring performance against them, and making incremental improvements can be a great starting point. While achieving "five nines" might be aspirational for GTM at this stage, aiming for a goal like one nine, as in 9%, could be a valuable step towards increased consistency and efficiency. Moritz, I appreciate you taking the time to share your perspective, which undoubtedly helped other readers enrich their understanding of the topic. A healthy discussion about these subjects is valuable, and it seems we share a passion for challenging conventional thinking and driving innovation.