Wondering where technical communication is headed, in 2010 and beyond? Sarah O’Keefe, Ellis Pratt, and Tony Self offer their insights.
There are plenty of definitions regarding Rapid e-Learning. A lot of them are variations of strange theories. But, I have only one definition:
“Rapid e-Learning is the development of learning courseware within a short timeline, which is achieved using basic templates which form a static framework and contains the learning content.”
This implies that not much time is spent on creating complex and pretty animations and interactions. There is debate aplenty in e-learning circles and many people may consider e-learning not valid unless it has a high level of interactivity, pulsing text and images and other bells and whistles, such as nonsensical games. Anything less may be considered as boring click-and-read material. All this just adds extra time (lots of it) and extra expense.
It is easy to disguise poor instructional design with slick effects and animations. However, a lot of this stuff is neither necessary or effective and I believe all these repetitive flying, flashing texts and images can trigger extreme irritation.
According to the United States Department of Labor (DOL), the official description, written years ago, of the technical writer’s responsibilities is the following:
“Write technical materials, such as equipment manuals, appendices, or operating and maintenance instructions. May assist in layout work.”
Today, communication covers much, much more. STC members do much, much more. Their work is dynamic and interactive. The old definition isn’t nearly broad enough.
Read the original article at http://www.stc.org/story/tc_tw.asp
I bring this article to you courtesy of Gryphon Mountain Journals, as I think it adds enormous pertinence to what I do. You may view the original article here.
In our ongoing department reorganization, we technical writers are experiencing some angst as we carve out a desirable place for ourselves. However, as we’ve talked about it as a community of practice (no longer as an organized team with our own manager), I think we’re coming to an agreement that now is the time to make things happen—to strike, as Tom likes to say.
I bring this article to you courtesy of UXmatters, as I think it adds enormous pertinence to what I do. You may view the original article here.
Making the Deal: Supporting Product Demos with User Assistance
By Mike Hughes
Published: August 23, 2010
I bring this article to you courtesy of Forbes.com, as I think it adds enormous pertinence to what I do. You may view the original artical here.
Aaron Fulkerson, 08.09.10, 12:00 PM EDT
Product and services documentation is now a core business asset that can drive revenues.
When people in technology hear the word “documentation” it conjures images of the ’90s, when software shipped on CDs, in boxes, with thousand-page user manuals that were costly to create and bordered on useless to the end user. The teams authoring those materials have been viewed as a cost center, and their products only minimally satiating customer demand for product documentation.
The First Help Desk Call
What is Technical Writing?
Technical Writing in South Africa is, in my opinion, very much in its infancy.
In my time as a self-employed contract Technical Writer, I have come to realise that some software development houses would appear to regard a Technical Writer as not dissimilar to that of a glorified typist who would produce something resembling a user manual. The practice of delegating the production of a user manual to the developer or to the marketing department is also one that is used quite often.
Just when you thought Technical Writing was a function that only specialists did, then they go and create a musical. Have a listen to the “The Technical Writer Song”, a video created by an unknown technical writer.