RPDO staff revisit forte at tech writing

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
 

tech writingCOTABATO CITY (Jan. 10, 2014)— Staff-members in the tutelage of mid-level executives briefly revisited today their own forte of technical writing, albeit in more collective ways at relearning, and even unlearning some traditional practices in the trade.

Executive Director Baintan Adil-Ampatuan of the Regional Planning and Development Office said she wants her staff to be more technically competent, through continuing staff-development activities in terms of training and in their day-to-day official functions.

Thus, the RPDO hosted for its staff-members an in-house refresher on technical writing, during the third of a series of Writers’ Forum Workshop at the RPDO Conference Room here on Friday.

A participant shared with the group a rather more philosophical view that, “Technical writing is sometimes defined as simplifying the complex.  Inherent in such a concise and deceptively simple definition is a whole range of skills and characteristics that address nearly every field of human endeavor at some level.  A significant subset of the broader field of technical communication, technical writing involves communicating complex information to those who need it to accomplish some task or goal.”

Journalist Nash Maulana, a resource person, delved on explaining and rationalizing formats as well as the importance of “established facts” as a primary element of technical writing. He said more than “available facts” and “gathered facts” which journalists usually need in news writing, obtaining “established facts” essentially support the technical writers’ efforts at harmonizing or matching “objectives” with “desired outputs” in more complex technical proposals.

He added that: knowing “what to write” straight from facts makes the writing job easier and relatively faster even for beginners.  

Just like in more inclusive publication articles, test questions in exclusive office communication and other forms of technical writing, should be: 1) is the narrative or office communication written to be easily understood by other parties of exclusive readers?; 2) can it be appreciated by an exclusive party of readers?; 3) will it best represent the office when read by concerned persons within the organization and in other offices, as well?; 4) is the writer being concisely informative with paragraphs?, and 5) can the writer be honest to assure the exclusive reading parties that nothing in the work comes from plagiarism, rephrased from other sources or is copy-pasted verbatim without proper attribution?   

“It was a very fruitful day for the participants for they know that technical writing is part of their daily work in the office, and queries regarding technical writing were addressed properly by the resource person,” another participant said. (HEU of RPDO-ARMM)

Archive

Powered by mod LCA