Chapter 21 which talks about oral presentations did not give me that much insight into doing them that I did not already know. A lot of the information was a repeat from when I took com 101 or public speaking. It talks about the same format which we used for that.
I don't think the example that the book gets on preparing for speeches by saying them out loud is that helpful. I think by doing it in your head helps a lot more. I think this gives you a pretty good estimate of how long the presentation should actually last.
I really when doing a presentation like to follow the Extemporaneous way of doing it. Making an outline always works well for me and just following close. I feel like the scripted way of doing a presentation like the text talks about makes you sound like a robot and you end up looking at note cards not focusing on your audience which is why you are giving the speech in the first place.
Sunday, February 27, 2011
Wednesday, February 16, 2011
Markel Chapter 4 Week of Jan 25th
Chapter 4 was about writing collaboratively. This is important because most businesses work with "team work" which often calls for numerous people looking over one object. In the end the project should end up being really well written but also looking as if one person wrote it and not sloppy. We already practice collaboratively writing in school when we work on group projects, so we all know the ups and downs. The Markel chapter 4 starts out talking about the problems of writing collaboratively then goes on to talk about the positive sides.
This is very important especially in this class as we work on a lot of group assignments. It helps us split up work and take the load of one person. It also creates problems though as people don't always agree and there's always a free-rider in most groups. It's especially relevant because we use Google Docs in this class a lot and it teaches us how to not get frustrated when their are two or more sets of eyes on a paper changing things.
This is very important especially in this class as we work on a lot of group assignments. It helps us split up work and take the load of one person. It also creates problems though as people don't always agree and there's always a free-rider in most groups. It's especially relevant because we use Google Docs in this class a lot and it teaches us how to not get frustrated when their are two or more sets of eyes on a paper changing things.
week of 2/1/11 Instruction Manual
I think the instruction manual assignment helped us not only learn how to write an instuction manual that is very detailed, but also taught us the importance of communicating so that people we work with understand every step. When you don't say things the correct way things can be misconstrued. Not only do people communicate differently when they are very similar we have a vast array of different types of people in the U.S. who think and speak differently so it's important to go with a universal approach when constructing an instruction manual. We learned this after our first attemt. We did not think that people could mess up an object so simple.
When we started having another group work on the project their's looked similar but was not exact. We'd missed telling them how much clay exactly they needed when building the object so it was not preportioned correct and the object was not the right size in areas. By being able to watch someone else fail at our directions we were able to fix them when re-writing our next set of instructions. It was very hands on and overall the perfect way to learn how to write a good instruction manual.
When we started having another group work on the project their's looked similar but was not exact. We'd missed telling them how much clay exactly they needed when building the object so it was not preportioned correct and the object was not the right size in areas. By being able to watch someone else fail at our directions we were able to fix them when re-writing our next set of instructions. It was very hands on and overall the perfect way to learn how to write a good instruction manual.
Markel Chapter 16 and 19
Chapters 16 and 19 of Markel are a lot like the other chapters. They give you guidelines on how to prepare to write a successful proposals and reports. In chapter 16 we learn about proposals which are very vital in business decisions. People in business will not take you seriously if you don't pay attention to detail when writing one. Knowing who you are writing a proposal to is very important, for example your own company, or another company. It is also to make sure you have all the facts clear so that you look like you know what you are dong.
My parents own their own business and have to write proposals to other stores all the time so they use solicited proposals when they are trying to get another business to supply to their store. They tend to use an unsolicited proposal when selling to other businesses they feel would save from buying their products as they run a liquidation tool store. I found some valuable information on some of the proposal ideas for them. It was also valuable information because I plan on going into event coordinating. I will need to work with supply businesses by using proposals.
Chapter 19 talks about writing recommendation reports. I used to work at Nissan so I've gotten pretty good at writing recommendation letters. You use them everyday pretty much in any business. When writing one you almost always give a definition of the problem that has occurred. It is then followed about a way or possible ways that problem can be potentially resolved.
My parents own their own business and have to write proposals to other stores all the time so they use solicited proposals when they are trying to get another business to supply to their store. They tend to use an unsolicited proposal when selling to other businesses they feel would save from buying their products as they run a liquidation tool store. I found some valuable information on some of the proposal ideas for them. It was also valuable information because I plan on going into event coordinating. I will need to work with supply businesses by using proposals.
Chapter 19 talks about writing recommendation reports. I used to work at Nissan so I've gotten pretty good at writing recommendation letters. You use them everyday pretty much in any business. When writing one you almost always give a definition of the problem that has occurred. It is then followed about a way or possible ways that problem can be potentially resolved.
Subscribe to:
Posts (Atom)