UPI Study › Courses › Ethics in Technology › Free lessons › Lesson 15.9 Free with a free account
The Unwritten Rules for Professional and Respectful Communication Using Technology
Ethics in Technology · Chapter 15: Doing the Right Thing: Ethics, Media Responsibility, and Digital CitizenshipSection 15.9 · lesson 108 of 11614 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Ethics in Technology.
Lesson complete
Earn the 3 college credits for Ethics in Technology
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: What Employers Can Monitor, What Employees Can Expect, and Where the Law Draws the Line →← How Privacy, Security, and Ownership Rights Overlap in the Digital LandscapeNext lesson: What Employers Can Monitor, What Employees Can Expect, and Where the Law Draws the Line →
In this lesson
Unwritten norms for email, messaging and video meetings.
- Explain netiquette and how it varies by channel
- Recognize how written tone and clarity can be misread
- Describe typical channel response expectations
- Apply professional reply-all and CC etiquette
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,907 words). Read along, or search it.
Doing the Right Thing: Ethics, Media Responsibility, and Digital Citizenship
Professional Digital Communication
Digital communication depends on informal expectations, which shape how colleagues interpret professional behavior. This lesson calls those expectations netiquette, across email, messaging, and video meetings. First, explain what netiquette means, and why the same behavior can differ across channels. The second objective examines written tone, which can be lost or misread without vocal cues. Then describe typical response expectations, while recognizing that actual deadlines and workplace agreements matter. Finally, apply reply-all and carbon-copy etiquette, to choose an appropriate audience for a message. These norms are often unwritten, and people learn them through observation or occasional correction. That does not make their effects unimportant, to the people receiving the communication. A reader needs to understand the purpose, the timing, and any action expected from them. The writer can support those needs, through clear wording and thoughtful channel choices. We will connect courtesy with those practical decisions, rather than treat it as decorative politeness.
Netiquette Across Channels
The Same Style Can Carry Different Expectations
Netiquette means informal norms. They govern polite and professional behavior in digital communication. The source compares three channels. Each carries different expectations about style and behavior. Email generally has the most formal register, with a subject, greeting, sign-off, and complete sentences. Messaging permits more casual language, shorter fragments, and faster exchanges between participants. Professional messaging still expects clarity and courtesy, beyond what friends may accept in private texting. Video meetings add live expectations, including punctual joining, muting, and attention to the speaker. These behaviors affect a shared conversation, rather than only the written words on a screen. A style learned in one channel, may therefore seem careless when carried into another. Local norms can differ, and accessibility needs may affect how people participate in meetings. The useful principle is to understand the medium, and the people relying on the communication. Adapt thoughtfully, rather than assume every channel should behave like a conversation with a close friend.
Professional Email
Structure Helps the Recipient Understand the Message
Professional email typically uses structure, which helps the reader understand and locate its purpose. A clear subject line signals what the message concerns, before the recipient opens it. A greeting establishes the professional register, while a sign-off gives the exchange a clear ending. Complete sentences remain a common expectation, in most professional email contexts described by the source. Together, these features help carry meaning, without depending on the familiarity of a chat conversation. They also reduce the chance that abrupt fragments, seem careless to someone expecting a formal message. The lesson is not a claim, that every workplace uses identical conventions or the same degree of formality. Consider the context and relationship, while preserving the information the recipient needs to understand. Clarity and courtesy give the structure a purpose, rather than adding formality for its own sake. A professional message should make its meaning accessible, to the particular person receiving it. Email's typical expectations provide a useful starting point, when the relationship is less familiar.
Messaging and Video
Informality Still Needs Courtesy; Meetings Add Live Behavior
Messaging allows a more casual register, but professional chat still needs a clear meaning. Short fragments can fit a quick exchange, when both people understand the context. They should not leave a colleague guessing, about what is being asked or why it matters. The source distinguishes this setting, from texting between friends who share extensive personal context. Video meetings require another adjustment, because several people experience the interaction at the same time. Joining on time helps respect the shared schedule, rather than disrupting the discussion after it begins. Muting when not speaking can reduce background sound, which makes other participants harder to hear. Giving attention to the speaker supports the live exchange, alongside the meeting's participation expectations. These concerns involve timing, sound, and attention, in ways a written message does not. Match the behavior to the medium, while remaining attentive to local norms and participation needs. The common purpose is communication that colleagues, can understand and use without avoidable disruption.
Tone and Clarity
Written Words Lose Helpful Vocal and Visual Cues
Written text removes several cues, which normally help people understand the emotional meaning of speech. The recipient cannot hear the writer's tone of voice, or see a facial expression. Conversational timing is also different, which can change how a brief question is experienced. A writer intending a neutral request, may produce words that look curt or annoyed. The risk can be greater when the reader, does not already know the sender's usual style. One useful habit is reading the message back, before deciding it is ready to send. Reading aloud can make an unintended tone noticeable, rather than leaving it hidden in silent drafting. Ask how the words might sound, to someone who does not share the writer's assumptions. The perceived tone may differ from the intended one. That difference can create avoidable friction. Clear wording helps carry the meaning, which voice and expression would otherwise supply. The goal is to help the reader understand, rather than expect them to reconstruct missing cues.
Intent and Relationship
Make the Request Clear Instead of Relying on Familiarity
The source suggests stating intent explicitly, instead of relying only on punctuation to communicate tone. Its example says, just a quick question, no rush, making the timing clearer to the reader. Such wording should truthfully match the request, rather than conceal urgency behind reassuring language. Sarcasm and dry humor need care, because text can make their intended meaning difficult to recognize. They are safer in relationships or channels, where the reader already understands the writer's style. The reading also asks us to consider, an all-lowercase message with no punctuation. From a familiar colleague, that style may seem relaxed, friendly, and entirely ordinary. From someone the reader barely knows, the same style may look careless or insufficiently professional. Tone therefore depends partly on the words, and partly on the existing relationship. Familiarity can explain an interpretation. It cannot guarantee that every joke will land. Read the message from the recipient's perspective, and state important intent directly when needed.
Typical Response Expectations
Treat the Source’s Times as Illustrations, Not Deadlines
Different communication channels carry different typical expectations, about the time before a response. The source's chart describes instant messages, as receiving replies within minutes during working hours. Text messages have a looser illustration, with a response within a few hours. Email operates on a slower business-day timescale, and the chart also mentions twenty-four to forty-eight hours. Those phrases are not identical durations, so the chart should not be treated as an exact deadline. Formal letters or memos illustrate a still slower expectation, measured in several business days. These are general examples, rather than fixed promises from every recipient in every workplace. A stated deadline, manager's communicated expectation, or agreed workplace practice can replace the generic illustration. Working hours and actual availability also matter, particularly when a channel feels instant to the sender. Choose and interpret the medium with those expectations in mind, instead of assuming constant access to a colleague. The purpose of the chart is comparing channels, rather than creating unsupported response guarantees.
Urgent Requests
The Sender Should Choose a Channel That Fits the Need
A genuinely urgent request makes channel choice, part of the sender's responsibility. The source warns against sending an email, then silently expecting the recipient to respond immediately. That expectation conflicts with the slower timescale, often associated with professional email. An instant message or phone call, may better fit a request requiring faster attention. The choice still depends on the workplace, the recipient's availability, and any agreed escalation process. State the actual timing clearly, instead of relying on the medium to explain everything. A request can be understandable in content, yet still create friction through an unrealistic response assumption. The sender should consider that risk, before choosing how to contact the recipient. This does not turn a fast channel, into a promise that every person is always available. It connects urgency with deliberate communication, rather than an unspoken demand for immediate action. Match the request, channel, and timing, so the recipient can understand what is needed.
Reply-All Decision
Send a Group Reply When the Group Needs Its Content
The reply-all decision begins with the people, who genuinely need the content of this particular response. Ask whether everyone on the thread, needs to see what you are about to send. If the answer is no, reply to the sender, or an appropriate relevant subset instead. If everyone needs the information, check whether the reply is only a routine acknowledgment. A message consisting of thanks or sounds good, usually adds little value to a large group. Consider skipping that acknowledgment, or sending it only to the original sender where appropriate. A substantive update can justify reply-all, when it changes what the entire group needs to do. The source's diagram separates shared need, from the unnecessary repetition of a brief acknowledgment. Avoiding needless recipients reduces noise. Leaving out necessary recipients can also cause problems. Check responsibilities before sending, rather than assume a later correction always repairs an important omission. The right audience is the group that needs this content, rather than automatically everyone or automatically fewer people.
To, CC and Escalation
Identify Who Needs to Act and Who Needs Awareness
The To field normally identifies people, expected to read, respond, or act on the message. The carbon-copy field normally signals awareness, without assigning that recipient an action. That distinction helps readers understand their role, alongside the message's actual wording. When someone needs to do something, make that responsibility explicit, rather than rely entirely on recipient fields. The source contrasts a one-word acknowledgment, sent to a group of twenty people, with a substantive update. The acknowledgment usually adds unnecessary notifications, while the update may change everyone's next steps. Shared need makes the difference, rather than the simple fact that both are replies. Adding a colleague's manager merely to apply pressure, is generally poor professional etiquette. When escalation is genuinely necessary, the source favors addressing the concern through a direct conversation. Audience selection should serve the task, rather than covertly turn a message into a threat. Use To, carbon copy, and reply-all deliberately, to communicate the right information to the right people.
4 Key Terms and Takeaways
Courtesy Connects Channel, Tone, Timing and Audience
Review four terms, connecting digital courtesy with the practical experience of the recipient. Netiquette means informal norms, for polite and professional digital communication across channels. Tone is the emotional quality a reader perceives, which may differ from what the writer intended. Reply-all sends the response to every recipient, rather than only to the original sender. Carbon copy includes someone primarily for awareness, rather than automatically assigning an action. The first takeaway is channel fit, with email, messaging, and video carrying different expectations. The second is clarity, because missing vocal and visual cues make explicit intent useful. The third is timing: choose a channel, which matches a genuinely urgent request. The fourth is audience selection, using reply-all for shared need and carbon copy for awareness. These habits reduce uncertainty about meaning, timing, and the role of each recipient. Courtesy becomes useful when it helps colleagues, understand the communication and act appropriately.
Review and Apply
Explain the Reader’s Needs Before Choosing the Message Style
The first review asks why the same casual style, can be interpreted differently from different senders. The words and the existing relationship both shape, the tone a reader perceives. The second asks for one habit, that reduces the risk of a message being misread. Read the draft back, ideally aloud, or state the intent explicitly rather than leaving it implicit. The third asks who should match an urgent request, with an appropriately fast channel. The sender chooses the channel and states the timing, while considering actual workplace expectations. The fourth asks reply-all's guiding question: does everyone, genuinely need this particular response? A substantive shared update may qualify, while a routine acknowledgment usually does not. The fifth distinguishes carbon copy from To, comparing awareness with an expected response or action. Explain the recipient's role clearly, so the fields support rather than replace the message's meaning. Across all five answers, connect professional courtesy, with clarity, truthful timing, and an appropriate audience.
About Ethics in Technology at UPI Study
Ethics in Technology (Computer Science 195) is a self-paced online course of 116 video lessons in 15 chapters, from cybersecurity basics, privacy and surveillance to big data, hacking, malware, network defense, intellectual property, cybercrime, encryption, emerging technology and digital citizenship. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Computer Science courses
Compare: Cybersecurity vs Ethics in Technology · Which ethics course?
Why take it here
Why students take Ethics in Technology with UPI Study
Where the credit goes
Universities that work with NCCRS
Ethics in Technology carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About The Unwritten Rules for Professional and Respectful Communication Using Technology
What is netiquette, and how does it differ across email, chat, and video meetings?
How do you avoid sounding rude or curt in a work email or message?
How quickly should you reply to work emails and messages?
When should you use reply-all, and what is the difference between To and CC?
About the Ethics in Technology course
How many college credits is Ethics in Technology?
How much does Ethics in Technology cost and what is included?
Which universities accept UPI Study credits?
How long does Ethics in Technology take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Ethics in Technology.
116 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →