Group Project - Lab Reports

I am a part of the group that will be teaching the class to write lab reports. I am not familiar with how to write up professional lab reports, and fellow members in my group are also not totally familiar with the process, so this should be an experience. We are learning just as much as the rest of the class will be learning. We all get along well and haven't had any disagreements of any sort.
Through research we have found that all lab reports follow the same sort of structure. The group has split the portions of a typical lab report up so we can each research on our own over the course of the week. There is a title, an introduction, methods and materials, and more. Essentially, what I've learned so far that is most important is that the lab report should make the experiment easy for other scientists or interested parties to repeat on their own.
I have got the pieces that include the results (sort of the numerical data), analysis and discussion. This is the part of the report that summarizes what happened over the course of the experiment, why it's important, and whether or not the results support the hypothesis. These reports are super meticulous and detailed, and done for almost every experiment. I've discovered through this research that I am glad I did not choose the path of science, because I've never been accurate with numbers. It stresses me out just reading about it.

I did find a good resource on how to make an accurate and concise lab report:

https://writingcenter.unc.edu/handouts/scientific-reports/

Instructions

I'm going to do my instructions on how to make a great coffee as an employee of Dunkin' Donuts. I have worked there for about 5 years, and consider this one of my greatest (and also really one of my lamest)  accomplishments. There is actually a process beyond what you are trained to do that adds to the flavor. It is all in the tiny details of what you do. It will be interesting to write what comes naturally to me at this point. It might honestly be a challenge, but I'm up for it. It may also be a challenge color coordinating these instructions because Dunkin's mix of orange and purple isn't easy to work with.

Instructions and Manuals

This week's reading was about creating effective instruction for products, and also clear and efficient manuals.
This chapter read to me a lot like creating a website as in our last reading, or informational pamphlets. As usual, to start, always keep the audience in mind when making a technical document. Who are they?  What is their goal? What might their age group be? Where will they be reading the document? What is the general demographic of the document, and what might others be? Which languages and images should go into the instructions?
I also wasn't aware that even using a left hand in images can be offensive in some places in the Middle East. It pays to know the culture that an instruction booklet might enter, even the smallest of details.
Of course, anything that can be written simply should be written that way, especially when it comes to the safety section of a manual. The warnings should also stand out amid the instructions. The writer of these documents can be sued if someone is hurt - there is a liability that comes with giving efficient instructions.
Instructions should be numbered, and organized. Steps should not run into each other, or be confusing. I know there have been many times in my life when I've tried to build something using a manual, and I've had left over parts and panicked. No consumer wants to have to rebuild something the've already spent hours building.
While instructions typically are just for the startup of a product, manuals require way more care and concern, as it is for the start, anad a future reference point if there is ever an issue with the product in question.
Important points to remember:

• Know the audience
• Be clear and concise
• Use appropriate images
• Organize information properly

Designing Documents and Web Sites

The reading today was on the most efficient way to design a document, and also a web site. The advice varies, as it depends on which technical document is being created. Five important pieces of advice for creating both a web site and a document are:

• Know the audience, and know what they want from the document.
• Know the overall goal of the document. Does it achieve the goal?
• Clearly label the document, because the audience most likely does not need every bit of information available in it.
• Keep it as organized and as appealing to the eye as possible.
• Always keep the values of the company and audience in mind.

 The chapter goes into great detail regarding not only keeping information accurate and understandable, but also advice on selecting a typeface for the document. Every factor must be considered in the plan of the design, even the white spaces, which I was not aware of. There is really a science to the creation of a technical document, from the amount of columns on one page to the next. It must take a lot of planning and effort to make the document that best holds the value of an organization and its goals.
It also suggests not compiling a ton of information on one single page, as the audience must be drawn to the document in order to continue paying attention to it. A web site should be clearly labeled and easy to navigate, for any member of the audience. Utilize icons, and other recognizable images to assist the journey through the document, while keeping various cultures in mind.
In my fifth year of college, I can agree to all of the advice. When I have to shuffle through a ton of websites to find certain information, it can get frustrating. I'm naturally going to be drawn toward the website or document that is well put-together. I don't want to have to read a giant block of text if I can help it, and I know others feel the same way.
I also thought it was funny that the book told readers on page 157 not to use shadowed or outlined variations of text, because we "can live a full, rewarding life without ever using them."

Assignment #1

The pamphlet I will be analyzing for class is titled "Why Animals Don't Smoke," and it has been in circulation for many years as I first saw this pamphlet in a dentist's office as a kid. It's filled with pictures of various animals, like giraffes and tortoises, who explain individually why they don't smoke (for example, the giraffe says that he doesn't want a sore throat). The audience is younger children, as the pictures are brightly-colored and cartoon-like. It's also from a company called Journeyworks who publish a lot of similar pamphlets for people of all ages regarding subjects like hand-washing, the flu, and even heart disease. It's definitely clear, simple, and easy to understand.