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.
Therefore, it is not always fiscally prudent for corporations to spend a
gajillion dollars on hiring tech writers to sit around all day dreaming up
rock-solid documentation processes and designs.
"Rock-solid" designs are better than poor designs. And, provided the
end-user goals & tasks have been properly analyzed, excellent design does
not take long.
I agree with your point that a lot of time can be spent "dreaming up" ideal
processes. The answer may be to think in terms of deliverables - not so
much the processes that develope them. Processes needed vary (sometimes
radically) from organization to organization. Deliverables not nearly so
much. Deliverables provide early project matrices.