Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sites/cherryleaf.com/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/sites/cherryleaf.com/public_html/wp-includes/functions.php:6114) in /home/sites/cherryleaf.com/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":16932,"date":"2023-09-11T07:34:31","date_gmt":"2023-09-11T07:34:31","guid":{"rendered":"https:\/\/www.cherryleaf.com\/?p=16932"},"modified":"2023-09-04T07:45:36","modified_gmt":"2023-09-04T07:45:36","slug":"podcast-139-techsmiths-daniel-foster-on-the-contentious-relationship-between-technical-writers-and-video-content","status":"publish","type":"post","link":"https:\/\/www.cherryleaf.com\/2023\/09\/podcast-139-techsmiths-daniel-foster-on-the-contentious-relationship-between-technical-writers-and-video-content\/","title":{"rendered":"Podcast 139: Techsmith\u2019s Daniel Foster on the contentious relationship between technical writers and video content"},"content":{"rendered":"

In this podcast episode, we talk to Daniel Foster, Director of Strategy at TechSmith, about the contentious relationship between technical writers and video content.<\/p>\n

A growing trend among technical writers is the integration of video content alongside traditional documentation and visuals, offering a dynamic and immersive medium to enhance user understanding and engagement. However, writers generally prefer words because they\u2019re easier to reuse and scale, as well as being more efficient for their overall business. This leads to a rather contentious relationship with video elements…especially with clients specifically requesting more of them.<\/p>\n

Daniel regularly works with technical writers on how to bridge this gap and effectively leverage video content to complement their writing.<\/p>\n

We discuss how technical writers can effectively manage this contentious relationship.<\/p>\n

 <\/p>\n