06.09.2021 Views

Interpersonal Communication- A Mindful Approach to Relationships, 2020a

Interpersonal Communication- A Mindful Approach to Relationships, 2020a

Interpersonal Communication- A Mindful Approach to Relationships, 2020a

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

First, our definition of netiquette emphasizes that different contexts can create different netiquette needs.<br />

Specifically, how one communicates professionally and how one communicates socially are often quite<br />

different. For example, you may find it entirely appropriate <strong>to</strong> say, “What’s up?!” at the beginning of an<br />

email <strong>to</strong> a friend, but you would not find it appropriate <strong>to</strong> start an email <strong>to</strong> your boss in this same fashion.<br />

Furthermore, it may be entirely appropriate <strong>to</strong> downplay or disregard spelling errors or grammatical<br />

problems in a text you send <strong>to</strong> a friend, but it is completely inappropriate <strong>to</strong> have those same errors<br />

and problems in a text sent <strong>to</strong> a professional-client or coworker. One of the biggest challenges many<br />

employers have with young employees who are fresh out of college is that they don’t know how <strong>to</strong><br />

differentiate between appropriate and inappropriate communicative behavior in differing contexts.<br />

This lack of professionalism is also a problem commonly discussed by college and university faculty<br />

and staff. Think about the last email you sent <strong>to</strong> one of your professors? Was this email professional?<br />

Did you remember <strong>to</strong> sign your name? You’d be amazed at the lack of professionalism many college<br />

and university faculty and staff see in the emails sent by your peers. Here are some general guidelines for<br />

sending professional emails:<br />

• Include a concise, direct subject line.<br />

• Do not mark something as “urgent” unless it really is.<br />

• Begin with a proper greeting (Dear Mr. X, Professor Y:, etc.)<br />

• Double-check your grammar.<br />

• Correct any spelling mistakes.<br />

• Include only essential information. Be concise.<br />

• State your intention clearly and directly.<br />

• Make sure your message is logically organized.<br />

• Be polite and ensure your <strong>to</strong>ne is appropriate.<br />

• Avoid all CAPS or all lowercase letters.<br />

• Avoid “textspeak” (e.g., plz, lol)<br />

• If you want the recipient <strong>to</strong> do something, make the desired action very clear.<br />

• End with a polite closing (using “please” and “thank you”).<br />

• Do not send an email if you’re angry or upset.<br />

• Edit and proofread before hitting “send.”<br />

• Use “Reply All” selectively (very selectively)<br />

Rules and Norms<br />

Second, our definition of netiquette combines both rules and norms. Part of being a competent<br />

communica<strong>to</strong>r in a CMC environment is knowing what the rules are and respecting them. For example,<br />

if you know that Twitter’s rules ban hate speech, then engaging in hate speech using the Twitter platform<br />

shows a disregard for the rules and would not be considered appropriate behavior. In essence, hate<br />

speech is anti-netiquette. We also do not want <strong>to</strong> ignore the fact that in different CMC contexts, different<br />

norms often develop. For example, maybe you’re taking an online course and you’re required <strong>to</strong> engage<br />

in weekly discussions. One common norm in an online class is <strong>to</strong> check the previously replies <strong>to</strong> a post<br />

before posting your reply. If you don’t, then you are jumping in<strong>to</strong> a conversation that’s already occurred<br />

and throwing your two-cents in without knowing what’s happening.<br />

<br />

<strong>Interpersonal</strong> <strong>Communication</strong> 416

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!