<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='/Content/StratML.xslt'?>
<PerformancePlanOrReport>
  <Name>Best Practices for Business-Quality Communications:  Moving to a Higher Level of Maturity than E-mail</Name>
  <Description>The Capability Maturity Model (CMM) is a widely recognized framework for evaluating the formality and optimization of processes.E-mail is a highly immature (CMM Level 1, Chaotic) means of creating, sharing, and managing business records.  A more mature process for meeting the underlying requirements would achive the following goals.</Description>
  <OtherInformation>
  </OtherInformation>
  <!--Strategic Plan Core-->
  <StrategicPlanCore>
    <Vision>
      <Description>
      </Description>
      <Identifier>Vision_676bac22-3425-482e-8d44-c8a4c03b54a8</Identifier>
    </Vision>
    <Mission>
      <Description>
      </Description>
      <Identifier>Mission_676bac22-3425-482e-8d44-c8a4c03b54a8</Identifier>
    </Mission>
    <Goal>
      <Name>Strategic Alignment</Name>
      <Description>Enable users to retrieve information that is directly and explicitly related to their own objectives.</Description>
      <Identifier>Goal_fbb240e2-2734-42bd-8612-8170af14c5b0</Identifier>
      <SequenceIndicator>1</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>Importance &amp; Relevance</Name>
      <Description>Enable users to automatically prioritise communications according to relevance to tasks which are aligned with their strategic objectives.</Description>
      <Identifier>Goal_921342fc-ea9b-401d-810c-f1abebcc00aa</Identifier>
      <SequenceIndicator>2</SequenceIndicator>
      <OtherInformation>Enable users to automatically prioritise communications according to relevance to tasks which are aligned with their strategic objectives.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Retrieval</Name>
      <Description>Enable users to retrieve information exactly when and where they choose.</Description>
      <Identifier>Goal_9a48c03f-80ae-4e35-b3b7-247b1e9aa974</Identifier>
      <SequenceIndicator>3</SequenceIndicator>
      <OtherInformation>Enable users to retrieve information exactly when and where they choose.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Narrow Casting</Name>
      <Description>Enable users to receive information that is discretely targeted to them based upon their personal attributes, interests, and particularly their intentions (longer-term goals and near-term objectives).</Description>
      <Identifier>Goal_905ab8bf-0e8d-4ad1-827a-490904c61e1d</Identifier>
      <SequenceIndicator>4</SequenceIndicator>
      <OtherInformation>Enable users to receive information that is discretely targeted to them based upon their personal attributes, interests, and particularly their intentions (longer-term goals and near-term objectives).</OtherInformation>
    </Goal>
    <Goal>
      <Name>Attachments</Name>
      <Description>Prohibit the transmittal of attachments</Description>
      <Identifier>Goal_278e50aa-4086-4189-8797-59dbb9bec721</Identifier>
      <SequenceIndicator>5</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>Requirements</Name>
      <Description>Enable usage of the applications, tools, and services that are well suited to the underlying requirements.</Description>
      <Identifier>Goal_9ec179b0-d00a-4bf2-b8fc-ada328dd610d</Identifier>
      <SequenceIndicator>6</SequenceIndicator>
      <OtherInformation>Enable usage of the applications, tools, and services that are well suited to the underlying requirements.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Trusted Networks</Name>
      <Description>Establish White List trusted networks based upon an open standard(s).</Description>
      <Identifier>Goal_bf6c00b6-701a-4d5a-88d5-6122542584de</Identifier>
      <SequenceIndicator>7</SequenceIndicator>
      <OtherInformation>Establish White List trusted networks based upon an open standard(s).</OtherInformation>
    </Goal>
    <Goal>
      <Name>De-Duplication</Name>
      <Description>Disallow the needless duplication of information.</Description>
      <Identifier>Goal_b56e4a98-4349-4483-8846-b7c6c90861ca</Identifier>
      <SequenceIndicator>8</SequenceIndicator>
      <OtherInformation>Disallow the needless duplication of information.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Context</Name>
      <Description>Ensure that business records contain sufficient context.</Description>
      <Identifier>Goal_7a06c829-785a-4fe0-a519-99c030f97f0b</Identifier>
      <SequenceIndicator>9</SequenceIndicator>
      <OtherInformation>Each business record should contain sufficient context to meet the requirements for the purpose for which it was created. Additionally, sufficient metadata should be associated with each record to facilitate its management and discovery.</OtherInformation>
    </Goal>
    <Goal>
      <Name>E-Discovery</Name>
      <Description>Reduce the cost and increase the precision of discovery.</Description>
      <Identifier>Goal_5e5d08c1-8f08-4880-bf8f-c6bd91ec3516</Identifier>
      <SequenceIndicator>10</SequenceIndicator>
      <OtherInformation>Apply the best practices outlined in this plan in order to reduce the cost and increase the precision of discovery not only in litigation but also in support of routine business processes as well as queries by interested stakeholders.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Spoliation</Name>
      <Description>Ensure that records cannot be destroyed except in accordance with an approved disposition schedule.</Description>
      <Identifier>Goal_3adbb6ab-b38b-4541-96a1-d49e78356cf4</Identifier>
      <SequenceIndicator>11</SequenceIndicator>
      <OtherInformation>Ensure that records may not be destroyed or made inaccessible if they may exist anywhere else.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Vampire Effect</Name>
      <Description>Avoid using systems that enable the distribution of records in way that are unmanageable.</Description>
      <Identifier>Goal_c802d785-b13a-4758-9b31-7e6b8c69fd08</Identifier>
      <SequenceIndicator>12</SequenceIndicator>
      <OtherInformation>Avoid using systems that enable the distribution of records in ways that are unmanageable.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Collaboration</Name>
      <Description>Use tools, applications, and services that meet the underlying requirements for efficient and effective collaboration</Description>
      <Identifier>Goal_dbf3b38a-40ec-433e-9c21-f957b7ae4354</Identifier>
      <SequenceIndicator>13</SequenceIndicator>
      <OtherInformation>
      </OtherInformation>
    </Goal>
    <Goal>
      <Name>Linkages</Name>
      <Description>Linkages</Description>
      <Identifier>Goal_90343cdd-eee2-4b43-b480-a7e4584f8e09</Identifier>
      <SequenceIndicator>14</SequenceIndicator>
      <OtherInformation>Allow links to be created between any different pieces of information whilst retaining the context of both the source and the destination.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Security</Name>
      <Description>Security</Description>
      <Identifier>Goal_b08854b9-a115-42d5-8690-1653bef5f41c</Identifier>
      <SequenceIndicator>15</SequenceIndicator>
      <OtherInformation>Communications should be secured against unauthorised access.

