{"id":44,"date":"2022-07-13T16:54:03","date_gmt":"2022-07-13T20:54:03","guid":{"rendered":"https:\/\/pressbooks.bccampus.ca\/communicating\/chapter\/eliminating-wordiness\/"},"modified":"2026-02-13T18:50:09","modified_gmt":"2026-02-13T23:50:09","slug":"chapter-14","status":"publish","type":"chapter","link":"https:\/\/pressbooks.bccampus.ca\/communicating\/chapter\/chapter-14\/","title":{"raw":"Achieving Conciseness","rendered":"Achieving Conciseness"},"content":{"raw":"In many of your classes, you are probably used to trying to stretch out your writing to reach that 1,000-word goal for an essay. This is a habit you want to <em>avoid<\/em> in professional communication because professional audiences\u2014employees, clients, supervisors, and others\u2014prefer writing that is clear and, most importantly, <strong>concise<\/strong>. For our purposes, [pb_glossary id=\"167\"]<strong>conciseness<\/strong>[\/pb_glossary] means using the fewest words possible to achieve the goal of communication.\r\n\r\nWhat is the goal of communication? It is to ensure that your reader understands your intended meaning. Just ask yourself, if you were given the choice between reading a 500 word article and a 250 word article that both communicate the same meaning, which one would you prefer to read?\r\n\r\nTo be clear, there is nothing grammatically wrong with all the examples we will cover below. However, having perfect grammar doesn't mean a message is particularly well-written. The issue here is a matter of style\u2014and style is perhaps the most important and most difficult skill professional writers need to master. Using the techniques listed below will keep readers focused on your message and help them interpret what you are saying more easily.\r\n\r\nSo, how do we make our writing more <strong>concise<\/strong>? Here are a few basic steps you can follow.\r\n<h2>1. Mass-delete whatever doesn\u2019t belong<\/h2>\r\nThe first practical step towards trimming your document is a large-scale purge of whatever doesn\u2019t contribute to the purpose you set out to achieve. Such a purge is important because you don\u2019t want to waste time proof-editing anything that you\u2019re just going to delete anyway. However, this action is probably the most difficult one to take because it involves deleting large swaths of writing that may have taken some time and effort to compose.\r\n\r\nDon't be sentimental about your own writing, especially with professional documents. If the writing is better without it, cut it.\r\n\r\nA good rule is that, if the content could potentially sidetrack readers, whose understanding of the topic would be unaffected (at best) or overwhelmed (at worst) by it's inclusion, those sentences, paragraphs, and even whole sections simply must go. Highlight, delete, and\u00a0 move forward.\r\n\r\n(Save older versions of your work just in case you end up wanting to retrieve any of that later or use tracked changes technology to keep a record of what was deleted.)\r\n<h2>2. Delete long lead-ins<\/h2>\r\nThe next way to be concise comes from deleting lead-ins.<strong> [pb_glossary id=\"168\"]Lead-ins[\/pb_glossary] <\/strong>are the groups of words that you wrote to gear up towards your main point. In ordinary speech, we use <strong>lead-ins<\/strong> as something like throat-clearing exercises. In writing, however, these are often useless (at best) because they state the obvious. At worst, <strong>lead-ins<\/strong> immediately upset the reader by signaling that the rest of the message will contain some time-wasting text.\r\n\r\nTake the following the examples:\r\n<div class=\"textbox shaded\">\r\n<ul>\r\n \t<li>I\u2019m Jerry Mulligan and I\u2019m writing this email to ask you to please consider my application for a co-op position at your firm.<\/li>\r\n \t<li>You may be interested to know that\u00a0you can now find the updated form in the company shared drive.<\/li>\r\n \t<li>To conclude this memo, we recommend a cautious approach to using emojis when texting clients and only after they\u2019ve done so first themselves.<\/li>\r\n<\/ul>\r\n<\/div>\r\nThey're all a bit long-winded, aren't they? Can you identify the <strong>lead-ins<\/strong>?\r\n\r\nIf not, here are the same examples with the <strong>lead-ins<\/strong> highlighted.\r\n<div class=\"textbox shaded\">\r\n<ul>\r\n \t<li><span style=\"background-color: #ffff00\"><strong>I<\/strong><strong><span style=\"background-color: #ffff00\">\u2019<\/span>m Jerry Mulligan and I\u2019m writing this email to ask you to<\/strong><\/span> please consider my application for a co-op position at your firm.<\/li>\r\n \t<li>You <span style=\"background-color: #ffff00\"><strong>may be interested to know that\u00a0you<\/strong><\/span> can now find the updated form in the company shared drive.<\/li>\r\n \t<li><span style=\"background-color: #ffff00\"><strong>To conclude this memo<\/strong><strong><span style=\"text-decoration: underline\">,<\/span><\/strong><\/span>\u00a0we recommend a cautious approach to using emojis when texting clients, and only after they\u2019ve done so first themselves.<\/li>\r\n<\/ul>\r\n<\/div>\r\nThese <strong>lead-ins<\/strong> are unnecessary.\r\n\r\nIn the first example, the recipient sees the name of the sender before even opening their email. It\u2019s redundant for the sender to introduce themselves by name and say that they wrote this email. Likewise, in the third example, the reader can see that this is the conclusion if it\u2019s the last paragraph, especially if it comes below the heading \u201cConclusion.\u201d\r\n\r\nIn each case, the sentence really begins after these <strong>lead-in<\/strong> expressions and the reader misses nothing in their absence. Here's how they look with their <strong>lead-ins<\/strong> removed.\r\n<div class=\"textbox shaded\">\r\n<ul>\r\n \t<li>Please consider my application for a co-op position at your firm.<\/li>\r\n \t<li>You can now find the updated form in the company shared drive.<\/li>\r\n \t<li>We recommend a cautious approach to using emojis when texting clients, and only after they\u2019ve done so first themselves.<\/li>\r\n<\/ul>\r\n<\/div>\r\nAll three examples are improved by having their <strong>lead-in<\/strong> removed. If your writing has similar long <strong>lead-ins<\/strong>, delete them.\r\n<h2>3. Pare down unnecessarily wordy phrases<\/h2>\r\nWe habitually use long stock phrases in our writing and speech because they sound fancy. However, length does not grant respectability. These phrases look ridiculously cumbersome when seen next to their more <strong>concise<\/strong> equivalent words and phrases, as you can see in Table #1 below. Unless you have good reason to do otherwise, always replace the wordy phrases with <strong>concise<\/strong> ones in your writing.\r\n<h4 style=\"text-align: left\">Table #1: Replace unnecessarily wordy phrases with concise equivalents<\/h4>\r\n<table class=\" aligncenter\">\r\n<tbody>\r\n<tr>\r\n<th>Replace These Wordy Phrases<\/th>\r\n<th>with These Concise Equivalents<\/th>\r\n<\/tr>\r\n<tr>\r\n<td>due to the fact that\r\n\r\nnot later than July 7\r\n\r\nat this present moment in time<\/td>\r\n<td>because\r\n\r\nby July 7\r\n\r\nnow<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in any way, shape, or form<\/td>\r\n<td>in any way<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>pursuant to your request<\/td>\r\n<td>as requested<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>thanking you in advance<\/td>\r\n<td>thank you<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in addition to the above<\/td>\r\n<td>also<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in view of the fact that<\/td>\r\n<td>because<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>are of the opinion that<\/td>\r\n<td>believe<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>afford an opportunity<\/td>\r\n<td>allow<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>despite the fact that<\/td>\r\n<td>although<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>during the time that<\/td>\r\n<td>while<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>on a weekly basis<\/td>\r\n<td>weekly<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>at a later date\/time<\/td>\r\n<td>later<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>until such time as<\/td>\r\n<td>until<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in the near future<\/td>\r\n<td>soon<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>fully cognizant of<\/td>\r\n<td>aware of<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in the event that<\/td>\r\n<td>if<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>for the period of<\/td>\r\n<td>for<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>attached hereto<\/td>\r\n<td>attached<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>each and every<\/td>\r\n<td>all<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>in as much as<\/td>\r\n<td>because<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nAgain, the reader misses nothing if you use the words and phrases in the second column instead of those in the first. Also, <strong>concise<\/strong> writing is more accessible to readers who are learning English as an additional language.\r\n\r\n&nbsp;\r\n\r\n[h5p id=\"19\"]\r\n<h2>4. Delete redundant words<\/h2>\r\nOur writing and speech is also filled with redundant words in stock expressions. These prefabricated phrases aren\u2019t so bad when spoken, but are tiresome in their written form. Be on the lookout for the expressions below so that you are in command of your language.\r\n\r\nSimply delete the crossed-out words in red if they appear in combination with those in blue:\r\n<ul>\r\n \t<li><span style=\"color: #ff0000\"><del>absolutely<\/del>\u00a0<\/span><span style=\"color: #0000ff\">essential<\/span> (You can\u2019t get any more essential than essential.)<\/li>\r\n \t<li><span style=\"color: #ff0000\"><del>future<\/del>\u00a0<\/span><span style=\"color: #0000ff\">plans<\/span> (Are you going to make plans about the past? Plans are always future.)<\/li>\r\n \t<li><span style=\"color: #0000ff\">small\u00a0<\/span><span style=\"color: #ff0000\"><del>in size<\/del>\u00a0<\/span>(The context will determine that you mean small in size, quantity, or otherwise.)<\/li>\r\n \t<li><span style=\"color: #0000ff\">refer\u00a0<\/span><span style=\"color: #ff0000\"><del>back<\/del>\u00a0<\/span><span style=\"color: #0000ff\">to <\/span>(\"Back\" doesn't help the verb \"refer\" in anyway, so cut it.)<\/li>\r\n \t<li><span style=\"color: #ff0000\"><del>in order<\/del><\/span>\u00a0<span style=\"color: #0000ff\">to<\/span> (Only use \u201cin order\u201d if it helps distinguish an infinitive phrase, which begins with \u201cto,\u201d from the preposition \u201cto\u201d appearing close to it.)<\/li>\r\n \t<li><span style=\"color: #0000ff\">each<\/span><span style=\"color: #ff0000\"><span style=\"color: #0000ff\">\u00a0<\/span><del>and every<\/del><\/span>\u00a0or\u00a0<span style=\"color: #ff0000\"><del>each and<\/del><\/span>\u00a0<span style=\"color: #0000ff\">every<\/span> (Alternately, write \u201call,\u201d as we saw in the Table #1 above.)<\/li>\r\n \t<li><span style=\"color: #0000ff\">repeat\u00a0<\/span><span style=\"color: #ff0000\"><del>again<\/del><\/span> (Is this d\u00e9j\u00e0 vu?)<\/li>\r\n<\/ul>\r\n<h2>5. Delete filler expressions and words<\/h2>\r\nIf you audio-record your conversations and make a transcript of just the words themselves, you\u2019ll find an abundance of filler words and expressions that you could remove without harming the meaning of your sentences. A few common ones that appear at the beginning of sentences are \u201cThere is,\u201d \u201cThere are,\u201d and \u201cIt is,\u201d which must be followed by a [pb_glossary id=\"1907\"]clause [\/pb_glossary]starting with the pronoun \"that\" or \"who.\" Consider the following examples:\r\n<table>\r\n<tbody>\r\n<tr>\r\n<td><em>1.<\/em><del>There are<\/del>\u00a0many\u00a0<del>who<\/del>\u00a0want to take your place.<\/td>\r\n<td><strong>Many want to take your place.<\/strong><\/td>\r\n<\/tr>\r\n<tr>\r\n<td><em>2.\u00a0<\/em><del>There is<\/del>\u00a0nothing you can do about it.<\/td>\r\n<td><strong>You can do nothing about it.<\/strong><\/td>\r\n<\/tr>\r\n<tr>\r\n<td><em>3.\u00a0<\/em><del>It is<\/del>\u00a0the software\u00a0<del>that<\/del>\u00a0keeps making the error.<\/td>\r\n<td><strong>The software keeps erring.<\/strong><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nOther common filler words include the articles \"a,\" \"an,\" and \"the,\" especially in combination with the [pb_glossary id=\"231\"]preposition[\/pb_glossary]\u00a0<em>of<\/em>. You can eliminate many instances of \"<em>of the\"<\/em>\u00a0simply by deleting them and flipping the order of the nouns on either side of them.\r\n<table>\r\n<tbody>\r\n<tr>\r\n<td>technology\u00a0<del>of the<\/del>\u00a0future<\/td>\r\n<td><strong>future technology<\/strong><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nObviously, you can\u2019t do this in all cases (e.g., changing \u201cfirst of the month\u201d to \u201cmonth first\u201d makes no sense). When proofreading, however, just be on the lookout for instances where you\u00a0can.\r\n\r\nThe definite article \"the\" preceding plural nouns is also an easy target. Try deleting the article to see if the sentence still makes sense without it.\r\n<table>\r\n<tbody>\r\n<tr>\r\n<td><del>The<\/del>\u00a0shareholders unanimously supported the initiative.<\/td>\r\n<td><strong>Shareholders unanimously supported the initiative.<\/strong><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nThough the above excess words seem insignificant on their own, they bulk up the total word count unnecessarily when used in combination throughout a large document.\r\n<table>\r\n<tbody>\r\n<tr>\r\n<td><del>Basically<\/del>, you can\u2019t\u00a0<del>really<\/del>\u00a0do much to\u00a0<del>fully<\/del>\u00a0eliminate bad ideas because they\u2019re\u00a0<del>quite<\/del>\u00a0common.<\/td>\r\n<td><strong>You can\u2019t do much to eliminate bad ideas because they\u2019re so common.<\/strong><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<h2>6. Favour short, plain words and revise jargon or bureaucratic expressions<\/h2>\r\nIf you pretend that every letter in each word you write costs money from your own pocket, you would do what readers prefer: use shorter words. The beauty of [pb_glossary id=\"170\"]<strong>plain words<\/strong>[\/pb_glossary] is that they are more accessible and draw less attention to themselves than big, fancy words, while still getting the point across. This is especially true when you are writing reports, which are often filled with unnecessary [pb_glossary id=\"169\"]<strong>jargon<\/strong>[\/pb_glossary]. Choosing shorter words is easy because they are often the first that come to mind, so writing in plain language saves you time.\r\n\r\nObviously, you would use\u00a0<strong>jargon<\/strong>\u00a0for precision when appropriate for your audience\u2019s needs and your own. You would use the word \u201cphotosynthesis,\u201d for instance, if (1) you needed to refer to the process by which plants convert solar energy into sugars, and (2) you know your audience knows what the word means. In this case, using the <strong>jargon<\/strong> saves word space because it\u2019s the most precise term for a process that otherwise needs several words. Using <strong>jargon<\/strong> merely to extend the number of words, however, reduces the quality of your writing and tires your audience unnecessarily.\r\n\r\nFor business writing, simplifying language is more effective.\u00a0 Table #2 shows examples of commonly used, complicated, or bureaucratic expressions and their simpler alternative.\r\n<h4 style=\"text-align: left\">Table #2: Plain and simple language<\/h4>\r\n<table class=\" aligncenter\">\r\n<tbody>\r\n<tr>\r\n<th>Complicated or Bureaucratic Expression<\/th>\r\n<th>Simpler Alternative<\/th>\r\n<\/tr>\r\n<tr>\r\n<td>in lieu of\r\n\r\nsolicit<\/td>\r\n<td>instead of\r\n\r\nrequest<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>apparent<\/td>\r\n<td>clear<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>as per your request<\/td>\r\n<td>as requested<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>commence<\/td>\r\n<td>begin or start<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>consolidate<\/td>\r\n<td>combine<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>ascertain<\/td>\r\n<td>determine<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>disseminate<\/td>\r\n<td>distribute, send<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>endeavour<\/td>\r\n<td>try<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>erroneous<\/td>\r\n<td>wrong<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>facilitate<\/td>\r\n<td>help or assist<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>inception<\/td>\r\n<td>start or beginning<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>leverage<\/td>\r\n<td>use<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>optimize<\/td>\r\n<td>perfect<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>terminate<\/td>\r\n<td>end<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>proximity<\/td>\r\n<td>near<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>finalize<\/td>\r\n<td>complete<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>subsequent<\/td>\r\n<td>later<\/td>\r\n<\/tr>\r\n<tr>\r\n<td>utilize<\/td>\r\n<td>use<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<p style=\"text-align: center\">Source:\u00a0<a href=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\">Brockway (2015)<\/a><\/p>\r\nThe longer words in Table #2 tend to come from the Greek and Latin side of the English language, whereas the shorter words come from the Anglo-Saxon (Germanic) side. When toddlers begin speaking English, they use Anglo-Saxon-derived words because they\u2019re easier to master and, therefore, recognize them as plain, simple words throughout their adult lives.\r\n\r\n&nbsp;\r\n\r\n[h5p id=\"20\"]\r\n<h1>References<\/h1>\r\n<p class=\"hanging-indent\">Brockway,\u00a0L. (2015, November 3).\u00a0<em>24 complex words\u2014and their simpler alternatives<\/em>. PR Daily.\u00a0 <a href=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\"><span class=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\">https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/<\/span><\/a><\/p>\r\n\r\n<h1>Attributions<\/h1>\r\nThis chapter was adapted from <a href=\"https:\/\/openpress.usask.ca\/rcm200\" rel=\"cc:attributionURL\">Effective Professional Communication: A Rhetorical Approach<\/a> by Rebekah Bennetch, Corey Owen, and Zachary Keesey, which is licensed under a <a href=\"https:\/\/creativecommons.org\/licenses\/by-nc-sa\/4.0\/\" rel=\"license\">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License<\/a>, except where otherwise noted.\r\n\r\nBennetch, Owen, and Keesey adapted their chapter\u00a0from <a href=\"https:\/\/openpress.usask.ca\/fashbuscomm\/chapter\/5-1-substantial-revisions\/\">Business Communications for Fashion<\/a> (on <a href=\"https:\/\/openpress.usask.ca\/\">openpress.usask.ca<\/a>) by Anna Cappuccitti. It is licensed under a <a href=\"https:\/\/creativecommons.org\/licenses\/by-nc\/4.0\/\">Creative Commons Attribution-NonCommercial 4.0 International License<\/a>.","rendered":"<p>In many of your classes, you are probably used to trying to stretch out your writing to reach that 1,000-word goal for an essay. This is a habit you want to <em>avoid<\/em> in professional communication because professional audiences\u2014employees, clients, supervisors, and others\u2014prefer writing that is clear and, most importantly, <strong>concise<\/strong>. For our purposes, <a class=\"glossary-term\" aria-haspopup=\"dialog\" aria-describedby=\"definition\" href=\"#term_44_167\"><strong>conciseness<\/strong><\/a> means using the fewest words possible to achieve the goal of communication.<\/p>\n<p>What is the goal of communication? It is to ensure that your reader understands your intended meaning. Just ask yourself, if you were given the choice between reading a 500 word article and a 250 word article that both communicate the same meaning, which one would you prefer to read?<\/p>\n<p>To be clear, there is nothing grammatically wrong with all the examples we will cover below. However, having perfect grammar doesn&#8217;t mean a message is particularly well-written. The issue here is a matter of style\u2014and style is perhaps the most important and most difficult skill professional writers need to master. Using the techniques listed below will keep readers focused on your message and help them interpret what you are saying more easily.<\/p>\n<p>So, how do we make our writing more <strong>concise<\/strong>? Here are a few basic steps you can follow.<\/p>\n<h2>1. Mass-delete whatever doesn\u2019t belong<\/h2>\n<p>The first practical step towards trimming your document is a large-scale purge of whatever doesn\u2019t contribute to the purpose you set out to achieve. Such a purge is important because you don\u2019t want to waste time proof-editing anything that you\u2019re just going to delete anyway. However, this action is probably the most difficult one to take because it involves deleting large swaths of writing that may have taken some time and effort to compose.<\/p>\n<p>Don&#8217;t be sentimental about your own writing, especially with professional documents. If the writing is better without it, cut it.<\/p>\n<p>A good rule is that, if the content could potentially sidetrack readers, whose understanding of the topic would be unaffected (at best) or overwhelmed (at worst) by it&#8217;s inclusion, those sentences, paragraphs, and even whole sections simply must go. Highlight, delete, and\u00a0 move forward.<\/p>\n<p>(Save older versions of your work just in case you end up wanting to retrieve any of that later or use tracked changes technology to keep a record of what was deleted.)<\/p>\n<h2>2. Delete long lead-ins<\/h2>\n<p>The next way to be concise comes from deleting lead-ins.<strong> <a class=\"glossary-term\" aria-haspopup=\"dialog\" aria-describedby=\"definition\" href=\"#term_44_168\">Lead-ins<\/a> <\/strong>are the groups of words that you wrote to gear up towards your main point. In ordinary speech, we use <strong>lead-ins<\/strong> as something like throat-clearing exercises. In writing, however, these are often useless (at best) because they state the obvious. At worst, <strong>lead-ins<\/strong> immediately upset the reader by signaling that the rest of the message will contain some time-wasting text.<\/p>\n<p>Take the following the examples:<\/p>\n<div class=\"textbox shaded\">\n<ul>\n<li>I\u2019m Jerry Mulligan and I\u2019m writing this email to ask you to please consider my application for a co-op position at your firm.<\/li>\n<li>You may be interested to know that\u00a0you can now find the updated form in the company shared drive.<\/li>\n<li>To conclude this memo, we recommend a cautious approach to using emojis when texting clients and only after they\u2019ve done so first themselves.<\/li>\n<\/ul>\n<\/div>\n<p>They&#8217;re all a bit long-winded, aren&#8217;t they? Can you identify the <strong>lead-ins<\/strong>?<\/p>\n<p>If not, here are the same examples with the <strong>lead-ins<\/strong> highlighted.<\/p>\n<div class=\"textbox shaded\">\n<ul>\n<li><span style=\"background-color: #ffff00\"><strong>I<\/strong><strong><span style=\"background-color: #ffff00\">\u2019<\/span>m Jerry Mulligan and I\u2019m writing this email to ask you to<\/strong><\/span> please consider my application for a co-op position at your firm.<\/li>\n<li>You <span style=\"background-color: #ffff00\"><strong>may be interested to know that\u00a0you<\/strong><\/span> can now find the updated form in the company shared drive.<\/li>\n<li><span style=\"background-color: #ffff00\"><strong>To conclude this memo<\/strong><strong><span style=\"text-decoration: underline\">,<\/span><\/strong><\/span>\u00a0we recommend a cautious approach to using emojis when texting clients, and only after they\u2019ve done so first themselves.<\/li>\n<\/ul>\n<\/div>\n<p>These <strong>lead-ins<\/strong> are unnecessary.<\/p>\n<p>In the first example, the recipient sees the name of the sender before even opening their email. It\u2019s redundant for the sender to introduce themselves by name and say that they wrote this email. Likewise, in the third example, the reader can see that this is the conclusion if it\u2019s the last paragraph, especially if it comes below the heading \u201cConclusion.\u201d<\/p>\n<p>In each case, the sentence really begins after these <strong>lead-in<\/strong> expressions and the reader misses nothing in their absence. Here&#8217;s how they look with their <strong>lead-ins<\/strong> removed.<\/p>\n<div class=\"textbox shaded\">\n<ul>\n<li>Please consider my application for a co-op position at your firm.<\/li>\n<li>You can now find the updated form in the company shared drive.<\/li>\n<li>We recommend a cautious approach to using emojis when texting clients, and only after they\u2019ve done so first themselves.<\/li>\n<\/ul>\n<\/div>\n<p>All three examples are improved by having their <strong>lead-in<\/strong> removed. If your writing has similar long <strong>lead-ins<\/strong>, delete them.<\/p>\n<h2>3. Pare down unnecessarily wordy phrases<\/h2>\n<p>We habitually use long stock phrases in our writing and speech because they sound fancy. However, length does not grant respectability. These phrases look ridiculously cumbersome when seen next to their more <strong>concise<\/strong> equivalent words and phrases, as you can see in Table #1 below. Unless you have good reason to do otherwise, always replace the wordy phrases with <strong>concise<\/strong> ones in your writing.<\/p>\n<h4 style=\"text-align: left\">Table #1: Replace unnecessarily wordy phrases with concise equivalents<\/h4>\n<table class=\"aligncenter\">\n<tbody>\n<tr>\n<th>Replace These Wordy Phrases<\/th>\n<th>with These Concise Equivalents<\/th>\n<\/tr>\n<tr>\n<td>due to the fact that<\/p>\n<p>not later than July 7<\/p>\n<p>at this present moment in time<\/td>\n<td>because<\/p>\n<p>by July 7<\/p>\n<p>now<\/td>\n<\/tr>\n<tr>\n<td>in any way, shape, or form<\/td>\n<td>in any way<\/td>\n<\/tr>\n<tr>\n<td>pursuant to your request<\/td>\n<td>as requested<\/td>\n<\/tr>\n<tr>\n<td>thanking you in advance<\/td>\n<td>thank you<\/td>\n<\/tr>\n<tr>\n<td>in addition to the above<\/td>\n<td>also<\/td>\n<\/tr>\n<tr>\n<td>in view of the fact that<\/td>\n<td>because<\/td>\n<\/tr>\n<tr>\n<td>are of the opinion that<\/td>\n<td>believe<\/td>\n<\/tr>\n<tr>\n<td>afford an opportunity<\/td>\n<td>allow<\/td>\n<\/tr>\n<tr>\n<td>despite the fact that<\/td>\n<td>although<\/td>\n<\/tr>\n<tr>\n<td>during the time that<\/td>\n<td>while<\/td>\n<\/tr>\n<tr>\n<td>on a weekly basis<\/td>\n<td>weekly<\/td>\n<\/tr>\n<tr>\n<td>at a later date\/time<\/td>\n<td>later<\/td>\n<\/tr>\n<tr>\n<td>until such time as<\/td>\n<td>until<\/td>\n<\/tr>\n<tr>\n<td>in the near future<\/td>\n<td>soon<\/td>\n<\/tr>\n<tr>\n<td>fully cognizant of<\/td>\n<td>aware of<\/td>\n<\/tr>\n<tr>\n<td>in the event that<\/td>\n<td>if<\/td>\n<\/tr>\n<tr>\n<td>for the period of<\/td>\n<td>for<\/td>\n<\/tr>\n<tr>\n<td>attached hereto<\/td>\n<td>attached<\/td>\n<\/tr>\n<tr>\n<td>each and every<\/td>\n<td>all<\/td>\n<\/tr>\n<tr>\n<td>in as much as<\/td>\n<td>because<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Again, the reader misses nothing if you use the words and phrases in the second column instead of those in the first. Also, <strong>concise<\/strong> writing is more accessible to readers who are learning English as an additional language.<\/p>\n<p>&nbsp;<\/p>\n<div id=\"h5p-19\">\n<div class=\"h5p-iframe-wrapper\"><iframe id=\"h5p-iframe-19\" class=\"h5p-iframe\" data-content-id=\"19\" style=\"height:1px\" src=\"about:blank\" frameBorder=\"0\" scrolling=\"no\" title=\"Wordy Phrase Replacer\"><\/iframe><\/div>\n<\/div>\n<h2>4. Delete redundant words<\/h2>\n<p>Our writing and speech is also filled with redundant words in stock expressions. These prefabricated phrases aren\u2019t so bad when spoken, but are tiresome in their written form. Be on the lookout for the expressions below so that you are in command of your language.<\/p>\n<p>Simply delete the crossed-out words in red if they appear in combination with those in blue:<\/p>\n<ul>\n<li><span style=\"color: #ff0000\"><del>absolutely<\/del>\u00a0<\/span><span style=\"color: #0000ff\">essential<\/span> (You can\u2019t get any more essential than essential.)<\/li>\n<li><span style=\"color: #ff0000\"><del>future<\/del>\u00a0<\/span><span style=\"color: #0000ff\">plans<\/span> (Are you going to make plans about the past? Plans are always future.)<\/li>\n<li><span style=\"color: #0000ff\">small\u00a0<\/span><span style=\"color: #ff0000\"><del>in size<\/del>\u00a0<\/span>(The context will determine that you mean small in size, quantity, or otherwise.)<\/li>\n<li><span style=\"color: #0000ff\">refer\u00a0<\/span><span style=\"color: #ff0000\"><del>back<\/del>\u00a0<\/span><span style=\"color: #0000ff\">to <\/span>(&#8220;Back&#8221; doesn&#8217;t help the verb &#8220;refer&#8221; in anyway, so cut it.)<\/li>\n<li><span style=\"color: #ff0000\"><del>in order<\/del><\/span>\u00a0<span style=\"color: #0000ff\">to<\/span> (Only use \u201cin order\u201d if it helps distinguish an infinitive phrase, which begins with \u201cto,\u201d from the preposition \u201cto\u201d appearing close to it.)<\/li>\n<li><span style=\"color: #0000ff\">each<\/span><span style=\"color: #ff0000\"><span style=\"color: #0000ff\">\u00a0<\/span><del>and every<\/del><\/span>\u00a0or\u00a0<span style=\"color: #ff0000\"><del>each and<\/del><\/span>\u00a0<span style=\"color: #0000ff\">every<\/span> (Alternately, write \u201call,\u201d as we saw in the Table #1 above.)<\/li>\n<li><span style=\"color: #0000ff\">repeat\u00a0<\/span><span style=\"color: #ff0000\"><del>again<\/del><\/span> (Is this d\u00e9j\u00e0 vu?)<\/li>\n<\/ul>\n<h2>5. Delete filler expressions and words<\/h2>\n<p>If you audio-record your conversations and make a transcript of just the words themselves, you\u2019ll find an abundance of filler words and expressions that you could remove without harming the meaning of your sentences. A few common ones that appear at the beginning of sentences are \u201cThere is,\u201d \u201cThere are,\u201d and \u201cIt is,\u201d which must be followed by a clause starting with the pronoun &#8220;that&#8221; or &#8220;who.&#8221; Consider the following examples:<\/p>\n<table>\n<tbody>\n<tr>\n<td><em>1.<\/em><del>There are<\/del>\u00a0many\u00a0<del>who<\/del>\u00a0want to take your place.<\/td>\n<td><strong>Many want to take your place.<\/strong><\/td>\n<\/tr>\n<tr>\n<td><em>2.\u00a0<\/em><del>There is<\/del>\u00a0nothing you can do about it.<\/td>\n<td><strong>You can do nothing about it.<\/strong><\/td>\n<\/tr>\n<tr>\n<td><em>3.\u00a0<\/em><del>It is<\/del>\u00a0the software\u00a0<del>that<\/del>\u00a0keeps making the error.<\/td>\n<td><strong>The software keeps erring.<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Other common filler words include the articles &#8220;a,&#8221; &#8220;an,&#8221; and &#8220;the,&#8221; especially in combination with the <a class=\"glossary-term\" aria-haspopup=\"dialog\" aria-describedby=\"definition\" href=\"#term_44_231\">preposition<\/a>\u00a0<em>of<\/em>. You can eliminate many instances of &#8220;<em>of the&#8221;<\/em>\u00a0simply by deleting them and flipping the order of the nouns on either side of them.<\/p>\n<table>\n<tbody>\n<tr>\n<td>technology\u00a0<del>of the<\/del>\u00a0future<\/td>\n<td><strong>future technology<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Obviously, you can\u2019t do this in all cases (e.g., changing \u201cfirst of the month\u201d to \u201cmonth first\u201d makes no sense). When proofreading, however, just be on the lookout for instances where you\u00a0can.<\/p>\n<p>The definite article &#8220;the&#8221; preceding plural nouns is also an easy target. Try deleting the article to see if the sentence still makes sense without it.<\/p>\n<table>\n<tbody>\n<tr>\n<td><del>The<\/del>\u00a0shareholders unanimously supported the initiative.<\/td>\n<td><strong>Shareholders unanimously supported the initiative.<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Though the above excess words seem insignificant on their own, they bulk up the total word count unnecessarily when used in combination throughout a large document.<\/p>\n<table>\n<tbody>\n<tr>\n<td><del>Basically<\/del>, you can\u2019t\u00a0<del>really<\/del>\u00a0do much to\u00a0<del>fully<\/del>\u00a0eliminate bad ideas because they\u2019re\u00a0<del>quite<\/del>\u00a0common.<\/td>\n<td><strong>You can\u2019t do much to eliminate bad ideas because they\u2019re so common.<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>6. Favour short, plain words and revise jargon or bureaucratic expressions<\/h2>\n<p>If you pretend that every letter in each word you write costs money from your own pocket, you would do what readers prefer: use shorter words. The beauty of <a class=\"glossary-term\" aria-haspopup=\"dialog\" aria-describedby=\"definition\" href=\"#term_44_170\"><strong>plain words<\/strong><\/a> is that they are more accessible and draw less attention to themselves than big, fancy words, while still getting the point across. This is especially true when you are writing reports, which are often filled with unnecessary <a class=\"glossary-term\" aria-haspopup=\"dialog\" aria-describedby=\"definition\" href=\"#term_44_169\"><strong>jargon<\/strong><\/a>. Choosing shorter words is easy because they are often the first that come to mind, so writing in plain language saves you time.<\/p>\n<p>Obviously, you would use\u00a0<strong>jargon<\/strong>\u00a0for precision when appropriate for your audience\u2019s needs and your own. You would use the word \u201cphotosynthesis,\u201d for instance, if (1) you needed to refer to the process by which plants convert solar energy into sugars, and (2) you know your audience knows what the word means. In this case, using the <strong>jargon<\/strong> saves word space because it\u2019s the most precise term for a process that otherwise needs several words. Using <strong>jargon<\/strong> merely to extend the number of words, however, reduces the quality of your writing and tires your audience unnecessarily.<\/p>\n<p>For business writing, simplifying language is more effective.\u00a0 Table #2 shows examples of commonly used, complicated, or bureaucratic expressions and their simpler alternative.<\/p>\n<h4 style=\"text-align: left\">Table #2: Plain and simple language<\/h4>\n<table class=\"aligncenter\">\n<tbody>\n<tr>\n<th>Complicated or Bureaucratic Expression<\/th>\n<th>Simpler Alternative<\/th>\n<\/tr>\n<tr>\n<td>in lieu of<\/p>\n<p>solicit<\/td>\n<td>instead of<\/p>\n<p>request<\/td>\n<\/tr>\n<tr>\n<td>apparent<\/td>\n<td>clear<\/td>\n<\/tr>\n<tr>\n<td>as per your request<\/td>\n<td>as requested<\/td>\n<\/tr>\n<tr>\n<td>commence<\/td>\n<td>begin or start<\/td>\n<\/tr>\n<tr>\n<td>consolidate<\/td>\n<td>combine<\/td>\n<\/tr>\n<tr>\n<td>ascertain<\/td>\n<td>determine<\/td>\n<\/tr>\n<tr>\n<td>disseminate<\/td>\n<td>distribute, send<\/td>\n<\/tr>\n<tr>\n<td>endeavour<\/td>\n<td>try<\/td>\n<\/tr>\n<tr>\n<td>erroneous<\/td>\n<td>wrong<\/td>\n<\/tr>\n<tr>\n<td>facilitate<\/td>\n<td>help or assist<\/td>\n<\/tr>\n<tr>\n<td>inception<\/td>\n<td>start or beginning<\/td>\n<\/tr>\n<tr>\n<td>leverage<\/td>\n<td>use<\/td>\n<\/tr>\n<tr>\n<td>optimize<\/td>\n<td>perfect<\/td>\n<\/tr>\n<tr>\n<td>terminate<\/td>\n<td>end<\/td>\n<\/tr>\n<tr>\n<td>proximity<\/td>\n<td>near<\/td>\n<\/tr>\n<tr>\n<td>finalize<\/td>\n<td>complete<\/td>\n<\/tr>\n<tr>\n<td>subsequent<\/td>\n<td>later<\/td>\n<\/tr>\n<tr>\n<td>utilize<\/td>\n<td>use<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"text-align: center\">Source:\u00a0<a href=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\">Brockway (2015)<\/a><\/p>\n<p>The longer words in Table #2 tend to come from the Greek and Latin side of the English language, whereas the shorter words come from the Anglo-Saxon (Germanic) side. When toddlers begin speaking English, they use Anglo-Saxon-derived words because they\u2019re easier to master and, therefore, recognize them as plain, simple words throughout their adult lives.<\/p>\n<p>&nbsp;<\/p>\n<div id=\"h5p-20\">\n<div class=\"h5p-iframe-wrapper\"><iframe id=\"h5p-iframe-20\" class=\"h5p-iframe\" data-content-id=\"20\" style=\"height:1px\" src=\"about:blank\" frameBorder=\"0\" scrolling=\"no\" title=\"Wordy Phrase Flashcards\"><\/iframe><\/div>\n<\/div>\n<h1>References<\/h1>\n<p class=\"hanging-indent\">Brockway,\u00a0L. (2015, November 3).\u00a0<em>24 complex words\u2014and their simpler alternatives<\/em>. PR Daily.\u00a0 <a href=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\"><span class=\"https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/\">https:\/\/www.prdaily.com\/24-complex-words-and-their-simpler-alternatives\/<\/span><\/a><\/p>\n<h1>Attributions<\/h1>\n<p>This chapter was adapted from <a href=\"https:\/\/openpress.usask.ca\/rcm200\" rel=\"cc:attributionURL\">Effective Professional Communication: A Rhetorical Approach<\/a> by Rebekah Bennetch, Corey Owen, and Zachary Keesey, which is licensed under a <a href=\"https:\/\/creativecommons.org\/licenses\/by-nc-sa\/4.0\/\" rel=\"license\">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License<\/a>, except where otherwise noted.<\/p>\n<p>Bennetch, Owen, and Keesey adapted their chapter\u00a0from <a href=\"https:\/\/openpress.usask.ca\/fashbuscomm\/chapter\/5-1-substantial-revisions\/\">Business Communications for Fashion<\/a> (on <a href=\"https:\/\/openpress.usask.ca\/\">openpress.usask.ca<\/a>) by Anna Cappuccitti. It is licensed under a <a href=\"https:\/\/creativecommons.org\/licenses\/by-nc\/4.0\/\">Creative Commons Attribution-NonCommercial 4.0 International License<\/a>.<\/p>\n<div class=\"glossary\"><span class=\"screen-reader-text\" id=\"definition\">definition<\/span><template id=\"term_44_167\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_167\"><div tabindex=\"-1\"><p>using the fewest words possible to achieve the goal of communication<\/p>\n<\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><template id=\"term_44_168\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_168\"><div tabindex=\"-1\"><p>long strings of words that don't add much to the overall meaning of the message<\/p>\n<\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><template id=\"term_44_1907\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_1907\"><div tabindex=\"-1\"><\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><template id=\"term_44_231\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_231\"><div tabindex=\"-1\"><p>words that show relationships between other words. Some examples include <em>in<\/em>, <em>on<\/em>, <em>at<\/em>, <em>of<\/em>, and <em>under<\/em><\/p>\n<\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><template id=\"term_44_170\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_170\"><div tabindex=\"-1\"><p>words that are more common and easier for readers to understand<\/p>\n<\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><template id=\"term_44_169\"><div class=\"glossary__definition\" role=\"dialog\" data-id=\"term_44_169\"><div tabindex=\"-1\"><p>certain words that are used by a profession or group that are difficult for others to understand<\/p>\n<\/div><button><span aria-hidden=\"true\">&times;<\/span><span class=\"screen-reader-text\">Close definition<\/span><\/button><\/div><\/template><\/div>","protected":false},"author":1660,"menu_order":2,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-44","chapter","type-chapter","status-publish","hentry"],"part":377,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapters\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/wp\/v2\/users\/1660"}],"version-history":[{"count":20,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapters\/44\/revisions"}],"predecessor-version":[{"id":1166,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapters\/44\/revisions\/1166"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/parts\/377"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapters\/44\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/pressbooks\/v2\/chapter-type?post=44"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/wp\/v2\/contributor?post=44"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/communicating\/wp-json\/wp\/v2\/license?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}