Against form follows function An Essay by Andrea Resmini andrearesmini.com I cannot get past the fact that any *designer* who throws that phrase around matter-of-factly, as in “of course form follows function”, comes out as a complete ignoramus. An ignoramus who's not just repeating an 1896 “law” without any clues as to what it means but who also, most poignantly, demonstrates to possess no knowledge of what has happened in design and architecture since Sullivan and Adler contributed to inventing the high rise building and, by extension, much of the world we live in. Useless work on useful thingsForm follows functionForm follows failure formfunctionarchitecture
So that you can get feedback on it and make it better Fascinatingly, one of the other big complaints people had about agile is no iteration. I don't understand how being in an agile environment makes people less iterative, but somehow that seems to be the case. And I think it's because people misunderstand and think that agile is just about putting features out faster, and not about the important part, which is getting something in front of users faster so that you can get feedback on it and make it better. Laura Klein & Kate Rutter, Problems With Agile UX The most rewarding iterationsTo anticipate all the uses and abuses agileiteration