Category Archives: Video
As video usage and video views continue to grow, so does the importance of making video a key part of digital design. A Forbes headline from June reads “Video Marketing in 2018 Continues to Explode.” Consider this statistic from the article: more than 500 million hours of videos are watched daily on YouTube. In a 2018 survey that Hubspot conducted, 81% of businesses reported using video as a marketing tool, which is up 18% from last year’s survey.
Video Placement Guidelines
Despite the increased profile of videos, many people still place them at the bottom of emails, hide them in links, or forget about them altogether. A 2015 article by Stjepan Alaupovic for OnlineVideo.net has some practical guidelines for the placement of video on websites:
- Use a simple video player that viewers are used to seeing such as YouTube or Vimeo with a video play button to provide a visual cue to users.
- Place videos above the fold (in the top part of the screen) and in a prominent spot so that viewers see them easily.
- Enhance search engine optimization (SEO) with good metadata including a description that includes the word video and a verbatim transcription.
Recently, my own firm was redesigning our website. When the plan for the site was presented at a meeting, video was not part of it. Not only is video a product of most agencies today, it is essential for capturing an audience’s attention and presenting information in today’s digital environment.
Video Gallery or Library
In Chapter 4 of Digital Literacy for Technical Communication on information design, Michael J. Salvo and Paula Rosinski discuss the need for technical communicators to consider “findability” of documents and information. Today, users want to be able to find information in many formats including video. Websites should have a video gallery or library that is linked in a tab, card, or area of the homepage that is easy to see. Videos should be organized by category and playlists. Descriptive thumbnail images are useful, too.
Many organizations spend time, effort, and money producing videos, but they fail to consider where the video will be placed online, how it will be seen, and why users will view it. I recommend starting any video project by completing a video creative brief that lists a series of questions that should be considered. One of the most important questions to answer is “where will this video live online?” Below, you’ll find an example of a video creative brief.
Hart-Davidson hits the nail on the head, Content Management Systems (CMS) “do not do that work by themselves” (p. 14). A CMS can give a company what they are willing to put into it. They are not a solution, they are a tool. They are exactly what we make of it. Hart-Davidson states that “technical communicators typically come to play many different roles and deploy diverse sets of skills over the course of a career” when using CMS (p. 134). The roles mentioned must be assumed, but to successfully integrate the CMS into the company, the company must also integrate one or more company processes into the system to really benefit from it.
Training or some kind of education on how the company uses a CMS is a key to success. I’ve used quite a few systems and have seen excellent and poor uses of them in companies. When companies don’t have any rules around how a CMS is used, it becomes a free-for-all of good and bad information. It’s confusing. There is a plethora of online content available online for learning how to use and manage CMS systems online. However, even if you know how to use the system, this may not be how the company uses it. The video below only touches on some common mistakes in administrating SharePoint itself and it’s over an hour long.
Michael J. Salvo and Paula Rosinski both discuss “mapping” and “signposting” in information design (pp. 112-114). These concepts are a big part of UX and extremely important to ensure users can become literate in a system. I’ve found these levels of user interface designs are not well applied to most CMS. At one of the companies I worked for I had to redesign the front-end of a SharePoint site to make it more accessible and simplified for others in the company. This tells me that we have a long way to go in our design of CMS from a design perspective. Confusion in using the interface itself will almost surely create inconsistent data, especially when most people will have access to the system.
Process in how you use a CMS is key to making the system useful. Yes, it can allow versioning of documents, but when people are not required to update or sign off on documentation, it can create data that looks trustworthy but is not. Most systems have workflows integrated into them, but unless going through that workflow is a part of a sign off process for the deployment of a product, then why would people go through the hassle?
To make sure our documentation is trustworthy, my team and I will link our documents to specific releases of software. This way it will be clearer in what context you can assume a document may be relevant for. In terms of metadata we make sure that everything is under our team’s section in the system. We also have the option to tag certain customers if the document is specifically relevant to that context. The process we employ around this ensures that we do not have to continually maintain every document, but instead deploy documentation at our own pace and as needed.
I don’t think I could live without a CMS at a company these days, because the alternatives are much worse. But literacy in these systems remains a problem. This is probably due to the fact that the users are not the same as the customer. Additionally, I see many systems treated as a golden solution instead of a platform. It will be interesting to see how these systems and their usages evolve over time.