{"id":4250172,"date":"2017-01-14T13:06:04","date_gmt":"2017-01-14T13:06:04","guid":{"rendered":"https:\/\/www.deptagency.com\/insight\/the-challenges-faced-by-content-editors\/"},"modified":"2017-01-14T13:06:04","modified_gmt":"2017-01-14T13:06:04","slug":"the-challenges-faced-by-content-editors","status":"publish","type":"article","link":"https:\/\/www.deptagency.com\/en-nl\/insight\/the-challenges-faced-by-content-editors\/","title":{"rendered":"The challenges faced by content editors"},"content":{"rendered":"
\n\t\n\t<\/svg>\n\t\t\t\n\t\t\tBack to all articles\t\t<\/span>\n\t\n<\/button>\n\t\tThe challenges faced by content editors\t<\/h1>\n\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t<\/picture>\n\t\n\t<\/div>
\n\t\t\t\n\t\n\t
\n\t\tKatya Tyshkul\t\t
\n\t\tLead Content Editor\n\t\t\t<\/div>\n<\/div>\n\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\tDate\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t14 January 2017\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t<\/div>\n<\/div>\n\n
\n\t
\n\t\t\n\t\t\t\t\t
\n\t\t\t\t\n\n\t\tFinding solutions to various everyday challenges can be a cause of much frustration for content editors. Of course some troubleshooting is to be expected (and the ability to handle that is a necessary skill for any editor) but many of these challenges can be minimised just by identifying them and putting in place measures to help fix them.\t<\/h2>\n\n\n\t\tThe business case for doing this is simple: by making the best use of your expert resources and ensuring the smooth running of your content teams, information can be brought to an audience faster and begin selling your products and building relationships with your customers all the more quickly.\t<\/p>\n\n\n\t\tAcknowledging and addressing these challenges will also go a long way towards keeping your editorial, sales and marketing staff happy!\t<\/p>\n\n\n\t\tBelow we have identified some of the challenges that we see regularly see faced by Content Editors. We have split them into Human and Technical issues, but this serves mainly to highlight the overlap between these two areas and how they impact on each other, as they are closely linked.\t<\/p>\n\n\n\t\tHuman\t<\/h2>\n\n\n\t\t1. Lack of good training & technical understanding\t<\/h2>\n\n\n\t\tContent editors need to be well-trained in whatever systems they are expected to use and whatever tasks they are expected to carry out. Are your content editors fully trained and confident? Ask them. You may be surprised by the conversation this opens up!\t<\/p>\n\n\n\t\tGood training means editors know how to action a particular task immediately. The more tasks that editors can action without assistance, the greater the speed and confidence with which they can work.\t<\/p>\n\n\n\t\tSome technical understanding is also important for content editors to grasp the broader picture of your digital properties. A little technical knowledge will also help editors to relate to the development team and make any updates developers are making to the site more understandable.\t<\/p>\n\n\n\t\t2. Bad requests, lack of information, incorrect content, mis-assigned issues\t<\/h2>\n\n\n\t\tThese issues can really be summed up as Poor Communication.\t<\/p>\n\n\n\t\tBad Requests are usually made by staff who aren\u2019t aware of:\t<\/p>\n\n
    \n\t
  • The limitations of the system.<\/li>
  • How long edits can be expected to take.<\/li>
  • Necessary information to make an edit possible.<\/li><\/ul><\/div><\/div>\n\n\n\t\tSuch changes can also be mis-assigned \u2013 a technical problem needing specialist coding skills given to an content editor for instance.\t<\/p>\n\n\n\t\tssues like these can lead to tension between content editors and other teams and also slow down progress while the correct information is obtained or the reasons why something can\u2019t be done are explained. However, this is easy to avoid by:\t<\/p>\n\n
      \n\t
    • Ensuring that everyone knows what can\u2019t be done.<\/li>
    • Who actions items.<\/li>
    • What content and additional information they have to provide.<\/li><\/ul><\/div><\/div>\n\n\n\t\tSome communication issues are inevitable in organisations, but problems can be heavily minimised by ensuring that staff are well-informed.\t<\/p>\n\n\n\t\t3. Request volume and prioritisation\t<\/h2>\n\n\n\t\tThe volume of updates and how to prioritise them is one of the most persistent challenges for content editors.\t<\/p>\n\n\n\t\tMany regular updates are needed, everyone wants their update or new item to be done first and editors have only limited time.\t<\/p>\n\n
        \n\t
      • Staff requesting updates need to have some awareness of the volume editors are dealing with.<\/li>
      • Ideally there should be a clear system of prioritisation.<\/li><\/ul><\/div><\/div>\n\n\n\t\tEditors must balance various updates at different stages of completion, major edits, minor edits, new blog posts and the last-minute but critical changes that sometimes arise \u2013 all the while keeping their task list moving to meet deadlines.\t<\/p>\n\n\n\t\tConsider having 1-2 hours each day earmarked for editors to deploy completed content changes to the live environment. (This keeps things moving and prevents time being eaten up by critical or time-consuming edits).\t<\/p>\n\n\n\t\tTechnical\t<\/h2>\n\n\n\t\t1.Time-intensive processes, slow systems, publishing\/cacheing issues\t<\/h2>\n\n\n\t\tThese are more problems that may seem obvious but are worth remembering because they:\t<\/p>\n\n
          \n\t
        • Turn simple tasks into long, frustrating projects.<\/li>
        • Cause editors to spend lots of time troubleshooting.<\/li>
        • Create a lack of confidence in the system.<\/li><\/ul><\/div><\/div>\n\n\n\t\tFor example, if an editor needs to replace a PDF on the website then this should be a straightforward update but these difficulties can turn it into a long and pernicious process. Your systems should be configured to allow as few opportunities for mistakes as possible.\t<\/p>\n\n\n\t\tWherever you can, streamline processes and ensure that systems have the support of appropriate technical equipment and staff. This will help to:\t<\/p>\n\n
            \n\t
          • Make edits faster and smoother.<\/li>
          • Keep editors happy.<\/li>
          • Avoid the confusion poorly organised content creates.<\/li><\/ul><\/div><\/div>\n\n\n\t\t2. Complex user interface, complex\/awkward implementations\t<\/h2>\n\n\n\t\tIf your CMS has a complicated interface or is implemented in an awkward way then this will mean:\t<\/p>\n\n
              \n\t
            • Slowing content editors and the flow of content down and have a negative impact on quality.<\/li>
            • Editors will need more training and more technical knowledge.<\/li><\/ul><\/div><\/div>\n\n\n\t\tAll systems have some quirks or difficulties but the more these can be minimised the more editors\u2019 frustrations can be minimised and the better and more efficient their work will be.\t<\/p>\n\n\n\t\tAll systems have some quirks or difficulties but the more these can be minimised the more editors\u2019 frustrations can be minimised and the better and more efficient their work will be.\t<\/p>\n\n\n\t\tOf course, any CMS also needs to be powerful enough to meet your needs and a balance may well have to be struck between complexity and ease-of-use. Thus regular housekeeping and diligence are needed in any CMS to ensure that things are kept well organised.\t<\/p>\n\n\n\t\tConclusion\t<\/h2>\n\n\n\t\tThe above is not exhaustive and there are many other challenges that content editors have to manage. However, in this brief assessment we have sought to highlight those problems that make simple tasks unnecessarily complicated and which actively promote tensions between editors and other staff.\t<\/p>\n\n\n\t\tLuckily the majority of these challenges can be easily dealt with if you are willing to be proactive. If there are concerns about budget and time-frames then think about the potential value of better organised and higher quality content in the long-term and consider this alongside the probable costs of:\t<\/p>\n\n
                \n\t
              • Better training and guidelines.<\/li>
              • Bringing in expertise.<\/li>
              • A CMS switch or redesign.<\/li><\/ul><\/div><\/div>\n\n\n\t\tAsk questions of your editors on a regular basis, especially questions about what could be done to make content and the editing process better. Editors need to be proactive too and should not be afraid to bring any difficulties they are having up for discussion. Try to create opportunities for content editors, technical and marketing staff to swap ideas and concerns.\t<\/p>\n\n\n\t\tAsk questions of your editors on a regular basis, especially questions about what could be done to make content and the editing process better. Editors need to be proactive too and should not be afraid to bring any difficulties they are having up for discussion. Try to create opportunities for content editors, technical and marketing staff to swap ideas and concerns.\t<\/p>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\n\t\n\t