When I started reaching Chapter 8 of TCT there was one idea right out of the introduction stood out to me: “You need to organize the information… into patterns that are familiar to your readers” (TCT 180). Thinking about the way we view and transmit information, organization is important, and not just in writing applications.
Take data for example. Data is almost always organized into tables. It's difficult to even think about data organized in any other method. Data that isn't in tabular form would be hard to view coherently, let alone analyze. Tabular organization of data is just one pattern people are used to dealing with. And again, once we have data in tabular form, the logical progression for analysis and viewing is a graph. And with a graph, in order to show what means what without having to explain your package in great detail, you have to know what kind of graph to use (line, scatter, bar, etc), you have to know what information to include and on what axis, and you have to add tools for the reader such as axis titles and legends to help that person grasp the meaning of your graph.
That’s the image that popped into my head when I read "familiar patterns." A big part of what I’m doing right now in my internship is developing quantity and man-hour data into trend charts, which fits into this reading’s theme of organizing technical information.
It makes sense then to think about non-data-like technical information, such as support for a researched argument or a technical analysis, in a similar fashion. After all, tables and graphs are common visuals used to complement and support technical arguments and conclusions.
The idea of organization into familiar patterns definitely lends itself to building resumes. The chapter only briefly touched on resumes, which don’t follow the same pattern outlined in the reading. But the structure of a resume is never-the-less important for similar reasons. A recruiter at a job fair, for example, will typically scan a resume for specific pieces of information. If a resume follows one of the common structures given in the last reading, chances are the recruiter will know where to find the information he or she may be looking for. If not, that person might get confused or may not be able to find the information, which probably wouldn’t help the resume’s owner who would presumably looking for a job.
All-in-all, thinking in terms of familiar patterns should be a good aide in keeping audience needs in mind and lead to more success in writing.
Good point on Data Tables!
You make a great point about putting data in tables and how this is a familiar pattern for readers. As a psychology major who has to read several journal articles on studies, I know how useful these data tables can be. However, I think it’s important to point out that it’s often important (and usually expected) that you verbally explain that data as well. With the use of keys and legends, a data table or chart can usually speak for itself, but depending on your audience, you may need to spell out data and draw conclusions for your audience instead of relying on charts and/or graphs alone.
Kristin
Re: Good point on Data Tables!
I also like his comparison of placing data in tables, and using charts and figures, to the structure and organization of business documents, however I think these ideas merge. Data tables, charts, and figures are just another part of design patterns for organizing documents. White papers, for example, attempt to use graphics to make their details easier to understand. However, I've always found that I can understand a graph a lot easier if their is some text to explain it, even if there is a key or legend provided with it, so I agree on that point.
Tables and Graphs
Great analogy with the tables and graphs idea. In my major, I have to read way too many scientific papers on recent research and breakthroughs. These same scientists are notoriously terrible at english and organizational skills. More often than not I find myself just scanning the majority of the incomprehensible papers and getting the majority of my information directly from the graphs and figures. The other thing that helps me is that scientific papers are always divided into distinct sections, such as abstract, intro, results, methods, conclusion. This makes it much easier to find the information I am looking for and allows me to skip the sections that I don't care about and probably won't understand anyways. These section divisions are another example of organizational patterns. Without them, I would have no idea where to find this information. I have never seen a scientific paper without these divisions. Most journals will even reject articles that don't include these divisions, because journals frequently print only the important sections of papers due to limited space. This is just another example of how you need good organization when writing, otherwise, your paper may not even make it past your gatekeeper audience.
Data and Resumes
I understand what you mean that almost all data are put in tables and graphs. When you take a look at your typical audience responsible for evaluating your documentation involving data, it is important to follow specific guidelines to entertain their needs. The last thing you want is someone important wasting their time deciphering your format. As I read through this paragraph I immediately drew the connection between this and resumes. It is so crucial to follow expected formats because everything is done in such a time efficient manner. When you only have one minute to convince you’re qualified or 15 minutes to explain two pages of test results, it is important to trim any unnecessary mistakes.
R3 The Norm
I also think it is important to stay within the norm when writing a technical document for an audience which has time as a factor. Although being creative in writing can be a good way to stand out and be noticed in many respects, this is not one of them. The point is not to be noticed but to be effective and efficient. So, conforming to the preset writing style is this type of document is most certainly preferred if you want to be good at your job. That’s one area that I think that the system of these blogs misses the point on. If we are to learn to write technically then we should be able to get our point across quickly and effectively and be done with it. Word minimums tend to steer a writers style away from this idea.
Shane
Graphs target different readers
I like the analogy about he tables and graphs following a pattern. Perhaps these tables and graphs are created for a different audience. As many of you have stated, you just get what you need from these tables and graphs and ignore a majority of the text. I would argue that the graphs are there for that specific purpose. For someone that doesn’t car about the methodology, materials, or steps, but just care about the final answer, graphs are great. The text comes in when someone wants to understand the path taken or maybe try to recreate what the author is writing about. By providing both in the same paper, you have just hit two completely different audiences with one piece of writing.
Resume Organization
I really like your example of organizing information in a certain structure in your resume. It’s interesting how there’s a sort of de facto standard to writing a resume. Recruiters have a certain structure they look for already in mind in order to get the information out of it as quickly as possible. Organizing your resume to cater to your audience is a must because inherently you want to please your audience in this sort of scenario as much as possible. Also strategically placing things that are more important in your resume would give you the edge by knowing how recruiters usually scan over these documents.
Resume
I agree, knowing what an employer is looking for is the best information a job hunter can have. structuring your resume in a "pattern" that caters to an employers wants or needs is a great way to get an interview. Even if you are well qualified for the job, a poorly structured resume that doesn't highlight your good attributes could cost you. Nice job though adding in points from past readings.
Evan
Graphs/Charts
Something interesting that I have noticed for some time now, is that when people read scientific journal articles they typically scan the whole document and look at the graphs and tables for relevant information. Nine times out of ten, if the graphs or charts are bad or didn't have good information-the reader will not read anything else in that article. Your comment on familiar patterns in resumes is important-the opposing argument was brought up in another blog post. I think you're right here, though, you should use a standard 'pattern' for this-you make a good point here.