I don't think Steve is so much referring to the "wizard" concept here, but things that just make the product easier to use. His comment on removing the need to re-create the database exactly as it was created, grown, shrunk, etc. is a great example. I still remember having to script out a database create script against the original database so I could restore it later. Moving the database files on restore is another example. Neither of those are wizards, just ways that make restores less painful. In the original article he mentions the idea of including useful error messages in the alert e-mails. MS has made some progress in these areas - SSIS logging now exists at a some level. However, there are many other little areas that remain frustrating for the accidental DBA or for someone who does these tasks, but infrequently.

I tend to agree for the most part about wizards. They're useful, but once you have some idea about what you're doing, you'll generally not use the wizards or not use them as often. For someone who's new or doesn't know what they're doing and just need the box to run - they serve a useful purpose.