Technical Writing
(28 reviews)
Annemarie Hamlin, Central Oregon Community College
Chris Rubio, Central Oregon Community College
Copyright Year: 2016
ISBN 13: 9781636350653
Publisher: Open Oregon Educational Resources
Language: English
Formats Available
Conditions of use.
Learn more about reviews.
Reviewed by Amine Oudghiri-Otmani, Instructor, Marshall University on 10/15/22
This text offers a good amount of instruction (though at times limited) underlying effective workplace and technical writing/communication. Having personally examined a number of technical writing materials, this is by far one of the very few... read more
Comprehensiveness rating: 4 see less
This text offers a good amount of instruction (though at times limited) underlying effective workplace and technical writing/communication. Having personally examined a number of technical writing materials, this is by far one of the very few texts that incorporate a section about texting. Freshman students will benefit from this introductory-level text and will appreciate the authors' emphasis on conventional technical documents including emails, letters, memos, reports, and proposals. The textbook, however, may not satisfy the needs of students in advanced technical writing courses looking for guidance on complex documents beyond the conventional ones identified here. Visual representation of information could be improved, and the organization of chapters could be more strategic. A separate section about reports with important introductory information, for instance, could precede the progress reports and technical reports sections.
Content Accuracy rating: 2
A full citation guide is not provided, which may not reflect well on the credibility of the authors and/or the accuracy of the information provided. The attribution information at the end of each chapter is the only reference provided, contradicting the authors' recommendation to support one's writing with material from outside research.
Relevance/Longevity rating: 4
Although the materials are relevant to orthodox technical writing contexts, the text could benefit from a separate section that introduces writing in the digital world to reflect the evolving nature and changing landscape of technical communication. As part of the additional section, for instance, the authors could discuss potential similarities/differences between documents produced traditionally (e.g., pencil and paper, in addition to those developed by means of regular Word processor) and those produced digitally using various contemporary media. Similarities and/or differences could be discussed in light of prose and rhetorical strategies, among others.
Clarity rating: 5
The authors use simple, clear, and easy-to-understand prose. After all, sentence structure in technical writing is expected to be short, concise, and to the point. This text fits under this category of direct and unambiguous language. In addition to the authors identifying and covering essential technical terminology, the reader will appreciate the combination of descriptive (i.e., regular declarative) and direct (i.e., imperative, instructional) language. The memo, for instance, "has a header that clearly indicates who sent it and who the intended recipients are," and the reader is asked to "always consider the audience and their needs when preparing a memo."
Consistency rating: 4
Consistency is off a few times throughout the text. At the beginning of the first chapter, "Professional Communications," for instance, the authors write, "From text messages to reports, how you represent yourself with the written word counts." In this first chapter, however, only texting, emails, memos, and letters are discussed. Reports are mentioned only briefly under the cover letter to a technical report section, but no prior background about reports is provided.
Modularity rating: 5
Consistent use of headers and special highlights (e.g., boldface, etc.) helps chapter sub-sections and other important information stand out. The headings and sub-headings minimize potential distractions or other inconsistencies in modular presentation of chapter content.
Organization/Structure/Flow rating: 3
Chapter organization throughout the text consists of introduction and discussion. A conclusion in which a general, targeted final reflection is provided, however, is missing. Although the same chapter structure is used throughout the text, which will help keep the reader focused as they navigate subsequent chapter content, the authors could discuss chapter presentation, structure, and framework prior to the first chapter. The introduction section could benefit from a few sentences previewing this across-the-board structure.
Chapter lineup could also be more strategic. The chapter "Ethics in Technical Writing," for instance, could go first before "Information Literacy" and "Citations and Plagiarism."
Interface rating: 4
Readers may be distracted by the number of blank pages at the end of chapters. Readers looking to print individual chapters with ample text on each page (or those simply interested in saving trees by minimizing the number of pages printed in multiple jobs) may be disappointed. Text navigation and individual chapter selection, however, are made easy thanks to the hyperlink attached to each line/item under "Contents." Readers looking to go to a specific chapter do not need to engage in much scrolling and are given the opportunity to jump straight to the specific chapter or chapter sub-section by clicking the link.
Grammatical Errors rating: 4
No grammar errors have been detected. The authors' occasional use of the "conversational" tone may not be an issue, especially in terms of deciding whether the language matches the universal, agreed-upon conventions of technical writing. The textbook being an introduction to technical writing is meant to provide a general overview of the field, and technicality at the clause level is not required. The latter is expected to be a feature of advanced-level texts. The authors, however, could consider adding a separate section that discusses style and tone (in addition to orthodox grammar/sentence structure error patterns like splices, fragments, etc.). That the language used in the text may not match the conventions of technical writing - in terms of style and tone - could also be emphasized.
Cultural Relevance rating: 5
Chapter 13, "Communicating Across Cultures," introduces the reader to the importance of considering the variety of cultures and culture uniqueness (and peculiarity) in technical communication, which I believe does the job. Advanced-level texts may delve deeper into the requisite component of culture and culture sensitivity in both drafting certain technical documents and deciding on the style/tone to be used, context dependent. This textbook subscribes to the general/introductory category in this (i.e., discussion of culture) respect.
Reviewed by Sylvia Hayes, English Instructor, Midlands Technical College on 7/26/21
This book is concise and covers an array of Technical Communication topics and genres. This text provides flexibility in the fact that it focuses on Technical Communication for a more generalized audience and therefore this would work well as a... read more
This book is concise and covers an array of Technical Communication topics and genres. This text provides flexibility in the fact that it focuses on Technical Communication for a more generalized audience and therefore this would work well as a Technical Communications text for a First-Year Writing course at a 2 or 4-year college. The organization of the section is not very logical, luckily most instructors do not use textbook chapters in order. The text could use more examples for students in the medical and legal fields. It could use more visual support within the chapters.
Content Accuracy rating: 4
The information presented in this text is accurate, error-free, and unbiased; however, there are no references to original sources for most of the content.
Relevance/Longevity rating: 5
The content of this text is written so students can use the information in many different technical communication settings.
Clarity rating: 4
The text is clear, the prose is accessible and it defines and provides adequate context for concepts college-level students may find unfamiliar. There are multiple instances of the text directing you to a hyperlink to another resource that explains the concept in more depth. However, the text does not model the level of clarity necessary for technical communication. There are various sections that are underdeveloped and need more graphics and examples.
Consistency rating: 3
Due to the sheer number of contributing authors, it is hard to create a consistent framework for the chapters. They each seem to be designed by the separate contributors in ways that make sense to them and are not uniform to the book. In terms of terminology, the text is consistent.
Modularity rating: 3
This text is broken up into sections and subsections, that can be assigned at different points within a course. As the organization of the chapters is chaotic, I believe most instructors would have to move sections around as assign them individually instead of starting at chapter 1 and working through the textbook.
Organization/Structure/Flow rating: 1
The organization of chapters is confusing. Why are citations in between Proposals and Progress Reports? Chapters refer to students learning of concepts found later in the textbook.
Interface rating: 2
Not all sections are set up the same, which makes it harder to navigate and find information. In some versions of the text, you can't see the graphics. You cannot search the text using normal search indicators "AND," "NOT," etc. this makes searching this text much more difficult than some others. Why are there so many blank pages in the PDF, if someone was to print the text they would waste about 1/4 of the pages.
Grammatical Errors rating: 3
There weren't any noticeable grammatical errors. The sentence structure is varied, however, there were some long, wordy, confusing sentences. The tone is very casual and not professional.
Cultural Relevance rating: 3
There is no culturally insensitive or offensive language in the text, however, the text is not inclusive of a variety of races, ethnicities, and backgrounds in its examples or images.
Reviewed by Mary Larsen, Instructor, Pittsburg State University on 5/14/21
This textbook highlights important components of technical writing, including various forms of technical writing in the workplace and also approaches to audience analysis, graphics, and ethics within the writing of these documents. This text also... read more
Comprehensiveness rating: 5 see less
This textbook highlights important components of technical writing, including various forms of technical writing in the workplace and also approaches to audience analysis, graphics, and ethics within the writing of these documents. This text also includes information about resumes and employment, which is very applicable to technical writing and provides readers with a dual layer of content.
Content Accuracy rating: 5
Content within this text is accurate and mostly error-free. The content is based off of multiple authors rather than one single-viewpoint, which provides additional insights into topics versus only one limited view. Content is cited and derived from David McMurrey, who has experience and a plethora of knowledge in all aspects of technical writing.
The text is relevant to writing in the workplace as it covers aspects of "netiquette," which is something technical writers will encounter more and more as workplace functions are moved more to online formats. The formats covered are also frequently used forms of communication in the workplace, such as email, letters, memos, proposals etc. This provides a large scope of relevant documents that readers could encounter when writing in the workplace.
This text is written in plain language and easy to read. Content is sectioned off pretty well for easier readability and there were few, if any, areas of jargon or overly technical language. Tips are provided in various sections that assist readers in actually applying the content.
Consistency rating: 5
How text and visuals are presented and the sense of organization of various chapters and sections are all consistently presented within.
Modularity rating: 4
Subheadings are used within for easier readability; however, content is text-heavy at times. Content jumps around some, but is otherwise organized into a logical progression of points (such as discussing audience and types of documents in the beginning and saving design and employment content for later in the text).
Organization/Structure/Flow rating: 5
The organization follows a logical progression of ideas and concepts that would be presented within a technical writing course. The Table of Contents includes easily recognized sections and page numbers and each new section is noted at the top of the page. At times the images presented conflict with the text and spacing on pages, but is otherwise easy to attribute to the content pertaining to the image.
Interface rating: 5
Some of the images / videos are pixelated. The textbook includes links to videos and images that further touch upon the concepts of a chapter, which is very helpful and engaging. Images link to direct PDF files for easier access of a document. Seems to be some unnecessary space left on pages or between section changes.
Text is mostly free of grammatical errors, although a few minor grammar mistakes were present. For example, "insure" is used instead of "ensure" in Section 3.7.
Chapter 13 of the text is "Communication Across Cultures," which lends to its response to cultural sensitivity. The text seems to keep in mind readers of various races and backgrounds and uses relevant pop culture references that are inclusive. If anything, the textbook could incorporate aspects of gender in relation to technical writing in the workplace.
This textbook covers most all of the content I currently use in my own technical / professional writing courses and I am considering adopting this textbook in future courses that I teach.
Reviewed by Bjorn Smars, Career Instructor, University of Oregon on 7/2/20
As far as I can tell, this textbook does not include an index or glossary. However, each chapter is broken into separate sections with descriptive titles and headings, so navigating to specific concepts and ideas is not difficult without the use... read more
As far as I can tell, this textbook does not include an index or glossary. However, each chapter is broken into separate sections with descriptive titles and headings, so navigating to specific concepts and ideas is not difficult without the use of an index. My only complaint about this text, at least in regards to its comprehensiveness, is that many of the sections or pages are underdeveloped or do not contain sufficient explanation and/or examples to illustrate important concepts. For example, the chapter on communicating across cultures provides useful tips that students can use to think critically about cross-cultural communication, but these suggestions are limited in that they are designed to apply broadly to most situations in which cross-cultural communication occurs and therefore do not offer clear guidelines or practical strategies for students to learn about and identify a particular culture's communication norms.
As far as I can tell, the information presented in this text is accurate, error-free, and unbiased. The purpose of this textbook is to serve as an introduction to technical writing, and as such is designed to provide students with practical strategies for engaging in effective technical communication.
As I mentioned in an earlier comment, most of the content in this textbook is written in such a way that it can be applied practically and broadly to a variety of situations in which students may find the need to engage in technical writing and/or communication. The focus is more on providing practical strategies and helping students develop critical thinking skills than it is about using a particular software.
The prose is clear and accessible to college-level readers, and unfamiliar concepts are either defined in-text by the textbook's authors or via hyperlink to another source. For example, in chapter "13.2 Understanding Cultural Context," the authors provide a link to a YouTube video that explains the differences between high-context and low-context cultures in more depth.
The textbook uses consistent terminology and frameworks throughout.
As I mentioned in an earlier comment, the organization of the textbook is easy to navigate and understand. Each chapter is broken into separate sections with descriptive titles and headings. My only complaint is that there is some inconsistency between the lengths of each chapter's subsections. Some sections are very short (150-300 words max) while others are much longer, ranging in the 2,000-3,000 word range. That said, each section is clearly labeled, and the headings are highly descriptive.
See previous comment.
Each chapter's subsection has navigational arrows that allow the reader to move on to the next section easily, and the table of contents is easily accessible on every page. However, locating the table of contents may not be intuitive for some students, and some students may not know how to navigate through each chapter's subsections.
Grammatical Errors rating: 5
I did not notice any grammatical errors.
Cultural Relevance rating: 4
As I mentioned in an earlier comment, this text could provide more examples to help students better understand cultural differences in terms of communication. More examples that are relevant to students attending one of Oregon's many colleges or universities would help to illustrate these cultural differences and provide students with a practical, real-world strategies for engaging with their peers, professors, and other folks from other cultures and/or regions.
Overall, I found this textbook very useful, though I had to supplement much of the information either with links to other sources or with material I developed personally. It's a useful and accessible introduction to technical writing for most undergraduate students, but it is not a comprehensive document and therefore may require the instructor to provide additional information or resources.
Reviewed by Elizabeth Aydelott, Part-Time Instructor, Lane Community College on 6/26/20
This text covers almost every topic that I would cover in a Technical Writing Class for generalized studies. A class geared toward a specific aspect of the field - engineering or a medical field, for example - would need to add material. This text... read more
This text covers almost every topic that I would cover in a Technical Writing Class for generalized studies. A class geared toward a specific aspect of the field - engineering or a medical field, for example - would need to add material. This text provides a solid basis for any course in technical writing, though.
The information is accurate, the citation guide up-to-date, and most material is relevant to any aspect of the field.
The content is almost all up-to-date. I would suggest adding a section on conference calls in the chapter on Professional Communications. That format has its own specific netiquette rules, ethics, and audience considerations. And conference calls, in a variety of formats, are increasingly essential to the working life.
Clear, common sense prose. The beginning of each chapter should probably be titled "Overview" or something similar, perhaps with a brief outline, for more clarity.
The book's structure changes with each format. I suggest that the instructor designate a preferred version for the class. Within the text, however, it becomes fairly easy to navigate through the material.
This text would be easy to assign in appropriate chunks for the students.
The text has a logical order, but I would assign the last chapters first since I usually begin with employment application materials and then cultural awareness almost immediately afterwards.
Interface is fairly straightforward and clear. Some of the videos, particularly in the beginning, are a bit referential to a specific course rather than to the topic in general.
Grammar has no problem. I wish, though, that a general chapter on grammar was included for the students.
I really appreciated the chapter on Communicating Across Cultures, but I wish it had been included earlier in the book. Perhaps a reference to Cultural Literacy within the chapter on Audience.
I'm confused about why the Open Textbook Library lists the book with only one author instead of the seven listed in the book itself.
Reviewed by Christopher Schott, Assistant Teaching Professor, University of Missouri - St. Louis on 4/23/20
This book really does cover a great deal of ground. However, I found the pacing and the organization of the section to be a little sporadic, especially if the book were to be read linearly by students. This may not be a serious concern as,... read more
This book really does cover a great deal of ground. However, I found the pacing and the organization of the section to be a little sporadic, especially if the book were to be read linearly by students. This may not be a serious concern as, especially in a digital format, the book can be navigated easily from topic to topic. Many chapters are short (some are quite detailed, though), which can be a real asset, but the lack of technical writing theory might be a concern for instructors looking to balance practice with understanding approach. While the book does cover a great of texts that are useful for students studying engineering and computer science, it may provide fewer examples and cover less in terms of students looking for technical communication instruction in medical fields, journals, legal fields. Another issue, when it comes to comprehensiveness, is the lacking of exercises and assignments. For my own teaching, this is not an issue (I try to craft assignments that fit the culture of my students' academic programs), but I could see it limiting the use of this book for other professors who would like corresponding assignments and readings.
As a reader, this book seems unbiased to me. That said, there are some prescriptive outlooks on crafting documents that may lead a reader to believe there is a one-size-fits-all way to compose a text. For example, there is a recommendation that emails are limited to three paragraphs, which is a very narrow view of that genre (shouldn't it depend on the rhetorical context, audience, etc.?). Overall, the content in the book appears accurate, even if a little prescriptive at times. However, this can be remedied through instruction from the professor.
The information that is presented in this book is very similar (and in some cases, exactly the same) as the information I've been teaching for the ten years I've been teaching technical communication. Some concepts in this course, such as audience, purpose, tone, precision--these will forever be touchstones of any professional writing course, technical writing is no exception. I very much am happy to see a chapter on information literacy, which is honestly and unfortunately absent from a surprising amount of existing (and expensive) technical writing textbooks. Some of the information does seem to not work (some links, for example), which may hurt longevity, but the authors do note this might be a possibility when using the book.
This book is clear. As a technical communication text, I would hope it would be and I was happy to see the authors not utilize jargon, instead stick to very explicitly presented ideas, sentence structure, and offering simple language that will appeal to readers, make them feel smart, all while retaining the level of academic rigor a text like this needs.
The chapters in this book are all formatted relatively the same. This offers readers a consistent and predictive reading experience (which, in itself, is a valuable technical communication skill). Each chapter starts with a very useful introduction, leading nicely into the rest of the chapter. There are, at times, inconsistencies in how thoroughly topics are treated and covered, but that is to be expected with many textbooks.
This text seems to be designed for purposeful fragmentation in a course. By this, I mean that the text does not have to be read linearly to be useful for students. In fact, and this is something the authors may have had in mind when writing, but most textbooks are not read and interacted with linearly anyway. Chapters are skipped, brought back, and revisited. I think this is just fine and, in many ways, provides a more fruitful reading experience.
Along with the previous idea of Modularity, I do not think the text is perfectly organized. One could argue that a textbook should move from more simple to more complex concepts. However, I disagree and do not think this needs to be the case. Instead, while the chapters here might seem a bit out of order in terms of their "difficulty," to do seem to be ordered nicely in terms of some theoretical understanding (though, very little) into more genre-based writing. Because the text can function in ways that benefit the class, this is not an issue.
The book is incredibly easy to navigate and use. Some links are broken, which can be frustrating, but it doesn't distract from the usefulness of the book overall.
I did not notice any grammar and mechanical errors in the text.
Despite an opening comment in the Introduction that claims students will learn to write "in such a way that even Grandad can understand," a which is a bit insulting to grandpas everywhere (it's ageist), the book seems to be culturally respectful and appropriate. I am a big fan of the cultural sensitivity section in the book, which I think is very carefully and thoughtfully presented to readers. There are topics that can be included that were not. In technical communication, it's important to remember that standards are always changing in business and this will undoubtedly shift the way professionals communicate, interact, and write. For example, a section on language inclusivity would be useful.
I'm grateful for this book. The authors have really put together a text that is useful in terms of what it can do in different kinds of technical communication classroom. I've seen many different kinds of technical writing courses and they are all taught differently. It seems this book has the unique ability to fit many different kinds of teaching styles, learning environments, and student abilities--and the book's design and functionality allows for professors to be very malleable in their pedagogy.
Reviewed by Brian Ballentine, Professor, West Virginia University on 4/20/20
The book is being reviewed the book in the web PDF format. At least one other reviewer has noted that there are inconsistency issues across various formats in which the book is offered. The web PDF format functions as expected in Acrobat reader... read more
Comprehensiveness rating: 2 see less
The book is being reviewed the book in the web PDF format. At least one other reviewer has noted that there are inconsistency issues across various formats in which the book is offered. The web PDF format functions as expected in Acrobat reader with the sidebar thumbnails and toc providing hyperlinks to specific pages and sections. This format does not have a much-needed index or glossary. The book does not have the same comprehensive content that a student would find in one of the large, mainstream, and admittedly costly technical communication texts by authors like Markel and Selber, Lannon and Gurak, or Anderson. There isn't enough or any coverage on important topics like instruction sets, technical procedures or definitions, user experience testing (including testing instruction sets and other technical documentation), and oral presentations. Documents like instruction sets are mentioned but only in passing. E.g., "Examples are one of the most powerful ways to connect with audiences, particularly in instructions" (2.3). There is content on preparing PPT slides but no content on giving a presentation.
The content does not cite original sources. Each chapter and even sub-section has author attributions for the book itself but rarely does it reference external sources. This becomes particularly obvious for writing instructors in parts of the book like chapter 14 that contend with genre, genre analysis, and genre systems but with no references to the writing scholars we attribute to genre studies (Miller, Bawarshi, Russell). This is not to say that the content is automatically inaccurate but one of the points the authors themselves make about the need to cite sources is the importance of using those sources to build confidence in the audience.
Relevance/Longevity rating: 1
The book opens with content on texting and email but then largely abandons digital communication platforms. Again, in larger technical communication textbooks instructors would expect to find chapters dedicated to "blogs, wikis, and web pages" and "social media" platforms as in offerings by Lannon and Gurak. A more contemporary text would no doubt include online collaborative tools and meeting platforms like Slack and Microsoft Teams. The recommendation here would be to create a separate chapter or chapters dedicated to technology platforms with the idea that it would be easier to update in the future.
Clarity rating: 2
The writing is more conversational than professional. The book does not model the level of clarity needed for technical writers. E.g., section 9.2 on "Presentation of Information" begins with a longer paragraph that attempts to summarize the space shuttle Challenger disaster as an example of why clear communication is important. The textbook authors write: "Possibly the engineers were just poor writers; possibly they did not consider their audience; or possibly they did not want to look bad and therefore emphasized all the things that were right with the Challenger. (Incidentally, the O rings had worked fine for several launches.)" Edward Tufte's now famous case study of the Challenger contradicts this summary. The rocket company and its engineers did indeed make a no launch recommendation (their first in 12 years) precisely because they had data showing the O-rings failed in cold temperatures. It is moments like these in the textbook that give me pause.
Consistency rating: 2
The multiple authors on this textbook likely pose challenges for creating consistency across the project. For example, in the chapter dedicated to Proposals, the first section is titled "Some preliminaries" and it offers a narrative overview of proposals and the roles they may play. In the chapter dedicated to "Progress Reports," the first section offers "functions and contents of progress reports" that has just two bullet lists. Students like to become acquainted with a consistent format across a book's chapters so they know where to find answers/resources that they need, regardless of the topic.
The textbook does contain self-referential content but overall the chapters could be used in a modular fashion to supplement other learning materials/readings in a technical writing course.
Organization/Structure/Flow rating: 2
Even if the textbook was designed to be modular, it is still prepared and presented in a specific order (with linked toc in the PDF version). Concepts of genre and genre analysis are presented as fundamental to understanding the writing process yet they come at the end of the text. Audience analysis comes much earlier (chapter 2) but not before texts, emails, and netiquette. Proposals are in chapter 3 but information literacy, including instruction on how to begin research for a proposal isn't until chapter 4. Organizing a textbook toc must be incredibly challenging but there are many models out there that overcome some of these organizational challenges.
Interface rating: 3
The PDF version of the textbook works as expected in terms of the links in the toc and the thumbnails visible in Acrobat. It can be challenging to orient yourself in the text especially because there are many pages with minimal content. The PDF version has 242 pages but I would recommend to students that they only print selectively as many pages are blank.
Despite having many authors (and some open source content), the book does not have an abundance of grammatical errors. As mentioned before, the more casual tone of the textbook does not help with modeling technical and professional communication. There are grammatical issues (or perhaps more stylistic issues) that could be edited. E.g., the book uses the opening phrase, "In other words..." ten times throughout the book. Overall, though, the book scores high in the grammatical category.
Chapter 13 is dedicated to "Communicating Across Cultures" and offers students an overview of "culture" as a term as well as some important guidance on global communication. The book does break some of its own advice in these sections with references to authors with no attribution. E.g., "Geert Hofstede views culture as consisting of mental programs, calling it softwares of the mind, meaning each person 'carries within him or herself patterns of thinking, feeling, and potential acting which were learned throughout their lifetime.'” This chapter could make more specific references to technical communication and globalization. A longer paragraph in 13.4 on intercultural communication uses sheep as an example when there are so many ways to talk about the importance of good technical writing in support of technical products and services when they go global.
I would like to thank all of the authors as well as David McMurrey for their efforts in writing and editing this open source textbook. I will likely use chapters or sections to supplement other course materials in an effort to save students money on textbook costs. It may be possible to pair chapters from this textbook with one of the smaller "handbooks" on technical communication out there. While the ratings here aren't overly high, the standard of comparison was challenging. I am looking for options to supplant one of the large, mainstream technical communication textbooks and that is a high bar.
Reviewed by Lars Soderlund, Associate Professor of English, Western Oregon University on 3/7/19
The book has a strong balance of topics. In addition to the mix of genres that it discusses, the book is also effective in its coverage of different aspects of writing such as audience, context, ethics, etc. read more
The book has a strong balance of topics. In addition to the mix of genres that it discusses, the book is also effective in its coverage of different aspects of writing such as audience, context, ethics, etc.
The book contains no inaccuracies as far as I could tell, nor any political or social bias.
The book is relevant in a way that seems sustainable. It is not at the cutting edge of technical writing technologies or software, but it is the sort of book that would have (and probably has) helped students a decade ago and will still be useful in another decade owing to its coverage of general topics and its emphasis on writing fundamentals.
The book is extremely easy to read, and should not hold any students back.
The book's format changes occasionally, probably owing to the various authors involved, but it is not especially noticable and does not affect the book in a negative way.
The book seems to have been designed for modular use, and indeed that is how I plan to use it in my future classes. The way that the book starts with a quick reference guide to genres and then moves into the big-picture writing theory is evidence that the writers want the book to be immediately useful.
The book's organization seems maximally effective for teachers and students. As I mentioned above, the book starts by covering genres with relative swiftness, then it digs into essential writing topics, and then it covers larger genres in more detail. It ends with a section on "Thinking About Writing" that is pretty clearly designed for more advanced readers, and I think that's an effective choice.
The book was extremely easy to navigate and to use.
The book is very well-written and contains no grammatical errors.
The book is fairly dry, and so I did not notice cultural issues that might be of note.
The book is very good, and I look forward to using it.
But I do want to say that although above the book got 5-stars across the board, I'm not sure if I would give it a perfect review if I were to rate it. Basically, I find that students seem to flourish when a class (and a textbook) regularly comes back to explicitly stated themes, and the book didn't necessarily have those. They were there (audience, genre, etc.), but they weren't really up-played in a way that students will definitely get.
Still, again, this is a very strong book and I plan to redesign my future Technical Writing class with it.
Reviewed by Kathryn Northcut, Professor, Missouri University of Science and Technology on 1/13/19
The book is offered in various formats, and they aren't parallel. The organization of chapters in the web-native version defies logic. The expandable table is tricky to get used to because the hyperlink from the Chapter title goes to the chapter... read more
Comprehensiveness rating: 1 see less
The book is offered in various formats, and they aren't parallel. The organization of chapters in the web-native version defies logic. The expandable table is tricky to get used to because the hyperlink from the Chapter title goes to the chapter but the arrow on the right shows the subsections. It's hard to remember where you are as you navigate. I did not locate a glossary or index, and the book is not fully searchable in the web-native version because all sections can't be expanded onto one screen.
Content Accuracy rating: 1
Almost none of the content has references to original sources, and far too little theory is made explicit. Too much of the writing is chatty and conversational to provide a model of technical writing for university students.
The first section includes both platforms and genres. However, currently relevant platforms like Twitter are excluded from this section. Mixing platforms and genres seems odd logically. Later chapters jump between concepts and genres with no obvious logic to the order.
The style is accessible but not professional. The writing attempts to be engaging but is not rich enough in evidence, references, or good, contemporary examples for university students.
Consistency rating: 1
Unfortunately, the book consistently raises questions about whether these authors/editors have worked in technical contexts recently. Their advice seems to be off-base, including comparing omitting a conclusion to slamming down a phone on a caller. In fact, much professional writing starts with an abstract, executive summary, or cover sheet that obviates the need for a conclusion. The worst thing we can do in much scientific and technical discourse is build suspense and save the point, answer, or recommendations to the end. The way this book is designed and written does not seem to engage the exigencies of technical writing as I'm familiar with them. Other textbooks, whether consistent or not, provide better examples of practices from many industries to help prepare students from writing after college. This textbook focuses not just on the college experience, but on the Central Oregon Community College experience to the exclusion of other contexts.
Modularity rating: 2
The text does not contain modules that stand independently, despite appearing at the outset to be designed that way. Many phrases such as "as seen in the last section," make it difficult for students to follow what's happening. The videos address students in a single section writing a specific assignment and the content of the videos is not transferable to other contexts. The videos I viewed would not work in my courses, ever. Further, the textbook refers constantly to watered-down assignments that I would not assign. In my courses, students DO write a full proposal, not just an academic topic proposal. No one in industry writes topic proposals, so I would not teach that genre in my technical writing course. In fact, this textbook constantly focuses on the specific introductory assignments and methods at Central Oregon Community College, so a more ambitious, advanced curriculum would directly contradict the information in the textbook. If you wanted to teach your students to write proposals, you would be better off with online examples of successful proposals and top-of-the-head commentary than this textbook.
The organization of the textbook appears to be clear and clean, but gets difficult to manage once specific questions are asked, such as, "how should I assign readings to prepare my students for specific assignments?" One of my specializations is teaching proposals. This book doesn't handle proposal writing in a way that fits what I know of proposal writing outside of essay topic proposals used in composition courses. Why is information on Citations and Plagiarism after the chapter on proposals? Professional and academic proposals are robust documents which cite sources, so that background information would be useful earlier. Despite the textbook attempting to be modular, numbering chapters does suggest that there is a logic to the order. Non-numbered TOC might be a solution to this problem. In this book, short chapters are split up into tiny subparts, and navigation between them is tricky in the web-native version. Other Technical Writing/Communication textbooks, from Burnett's 2005 Technical Communication 5th Ed., to the current editions of Markel (and Selber) and Lannon (and Gurak) are superior in terms of internal logic, as is the Engineering Communication Manual (House et al) if the authors/editors need better examples of structure.
Interface rating: 1
I found the design appealing initially. Using it was confusing and there are many incompatibilities between the various versions available. The students would have difficulty locating the correct version of the textbook unless a PDF were provided to them by the instructor, and the PDF is problematic in terms of design and omission of content. In the web-native version, the sections are all very short and navigating to the next section requires clicking back and re-finding your place every time. Not having a "next section" button or arrow almost ensures that students will not complete the readings because they will think, incorrectly, that they are done with the (very short) chapter. The PDF version has many blank pages, making navigation cumbersome. The PDF document is much thinner than the large number of pages suggests. If a student were to print the PDF, much paper would be completely wasted and blank.
The conversational tone isn't ideal for educating students who will need to do technical writing in industry, but there are few overt typographic and spelling errors. The ones that exist are obvious and instructors can correct them if they use those chapters. Sometimes the authors refer to specific genres (like reports, in section 5.1) in a way that would confuse students (because writers cite sources in proposals, memos, and presentations, not just reports), and those errors should be addressed lest the students be misled about the conventions of the genres. Further, references to "your paper" and "paper" demonstrate lack of focus on rhetorical concepts of audience and purpose that should drive every technical communicator in every task. Most of our work is electronic/digital/online, so references to paper may not be incorrect, but they are largely archaic. When the authors refer to student assignments, they might call them "assignments," not "papers." The writing in section 5.2 needs editing. Overuse of "it" and "there" and back-referencing through pronouns ensures that students will have difficulty parsing the information. Further, students are seeing a poor example of a strong technical writing style because the sentences are written in a vague style that would lead to comprehension and translation errors. Further, the authors state that plagiarism is institution-specific, but that's only true in our academic bubble. In fact, plagiarism is an important IP (intellectual property) concern globally, so reference to international publication and copyright standards would be far more useful to students, who are students for 4 years or so, but professionals for up to 40 years.
Cultural Relevance rating: 2
Ideally, the authors would employ a plain style to avoid usability problems for non-American-dialect users. In the section (2.1 types of audiences) about audience, an opportunity is missed by not getting into user profiles and usability theory. Contrary to what is stated, technicians do not always lack sophisticated theoretical knowledge. It is not true that executives are always the audience for whom our students will or should write. The lack of robust user-based terminology is a problem with this book. I wonder if any of the authors are currently active in the technical communication community or have worked in nonacademic technical environments on communication design tasks. If they have, I would implore them to use better industry examples and the jargon of writers in technical professions. The authors should also focus on plain language in this book, and exemplify it in their prose. Karen Schriver's work is a good starting point.
I recommend this book (only) to instructors at Central Oregon Community College, where it perhaps serves a useful, important purpose. Its structure and content is unsuitable for majors in professional fields including engineering and science, and therefore is not a good choice for instructors teaching at most institutions where the course is offered. The emphasis on MLA style demonstrates the limited appeal of the textbook (to English majors). To be clear, MLA is not used in a single industrial or professional context I am aware of, outside English departments and literature-oriented professions. No mention is made of IEEE, which is the largest professional society in the world and which publishes professional ethics and authorial style guides that many professionals will encounter. It's great to include APA, but that social-science emphasis should be balanced with another professional style such as ASME or IEEE. The authors may have heard this, because they mention ASME in section 5.1, but they give no examples of what ASME looks like in practice. I worry that this textbook potentially does a disservice to the technical communication field as well as to open-access materials, which should be of high quality and represent best practices based on an awareness of the range of communication tasks working professional undertake. David McMurrey's work was far more technical and usable in its time; I'm sad to conclude that this textbook does not build productively on his legacy.
Reviewed by Jennifer Wilde, Adjunct instructor, Columbia Gorge Community College on 12/18/18
The text does many things very well, but it is too uneven to be truly comprehensive. It will work best as an introduction to technical communication and business writing. It is less helpful, I think, to students going into health care fields and... read more
The text does many things very well, but it is too uneven to be truly comprehensive. It will work best as an introduction to technical communication and business writing. It is less helpful, I think, to students going into health care fields and the social sciences. Chapters are brief and pragmatic, with no discussion of theory, no instruction on clarity or sentence structure, and little discussion of diction and style. The index is helpful; there is no glossary, but this does not seem to be an omission as there is little jargon used throughout the book. Some of the chapters are extremely brief and rudimentary, while others are detailed and nuanced. An example of the former is the section headed "Types of audiences", and an example of the latter is the section on ethics of technical writing. One of the earliest chapters is about texting. There are useful chapters dedicated to resumes, incident reports, proposals, and several other genres - and there is an interesting, though perhaps not as practical, discussion of genres in writing. Like most other technical writing resources, this book has nothing to say about case reports, medical or nursing notes, letters to the editor or position papers for professional and trade journals, all of which are pertinent to the daily work of many professionals in human services or advocacy. Another issue with the book is the lack of writing exercises and assignments. There are some areas with a "Try This" section, but not very many of them, and the assignments lack an assessment component.
The book seems unbiased, although some advice feels a little arbitrary, such as the recommendation to limit emails to three paragraphs. I do not find any errors of content. There is a technical error in the middle of the book, where the author refers to a graph about voting in Australia; that graph does not exist on the page but there is this editorial comment that was no doubt not intended for publication: [“How to vote…” – this image is on a blog that is CC-licensed but I don’t think the author used the image with permission. Is it possible to find a sub?] Who is who? Which Australian are we voting for?
Much of the advice will be appropriate forever: know your audience, know your purpose in writing, be respectful, be specific and clear rather than general and vague. The sections about how to present information visually are helpful: contrast, repetition, alignment and proximity are given the unfortunate acronym CRAP (so no doubt the reader will never forget it!) I also appreciate the chapter on information literacy, which includes information on scholarly, professional and general publications. This includes trade journals, something that WR 121 classes tend not to mention but are important for technical writing students. Of course, there is some information about PowerPoint that is likely already past its best-buy date, but the authors discuss that and point the reader towards existing and upcoming technologies other than PowerPoint. I was able to see the video on the writing situation but not all of the other links worked. The authors include a caveat that not all links will work, so that seems fair, but a comprehensive resource would not rely on links to external sources with all their potential foibles.
The authors resist the temptation to use jargon, and they stick to simple sentence structures for the most part. In that sense, they exemplify the sort of simple, crisp (if unexciting) prose that technical communication strives for. There is abundant use of the colon to introduce lists, and the authors use bullet points frequently.
The book is highly consistent. Each chapter starts with a brief introduction to what comes in the sections included in the chapter. That means that the first segment of each chapter is extremely short, followed by more detailed segments. What is not consistent is the amount of time spent on various elements of technical writing, which, as mentioned in the section on comprehensiveness, varies quite a bit.
Chapters could be read out of order, and instructors can certain assign some sections and not others. I would be most inclined to use the chapters on ethical issues, research, and proposals. I think that's OK, but the book is almost too modular. Chapters do not relate to one another and the order in which they appear feels arbitrary. There is some redundancy - for example, the issue of audience is addressed repeatedly without adding anything new on the subject. I generally prefer a text in which each chapter leads logically to the material in the next chapter and adds to the student's understanding of technical writing, but there are advantages to a source like this, too.
Organization/Structure/Flow rating: 4
The book is highly modular and the chapters do not flow into one another. I'm not sure why the chapters are ordered this way. I would tend to put some basic information about what constitutes technical writing at the beginning, followed by some guidance around doing research and writing ethically, followed by chapters on different types of technical writing: texts, emails, case reports, letters, resumes, proposals, recipes, instruction manuals, position papers, abstracts, encounter notes from a visit or interview, letters to the editor, mini-biographies and autobiographies ("about the author"), annotations. I would include an appendix about conventions: when to use a colon, how to convey numbers, the rules of capitalization, and the like.
The navigation was extremely simple and easy to use. The charts and images that are used are minimal but every one is highly useful and easy to see. Some links are broken.
I am prone to noticing grammatical and punctuation errors, but nothing jumped out at me in this textbook.
There is an ageist comment about "so easy that Grandpa could understand it" in the early pages defining technical vs academic writing. There is a very thoughtful section on cultural sensitivity. The authors use an interesting example of cultural differences, using a world map to illustrate the different meanings of the color red in different countries. However, it seems like a serious omission to leave out a discussion of inclusive language. Things in that field are always changing, but the authors could provide information about where to find the most up-to-date recommendations on inclusive language, such as the acceptability of "they" as a singular personal pronoun for gender nonbinary people, and what language is appropriate to describe ethnic groups etc.
The book is quite well written and useful, but not comprehensive. I would love to see this text updated with more sections. Chapters on lab/case reports, medical/interview notes, abstracts, introductions, mini-biographies, position papers and letters to the editor would enhance this text and broaden its appeal to new audiences, especially social science/health care students. I would love to see sections on effective sentences, collaborative writing, inclusive language, and grammatical conventions. Finally, an effective text on this topic should include assignments along with discussion of how to assess the assignments.
Reviewed by Cynthia Kimball Davis, Chair of the Integrative & Interdisciplinary Studies (IES) Department, Southern Utah University on 8/2/18
Comprehensiveness - Appears to offer all of the standard technical writing topics with an excellent easy bulleted table of contents. It also contains an excellent index and glossary. read more
Comprehensiveness - Appears to offer all of the standard technical writing topics with an excellent easy bulleted table of contents. It also contains an excellent index and glossary.
Content Accuracy - Appears to provide accurate content.
Relevance Longevity - Information appears to fit the relevant longevity category with the exception of the Professional Communication chapter; however, that would be an easy update.
Clarity - Information is presented in a simple and clear format.
Consistency - Information was not found to be incongruent in any way.
Modularity - The text is laid out in chapters with clear and simple sub-headings underneath each one.
Organization Structure Flow - The flow of the text is easy to follow.
Interface - The images could be more ascetically pleasing to the eye. In come cases, it appears that a high school student made them. Investing in a graphic designer might make the graphics more ascetically appealing. Furthermore, breaking the text apart with colorful questions and answers, activities, quotes, etc., is suggested.
Grammatical Errors - There were no grammatical errors found.
Cultural Relevance - The text appears to be culturally sensitive of all races, nationalities and ethnicities.
A text I definitely want to consider for my Technical Writing course. :)
Reviewed by Adam Karnes, Adjunct Instructor, Linn-Benton Community College on 6/19/18
The book covers the typical range of topics for a technical writing guide. At times, the balance feels off. A significant amount of the length is dedicated to topics usually covered in other classes (including research, citations, outlining). I... read more
The book covers the typical range of topics for a technical writing guide. At times, the balance feels off. A significant amount of the length is dedicated to topics usually covered in other classes (including research, citations, outlining). I would have preferred to have more info about the modes typical to technical writing, but what the book has is useful. Also, while the book has examples, I would appreciate even more examples. The book has a dropdown menu with a table of contents and a search feature in the reader.
The book is accurate. I did not observe inaccuracies.
On the whole, the book is relevant and should remain so for several years without the need for updates.
One important consideration regarding relevancy is the thematic dominance of references to Oregon. While the frequent mention of things related to the Pacific Northwest does not limit the readability of the text, this reoccurring theme makes the book more relevant for readers from this area than from others.
The book is clear and written with appropriate vocabulary for the typical student of technical writing. The body of the text goes into an adequate depth in the explanation of key concepts. Crucial terms are adequately explained. Examples are frequently included, although even more examples would be a welcome addition. The book lacks a glossary, which would also be a helpful addition.
The text is adequately consistent from beginning to end, but at times the sections feel disconnected. In this respect, the text works well as a modular book with distinct sections. The various parts do seem separate, however. The crossover between chapters could be stronger. This is probably the case due to chapters being derived from other sources. The differences do not render the text unreadable, just lack cohesive than the average textbook.
This text excels as a modular work. The sections are distinct and could be read independently. Teachers can easily pick and choose between sections without assigning the entire text.
The order in which the book’s contents are presented is somewhat arbitrary. (The section on resumes, for example, comes at the end—in many technical writing texts, this would come at toward the beginning.) Still, the ordering of the text is not confusing.
Navigating the text can be slow, with lots of scrolling and clicking through. Some of the sections are particularly long, and can be tiresome to scroll through. However, the table of contents is accurate and helpful. The book also has a search feature.
The text has no grammatical errors. The overall quality of editing is high.
The text is geared towards an American culture. However, the text discusses at length the importance of audience awareness and cultural differences in writing, particularly applications that span multiple cultures.
The greatest value this book offers is the ease with which teachers can select limited portions to assign to students based on the class objectives. This could easily replace a standard technical writing textbook in many courses, particularly if other texts further supplemented the class.
Reviewed by Susan Engel, Instructor, St. Cloud Technical and Community College on 6/19/18
Although an index/glossary is not provided, the Table of Contents organizes the material and allows for readers to see the breadth of areas and subjects within the Technical Writing textbook. Topics common to technical writing courses are explored... read more
Although an index/glossary is not provided, the Table of Contents organizes the material and allows for readers to see the breadth of areas and subjects within the Technical Writing textbook. Topics common to technical writing courses are explored in this text and include an important section (4.6) on evaluating sources as well as sections on plagiarism and the importance of citing sources. Topics that could perhaps be added to the text include social media (LinkedIn in Chapter 12: Employment Materials, for example) and technical writing for web pages or using online technologies.
Overall, the content appears accurate, error-free, and generally unbiased. Figure 13 in Chapter 11.4, however, doesn’t offer a resume sample for the exercise and simply states “Text of fake resume here”.
Content appears to be mostly relevant and offers up-to-date information on information literacy and other important technical writing concepts. Some of the content could be further updated, however. For example, chapter 12 discusses the idea of the cover letter being potentially outdated but then proceeds to offer guidance on writing one. This and other sections could offer updates, particularly regarding electronic and online documents.
The text is accessible and concise in delivery. Further clarification is offered through examples/samples in the sections on emails, memos, outlines, cover letters, technical reports, and others. Examples could be given in sections on proposals, progress reports, and other sections to offer further clarity.
The text offers consistency through the organization of the chapters and sections. Some chapters have features that others do not have, however. For example, Chapters 11 and 13 are structured with interactive activities not found in other chapters. The “activity” and “try this” in these chapters would be helpful in other chapters, too.
Chapters and sub-units within this text are clearly labeled. Although some overlap is offered, overall chapters and sections can be used individually in a course.
The organization is clear, user-friendly, and easily navigable using all-cap chapter headings and numbers and lower case section headings and numbers.
This text is offered in various formats which likely will help eliminate interface issues with certain sections. The section on resumes and cover letters, for example, might offer display differences depending on the format.
Grammatical errors were not detected.
Much of the text appeared to be neutral, and sections were dedicated to discussing cultural sensitivity within workplace writing. With that said, additional work on representation could be added within the examples. Also, ideas for inclusivity through accessibility in design of workplace documents might be added, too, as well as an updated discussion on gender in written communications beyond using Mr. or Ms. in the sections on email, cover letters, and audience.
This text is well organized with topics appropriate to technical writing, and I will consider using it in technical writing and workplace writing courses for first- and second-year students.
Reviewed by Erica Stone, English Instructor, Technical Writing, University of Missouri Kansas City on 6/19/18
The textbook is comprehensive; however, it seems to cover both technical writing and professional or workplace writing. It is absolutely appropriate for a comprehensive service course, but the authors should consider another title. Perhaps... read more
The textbook is comprehensive; however, it seems to cover both technical writing and professional or workplace writing. It is absolutely appropriate for a comprehensive service course, but the authors should consider another title. Perhaps Technical and Professional Writing would be more accurate.
There are a few minor typos and notes from a previous editor in the document and a few leftover editing notes. Regarding bias, the entire text does seem to be written for a particular course. While it is generalized, it does refer to particular assignments and contexts, sometimes without an example given.
The content is up to date; however, it may require revision as technologies evolve and change. For example, the texting section may need to be updated within the next year to account for newer texting apps and conventions.
The entire textbook is clear and accessible. In some places, it is conversational; however, I find that quality increases its accessibility and approachability, which is necessary for a technical writing service course.
The framework and organization of the textbook is consistent and easy to follow.
The modularity is helpful, and the text is well-organized.
All of the topics are presented in a logical and clear fashion.
All of the available interfaces work well.
I did not see any grammatical errors during my review. I did, however, see a few leftover notes from the editor.
The text is culturally appropriate and all example are relevant and inclusive.
In some places, the example links do not work. When there is time, the editors and/or authors should review the book to check for errors and broken links.
As mentioned in my first comment, the textbook could benefit from separating technical writing and professional writing as they are separate disciplines.
Reviewed by Michael Nern, Associate Professor, Emeritus, Ohio University Zanesville on 2/1/18
The book does not contain an index or a glossary. The book's primarily focuses on the proposal but also covers other traditional technical writing assignments such as the cover letter and resume. read more
Comprehensiveness rating: 3 see less
The book does not contain an index or a glossary.
The book's primarily focuses on the proposal but also covers other traditional technical writing assignments such as the cover letter and resume.
The content is accurate. I would not call the book error free.
The book contains relevant content that could be updated with relative ease.
The book's prose is not tightly edited, but the prose is accessible.
The book's content is consistent.
The text is well-organized for assigning smaller sections of reading at different points within a course.
The book's organization is solid and clear.
The text does not have interfacing issues.
The book needs a careful and close editing by one person.
I found the short chapter on ethics to be presented almost as an afterthought and believe it would be of little help to students.
I would use the book as a resource but not as a textbook for students. I might assign certain sections for reading but would more than likely use information from the book to add to already existing lectures and discussions, of course, giving credit to the authors.
In general, I believe both the Web and open source materials provide enough material to work with that textbooks in writing courses are unnecessary.
Reviewed by Jennifer Dareneau, Assistant Teaching Professor, The Pennsylvania State University- Berks on 2/1/18
Based on the Table of Contents, all subject areas mentioned there were covered adequately. However, there are several mentions of the technical report being the main document produced at the end of the term (which is true) and mentions of several... read more
Based on the Table of Contents, all subject areas mentioned there were covered adequately. However, there are several mentions of the technical report being the main document produced at the end of the term (which is true) and mentions of several prefatory documents needed for benchmarking along the way. Only a couple of those mentioned documents are detailed or explained in the book.
There are a few minor typos and notes from a previous editor in the document, including a question about permission to use a chart. Content itself seemed accurate.
Content is up to date. With the inclusion of sections on MLA and APA citation style as well as the job application chapters, it would need to be updated in about 5 years to reflect changes to those areas.
Clarity of language and expression of concepts is well done. Language is easy to understand but remains at a college student's level. Special terms are explained and defined.
For the most part, the book is internally consistent. There are some inconsistent elements- some chapters include links to samples, but not all; there is a link to one video only; some chapters include an activity prompt, but others do not.
Modularity is well done. Each larger unit is broken into smaller, easily understood and relevant sub units.
Organization is simple and logical.
I did not experience any navigation problems. Some images had an editor's note next to them, or were quickly covered by a small icon in the top right. The chapters on graphics had some photos that did not connect well to technical writing, and I suspect students in a class would struggle to understand the rhetorical significance of them (particularly the sections with Obama and the girls gymnastics team).
I noticed only one or two minor typos. There were some fragments and sentences beginning with And or But, which I hope were stylistic choices.
There were no culturally insensitive examples or remarks.
Reviewed by Ethan Jordan, Lecturer, Bowling Green State University on 2/1/18
The book covers a broad range of technical communication genres, and it covers everything I would hope to cover in my upcoming course. read more
The book covers a broad range of technical communication genres, and it covers everything I would hope to cover in my upcoming course.
Due to the objective nature of most technical writing, this book certainly follows suit and contains little in terms of bias or subjectivity. The document genres covered fit with standards in the field, and I have found very few errors.
I agree that this book will remain relevant over time. Certainly, notions of "netiquette" and online forms might change, but the essential tech comm genres covered will remain an essential component of workplace literacies, and as such, this book should remain relevant and be easy to update as needed.
The textbook is written in a voice that is straightforward and no-nonsense for students. It isn't the most scintillating reading, but a book on technical writing clearly doesn't need to be! The voice of the text is one that I feel students would appreciate - let's get to the point!
I don't see any major inconsistencies. The text works to reinforce technical communication concepts both in its subject matter and in the style of the text itself. Clarity and intelligibility are essentials, and the text appears to work within those frameworks.
I appreciate the way the sections aren't overly extended or complicated - the individual components make up the larger whole and could easily be reconfigured to suit the needs of instructors. I feel like this is less of a textbook to read in order, but a set of modules for instructors to customize.
The overall structure of the piece makes sense, and I found myself following the process outlined within the overall book structure. It also is able to be modified quite easily if needed, so that's a plus.
Some of the graphics are a bit low-res, but nothing that would inhibit meaning... it's well presented overall.
Very few that I can see!
I see no issues here - it's quite objective overall.
I'm really happy I found this one! It will be a huge help in my upcoming course, and I'm excited to use this as a supplement to my in-class discussions!
Reviewed by Elizabeth McClure, Lecturer, University of Maryland, College Park on 2/1/18
This text includes several sections that I would expect to see in a technical writing textbook: job search materials, reports, proposals, using graphics, professional communications, and audience analysis. It also includes a couple of sections I... read more
This text includes several sections that I would expect to see in a technical writing textbook: job search materials, reports, proposals, using graphics, professional communications, and audience analysis. It also includes a couple of sections I wouldn't necessarily expect, but that would be very useful in any professional writing class: discussions of the ethics involved in report writing, information literacy, and document design. However, there was no section related to manuals or instructions, which is a large gap.
In terms of usability in relation to comprehensiveness, the table of contents is nicely detailed, but no index appears so locating overlaps of information among and between chapters would not be as simple or straightforward as it could be.
In general, the information in the text is accurate, although some areas and issues would benefit from more nuanced or complex discussion. For example, in the section on job materials, professional advice varies widely related to the design of resumes, but this text does not discuss any of the variety of advice.
One minor note: There are several sentence-level errors (i.e., subject-verb agreement) that don't compromise communication but are occasionally jarring.
The content generally seems up-to-date, and the chapter organization and breakdown appear to lend themselves to easy updating.
Clarity rating: 3
The text’s language is clear and accessible. Sufficient background information is presented to give context for new concepts.
Other structures that would enhance clarity are not consistently present, however. For example, not all chapters provide examples to illustrate concepts or discussion/reflection questions to encourage students to apply concepts to other situations. Additionally, most chapters have no graphic material – pull-out text boxes, illustrations, summary lists, etc. – that would offer a different presentation method for readers.
This text is consistent in its approach, terminology, and framework.
This text is divided into sections in such a way that individual sections could easily be assigned out of order and at different points in a course. There are few, if any, instances in the text that refer to earlier material in a way that would make non-consecutive reading unworkable or unwieldy. In general, sections are relatively short and are organized under useful headings. Few subheadings are used within the text itself, although chapters are broken down into sections, each of which is labeled on the page and in the table of contents with a heading. These headings should make finding relevant sections in the text fairly easy.
The topics in this text progress clearly enough to avoid confusion, but less clearly than they could. For example, starting with Audience Analysis rather than with a variety of workplace communication genres (text, email, memos, etc.) would be more rhetorically sensible. The progression from Proposals to Information Literacy (research) to Citations to Progress Reports makes sense in that it follows the progression one might follow in a particular workplace project. However, while the order of chapters follows the process of writing a workplace document (proposal, research, progress report, technical report), it doesn’t necessarily follow the order of writing skills. For example, research is usually an integral part of developing a writing topic rather than something that happens at a single defined point mid-way through a project; likewise, a discussion of ethics should happen before a technical report is underway, perhaps in relation to an analysis of audience or to a discussion of the rhetorical situations present in professional writing generally. Because these chapters can be read out of order, the problem isn’t serious, but the chapter order doesn’t make as much use of logical development as it could.
In general, the text’s interface is user-friendly. There are a couple of places, however, notably in the chapter on design, where graphics don’t appear above the caption.
The text is overall clean but there are a handful of grammatical errors.
The text is inoffensive. Its examples aren’t culturally specific – examples don’t refer to particular groups at all, so diversity does not seem to be at issue.
Reviewed by Pam Orel, Senior Lecturer , University of Maryland College Park on 2/1/18
This is a very compact book, with easily managed lessons in basic concepts that are a quick and easy read for most students in the sciences and technology fields (STEM). Where it summarizes the key details, it does so with general clarity and the... read more
This is a very compact book, with easily managed lessons in basic concepts that are a quick and easy read for most students in the sciences and technology fields (STEM). Where it summarizes the key details, it does so with general clarity and the links to other, more detailed resources appear to be effective, although one or two are dated. It is not designed as a comprehensive or exhaustive resource on technical writing and avoids a heavily academic tone.
The book’s advice, while brief, is extremely solid, backed up by authoritative evidence, and easy to follow. Students would appreciate the very good detail in the table of contents as well as the ease of navigating from section to section as needed. Charts, where used, easily help students find the key differences in concepts, which is something that more detailed, less approachable textbooks tend to overlook.
In general I don’t teach with a textbook, so my comments should be taken in the context of someone who uses texts more as a resource than a work that guides the entirety of our semester’s journey as writers. This is a very relevant work for busy writers who need to grasp the essentials quickly, and get leads on how to find more detail as needed. It is particularly good at using graphics to shape ideas which is a factor in more and more writing courses. If I had to point to one area where it might need updating, it might be in allowing more space for instructions, presentations and video content, as these are emerging as valuable tools and I am not seeing a lot in the text. It appears to focus a lot on the preparation of reports and print materials, but is a good basic resource in those areas.
Very clear, with short, effective paragraphs and guides to other resources clearly labeled as such. As noted earlier, graphics are well supported in the version that I reviewed. It should be noted that different formats might have issues relating to page presentation, as I have noticed that in other primarily online references I have seen.
It can be inconsistent in terms of the amount of space given to, say, some issues over others. However, in general the issues which are not treated in great detail are those for which often there are other, key resources focusing on general principles involved that are attached. Also, in some instance (plagiarism is one example) there are a wealth of other resources available in most higher education communities.
The sections in the book are effectively broken into segments which are short but emphasize key points in about a page or so. This is one of the areas where it might be most attractive to students who rely on it as a reference rather than a week-to-week resource. Teachers who wish to use, say, one or two segments while not using others would find this a very helpful resource.
This is an area of strength for this publication, as it shapes very well around ideas for most proposal writers as well as the ethics of the field as we know it today. Ethical concepts are generally brief, but clear as to impact on the STEM fields. It would be stronger with a little more emphasis on presentations and video, as noted, which are important as digital communications tools for STEM majors.
The online interface I used was generally very easy; with both arrows and a table of contents, writers can easily move to where they need to get their information. It is noteworthy that it does not have questions in the back of each section, so it’s not designed for, say, test development or study for exams. But most technical writing courses don’t focus on exams (there may be quizzes on concepts) so that is not a significant barrier.
I was not able to find any significant errors in grammar.
This could be stronger in its approach to culture across the STEM communities, which is not a small issue in a global economy. However, one challenge with that is attempting to keep it current -- culture, like everything else in science and technology, changes very rapidly.
I have taught from a range of different resources, which change from year to year as it’s important to keep a course relevant in the rapidly evolving STEM fields. I have had trouble finding resources, particularly open source ones, that are approachable but convey the key concepts in an easy to access format. Students in my classes use a text as needed, rather than as the foundation of an entire course. This has worked very well in that role in this semester, and I am hoping to keep it on my list of resources moving forward.
Reviewed by Amanda Izenstark, Professor, Reference & Instructional Design Librarian, University of Rhode Island on 2/1/18
This text covers numerous facets related to technical writing, including basic business correspondence and determining how best to reach the audience for the particular type of technical writing being done. The authors cover related and integral... read more
This text covers numerous facets related to technical writing, including basic business correspondence and determining how best to reach the audience for the particular type of technical writing being done. The authors cover related and integral elements that help writers produce better documents, including using outlines and graphics as well as information literacy skills that writers should have. While there is no index or glossary, the table of contents clearly displays the content of the text. It’s worth noting that the table of contents on the Open Textbook Library website does not include the two final sections of the book, which cover “Design and Readability of Publications” and “Employment Materials.”
The book is accurate, and even in sections where elements might change - such as screenshots in the Information Literacy chapter - they are general enough that even if the interface changes, the instructions will be relatively similar.
The topics in the book are not likely to become dated immediately. Some of the basic material related to communication and being concise will be consistently useful. While some of the linked material may change over time, that isn’t the fault of the authors. When I reviewed this text, the links tested were still working and relevant.
The text is written at a level accessible for college-level students, and perhaps some high school students. The materials are logically arranged and easy to understand.
As some of the material includes elements remixed from other open texts, there are some differences in the language and layout of chapters. For example, some of the elements of chapter 12 related to cover letters and resumes use color, and have more modern examples than those in chapter 1, which focuses on online etiquette.
Many of the chapters will do well on their own. I plan to adopt this for my information literacy and writing course, and anticipate re-arranging sections to fit the course structure.
This may be a result of my background as a teacher of information literacy first, but it might make more sense to start with the sections on information literacy and citations, then progress to audience analysis and outlines. It seems the chapter on “Professional Communication” might fit better toward the end. Otherwise the flow and structure are generally logical.
The online version of the book is hosted on the Pressbooks platform, which is intuitive to use, but long sections require significant scrolling. The PDF version of the book works as expected, with functioning links in both the table of contents and the text.
There are no grammatical errors in the text, which is what one would expect from a writing textbook.
As appropriate, the book highlights cultural issues to consider when writing for an audience. Examples don’t highlight a variety of backgrounds, but neither are they so pervasive that it’s a problem.
Given the appropriately broad coverage of this text, I can envision it being useful to students after they leave my course and have jobs in their chosen fields.
Reviewed by Jim Crawford, Adjunct English Instructor, Germanna Community College on 2/1/18
I examined this textbook as a resource for a 100-level Technical Writing class. In this context, questions of comprehensiveness arose almost immediately. The authors offer no discussion of theory, despite a claim on page 1 that theory underlies... read more
I examined this textbook as a resource for a 100-level Technical Writing class. In this context, questions of comprehensiveness arose almost immediately. The authors offer no discussion of theory, despite a claim on page 1 that theory underlies technical writing. There was no mention of the writing process, a confusing oversight on two fronts. First, the omission raised questions about course level. Did the textbook assume students already understood writing as a process? That would put this text higher than entry-level; writing as a process is usually taught in 100-level English. Or, by omitting the writing process, does the textbook defy modern writing pedagogy and emphasize the products of technical writing over the process?
There was also no mention of the rhetorical situation: the amalgamation of purpose, stance and tone, genre, media, and, of course, audience. The text offers a separate chapter on analyzing the audience, but no holistic examination of the roles that purpose, stance and tone, genre, and media play in reaching the audience.
Omitting a discussion of the rhetorical situation elicits more questions about course level and students’ prerequisite knowledge. Does the text assume students understood the interaction of purpose, stance, and genre in a writing project? The textbook mentions purpose, almost in passing - the purpose of a memo, for instance, or a report. Stance - how the writer feels about the topic versus how she expresses it through her tone - was not addressed at all. Given that technical communicators may be asked to write about things they don’t care about or may disagree with (e.g., an environmentalist writing a press release on new oil exploration), a discussion of stance and tone is important.
Lacking an essential discussion of theory and concept, the textbook covers a limited range of genres, another writerly term that is not mentioned. The first chapter reviews types of correspondence, starting with, oddly enough, texting. Next, comes e-mail, then an interjection about netiquette, followed by brief discussions of memoranda and letters. Later chapters describe proposals and progress reports. A recent revision added a chapter on employment-related documents, such as résumés.
While this is an adequate list of technical genres, the choices seemed limited and specific. Why the focus on progress reports? A broader chapter covering incident or recommendation reports seems more thorough. Other key genres are missing entirely. Instructions get no mention, although giving directions and documenting procedures are common workplace tasks. Presentations are another key genre for technical communication that is overlooked in the textbook.
Among the genres that are discussed, accuracy falters due to a handful of random, undocumented prescriptions. On page 12, for example, the authors declare,” a good e-mail should get to the point and conclude in three small paragraphs or less.” Really? According to who? In my 30 years of experience in the technical workforce, I have read, and written, countless e-mails longer than three short paragraphs. While I agree that students should keep e-mails short and direct, especially when corresponding with the instructor, there is nothing inherently wrong about a longer e-mail message. Some arguments cannot be made in three short paragraphs. Are the authors saying that longer arguments are better suited for a memorandum or a letter? If so, that indicates a need to discuss the conventions of genre. If the authors are recommending the abbreviated length as a best practice for emerging technical communicators, they should say so. If the authors proclaim the three-paragraph limit as their personal preference, they should say that, too. However, they must also inform students that they may occasionally need to write, and read, longer e-mails in the workaday world.
A similar prescription occurs on page 36, with the decree that “an average between 15 and 25 words per sentence is about right. Sentences over 30 words are to be mistrusted.” Again, I wondered, “Says who?” Had the authors cited evidence — a study finding that sentences over 25 words are ignored by readers, for instance — the claim might be more compelling. Lacking documentation, it’s puzzling at how five additional words can separate an effective sentence from an untrustworthy one.
Furthermore, while conciseness is an essential feature of technical and professional writing, establishing an arbitrary sentence length may encourage students to emphasize conciseness at the expense of clarity and accuracy. It would be more effective to educate students on the relationship between clarity, conciseness, and accuracy, and teach them to use the shortest, clearest, most direct language needed to effectively address the audience and accomplish the purpose of the text. But this relationship is impossible to discuss with this text, since overarching concepts and conventions are never introduced.
The digital nature of the textbook assures easy editing and the potential for long-term relevance. In fact, between July 2017, when I downloaded a PDF copy for review, and October 2017, when I began writing the review, the authors added chapter 11 on design and readability, and chapter 12 on writing employment materials. They also expanded chapter 10, adding information about successful report design.
As with comprehensiveness and accuracy, clarity is marred by odd omissions. Page 12 advises that “professional communications require attention to the specific writing context” but there is no explanation of what context is. Again, a question about prerequisite knowledge arises. Can the authors assume that students understand what context is, and how it impacts a writing product?
Another missed opportunity occurs on page 16, where the authors admonish “culture and even gender can play a part in how people communicate.” While this is undoubtedly true, two questions arise. First, can instructors assume that students will recognize this intricate interaction? Second, can instructors assume that students will tailor their writing to navigate the interaction and improve communication? Lacking examples, explanations, or a declaration of prerequisite knowledge, the answer to both questions is “no.”
Clarity is further diminished by Inconsistencies within the text. Chapter 8, “Creating and Integrating Graphics,” recommends “including identifying detail in the graphics” (128), yet does ignores its own advice. The sample bar chart on page 123, depicting types of produce grown in Sisters, Oregon, has axis titles, but the y-axis, entitled “Percentage produced in 2015,” has no scale. The chart shows that potatoes are the most plentiful crop. Its bar towers over that of carrots, the closest competitor, by about two-thirds. But, without a scale, the value for potatoes could be 30 percent, or 3 percent, compared to carrots at 10 percent or 1 percent.
A pie chart on page 122 shows a similar dearth of detail. The chart is entitled, simply, “Success with Vegetables Grown.” Potatoes account for 60 percent of vegetables grown; carrots for 23 percent. But percent of what? The pie chart doesn’t say. Is it percent of all total crops grown? Is it percent of crop yield, compared to crops planted? Students are left guessing, and, from this, may learn to create charts that inspire their own guesswork. More subtle inconsistency arises in the textbook’s formatting. Chapter 1, on correspondence, uses at least three different formats for bullet points. Pages 12-13 list characteristics of e-mail with bullets featuring a bolded opening phrase. Pages 15-16, on netiquette, uses headings, along with simply, un-bolded bullet points. Meanwhile, page 24 presents a list of correspondence types with no bullets at all; the different types are simply bolded. These inconsistencies model poor document design for students. This is especially problematic given the text’s emphasis on longer documents, such as the progress reports, which require consistent formatting throughout.
Formatting inconsistencies notwithstanding, the text is well-marked for modularity. Clear, consistent headings and sub-headings are used throughout. Students should have no trouble identifying a reading assignment such as “chapter 9, sections 9.1 through 9.3.”
Alas, the headings and sub-headings demarcate a haphazard arrangement of content. Topics are not grouped according to theory (should there be any) and practice, strategies and genres, or from easiest material to more challenging. The chapters appear randomly, with an early chapter often referring to material that has not been introduced yet. Chapter 1, on correspondence, advises, “careful consideration should be given to the audience...” (9), but the chapter on audience analysis follows 14 pages later.
Considering the recent addition of chapters on design and employment documents, it appears that chapters are organized in the order that they’re added. New chapters are simply tacked on at the end. While such labor-saving is understandable, it may be worth the effort to reorganize the textbook by introducing overarching concepts, such as audience, research methods, and ethics at the beginning, with specific writing strategies (e.g. outlining) and genres to follow.
This review was prepared from a print-out of a PDF file generated on the textbook’s Web site. Although the charts and graphics conveyed when printed, the videos, understandably, did not. It would have been helpful to include URLs for the videos, so that students preferring a paper-based text could find and watch the videos while reading.
The interface for the Web version of the book is clear, simple, and unobtrusive. [Home] and [Table of Contents] buttons are fixed on the right-hand side, allowing students to easily jump among sections. Gray “forward” and “backward” arrows, on the right and left, respectively, make it easy to flip pages. A “search” box, almost invisible in the upper, right-hand corner, offers quick full-text searching. A search for “audience” returned a list, itemized by clickable links to specific sections containing the term. Traditional search conventions, such as double-quotes to find phrases, work as expected. However, more sophisticated search operators, such as “AND,” “OR,” “NOT,” and “NEAR” do not work, though this is not a major shortcoming.
There were no noticeable grammatical errors, though there were occasional long, wordy, confusing sentences. The sentence describing crop yields in Sisters, Oregon was a staggering four lines long, strung together with “and” between three independent clauses (121).
Generally, the text is inoffensive. There was, however, one off-putting cliché: the notion that older people are slow to grasp technical concepts. The book’s Introduction advises, “…plan to write in such a way that even Grandad can understand!” (3). While this was surely a throwaway attempt at levity, the cliché may be discouraging to older students, while cultivating the bias of younger ones.
Reviewed by Linda Stewart, Instructor, Portland Community College on 6/20/17
The text covers proposals and progress reports in depth with links to examples of other types of technical writing including resumes and instructions (but no discussion of these forms in depth). The text does not cover multi-cultural audience in... read more
The text covers proposals and progress reports in depth with links to examples of other types of technical writing including resumes and instructions (but no discussion of these forms in depth). The text does not cover multi-cultural audience in any depth and does not consider disabled audiences (including visually impaired audiences). The text does not include an index or glossary.
The book is accurate, error-free, and unbiased.
The text begins with the most common kinds of professional communication, including texts and e-mails, which demonstrates an understanding of current workplace needs. This section may need updating since technology brings changes to workplace communications. The section on research rightly emphasizes electronic sources, and this too, may need updating as library databases and other electronic sources may change. Other sections, like the ones on audience and ethics, will not need updating.
Students would enjoy the bulleted lists and simple, readable prose. The authors provide some excellent, labeled figures and graphics so that students can comprehend the main ideas quickly. The authors do a good job of defining terms, but students will need to read the text to discover the important terms; no sidebars or lists are used to call attention to specialized vocabulary.
The formatting and tone are consistent with good use of numbered sub-topics and bulleted lists in each chapter. The sources provided as links are not consistent with the formatting of the main text. For instance, the link to examples (titled "Online Technical Writing: Contents") uses yellow background and blue lettering, and does not include any explanatory text. This linked resource is not formatted as professionally as the main text. The terminology is internally consistent.
The text is well organized and clearly divided into smaller reading sections that can be assigned at different points within the course.
Problems with organization: Since the topic of "ethics" is one that applies to all forms of technical writing, it seems out of place as "Chapter 9." It also seems that "Outlines" might be addressed sooner since those could apply to writing proposals as well as progress reports. Finally, it seems odd to separate the chapters on graphics and document design (they are chapters 8 and 10 with the ethics chapter in between them.
The overall organization progresses logically from shorter forms of technical writing to longer, more complex ones.
The text is free of significant interface issues, including navigation problems or problems with display.
The authors observe standard conventions of grammar.
The text is not culturally insensitive or offensive. The authors could do more to include a variety of races, ethnicities, and backgrounds as part of their discussion of "audience"
The text does an especially good job of explaining how to write proposals and reports in a clear, step-by-step manner.
Reviewed by Carol Jacobson, Instructor, Century College on 6/20/17
The text covers all areas that are part of the technical writing curriculum. There is a detailed Table of Contents that lays out the subjects that are covered. There is no index or glossary. read more
The text covers all areas that are part of the technical writing curriculum. There is a detailed Table of Contents that lays out the subjects that are covered. There is no index or glossary.
Content is accurate and error-free.
Content is current for the technical market. It covers current topics and concerns, but also includes all the traditional topics expected for Technical Writing courses.
The text gives full explanation of the content.
The text was consistent with its terms.
The text is divided into multiple sections that are each on a different topic or focus so these sections could be easily assigned at different point for a course.
The topics of the text are ordered in a logical way, beginning with topics that should be covered first in a Technical Writing course.
Some of the images are blurry and hard to see. The 2 videos are designed by an instructor for a specific course and reference specific assignments for that course so these are not good choices for this textbook that is meant to be a general source for any Technical Writing course.
The text contains no grammatical errors.
The text is presented in a neutral way with no offensive or insensitive words or examples.
The format of the content is very text heavy in paragraph structure, which is odd for a Technical Writing book because a general rule in Technical Writing is to use shorter, concise paragraphs with more lists, bullets, and tables for easy reading and referencing of the information. In addition, the text needs more real-life example that demonstrate the points being made in each section.
Reviewed by Shannon Kelley, English Faculty, Chemeketa Community College on 6/20/17
The text covers a good amount of information related to technical writing; some of the sections are more in depth than others. Many sections would benefit from further inquiry to assist students with more complex issues in the field of technical... read more
The text covers a good amount of information related to technical writing; some of the sections are more in depth than others. Many sections would benefit from further inquiry to assist students with more complex issues in the field of technical writing and communications. While all of the topics are relevant, it sticks to the basics of each topic without exploring innovations and trends in the field. The topics covered are appropriate for a low-level, introductory course in technical writing.
The book is accurate and unbiased. It is a straight-forward text that introduces the basics of technical writing in a clear, error-free format. Each chapter provides references and is accurately cited. The examples are neutral and helpful.
Relevance/Longevity rating: 3
The content is relevant, but not exhaustive. The text does not cover new trends in the field. Many technical writing students, particularly in community college courses, are entering a variety of fields. While this text provides the basics of technical writing, it does not help with a variety of concerns students may face in their chosen fields.
The text is arranged in way that will allow for necessary updates moving forward. The text seamlessly incorporates modalities, like video links, that prove helpful as examples. More of these new modalities are desirable as writing and reading moves to the Internet. There are places in the text that could benefit from utilizing new, innovative examples.
The text is written clearly and concisely. Each chapter is divided into sections. The section and chapter headings create parallelism that helps its overall clarity. The table of contents is clear and easy to use. There is not a lot of technical jargon present; the lack of technical writing terminology is one reason the book reads like introductory material.
The text is consistent in its layout. It is easy to use and access. The structural framework of the text is effective for online reading.
The text is not self-referential, but it does reference information only relevant to COCC. The text is divided in a way that feels manageable for students. The downside is the text borders on being too modular. The sections felt purposefully shortened and many chapters left me wanting more information. For instance, visual rhetoric and page layout were lumped together with audience. And in terms of this topic, topics like those deserve their own exploration.
The text works itself through the basics, from small workplace writing tasks like emails and memos, up through more complex writing like proposals and reports. Thought was given to the order of the text and it is logical and predictable.
There were no interface issues as I reviewed the text. i downloaded it as a PDF and also read some parts online.
The text contains no grammatical errors. It was edited well. The grammar is basic and reads at an introductory level reading.
The text remains neutral and uses voice or cartoon like figures in some of the videos. I would have liked to see more examples throughout the text. Visuals and page layout are important features of a lot of technical writing and this text doesn't take advantage of opportunities to incorporate a variety of examples. There are opportunities throughout the book that allow for incorporation of examples from fields of nursing, human services, engineering, computer science, and education.
It should be noted that I am reviewing this text for a 200 level course. At Chemeketa Community College students enter technical writing after completing two-three levels of prerequisite writing courses. Technical writing is the highest level of writing students receive before they enter their professional fields or transfer to four-year universities. The book is well written, clear, useful, and comprehensive for an introductory course, but not for a higher level technical writing course. Much of the focus felt repetitive and covered skills students in technical writing should already possess. There were missed opportunities to expand some of the more relevant topics, like the importance of visual rhetoric in page layout; solicited and unsolicited proposals; and, analytical report writing like feasibility studies.
Reviewed by Daniel Hocutt, Web Manager & Adjunct Professor, University of Richmond School of Professional & Continuing Studies on 4/11/17
The text does not include an index or glossary, but does provide a comprehensive table of contents. The text introduces itself as an introductory text to technical writing (or communication), and provides a definition of technical communication... read more
The text does not include an index or glossary, but does provide a comprehensive table of contents. The text introduces itself as an introductory text to technical writing (or communication), and provides a definition of technical communication that is limited to the types, content, and coverage of texts created. A more comprehensive text would address some of the responsibilities of technical writing as it relates to the technical writer herself: team building and collaboration, intermediary across multiple departments and divisions; and negotiator of meaning in workplace cultures. Also missing from the text are generous examples of document types generated by technical writers, like websites, brochures and flyers, and other types of written communication. The text's focus on report writing seems limiting, and its approach to technical writer as largely autonomous does not accurately reflect the complexity of technical writing workplaces.
The content is up-to-date and appears to be thoroughly accurate. Its authors clearly understand and practice technical communication, and its integration of external tools and links are current, complete, and appropriate to the content of the text itself. Chapters in the text address real-world examples and seek to connect communication techniques to workplace and technical contexts. Of particular importance is the text's approach to communication as audience focused and customized; this reflects theoretical accuracy and currency in technical and professional writing and, more broadly, in rhetoric and communications.
The applicability of this question to a text on technical communication is somewhat misplaced; technical writing handbooks must follow technical advances that will necessarily render older technologies less relevant. For example, the section on texting would not have appeared in earlier editions of this text, while the section on memoranda feels somewhat dated in paper-less or paper-reduced workplaces. As a result, the content will regularly have to be updated as modes and media of communication and writing evolve. This is a problem of all technical writing texts, but it's particularly acute as it relates to an online text, which will likely be expected to be current, relevant, and inclusive of the latest trends in technology and writing.
The text is remarkably approachable to its intended audience, those entering into the field of technical writing or those who will, by virtue of their technical positions, be required to compose technical artifacts. Its prose is clear and specific, and it follows the guidelines for writing technical prose that it presents to reader: clear, concise, and effective.
The field of technical and professional communication tends to use terms somewhat synonymously, so the conflation of certain terms in the text is not unusual in the field. For example, “writing” and “communication” are often used largely synonymously in the field, and that practice is also followed throughout this text. The same is true of “business” and “professional” as it relates to writing and communication. An introductory text should seek to better follow consistency while explaining the issues that exist in the field.
The text is quite modular, to the point that certain parts of it might be combined to keep from creating extremely short chapters or sections. This is especially true of several introductory sections. In general, segments are only a few paragraphs in length, with modules easily excerpted for re-use or revised usage. I could definitely see the potential of a teacher taking certain sections and incorporating them into class notes or as a customized resource. But I also see the value of using the entirety of the text as a stand-alone text; I believe the text’s structure enables both uses with little revision or customization necessary.
The text’s organization is not as clear or logical as I would expect. Given that modules or sections can be reordered on demand, this is not a significant drawback. However, I found the default order of modules confusing, shifting between more general, theoretical approaches (like audience analysis and information literacy) and more specific practical approaches (like proposals and progress reports) without a clear rationale for shifting from one to the other. A more logical structure might be to address the general theory in an opening section that includes examples for illustration, then to include a second section to address specific genres and types of technical writing. The structure is not off-putting, but as someone who might consider teaching from this text, I question the rationale behind the logic but am given little explanation.
The text’s interface is clean and clear. Serif fonts are a little unusual in web documents, but the type style used is quite readable online. Table formats don’t always fit on the page, and this requires left/right scrolling to access some of the columns. The text includes few images; most are linked to accessible PDF versions, which are full-screen and easy to read. Embedded videos appear to function as expected; the interface could benefit from a column-width inline viewer that would keep the video window from being narrower than the text columns. This is likely a result of making the interface mobile responsive, and represents what is often a necessary compromise.
Like its prose, the grammar appears to be clean and normalized to American standard English. The tone can be academic, but that is to be expected from a text used in an introductory classroom. I found no grammatical errors.
I did not encounter ethnicity- or gender-specific language in the text. The examples provided represent a number of different document types and genres, generally focused on the professional workplace or the academic environment. However, no text will free itself completely from ideology; I might like to have seen the text more directly address this issue as it relates to business writing. The text could do more to explore cultural contexts in which technical documents are planned, prepared, and consumed, especially given increasing internationalization of workforces. This may reflect an issue with the field — we tend to classify international communication differently from general technical communication — but a section on writing in the global community and for cross-cultural audiences might be useful.
I did not expect to find an open textbook as useful or well-constructed as this is. While its cover and design are unassuming — which, for a text on technical writing, might be a drawback — its content is erudite and targeted to its primary audience and purpose. I would consider using this text in an introductory technical writing class, with the addition of several notable sections identified elsewhere in this review.
Reviewed by Ruth Perkins, Adjunct instructor, Chemeketa Community College on 4/11/17
The text clearly focuses on research and report writing in a business context. These are appropriately and adequately covered. The table of contents is detailed and accessible on each page with a link to each section. The chapters lead students... read more
The text clearly focuses on research and report writing in a business context. These are appropriately and adequately covered. The table of contents is detailed and accessible on each page with a link to each section. The chapters lead students through the steps of producing a formal report including research, proposals, citation, and progress reports. There is a useful section on information literacy and conducting research beyond the first items in a Google search.
The importance of keeping readers in mind is stressed throughout. In addition to a link to an audience worksheet, there is a clear explanation of how reports might be used by different readers.
Chapter 10 includes a link to a wide variety of examples of technical writing.
Missing are sections on topics often included in technical writing: instructions, procedures, descriptions and definitions. These could be easily fit into the overall structure of the text although obviously other sources of information would need to be found.
The principles of professional communication are accurately presented. The authors make the useful point in several places that a business, agency, journal etc. will likely have its own preferences for professional communications but that some aspects, such as avoiding plagiarism, doing proper research, are consistent.
The content is up-to-date since there are not apt to be quick changes to the principles of technical writing nor to the precepts of e-mail, texting etc. and their place in business. Any changes could be quickly made.
There are links that are specific to or have comments that are specific to COCC that instructors will probably want to point out and substitute their institution’s or their class policy. Examples are the links in 1.3 and 6.2.
The book is clearly written in an informal, conversational tone that should appeal to students. The terminology is basic without down-writing. Any specialized terms are defined.
The link in 8.4 to visuals that need revision is probably not useful for most classes. Figures 1 and 2 are very specialized.
The text is consistently organized. There are clear signals that link each section to the main section. The emphasis is on professional communication throughout so chapters are linked through that context.
In section 4.1 there is inconsistency in terminology where “academic” and “scholarly” are used interchangeably.
The book is clearly arranged into chapters with clear titles and headings. The table of contents is linked to each section for quick finding. The pages have ample white space and large readable type.
The book is clearly organized around the perspective of researching and writing a final report. The chapters can easily be rearranged according to an instructor’s preference since the table of contents is linked to each section.
However, the book is arranged in a logical progression through the different aspects of research and writing the formal report.
The book is posted in 4 different formats which makes it readily accessible to students. There is an important missing link in 9.2. This link in 4.3 is no longer valid: The Research Cycle derived from A Cycle of Revolving Research by UC Libraries, CC: BY-NC-SA 3.0 Otherwise there are no issues.
There are grammatical errors in section 9 as well as confusing switches in point of view.
Grammar errors: 9 “Writers . . . she” 9.3 “. . .your employer to pursue and action” and “the groups’ goal”
Point of view First, chapters 1-8 and 10 are written in second person. Chapter 9 is written partly in second person, partly in third person. While some references to “the writer” are logical, it inconsistently directly addresses readers or talks about writers in general.
Second, there is inconsistency in an attempt to be gender neutral in the third person. In 9 “she” and “he” are used interchangeably. 9.3 uses “her/himself,” “s/he,” and “his/her.”
The examples in the text and references to writers are neutral. There is nothing to identify a particular culture, race or ethnicity.
The book doesn't completely fit the course in technical writing that I teach but I would consider using if it did. However, I do have some problems with Chapter 9, ethics in technical writing, that I would like to see addressed. These are in addition to the grammatical issues.
In 9.1 General Principles, the authors give examples of ethical dilemmas that range from trivial to life and death. These do more to complicate the subject than clarify it. Part of this is due to the phrasing about the friend’s haircut, “This lie, though minor, preserves . . .” What is “though” doing in this sentence? It signals a contrast which isn’t there.
More of a concern though is the phrasing of the third choice of saving lives. The person might “risk [her life] to save her children” but to save the stranger, she would have to “choose to die.” Risk and certainty are not equal choices.
The second paragraph concludes that “If you would . . . lose your job. . . the action is probably unethical” oversimplifies -- one can lose a job for being ethical as well.
Section 9.2 includes the Challenger disaster as an example of unethical writing. The missing link is vital here since there are definitely different accounts of the underlying causes beyond the O rings. The authors speculate about possible motives of the engineers with no source information to support their conjectures. They make statements about the priority of information in the engineers' report which imply that they are in a position to make that judgment.
I suggest deleting or re-writing this section of the book.
Reviewed by Corrine Holke-Farnam, Instructor, University of Northern Iowa on 2/8/17
The text provides an adequate overview of the field for beginners in technical writing. read more
The text provides an adequate overview of the field for beginners in technical writing.
The content is accurate and straight forward.
The text is up-to-date and covers the range of topics addressed in introductory technical and professional writing courses.
The information is presented effectively in clear, concise language. Provides accurate definitions and many links to examples for easy understanding.
I found no internal inconsistencies.
Text is user-friendly. Effective use of white space. Employ small chunks of text, bullet point lists, and hyperlinks.
Many technical writing textbooks begin with audience analysis. Hamlin, Rubio, and DeSiva begin with common types of professional communication like email and memo format; doing so provides an effective context for beginning writers. The chapters of the book could be easily reorganized to fit user needs and/or preferences.
The text is free of interface issues. Navigation between and within chapters is smooth. Website links opened easily.
Technical Writing contains no grammatical errors.
The text revolves around professional communication. Does not contain offensive or insensitive material or links.
This text seems like a good fit for students in my Technical Writing for Electrical Engineering Technologists course. Practical information, concise presentation.
Reviewed by Jennifer Barton, Advanced Instructor, Virginia Tech on 2/8/17
The book appears to be written for a course designed around a specific major project that asks students to write a proposal for a technical report and then to research and write the report itself. Those sections are adequate, but I would like to... read more
The book appears to be written for a course designed around a specific major project that asks students to write a proposal for a technical report and then to research and write the report itself. Those sections are adequate, but I would like to see more content in general.
In particular, I would like information on writing instructions and technical descriptions, as well as the finer points of correspondence writing, like strategies for persuasion, or handling negative news, or emphasizing reader benefits. I would also like to see information on team writing—a must for the modern workplace. The book would also benefit from a section on presentations and a broader section on document design. The current section on design is specific only to reports and is really about organization, not design.
The content is accurate. The book sticks to the basic writing principles which don’t change much over time. I especially appreciate the repeated emphasis on audience and that while particular elements are expected for particular genres, organization and approach can and should be modified to suit the writer’s purpose and the needs of the audience.
The core principles aren’t likely to go out of date any time soon. The limited scope and lack of discussion about the design expectations of the modern audience does make the book feel dated.
Although the concept of linking to examples and additional information is an excellent use of this medium, the choice of links could be improved. For example, many of the linked reports are nearly twenty years old, and while they may demonstrate many of the writing principles that stay constant over time, they do not demonstrate contemporary expectations for design, and the topics are so dated as to make them seem irrelevant to most students.
The authors do an excellent job of adhering to plain language principles. The style is clear, simple, and direct. It reads like the authors are speaking directly to the audience.
As mentioned previously, the book reads as though it were designed for a very specific class. It shifts quite a bit between universal advice about writing for a professional audience and specific advice about writing for an instructor. That’s confusing and limits the book’s applicability.
The book is divided into logical sections that would make it easy to customize for a course if not for the problem previously cited of its being designed around a specific course’s project.
Follows a familiar and standard organization for workplace writing textbooks, beginning with basic correspondence and working towards longer and more complex reports.
Some easily correctable issues here: Many widowed headings (which the text advises to avoid). Figures and tables are not always labeled correctly.
The visual weight of “Chapter Attribution Information,” which is currently the same as chapter titles, should be reduced. In some chapters, that information is repeated before every section, which adds visual clutter.
There are additional problems in the pdf version that make it the pdf only partially usable: Text boxes tend to exceed the width of the page and cannot therefore be read. Everything is rendered as plain text, which means that table formatting is screwy and all images (including images of example documents) are missing. Citations get embedded directly into the text.
Grammar looks fine.
Deals very little with cultural issues, which is surprising given the global ventures of many companies and the increasingly diverse workforce in the US.
The book has the potential to be quite good, but I don't think it’s yet ready to compete with the for-profit options. I look forward to seeing subsequent editions.
Table of Contents
- 1. Professional Communications
- 2. Audience Analysis
- 3. Proposals
- 4. Information Literacy
- 5. Citations and Plagiarism
- 6. Progress Reports
- 7. Outlines
- 8. Creating and Integrating Graphics
- 9. Ethics in Technical Writing
- 10. Technical Reports: Components and Design
- 11. Basic Design and Readability in Publications
- 12. Employment Materials
- 13. Communicating across Cultures
- 14. Thinking about Writing
Ancillary Material
- Submit ancillary resource
About the Book
This open textbook offers students of technical writing an introduction to the processes and products involved in professional, workplace, and technical writing. The text is broken up into sections reflecting key components of researching, developing, and producing a technical report. Readers will also learn about other professional communication, designing documents, and creating and integrating graphics. Written especially for an academic setting, this book provides readers with guidance on information literacy and documenting sources. This book was collected, adapted, and edited from multiple openly licensed sources.
About the Contributors
Annemarie Hamlin is an Associate Professor of English at Central Oregon Community College.
Chris Rubio is an Assistant Professor at Central Oregon Community College in Bend, OR.
Contribute to this Page
Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser .
Enter the email address you signed up with and we'll email you a reset link.
- We're Hiring!
- Help Center
Handbook of Technical Writing 9th Edition
The five-way access system of the Handbook of Technical Writing provides readers with multiple ways of retrieving information:
Related Papers
Kevin Karplus
This document contains course notes and exercises for a course in technical writing. The course is intended for third-year computer engineering majors, and emphasizes technical documentation directed to engineers, engineering managers, technical writers, and other specialized audiences.
Goy Alisara
Ayesha Kidwai
Vịt Quay Bắc Kinh
Bigra Shehzada
Pavel Collado
Elenie Coss
Juan Ayarza
Luján Di Benedetto
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.
RELATED PAPERS
eltrima laoly
Adrienne Jones Daly
Son Ca Bui Chuoi
Teacher Hernandez
Đông Dương hải
Andiwilda Muftiara S
Samson Shanchebo
Vinni triyani purba
- We're Hiring!
- Help Center
- Find new research papers in:
- Health Sciences
- Earth Sciences
- Cognitive Science
- Mathematics
- Computer Science
- Academia ©2023
Due to a planned power outage on Friday, 1/14, between 8am-1pm PST, some services may be impacted.
Internet Archive Audio
- This Just In
- Grateful Dead
- Old Time Radio
- 78 RPMs and Cylinder Recordings
- Audio Books & Poetry
- Computers, Technology and Science
- Music, Arts & Culture
- News & Public Affairs
- Spirituality & Religion
- Radio News Archive
- Flickr Commons
- Occupy Wall Street Flickr
- NASA Images
- Solar System Collection
- Ames Research Center
- All Software
- Old School Emulation
- MS-DOS Games
- Historical Software
- Classic PC Games
- Software Library
- Kodi Archive and Support File
- Vintage Software
- CD-ROM Software
- CD-ROM Software Library
- Software Sites
- Tucows Software Library
- Shareware CD-ROMs
- Software Capsules Compilation
- CD-ROM Images
- ZX Spectrum
- DOOM Level CD
- Smithsonian Libraries
- FEDLINK (US)
- Lincoln Collection
- American Libraries
- Canadian Libraries
- Universal Library
- Project Gutenberg
- Children's Library
- Biodiversity Heritage Library
- Books by Language
- Additional Collections
- Prelinger Archives
- Democracy Now!
- Occupy Wall Street
- TV NSA Clip Library
- Animation & Cartoons
- Arts & Music
- Computers & Technology
- Cultural & Academic Films
- Ephemeral Films
- Sports Videos
- Videogame Videos
- Youth Media
Search the history of over 788 billion web pages on the Internet.
Mobile Apps
- Wayback Machine (iOS)
- Wayback Machine (Android)
Browser Extensions
Archive-it subscription.
- Explore the Collections
- Build Collections
Save Page Now
Capture a web page as it appears now for use as a trusted citation in the future.
Please enter a valid web address
- Donate Donate icon An illustration of a heart shape
Technical report writing today
Item preview, share or embed this item, flag this item for.
- Graphic Violence
- Explicit Sexual Content
- Hate Speech
- Misinformation/Disinformation
- Marketing/Phishing/Advertising
- Misleading/Inaccurate/Missing Metadata
![[WorldCat (this item)]](https://archive.org/images/worldcat-small.png "[WorldCat (this item)]")
plus-circle Add Review comment Reviews
1,338 Previews
4 Favorites
DOWNLOAD OPTIONS
No suitable files to display here.
14 day loan required to access EPUB and PDF files.
IN COLLECTIONS
Uploaded by paul nguyen on April 5, 2010
SIMILAR ITEMS (based on metadata)
14 Books on Technical Writing Technical Writers Should Read
This comprehensive list of 14 technical writing books will cover the subject of documentation from all angles. Dive into our little library and become a master of the art of technical writing!
📚 Table of contents
Looking for a documentation platform that's easy to use?
Try Archbee for free. Capture complete product knowledge from across your company and publish it with fully customizable portals.
Discover Archbee
It is a truth universally acknowledged that a technical writer in possession of challenging documentation projects must be in want of good books on technical writing.
This list will provide you with a comprehensive list of books that cover the subject of documentation from all angles.
This includes job search, project management, writing practices, technology and tools , and much more.
Take a dive into our little library and become a master of the art of technical writing !
Handbook of Technical Writing
Author: Michelle Carey, Moira McFadden Lanyi, Deirdre Longo, Eric Radzinski, Shannon Rouiller, Elizabeth Wilde
Published: Twelfth edition (June 15, 2020) by Bedford/St. Martin's
Great for: Comprehensive overview of technical writing style and usage
This is one of the most comprehensive resources for technical writing available today.
It explores hundreds of topics, from job searches and career overviews to technology and tools used by technical writers.
The twelfth edition is still very fresh, and its handling of all topics is up-to-date.
The guide is also rich with sample documents, of which there are almost a hundred to choose from, and it’s organized alphabetically so that it can serve as a quick reference for all your technical writing needs.
The Essentials of Technical Communication
Author: Elizabeth Tebeaux, Sam Dragga
Published: 5th edition (November 6, 2020), by Oxford University Press
Great for: Learning to communicate technical information clearly
This textbook teaches the basic principles of clear communication in the workplace by providing a wealth of case studies, scenarios, and sample documents.
These principles are then applied to all forms of communication in the office, including emails, memos, reports, and most importantly, websites and instruction manuals.
To help these lessons stay with the reader, the book offers practical exercises readers can do to self-test their knowledge and new skills .
Technical Writing Process
Author: Kieran Morgan
Published: March 4, 2015, by Better On Paper Publications
Great for: Making technical writing more structured
Kieran Morgan’s simple five-step guide to writing technical documentation is an excellent starting point for writers who want to make their writing process repeatable and more efficient.
The guide covers multiple types of technical documentation, such as manuals, user guides, and procedures.
Like a true technical writer, Morgan uses simple language and a lot of example scenarios to explain the complexities of technical writing.
This is a great feature because it makes the book accessible to everyone interested in technical writing, even readers who haven’t written their first document yet.
The Insider’s Guide to Technical Writing
Author: Krista Van Laan
Published: May 1, 2012, by XML Press
Great for: People considering a career in technical writing
Technical writing is a great career choice for anyone with a penchant for writing and a special interest in technology.
This extensive overview of the technical writing field provides the reader with knowledge of what skills are needed for success in this industry and what steps to take to excel from day one.
It’s also full of helpful tips on handling the pressures and rewards of a technical writing job, making it the perfect choice for anyone considering entering this dynamic field.
Managing Your Documentation Projects
Author: JoAnn T. Hackos
Published: April 6, 1994, by Wiley
Great for: Learning project management principles for documentation
This isn’t a new book, but the lessons contained within it are definitely evergreens.
JoAnn T. Hackos is a veteran project manager and has consulted companies like IBM and Hewlett-Packard on managing their documentation project, so you know she knows her stuff.
Hackos is a master planner, and her book teaches readers to plan their documentation so meticulously that the first draft practically writes itself.
Technical writing isn’t all creativity, so her methodology is definitely worth visiting again and again.
Technical Communication
Author: Mike Markel
Published: Bedford/St. Martin's
Great for: Learning about technical writing in a broader sense
Still used as a textbook in many university courses about technical writing, communication, and documentation, Markel’s book provides one of the most comprehensive guides for all kinds of technical communication.
What really makes this book stand out is its practical approach to the subject.
The author provides strategies for writing situations everyone encounters in their professional and personal lives, as well as sample documents for all kinds of writing.
The latest edition of the book can be found here .
Technical Writing For Dummies
Author: Sheryl Lindsell-Roberts
Published: March 13, 2001, by For Dummies
Great for: A beginner’s overview of technical writing
Like most For Dummies books, this one is an excellent choice for anyone who wants to get a nice birds-eye view on topics like the technical writing job market, the process of creating technical documentation, and all kind of different documents that fall under this category.
Sheryl Lindsell-Roberts emphasizes the need for technical documentation to be engaging to really help users achieve their goals and provides ample advice on how to avoid writing tedious and confusing documents, which is a skill every technical writer should master.
Managing Writers: A Real World Guide To Managing Technical Documentation
Author: Richard L. Hamilton
Published: December 31, 2008, by XML Press
Great for: Managing people and projects in documentation
Another guide for project managers in documentation, this time more focused on the people aspect of documentation.
In other words, this is a great resource for technical writers and managers who lead technical writing teams.
The value of this book is that it provides a real-world perspective and doesn’t sugarcoat the ups and downs of working in the documentation.
For anyone considering a career in this field, this book will give you food for thought and help you decide if this is the right industry for you.
The Elements of Technical Writing
Author: Gary Blake, Robert W. Bly
Published: August 1, 1993, by Pearson P T R
Great for: Quick reference for technical writing
A must-have for any technical writer’s desk. The first part of the book is filled with actionable tips for clear, concise, and accurate writing.
This includes common rules like avoiding jargon and proper hyphenation. Every rule is properly explained and supplemented with examples to make these lessons stick.
The other part of the book is dedicated to technical document types and best practices for writing each one.
Some of the information may be a little outdated, but the general principles definitely still apply to modern technical writing.
Is the Help Helpful?
Author: Jean Hollis Weber
Published: November 28, 2004, by Hentzenwerke Publishing
Great for: Writing documentation for customer service
We’ve covered some resources that approach technical writing from a broader perspective, so here’s a book that’s more specialized.
Jean Hollis Weber literally wrote the book on writing documentation intended for customer service and other types of online help.
The book deals with what help guides often get wrong and establishes some principles on providing help literature that actually works for the typical internet user.
There are also some great chapters on prototyping and usability testing which can help writers establish writing processes that do the trick every time.
Technical Writing Basics: A Guide to Style and Form
Author: Brian R. Holloway
Published: 2nd edition (June 1, 2001) by Pearson College Div
Great for: Writing in more informative and persuasive style
This is another commonly found textbook on technical writing. It provides a great look at technical writing as both a career choice and a professional skill.
The author puts great focus on the style of writing as a key component to ensure documentation achieves the goals it sets for itself.
More specifically, the guide teaches the writer how to write informatively and persuasively in order to capture attention and motivate the reader.
A handy feature to take note of are the handy exercises and assignments in the book that are designed to help the writer improve their skills.
Technical Writing 101
Author: Alan S. Pringle, Sarah S. O’Keefe
Published: 3rd edition (May 1, 2009) by Scriptorium Publishing Services, Inc.
Great for: Overview of skills needed for technical writing
A lot of skill goes into creating technical documentation beyond just a talent for writing. Pringle and O’Keefe’s book details what those skills are and how to start acquiring them.
A particularly interesting part of the book focuses on creating content that’s easier to translate into other languages, which is of particular value to technical writers working on documentation for products that are used all over the world.
The third edition also makes reference to the Darwin Information Typing Architecture (DITA) standard for developing documentation which is a valuable tool for writers who want to bring structure to their work.
Technical Writing: A Practical Guide for Engineers and Scientists
Author: Phillip A. Laplante
Published: 2nd edition (August 10, 2018) by CRC Press
Great for: Specialized documentation for engineers and scientists
A practical, clearly written guide for anyone who wants to write about technology and science. And we’re not just talking about guides and manuals here.
This is a resource that will help you write entire books on these subjects in a structured way.
Technical writing books, especially on these complex subjects, are often boring and difficult to get through. But not this one.
Laplante’s guide is chock-full of storytelling and real-life examples that make even the most technical parts of the book easily digestible and interesting to read.
Developing Quality Technical Information: A Handbook for Writers and Editors
Published: 3rd edition (June 23, 2014) by IBM Press
Great for: developing user-centric documentation
When thinking about the best examples of technical documentation, a couple of names probably pop into mind. Google, Microsoft, and IBM, perhaps?
Well, if you want to develop this level of documentation, this guide straight from the minds of IBM’s doc design experts is your best bet.
The book will teach you how to create content that’s truly user-centric by showing you principles like information ordering, content optimization, and methods for providing easy access to users.
We think this covers everything. Having read just a part of this book list, you should be on your way to technical writing stardom.
Don’t forget that there’s much more to life than books, so supplement this list with other resources , like blogs, magazines, and websites, to ensure your skills are always on the cutting edge.
While you’re at it, check out Archbee , our multipurpose documentation tool that will allow you to easily create and share documentation with employees, users, and potential clients.
Continue Reading
.png)
- Advertising
- Applications
- Assessments
- Certificates
- Announcement
- Invitations
- Newsletters
- Questionnaires
- Food & Beverages
- Recruitment
- Marketing Examples
- Transportation
10+ Technical Report Writing Examples – PDF
Technical report example.
- Google Docs
- Editable PDF
Technical Service Report Example
Free Report Technical Specification
Technical Evaluation Report Letter Example
- Apple Pages
Free Letter of Transmittal for Technical Report
Report Examples:
Technical report writing example.
Parts of a Technical Report Writing
Engineering Technical Report Example
What is a Report used for?
Technical report example format.
Universal Qualities of Technical Report
Report format example.
The Proper Format of a Technical Report
1. the title page., 2. abstract., 3. table of contents., 4. introduction., 5. background theory., 6. theoretical analysis., 7. works cited., 8. appendices., school technical report format.
Technical Report Requirements
Tips in Writing Technical Reports
Types of Technical Reports Writing
General FAQs
1. what is a technical report, 2. what is the purpose of using a technical report, 3. what should a technical report include.
- Abstract and table of contents
- List of illustrations
- Executive summary
- Details you want to share with your client/investors
- Glossary and list of symbols
- Introduction, body, and conclusion of your observation.
4. Why is it important to use a Technical Report?
5. how is a techincal report written.
- Add the title page
- Introduction, highlighting the main aim of the report
- Experiment details and description of budget, if needed
- Results and discussions
- The body, which has details of what you want the reader to know
- Conclude on a positive note.
More Design
9+ formal report examples, 8+ feasibility report examples, 6+ examples of short report, 9+ english report writing examples for students, 5+ ways of writing an observation report examples, 5+ project report examples, what should be in an executive summary of a report, how to write an evaluation report, how to write a short report, 7+ activity report examples, related articles.
- 56+ Examples of Report Forms
- 50+ Report Examples
Papers and reports
Explore premium templates
Professionally designed and perfectly formatted report templates ready to be used as an outline
Paper and report templates in Word make formatting and writing your school and business papers a snap. Write outlines, cover letters, speeches, theses, team reports, and business papers with pre-built report template designs or add your own customizations. Many report templates have clearly delineated sections for summary, intro, and conclusions for ease of use. The Executive Summary report template simplifies writing comprehensive overviews with sections for your objective, audience, competition, risk and opportunities, and conclusion. There are also specialty project report templates, like a social media analytics report. Just fill in key stats to explain your progress and prove your work is delivering results. A report template can also save you time and keep revisions to a minimum and comes in a variety of formats of report styles. You’ll find you can cut your writing time in half with a readily available MLA or APA template format. Browse, customize, download, and print one of the report templates to create a professionally crafted paper that will impress readers.
- Try the new Google Books
- Advanced Book Search
- Barnes&Noble.com
- Books-A-Million
- Find in a library
- All sellers »
Get Textbooks on Google Play
Rent and save from the world's largest eBookstore. Read, highlight, and take notes, across web, tablet, and phone.
Go to Google Play Now »
What people are saying - Write a review
About the author (2005).
Daniel Riordan (Ph.D., University of North Carolina at Chapel Hill) teaches courses in technical writing at the University of Wisconsin-Stout.
Bibliographic information
We're sorry, no results found.
Search Tips
Note: This catalog contains only Cengage products.
Double check your search term:
- Search by ISBN alone, without other characters or terms Example: "XXXXXXXXXXXXX" Instead of: "13: XXXXXXXXXXXXX" or "simmonsXXXXXXXXXXXXX"
- Search by Title alone, without other terms Example: "Managerial Economics" Instead of: "Managerial Economics: A Problem Solving Approach, 5th edition"
- If your term is specialized, try a more general term Example: "American History" Instead of: "suffragette"
Students, have a course key? Enroll now
Technical Report Writing Today
Daniel g. riordan , steven e. pauley.
Technical Report Writing Today provides thorough coverage of the technical writing basics, techniques, and applications students are likely to encounter in both their academic courses and their future careers. Its practical presentation of varied examples and exercises helps students internalize the skills necessary to produce clear and effective documents and reports. Annotated student examplesmore than 100 in allillustrate different writing styles and approaches to problems. A chapter on Developing Web Sites introduces students to the basics of effective web site creation by presenting professional and student examples and references to current practices.
558 pages, Paperback
First published January 1, 1995
About the author
Daniel G. Riordan
Ratings & reviews.
What do you think? Rate this book Write a Review
Friends & Following
Community reviews.
Join the discussion
Can't find what you're looking for.
- Literature & Fiction
Sorry, there was a problem.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required . Learn more
Read instantly on your browser with Kindle for Web .
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the Authors
Technical Report Writing Today Paperback
- Hardcover $7.98 11 Used from $2.34
- Paperback $6.66 6 Used from $3.29
There is a newer edition of this item:
- Language English
- Publisher Houghton Mifflin College Div
- Dimensions 1 x 6.5 x 9.5 inches
- ISBN-10 039573052X
- ISBN-13 978-0395730522
- See all details
Product details
- Language : English
- ISBN-10 : 039573052X
- ISBN-13 : 978-0395730522
- Item Weight : 1.67 pounds
- Dimensions : 1 x 6.5 x 9.5 inches
About the authors
Daniel g. riordan.
Discover more of the author’s books, see similar authors, read author blogs and more
Steven E. Pauley
Customer reviews.
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
- Top reviews Most recent Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. please try again later..
Top reviews from other countries
- Amazon Newsletter
- About Amazon
- Accessibility
- Sustainability
- Press Center
- Investor Relations
- Amazon Devices
- Amazon Science
- Sell products on Amazon
- Sell apps on Amazon
- Supply to Amazon
- Protect & Build Your Brand
- Become an Affiliate
- Become a Delivery Driver
- Start a package delivery business
- Advertise Your Products
- Self-Publish with Us
- Host an Amazon Hub
- › See More Ways to Make Money
- Amazon Rewards Visa Signature Cards
- Amazon Store Card
- Amazon Secured Card
- Amazon Business Card
- Shop with Points
- Credit Card Marketplace
- Reload Your Balance
- Amazon Currency Converter
- Amazon and COVID-19
- Your Account
- Your Orders
- Shipping Rates & Policies
- Amazon Prime
- Returns & Replacements
- Manage Your Content and Devices
- Your Recalls and Product Safety Alerts
- Amazon Assistant
- Conditions of Use
- Privacy Notice
- Your Ads Privacy Choices
Last day of the OFFER FLAT 20% off & $20 sign up bonus Order Now
Last day of the offer FLAT 20% off & $20 sign up bonus
How To Write A Technical Report
A comprehensive guide to writing impeccable technical reports.
To get the grade from your tutor or your money back!
Files Missing!
Please upload all relevant files for quick & complete assistance.
Technical reports are an essential mode of information exchange in the field of science and engineering. A large number of engineering activities and tasks require extensive report making. These reports present a precise summary of information on a certain endeavor. Technical report writing is an essential part of any engineering program and requires a professional tone. Students have to state the results, methodologies and ongoing investigations of their research in their reports. Also, they must ensure to present all information clearly so that even no-technical audiences can understand the material with ease. Writing top-notch technical reports call for preemptive preparation and a thorough understanding of the subject under discussion. Documentation of these kinds must reflect the professionalism, technical knowledge and acumen of its writers. This write-up aims to assist you in approaching technical report writing with ease and élan.
How to write an accurate technical report?Pay close attention to your writing style
The domain-specific nature of a technical report makes it essential for one to possess a proper idea about the subject and the research under discussion. If you do not have a rigorous knowledge of your discipline, you will not be able to write a good report. However, the nuances of technical report writing along with all the unique formatting guidelines can put even the most knowledgeable pupils in a jam.The process is extensive and complicated and requires some looking into. So, let us dwell deep into the writing process and learn how to write impressive technical reports.
- Always keep your audience in mind
Your readers are one of the most important parameters of your technical report. Beside your evaluators, other potential readers may be a client, a manager or even your peers. Thus, a perfect blend of technicality, formality and accessibility is essential. Substantial background details are essential to convince readers about the veracity of your report. Be aware of the grading criteria to develop a report that fetches the best grades.
- Break down the work into individual tasks
Dividing the whole report into separate elements will not just help you write better, but also let your readers understand it well. Segregate the report into chapters at an early stage and plan the writing process accordingly. Follow the standard template or any specified formatting guidelines while creating the chapters. Try to break down all of the content early in the writing process. For example, in a mechanical engineering report, create a chapter on experimental details with the following:
- The instruments & types of equipment used in the investigation
- The environmental conditions during the testing process
- The parameters of the tests conducted
- Record of any changes made to the testing parameters
As evident, such segregation enables readers to gain a clear idea about the research methods and experimental steps.
- Present an abstract
The abstract will help your readers understand the contents with ease. As it is a summary of all that's done, the abstract will offer a glimpse of the topic, the experimental approach and research methodologies. Abstracts also help readers from the non-technical background grasp the technicalities of complicated research.
- Create a table of contents firsthand
This is one of the first and foremost things which you should do while writing. Having a table of contents ready at hand will help you keep track of your chapter-wise progress as well as overall completion. Write a chapter as soon as you complete a particular task.
- Pay attention to the microstructure
The microstructure of a technical report deals with the internal structure of every individual chapter. Every report must have an introduction, central chapters and a conclusion. Every chapter must also possess a similar layout, with an intro, a central body and concluding statement. Here are a few pointers to keep in mind while crafting individual chapters:
- Keep paragraphs short at about ten lines each. Readers seldom read a large chunk of words.
- Start every paragraph with a theme or topic sentence. Place it prominently to help readers understand the context of the write-up easily.
- Try to distinguish amongst introductory, explanatory, linking and concluding paragraphs to enhance its readability.
- Always place your main idea in the central section or main phrase of a paragraph.
- Maintain a proper flow in your writing. Link your sentences to increase the coherency of the content. Use markers to indicate the direction of an argument.
Though chapter structures do have a general structure, many institutions specify a particular layout. Follow it to a T to garner the best scores.
- Pay close attention to your writing style
Technical reports must be formal in tone and written in a professional manner. Take note of the following points and implement them in your writing.
- Write in the third person only.
- Always complete your sentences. Make sure they contain a subject, verb and an object.
- Do not connect sentences using commas.
- Be careful with your word choice, especially when using technical terminology.
- Active voices score over passive voice.
- Avoid making sweeping statements as they indicate a lack of knowledge.
- Do not include irrelevant information in the report. The more concise the content, the better the score.
- Avoid wordy expressions. Keep things formal and to the point.
- Write out common abbreviations and explain technical abbreviations as often as possible.
Imbibe all the above points in mind and utilize them for writing an excellent technical report. On that note, here is an example of a technical report written in the accurateformat.
A brief overview of the general technical report template
The following is a chapter wise description of a general technical report template. Note that your evaluator may specify a different format, but every permutation possesses similarities with the general version.
- Letter of transmittal
The letter of transmittal is a courteous gesture if the letter is meant for official purposes. It addresses the client and containsthe name of the author, along with its purpose and affiliations.
- Abstract
Summarize key information in the abstract. Mention the necessity of your research, methodologies, results and discussions in brief. Wrap everything up as briefly as possible. Try to keep the word count within 500.
- Table of Contents
- List of figures and tables
- Acknowledgements
- Introduction
The introduction should deliver adequate background information, including all necessary technical information. Mention all vital concepts associated with the research to illustrate your technical skills to the reader.
- Experimental Details
- Results and Discussions
This section is the “meat” of your technical report. Present any raw data or auxiliary and intermediate results in appendices and report only the final results. Since this segment displays your knowledge and acumen, make sure to craft it to perfection.
- Conclusions & Recommendations
Reinstate the points in the results section and make strong statements to put forth everything with emphasis.Explain the usefulness of your research methods and suggest ways to perform further research on the topic.
All raw data obtained during experimentation must be collected in this section. Supporting information from the appendices and experimental details should be enough for others to use your research work with accuracy. Go through all of the above information in details and imbibe them to master the tricks of writing the perfect technical report. Implement the above with diligence and deliver technical reports of unmatched quality. Yet, if unforeseen circumstances impede you from writing a proper paper, worry not for the experts of Assignmenthelp.us have your back.
Having difficulties delivering a comprehensive technical report?
Let Assignmenthelp.us help you out
At Assignmenthelp.us , our subject matter experts stand ready to deliver perfect solutions for any technical report on any stream.Our writers deliver well-researched and detailed technical reports. Every chapter is crafted to perfection, and all citations are written following specified guidelines. They take the utmost care while working on your order and follow all specified guidelines to perfection. Excellent grades are a guarantee on every report we deliver. Here are some of the fantastic perks that will make your experience worthwhile:
- Service Packages at Affordable Prices
- Attractive Combo Offers
- Loyalty Bonus Programs
- 24/7 Customer Support Service
- Introductory Discounts
- Free Proofreading & Editing Services
So, give us a call or drop a message and get impeccable academic writing assistance from America’s number one academic assistance service.
You Might Also Like
Quantitative Research Topics
Sports Research Paper Topics
Funny Persuasive Speech Topics
Thesis vs. Research Paper
Research Paper Topics
Difference Between MLA and APA Citation
Types of Research Papers
The Ideal Font for Dissertation Writing
Correlational Research
LEAVE A REPLY
Dissertation
Programming
Research Topics
Student Guide
Writing Service
Popular Posts
Deepak 06 Jun, 2019
Deepak 06 Jul, 2019
Julian Borger 20 Mar, 2018
Julian Borger 14 Mar, 2018
Deepak 31 Oct, 2018
The Newsletter
Subscribe to get regular Update!
Thank you for Subscribe to us.
You will receive a confirmation email shortly in your subscribe email address.
Please Check
You have already subscribed our newsletter.
Thank You For Commenting.
I've tried plenty of assignment services before, but Assignmenthelp.us takes the cake. My assigned writer made sure to clarify all the points of my assignment and reassured me he'd get it done in 3 days. I was surprised when he delivered the paper the next day! The writing quality was exceptionally high, and I ended up with the best grades in class.
Sarah Glove
I've always received low grades in my class for many years. I could ignore it before, but taking a risk in my final year would have been careless. My friends always spoke highly of Assignmenthelp.us, so I decided to give it a try. I was surprised at how low the prices were. My grades improved a lot, so I highly recommend everyone to try them out.
George Brian
If you're looking for a service that can provide you great assignments, Assignmenthelp.us is the best option there is. The writer was the most professional out of all the services I have hired till now. Any time I had a question, their customer care always replied to me in a few minutes. I'll surely come back to use their services again.
Samantha Rich
Not sure yet, get in touch with us or, get free price quote ., thank you for subscribe to us.
Thank you for Subscribe us. You will receive a confirmation email shortly in your subscribe email address.
Want to earn the quickest $10?
Just tell our agents what you need!
Have any Query? Contact with us
Technical Writing is Easy
Jan 16, 2019
What is Technical Writing Report?
Faq on technical writing.
In this article, I will tell you what a technical report is, why companies need it and how to write it.
What is a technical report?
Technical report is a document that describes the progress, process, or results of scientific or technical research. It also can include some recommendations and conclusions. Technical reports may be considered as grey literature because they rarely undergo comprehensive independent peer review before publication.
Technical reports are a great source of technical or scientific information. They can be written both for wider or internal distribution. In order to establish novelty, technical reports can be considered as a primary form of scientific paper when researchers don’t want to wait when academic journals publish their work.
So, as you see, a technical report is key part of the research that also should be written according to established rules. Below, you will find some tips on how to write it.
Technical Report Elements
A typical technical report consists of the following elements:
- The title page
- The introduction
- The summary
- Experimental details
- Results and discussions
The conclusion may include:
-Recommendations
-Bibliography
-Acknowledgments
-Appendices
Tips on how to write a technical report
A technical report doesn’t differ much from other types of technical documents. First steps are the same — learn your audience, goals of the technical report, what recourses (articles, blogs) can help you write a good report, and so on.
Then list all your ideas of topics as they come to your mind, sort them into groups — it will be a rough outline of your future technical report. Now, you’re ready for a first draft. I want to provide you with some tips on how to write a good technical report in order to help you create a great first draft and save your time:
- When you’re searching for information on the Internet, keep in mind, that not all the information is reliable, so check it twice. The best way is to read relevant books, journals, and articles.
- Speaking of formatting, stick to one format — don’t use different fonts in your work. If you want to highlight an idea, use bold or italic.
- Heading and subheadings should be clear in order to ease the searching for necessary information. They also help readers get the main idea quickly. In my recent post called ‘ Using Humor in Technical Documentation ’ I showed an example of using humor in the table of contents, and it’s not a good idea — nothing is clear.
- It’s ok to use the information of other people but use citation — plagiarism is not a good idea of writing content. Check out Top 10 Free Plagiarism Detection Tools in order to be sure that you cite all sources.
- Proofread your content using these tips or a free grammar checker .
How best to present your report?
A presentation is important part of the final outlook of your work. So, what do you need to do:
- Write a script . Your report should be printed on an A4 paper on one side. It should not be hand-written because it’s not accepted.
- You should number those pages that contain the content , so, a title page and a summary are exceptions.
- Staple your report at the top left; if a report is too long, you should bind it.
- Formatting : usually the font size is 12, style is Times New Roman, the spacing is 1.5 or 2.
As you see, a technical report is not something difficult. You can write it easily sticking these tips, and also it’s a good idea to read technical reports of other authors. You will get the experience and build your style. However, my main recommendation is to write concisely. Concise was the word of 2017, but I think, it’s still relevant ;)
How did I become a technical writer? What skills do you need? Read FAQ on Technical Writing .
Many people who are interested in technical writing frequently ask me a lot of different questions, but here are the…
More from technical writing is easy.
Technical writing is for everyone!
About Help Terms Privacy
Get the Medium app
Kesi Parker
Job position: Freelance Technical Writer. Read my FAQ to learn more about me!
Text to speech
IMAGES
VIDEO
COMMENTS
This open textbook offers students of technical writing an introduction to the processes and products involved in professional, workplace, and technical writing. The text is broken up into sections reflecting key components of researching, developing, and producing a technical report.
A Guide to Technical Report Writing was originally written by Joan van Emden and the late Jennifer Easteal, and revised for the IET by Alex Kerr. ... This Guide suggests laws of good report writing, but only because in the field of communication, laws should be generally applied but broken if necessary. For example, the second law concerns brevity.
Download Free PDF IEEE TRANSACTIONS ON PROFESSIONAL COMMUNICATION, VOL. 46, NO. 1, MARCH 2003 75 Daniel G. Riordan and Steven E. Pauley Technical Report Writing Today—8th Ed. Book Review Index Terms—Electronic documentation, electronic research, presentations, technical reports.
Handbook of technical writing : Alred, Gerald J : Free Download, Borrow, and Streaming : Internet Archive Handbook of technical writing by Alred, Gerald J Publication date 2012 Topics Technical writing -- Handbooks, manuals, etc, Technical writing Publisher Boston : Bedford/St. Martins Collection
Download Free PDF. Download Free PDF. ... Writing 9th Edition. Handbook of Technical Writing 9th Edition. zabee khan. The five-way access system of the Handbook of Technical Writing provides readers with multiple ways of retrieving information: ... academic writing BOOK. Goy Alisara. Download Free PDF View PDF. The SLL&CS Research Handbook ...
An illustration of an open book. Books. An illustration of two cells of a film strip. Video An illustration of an audio speaker. ... Technical report writing today by Riordan, Daniel G; Pauley, Steven E. Publication date 2002 Topics Technical writing ... DOWNLOAD OPTIONS No suitable files to display here.
Technical Writing Basics: A Guide to Style and Form Author: Brian R. Holloway Published: 2nd edition (June 1, 2001) by Pearson College Div Pages: 210 Great for: Writing in more informative and persuasive style Source: Amazon This is another commonly found textbook on technical writing.
Download Free Report Technical Specification Source Details File Format MS Word Google Docs Size: 68 KB Download Technical Evaluation Report Letter Example Details File Format MS Word Google Docs Apple Pages Size: 142 KB Download Free Letter of Transmittal for Technical Report Details File Format MS Word Google Docs Apple Pages PDF Size: 145 KB
After creating the technical report, the researcher submits it to the project's sponsor. Such a report may contain procedures, design criteria, research history, images or illustrations, and other data relevant to the project. Technical Report Examples Download 377 KB #01 Download 474 KB #02 Download 196 KB #03 Download 202 KB #04 Download 1 MB #05
Download 30 KB. #33. Even if technical writing skills take high-levels details, you should still explain these concisely and clearly to your audience. As a technical writer, you should come up with documents that are very clear, simple, and succinct. Sometimes, though, the results could just be the opposite.
A guide to technical report writing - What makes a good technical report? 03 10 laws of good report writing 1. produce the report for your reader(s) 2. keep the report as short as possible 3. organise information for the convenience of the reader 4. include accurate references 5. ensure your writing is accurate, concise and straightforward
26 Best Technical Report Examples (Format & Free Templates) A technical report is a document created by a researcher that discusses the project's outcomes and is delivered to the project's sponsor. It is defined as a written technical document that gives accurate and evidence-based information.
Paper and report templates in Word make formatting and writing your school and business papers a snap. Write outlines, cover letters, speeches, theses, team reports, and business papers with pre-built report template designs or add your own customizations.
This article provides some general guidelines and "tips" for writing technical reports. Throughout the Mechanical Engineering curriculum you will be required to write formal reports--lab reports in ME 360 and ME 460; design project reports in ME 372 and ME 415; a capstone design project report in ME 490; and similar reports in other courses.
Technical Report Writing Today provides thorough coverage of technical writing basics, techniques, and applications. Through a practical focus with varied examples and exercises, students internalize the skills necessary to produce clear and effective documents and reports. Project worksheets help students organize their thoughts and prepare for assignments, and Focus boxes highlight key ...
17 Professional Technical Report Templates and Examples (Free Download) Business 17 Professional Technical Report Templates (+Format Samples) Preparing a technical report may seem straightforward. A researcher has completed their work on a particular subject and needs to summarize the work for others to review and comment on.
Free eBook while your book ships; Buy Paperback {{ studentProduct.buyingOptions.platform_0_textbookOptions_0_2.currentPrice ... Add to Cart. About This Product. TECHNICAL REPORT WRITING TODAY provides thorough coverage of technical writing basics, techniques, and applications. Through a practical focus with varied examples and exercises ...
Technical Report Writing Today Daniel G. Riordan, Steven E. Pauley 3.74 80 ratings9 reviews Technical Report Writing Today provides thorough coverage of the technical writing basics, techniques, and applications students are likely to encounter in both their academic courses and their future careers.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required. Learn more. ... TECHNICAL REPORT WRITING TODAY provides thorough coverage of technical writing basics, techniques, and applications. Through a practical focus with varied examples and exercises, students ...
1 x 6.5 x 9.5 inches. ISBN-10. 039573052X. ISBN-13. 978-0395730522. See all details. "Love Made Me More" by Colleen Rowan Kosinski for $11.99. An unexpectedly heartfelt tale of a friendship between a boy and an origami crane that continues throughout the boy's life.| Learn more.
The more concise the content, the better the score. Avoid wordy expressions. Keep things formal and to the point. Write out common abbreviations and explain technical abbreviations as often as possible. Imbibe all the above points in mind and utilize them for writing an excellent technical report.
Kesi Parker. 6.6K Followers. Job position: Freelance Technical Writer. Read my FAQ to learn more about me!