Security is required both for information during transmission, and when it is in storage.</OtherInformation>
    </Goal>
    <Goal>
      <Name>Identity</Name>
      <Description>Each party to a communication should be verifiably identified</Description>
      <Identifier>Goal_ed58f9a0-dc2b-4288-bd9c-d4c6e31a8311</Identifier>
      <SequenceIndicator>16</SequenceIndicator>
      <OtherInformation>Identity confers context and credibility, and helps to prevent fraud. It is a requirement for contractual arrangements, KYC-type regulations, and in the event of communications subject to non-disclosure agreements.</OtherInformation>
    </Goal>
    <Framework>
      <SWOT>
        <Strength>
          <Name>Email is often the only way to collaborate through corporate firewalls</Name>
          <Description>When corporates do implement collaboration tools, they frequently contain access to them within their firewalls. As business becomes more flexible, making greater use of third party collaboration, email is often one of the few ways of sharing written communications and documents between organisations. To succeed, collaboration tools, and they way they are implemented, will need to overcome this limitation.</Description>
        </Strength>
        <Strength>
          <Name>Email is near universal</Name>
          <Description>One of emails biggest strengths is its near universality. Almost everyone has an eamil address (if not more than one), and almost anyone with with an email address can communication with almost anyone else with an email address. In that sense it is like the telephone or postal mail.

I believe that this occured since the introduction of the POP3 and SMTP standards. A post-email environment will need standards which are a simple and widely adopted.

Currently the world appears to be moving in the opposite direction. Consider the widespread adoption of various social media platforms, each of which is more or less proprietary, without so much as the adoption of RSS/Atom as a base standard.</Description>
        </Strength>
        <Weakness>
          <Name>Spam</Name>
          <Description>According to security company Symantec in its monthly intelligence report.
