Skip to main content
Business LibreTexts

3.5: Channels

  • Page ID
    36626
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Purpose is closely associated with channel. We need to consider the purpose when choosing a channel. From source to receiver, message to channel, feedback to context, environment, and interference, all eight components play a role in the dynamic process. While writing often focuses on an understanding of the receiver (as we’ve discussed) and defining the purpose of the message, the channel—or the “how” in the communication process—deserves special mention.

    So far, we have discussed a simple and traditional channel of written communication: the hard-copy letter mailed in a standard business envelope and sent by postal mail. But in today’s business environment, this channel is becoming increasingly rare as electronic channels become more widely available and accepted.

    When is it appropriate to send an instant message or text message versus a conventional e-mail or fax? What is the difference between a letter and a memo? Between a report and a proposal? Writing itself is the communication medium, but each of these specific channels has its own strengths, weaknesses, and understood expectations that are summarized in Table \(\PageIndex{1}\).

    Table \(\PageIndex{1}\) Written communication channels
    Channel Strengths Weaknesses Expectations When to choose
    Instant message or text message Very fastGood for rapid exchanges of small amounts of information

    Inexpensive

    InformalNot suitable for large amounts of information

    Abbreviations lead to misunderstandings

    Quick response Informal use among peers at similar levels within an organizationYou need a fast, inexpensive connection with a colleague over a small issue and limited amount of information
    Channel Strengths Weaknesses Expectations When to choose
    Email FastGood for relatively fast exchanges of information

    “Subject” line allows compilation of many messages on one subject or project

    Easy to distribute to multiple recipients

    Inexpensive

    May hit “send” prematurelyMay be overlooked or deleted without being read

    “Reply to all” error

    “Forward” error

    Large attachments may cause the e-mail to be caught in recipient’s spam filter

    Normally a response is expected within 24 hours, although norms vary by situation and organizational culture You need to communicate but time is not the most important considerationYou need to send attachments (provided their file size is not too big)
    Channel Strengths Weaknesses Expectations When to choose
    Fax FastProvides documentation Receiving issues (e.g., the receiving machine may be out of paper or toner)Long distance telephone charges apply

    Transitional telephone-based technology losing popularity to online information exchange

    Normally, a long (multiple page) fax is not expected You want to send a document whose format must remain intact as presented, such as a medical prescription or a signed work orderAllows use of letterhead to represent your company
    Channel Strengths Weaknesses Expectations When to choose
    Memo Official but less formal than a letterClearly shows who sent it, when, and to whom Memos sent through e-mails can get deleted without reviewAttachments can get removed by spam filters Normally used internally in an organization to communicate directives from management on policy and procedure, or documentation You need to communicate a general message within your organization
    Channel Strengths Weaknesses Expectations When to choose
    Letter FormalLetterhead represents your company and adds credibility May get filed or thrown away unreadCost and time involved in printing, stuffing, sealing, affixing postage, and travel through the postal system Specific formats associated with specific purposes You need to inform, persuade, deliver bad news or negative message, and document the communication
    Channel Strengths Weaknesses Expectations When to choose
    Report Can require significant time for preparation and production Requires extensive research and documentation Specific formats for specific purposes You need to document the relationship(s) between large amounts of data to inform an internal or external audience
    Channel Strengths Weaknesses Expectations When to choose
    Proposal Can require significant time for preparation and production Requires extensive research and documentation Specific formats for specific purposes You need to persuade an audience with complex arguments and data

    By choosing the correct channel for a message, you can save yourself many headaches and increase the likelihood that your writing will be read, understood, and acted upon in the manner you intended.

    In terms of writing preparation, you should review any electronic communication before you send it. Spelling and grammatical errors will negatively impact your credibility. With written documents, we often take time and care to get it right the first time, but the speed of instant messaging, text messaging, or emailing often deletes this important review cycle of written works. Just because the document you prepare in a text message is only one sentence long doesn’t mean it can’t be misunderstood or expose you to liability. Take time when preparing your written messages, regardless of their intended presentation, and review your work before you click “send.”

    Attribution

    This chapter is an adaptation of Chapter 5.2 “Think, then write: Writing preparation” in Business Communication for Success and is used under a CC-BY-NC-SA 4.0 International license.


    This page titled 3.5: Channels is shared under a CC BY-NC-SA license and was authored, remixed, and/or curated by Melissa Ashman (KPUOpen) .

    • Was this article helpful?