We learned formal and informal way of communication through Asia Pacific Video. While speaking, we use informal words and abbreviate combinations (Eg. We’ll). During the course of writing we use formal words. To make communication stronger, we should bring improvement in our writing style. As mentioned in the earlier blog, we don’t speak words in the way in which we write and vice versa. Certain language choices, words and structures are more formal than others and are reserved for more formal situations. I learned as to how I can bring development in writing by using formal words. E.g.; Rise is less formal than expansion. In a real scenario, we normally speak and write in informal language which may not turn in to effective writing.
Presentations were given by Hiren and Alpesh. Based past feedback on presentations given, I found pros and cons in both presentations. Presentation of Hiren felt better than Alpesh. Excessive usage of some of the words defeats the purpose. In presentation of Hiren, I observed that pauses are reduced and still he should make effort to bring further improvement. Frequent usage of “Right”, “ok?” defeats the purpose. He should still focus more on formulation of sentences and avoid grammatical mistakes. He needs to maintain eye contact. On the other hand, his charm was really good and he did good job in delivering presentation with the help of lesser number of slides.
Lots of improvement calls for presentation of Alpesh. Eye contact was not proper and lacking in charm. He was delivering presentation on Performance Measurement System where as he was frequently speaking “Performance Management system”. He stood at a corner. Movement was lacking. He has not done audience analysis and putting more stress on words was making presentation boring. He applied smart way to handle Q/A session. Overall I would say that it calls for lot of improvement.
Whatever feedback received by individual member in Task-2 were shared internally. While going though feedback, we came to know that almost all were lacking in mentioning flow of thoughts/ideas. Even I did one technical mistake for which I haven’t thought that some one can do critical analysis like this. I should cite example of AI after example of calculator. Some of the words I’ve used were redundant. I should avoid false starts like “There may be chances”. I’ll take care of feedback generally we’ve received in my next draft.
Presentations were given by Hiren and Alpesh. Based past feedback on presentations given, I found pros and cons in both presentations. Presentation of Hiren felt better than Alpesh. Excessive usage of some of the words defeats the purpose. In presentation of Hiren, I observed that pauses are reduced and still he should make effort to bring further improvement. Frequent usage of “Right”, “ok?” defeats the purpose. He should still focus more on formulation of sentences and avoid grammatical mistakes. He needs to maintain eye contact. On the other hand, his charm was really good and he did good job in delivering presentation with the help of lesser number of slides.
Lots of improvement calls for presentation of Alpesh. Eye contact was not proper and lacking in charm. He was delivering presentation on Performance Measurement System where as he was frequently speaking “Performance Management system”. He stood at a corner. Movement was lacking. He has not done audience analysis and putting more stress on words was making presentation boring. He applied smart way to handle Q/A session. Overall I would say that it calls for lot of improvement.
Whatever feedback received by individual member in Task-2 were shared internally. While going though feedback, we came to know that almost all were lacking in mentioning flow of thoughts/ideas. Even I did one technical mistake for which I haven’t thought that some one can do critical analysis like this. I should cite example of AI after example of calculator. Some of the words I’ve used were redundant. I should avoid false starts like “There may be chances”. I’ll take care of feedback generally we’ve received in my next draft.
No comments:
Post a Comment