- For the first time in twelve years, less than half of emails are spam - real emails are outnumbering junk for the first time since 2003.
- Spam still makes up 49.7 per cent of emails.
- This is the first time the percentage of spam dips below 50 per cent, but spam levels have been dropping for years, partly because of legal action being taken, and partly because better and more aggressive filters are keeping it out of our inboxes and so making it less profitable.
- It would also appear that spam’s disappearing quickly, as it’s gone down by 2.4 percentage points in just two months.

Although the report only measures Symantec’s clients, which stand at roughly two per cent of the market, it’s enough to give a good snapshot.</Description>
        </Weakness>
        <Weakness>
          <Name>Email is not good at managing context</Name>
          <Description>Email typically manages context by simply repeating previous emails in a thread in an ever-increasing trail at the bottom of each message.

Communications become bloated with repetiton and where thread branch and merge over time the context can quickly become confused.

 The more recent introduction of threads at the interface level partially solves the problem from the user perspective, and text deduplication algorithms can alleviate some, but ot all of the sorage and transmission overhead. HOwever, these are workarounds, rather than fundamental improvements.</Description>
        </Weakness>
        <Weakness>
          <Name>Email has increased the volume of written communications, but reduced its quality</Name>
          <Description>From: A modest proposal: eliminate email, HBR, 18 February 2016

"Accompanying the rise of this technology was a new, unstructured workflow in which all tasks — be it a small request from HR or collaboration on a key strategy — are now handled in the same manner: you dive in and start sending quick messages which arrive in a single undifferentiated inbox at their recipients. These tasks unfold in an ad hoc manner with informal messages sent back and forth on demand as needed to push things forward.

This unstructured workflow arose from the core properties of email technology — namely, the standard practice of associating addresses with individuals (and not, say, teams, or request type, or project), and the low marginal cost of sending a message. It spread for the simple reason that it’s easier in the moment. It takes significantly less effort to shoot off quick messages, for example, than it is to more carefully plan your work day, figuring out in advance what you need, from whom, and by when."</Description>
        </Weakness>
        <Weakness>
          <Name>Email fragments attention</Name>
          <Description>From: A modest proposal: eliminate email, HBR, 18 February 2016:

"... this incessant communication fragments attention, leaving only small stretches left in which to attempt to think deeply, apply your skills at a high level, or otherwise perform well the core activity of knowledge work: extracting value from information. To make matters worse, cognitive performance during these stretches is further reduced by the “attention residue” left from the frequent context switching required to “just check” if something important arrived.

...As more knowledge workers now acknowledge, the inbox-bound lifestyle created by an unstructured workflow is exhausting and anxiety-provoking. Humans are not wired to exist in a constant state of divided attention, and we need the ability to gain distance from work to reflect and recharge. Put simply, this workflow, which can transform even the highest skilled knowledge workers into message-passing automatons, is making an entire sector of our economy miserable."

This has a substantial impact on productivity and job satisfaction, as outlined in books such as Deep Work, andFlow: The Psychology of Happiness: The Classic Work on How to Achieve Happiness.</Description>
        </Weakness>
        <Weakness>
          <Name>Email is asynchronous</Name>
          <Description>From: A modest proposal: eliminate email, HBR, 18 February 2016

"Synchronous conversation is efficient and nuanced: not only does it allow you to handle in three minutes decisions that might have otherwise taken three days of attention-snagging messages, but it tends to also produce more thoughtful conclusions. Imagine, for example, that Alice and Bob need to work together to write a report. If they use email, the process would likely unfold in an inefficient manner, as both Alice and Bob, under the Sisyphean pressure of an ever-filling inbox, keep dashing off quick responses to each other so as to temporarily clear the issue out of their psychic space. In the office-hours scenario, however, Alice and Bob would be forced to talk in real time about the report project. This interaction, though taking more time than sending a quick message at first, is more likely to lead to a complete and coherent plan for how the work should best unfold in the days that follow."

Notwithstanding the above, I think there is a lot to be said for asynchronous communications. The answer should combine both seamlessly.</Description>
        </Weakness>
        <Weakness>
          <Name>Email is not secure</Name>
          <Description>According to a call to arms for e-mail security:

