I agree with what you're saying here. Except what you're saying is the antithesis of what the article is saying. > The mistake you're falling into is that you'

I agree with what you're saying here. Except what you're saying is the antithesis of what the article is saying. > The mistake you're falling into is that you're assuming that this means that _everything_ has to be defined up front. But nobody's actually saying that. This article is entirely focused on the idea that sketching and wireframes are bad ideas. I fundamentally disagree with that. From the article: > The temptation is to jump straight into building mode, to write code or build wireframes or sketch drafts of what you want to create. The better idea is to write your idea down as a way to think it through and improve upon it. Then, when you start building, you’ll know exactly what to build, and why, and you’ll have pre-written documentation at launch.