This item will probably be picked up in the e-learning newsletter circuit, so it's important to flag it as bad advice based on a misconception of interative design. The author depicts iterative design as bad design made better through a process of user testing, a methodology easily parodied ("Designer: Your back tire blew out when you were going at sixty miles an hour. Hmm … We'll have to solve that one in the next iteration.") But iterative design involves the gradual introduction of new features, not gradual improvements in design - the idea is to introduce and perfect each feature before moving on to the next. Sure, if you are planning to implement a known and limited set of features, these can be added as a unit. But if you are adding novel and untested features (as I am on OLDaily), it is important to assess how each affects the site as a whole before moving on.
Today: 2 Total: 21 [Direct link] [Share]
