June 19, 2007, 10:56 am
IA and the Agile Approach
By Lisa Agustin
Earlier this month, Fastcompany.com plugged the agile development approach that was used to redesign its home page. The approach in a nutshell, according to blogger Ed Sussman: “Vision, release, test, iterate. Repeat. Quickly.” Speaking metaphorically, think of design and development as a washing machine, not a waterfall. The organization initially planned to release the new design as part of a larger effort that encompassed new features and functionality. But in the end, they decided against it:
What if we had waited to get it all just right before we released FC Expert Bloggers? We’d still be in the dugout. We’d have been guessing instead of seeing what the market actually thinks. In an effort to make our product perfect, we probably would have been forced to spend loads of money fixing problems that might not have mattered to our readers.
The agile approach is one that certainly has its benefits — it’s flexible and means users get to see the latest features sooner, without waiting for an annual update. But in order to be successful, an agile approach still has to start with stakeholder and user requirements that are validated through an information architecture, design, and development process. Only then can an organization be sure its site’s “killer widgets” are truly meeting the needs of its audience.