"More than 80 percent of IT security managers agree that email is a major attack channel today. But, nearly just as many aren’t confident in their current email security and don’t think they could stand up to a future attack."</Description>
        </Weakness>
        <Opportunity>
          <Name>Apache Wave</Name>
          <Description>Appache Wave (originally Google Wave) is the most interesting attempt that I have seen to find an alternative to email. Unfortunately, Email is too entrenched, and Wave was too ambitious and poorly understood. Google eventually stopped developing wave, and handed it over to the Apache Software Foundation, who continue to develop it into a usable protocol with easy to implement servers.</Description>
        </Opportunity>
        <Opportunity>
          <Name>Dealing with email is a significant activity</Name>
          <Description>According to research reported in City A.M. on 14 April 2015:
- You spend, on average, 36 days a year writing emails.
- You send, on average, just over 4,000 emails a year.
- You receive, on average, just over 6,000 emails a year.

According to The Talent Imperative in Digital Business:
- German chemical company BASF found that project groups increased their efficiency by 25% by switching to a social media tool for collaboration, rather than email.</Description>
        </Opportunity>
        <Opportunity>
          <Name>There is a lot of investment in trying to solve the email problem</Name>
          <Description>The shift away from reliance on email is being made possible by funding. Sensing a great opportunity, investors are throwing money into companies creating systems that will draw people out of their daily email routine.
- Sparrow, Mailbox, Boxer, Triage and Handle are just some of the firms that have caught the attention of venture capitalists recently. 
- Task managers like Basecamp and Asana benefit meetings, reporting and browsing through a list of complete/incomplete tasks, but the tools don’t completely solve the problem. 
- Content management apps like Evernote, Box, Dropbox and Google Drive also help, but they aren’t communication-oriented.
- Workplace chat rooms like Slack are driving huge interest – the company drew 8,000 access requests in one day even before it was launched, and is now valued at $2.8bn (£1.8bn). But to really turn email on its head, an enterprise will require more than just a basic chat room.
- New innovations are beginning to appear, like Quip, which allows you to create a collaborative document from an email thread.</Description>
        </Opportunity>
        <Opportunity>
          <Name>Align with the Certified Information Professional Certification objective on legacy communications</Name>
          <Description>Objective 1.r: Legacy Collaboration of the Certified Information Professional Certification is to Identify issues associated with legacy collaboration approaches, e.g. email
- What do they think these issues are?
- Is there objective merely to educate on, or to do something about these issues?
- Who are the consumers of this education, and what might they be doing about these issues (other than just being educated)?</Description>
        </Opportunity>
        <Opportunity>
          <Name>Some companies are starting to ban internal emails</Name>
          <Description>For example, Thomas Knoll 'banned' email for all but a few specific tasks at his company, Prime Loop. he explains what and why at https://medium.com/life-at-primeloop/putting-email-in-its-place-27757946d9fe#.7bs3gogmx </Description>
        </Opportunity>
        <Threat>
          <Name>There is a lack of engagement in suitable alternatives to email</Name>
          <Description>Whilst there is plenty of engagement with social media as an alternative to email, these platforms are not considered suitable for business records management [probably requires some elaboration as to why not...].</Description>
        </Threat>
        <Threat>
          <Name>The internet is fragmenting from open standards into proprietary tools</Name>
          <Description>We need to continue to invest in open standards (like StratML, but also others) in order to combat this.</Description>
        </Threat>
        <Threat>
          <Name>Communications are fragmenting</Name>
          <Description>I used to have to watch emails.

Now I have to watch emails, Whatsapp, Linkedin, Slack, Teams, Texts/SMS, Facebook, Facebook Messenger, Telegram, etc., etc, etc.

Maybe the virtue is that most of those will remind me by... email... if I miss them!</Description>
        </Threat>
      </SWOT>
    </Framework>
  </StrategicPlanCore>
  <!--Administrative Information-->
  <AdministrativeInformation>
    <Identifier>StrategyPlan_676bac22-3425-482e-8d44-c8a4c03b54a8</Identifier>
    <StartDate>
    </StartDate>
    <EndDate>
    </EndDate>
    <PublicationDate>2025-09-04</PublicationDate>
    <Source>https://www.stratnavapp.com/StratML/Part3/676bac22-3425-482e-8d44-c8a4c03b54a8/Styled</Source>
    <Submitter>
      <Identifier>Submitter_676bac22-3425-482e-8d44-c8a4c03b54a8</Identifier>
      <GivenName>
      </GivenName>
      <Surname>
      </Surname>
      <PhoneNumber>
      </PhoneNumber>
      <EmailAddress>
      </EmailAddress>
    </Submitter>
  </AdministrativeInformation>
</PerformancePlanOrReport>