This client effectively uses a wizard to make sure all those steps are performed in the appropriate order. When a Wizard May Not Help Wizards are not a panacea. They can't fix all interface or usability problems. We've even seen cases where the wizard itself caused more problems than it solved. Furthermore, creating a wizard is not trivial.
Wizards are software, with all the associated up-front development costs.
The payoffs, in the form of reduced support and training costs, don't come until later. For example, when we tested the Table Wizard in Microsoft Access, one user told us he knew too much for the wizard. I would have had it done a lot sooner if I hadn't used the wizard. I was already doing what it was going to do for me. When it Doesn't Solve the Problem With the advent of Windows 95, wizards have become much more prevalent.