1. How do you think a small margin for error affects communication on a project? I would say in the article that I just read in the text book if there was any kind of error in the project meaning a communication break down between the teams it could set the project back for days. Also it could possibly make the project not work once in space and astronauts could not reach it. Here is a little from the text out of our book to help support my answer better “Communication strategies include one- to two-hour-long conference calls every week, to keep teams in various locations in touch, and one- to two-day-long technology interchange meetings (TIMs) every couple of months, where the teams meet to evaluate progress on all component systems of JWST. These face-to-face TIMs provide an important opportunity to discuss design options and the potentials of different technologies. Listening at these meetings is an essential skill as project managers and engineers convey ideas about the capabilities of a particular design and listen to their colleagues’ critiques and alternative ideas.”
2. In what ways do you act differently in a face-to-face meeting than you do during a telephone conference call? Well I have noticed when face to face some people don’t say things they would over a telephone conference. I would say also in face to face you can read people’s body language facial expressions where on a telephone conference you can’t. On a telephone conference you really only have to go by the tone of voice.
3 .Why is written communication essential in some situations (such as conveying specifications), while oral communication is essential in others (such as technology interchange transfers)? In some situations I think written communication is essential an example would be putting something together or certain
