I lost it when I saw requirements as a cornerstone. There are no requirements - it's all design. The word 'requirement' is an artifact from processes where you

I lost it when I saw requirements as a cornerstone. There are no requirements - it's all design. The word 'requirement' is an artifact from processes where you have handoffs from one group of people to another rather than integrated discovery and coding. When you look at things as requirements you lose the fact that most things are negotiable and should be negotiated in service of the ultimate design. Beyond that, it's worth noting that when the same people go from idea to A/B testing to full production the idea of a 'requirement' seems quaint.