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.
Betsy Pfister said:
>Haha! Welcome to the "Level 0" nightmare.
Keep in mind that the "Level 0" nightmare is self correcting. Miss a few
ship dates and the people in charge will lose their jobs--provided you are
in a "performance-based" organization.
But, if you cannot wait that long, you might want to consider specifications
to be unneccessary. If you are experimenting with the application, you
should be able to identify all the entities exposed in the UI. And, you
should be able to identify the functionality exposed in the UI. These things
contribute to the user's conceptual model. Outside information is only
necessary when the application deviates from the user's conceptual model.
But, the application should NEVER deviate from the user's conceptual model.
If it does, then consider that deviation a bug of the highest order, and
don't let the product ship. This will drive negative use costs to the moon.
And, no amount of wallpaper (documents) will be able to paper it over.
If I have to ask you how it works, its broken. Period. Spec or no spec. SME
descriptions or not.
