TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> <<...wizards are an effective way to help users perform tasks, but
> the wizard implementations I've seen don't really teach people
> how to perform the task without the wizard's help. Further, a wizard
> doesn't teach the underlying concept; it just steps the user through
> the task.>>
>
I've never had a problem with wizards not teaching how to accomplish a
task, or not teaching underlying concepts. If the wizard does the job,
that's all I need. If I need to go beyond the wizard, then I learn how
to do so, but I'm no worse off than if the wizard wasn't there in the
first place.
I think that worrying about teaching people is only a concern from a
writer's viewpoint. We feel compelled to do so. But from the user's
perspective, having to learn something is an obstruction to getting
their work done.
