A discussion of lean/agile methods for Web site development explains that lean/agile combines the best practices of manufacturing (with team empowerment that would please an organizational development expert) and prototyping acceleration. Many Web sites originated in an organic development process that relies on ad hoc development. However, there are drawbacks to the ad hoc approach, including lack of clarity in sponsorship, unpredictable schedules and expenses, transmogrification of requirements and drifting of overall project direction, and the high possibility of unpleasant surprises at implementation that result for risks overlooked during development. In contrast, software development life cycle (SDLC) and like methods rely on a thoroughly planned flow of activities directed by analysis and thought. Phases are predictable and common processes can be applied at each phase to increase the success rate. Each step creates a finalized work product that leads into the next step so that the project is completed linearly or in a waterfall approach. Scope is closely controlled, project management is monitored, and risk management is applied to each phase. Rapid prototyping, an iterative approach, makes project goals tangible, and a successful approach blends planning with speed arising from close focus on high-value functionality. A lean approach sets out to identify and eliminate sources of waste. As applied to Web site development and maintenance, the lean approach concentrates on jettisoning over-production and on careful inventory that focuses on functions that will make it to the final project. Lean also eliminates processing steps that do not add substantial overall value. Other targets are reduction of time wasted waiting for decisions as information moves up the chain of command, driving between locations for meetings, and defects (fixing bugs not found in testing).