Sei sulla pagina 1di 3

Narvaez 1

Simon Narvaez III

James Beatty

1010

3 February 2017

Email Reflections

Upon reflecting on my textual artifacts, I think my writing fulfilled the ideas of a

quote by Lawrence C. Powell. That quote it states, Write to be understood, speak to be heard,

read to grow. I found this quote to quite particular to my emails because when writing these

artifacts, I had to brainstorm about how I would introduce these thoughts or ideas so that my

directed audience would understand. In my texts, I was trying to interpret a firm but professional

voice in writing to help get my points across so I could be heard. I think in a way my audience

grew from reading my texts. Because before reading my emails they had no idea that I had an

issue with my computer or that I wanted to be transferred over to another department. Thats

why I think this quote really stood out to me because it hit most of my key points. I wanted to be

understood, I wanted my voice heard and, I was trying to get my directed audience to grow from

my texts.

In my first artifact, it was addressing a more concerning matter in regards of having

technical difficulties. So, before I began typing out this email it took me a minute to brainstorm

on what points or rather how I would even begin to alert my problem. I went on an early break

and discussed with another co-worker to get some input for my email. After about 15 minutes or

so I decided to go with a direct approach, instead of beating around the bush. After much

evaluation on this first artifact I determined that I was attempting to make this an informative

text. More or less because I was informing my directed audience about the issues I was

experiencing.
Narvaez 2

What I have also noticed when reviewing this email is that, if Im referring to a specific time like

in sentence 2. I should really indicate what time is early because it gives the reader a better

understanding of my issue.

On my second artifact that one took me some time to type up. I was brainstorming for

about a week on how I would type out an issue that Ive brought up in the past. I figured if I

wanted to get the best outcome or the best response would be to make this persuasive. I started

out by thinking the best way to start and all I could think of was the IT department and how slow

they were addressing my issue, so I started off there. I knew I needed something that would catch

his attention so I told him, My performance would be so much more efficient if I was able to

right click. Hoping that would persuade him into considering things for me to help improve my

performance.

Shortly after I sent out this email. Id say about 20 minutes later I got a response from him saying

that the IT department was going to be heading to my desk in about an hour or so. Although this

email took me about a week or so to complete, I was glad that it met the purpose that this email

was intended for.

On my final artifact, this one didnt take me much thought like the other two did. I have

had experience from working in that department in the past. Which made it easier to brainstorm

what I was going to write. I first started to think about the time that I had spent in that

department. Which so happened to be around the same time last year from when this email was
Narvaez 3

written. I wanted to make this email very professional as well as persuasive so I could get the job

in that department. In the third sentence I stated, I know open enrolment is coming up in

October. Which is really busy time of year for underwriting.

Because of my past experiences with that department and remembering how busy AEP (Open

Enrollment) can be. I thought if I mentioned that in the email that it would give me a better shot

of getting transferred. Even though I thought the structure and professionalism was enough when

I imputed it in my email. That department was already filled up and was told if there was an

opening they would let me know.

What I have noticed from all my artifacts is that they are all structured about the same.

They all have the main point at the beginning and trying to get a solution at the end. The level of

formality stays consistent with each of the emails. They all stay on topic and dont drift off into

something that doesnt pertain to what I was trying to get out of it. I also noticed in the second

artifact compared to the first and third one. Is that the first and third artifact are written in a more

formal text. Starting off with Hey Isaac, & Hey, While the second artifact was written in

more of an informal text by starting off with I have already informed... Besides that, Id have

to say my tone is consistent throughout my emails. Because I was writing these emails to be

understood regarding my issues and wanting to move to a different department. I also wanted my

supervisors to understand/grow what I wanted to get out from writing these emails. Thats why I

think the quote I mentioned at the beginning really pertains to my artifacts in a big way.

Potrebbero piacerti anche