Embedded Files
This is an Introduction to Technical Communication video presenting concepts such as purpose, audience, and genre, which you need to understand before you create your own documents. This video is foundational and provides definitions and examples geared to give you a basis for technical communication knowledge.
Run time: 13.52.
This video explains audience expectations, formatting, and organization for both digital and print workplace correspondence, including letters, memos, emails, texts, and IM. It focuses on rhetorical situations which should be identified before writing to ensure that you provide need-to-know information for your intended recipients. Run time: 13.17
This is what I call a "walk-through" video which provides a discussion of student examples for the Job Materials assignment. I believe that it is important for you to see real materials produced by students, so you understand the expectations for assignments and see that you CAN create the materials for class.
Run time: 12.24
This video explores ethics and how ethics affects technical communication and the choices you make as you write technical documents. Ethics is often viewed as black and white/right and wrong, but often ethics is a grey area. As technical communicators, you need to realize the documents you create affects readers and industries in specific ways, which produce consequences- both positive and negative. Run time: 13.56.
Analyzing your audience and understanding the purpose of your documents is the starting point of your writing process. It is impossible to write and design an effective document if you don't research and analyze to whom you are writing since education, skill, and experience levels of your audience determine the language and content you include in the document and if your document is persuasive or informative. Run time: 6.24.
Writing for your readers focuses on organizing content, writing cohesive paragraphs, and constructing effective and clear sentences, which will allow the primary audience to comprehend content and take action. Technical writing uses plain language, defines jargon (if they are necessary), and preferences simplicity over complexity.
Run time: 9.59.
Technical communicators rarely work alone; in fact, more often, they work in cross-functional teams with engineers, marketing, administrators, and other technical communicators to write and design deliverables for the company and clients. Students need to learn how to function within a team to help them become successful writers.
Run time: 15.24
Technical communicators write different genres of documents, and one of which is proposals. Proposals pitch ideas, seek approvals and funding, or initiate projects. They are persuasive documents that can be either solicited or unsolicited, internal or external.
Run time: 11.21
Another technical genre is instructions which are a short form of documentation. Instructions require attention to detail, numbered steps written in the imperative, and graphics that show users what to do. They include definitions and descriptions of objects and tasks, provide lists of materials and tools, and are written for specific users.
Run time: 7.18
Technical writers don't just write text; they design documents to be useful and usable. To design effectively, the principles of design (grouping, balance, contrast, alignment, and consistency) should be followed. Just as with the actual content, design elements depend on the specific audience of the document.
Run time: 8.27
The cliche "a picture says a thousand words" is accurate, and technical communicators need to create images, graphics, illustrations, charts, and tables to effectively present information. Simply writing all content out into paragraphs is not sufficient since users prefer to scan for the content they need.
Run time: 7.02
Page updated
Google Sites
Report abuse