Most of us have built and reviewed and rebuilt intranets using Waterfall project methodologies. It’s the process of understanding all of the requirements and risks first, developing specifications to describe them, and then implementing the solution. Using this approach, however, typically results in late and over budget intranets. This is because intranet projects are often plagued with changing requirements, unanticipated integration challenges, and usability annoyances that are difficult to accommodate in the fixed scope of the project
I can’t tell you how strongly I agree with the recommendations here – its one of the reasons I’ve been a fan of the MIKE 2.0 methodology, to help break that waterfall approach failure cycle with not just intranets projects but any kind of information management, knowledge management or collaboration system implementation.
BTW I couldn’t find the original article, so hat tip to Matthew Hodgson for sharing it.