{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Not-Boring Tech Writer","title":"Advocating for docs and choosing tools with Kelton Noyes","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/cfc7e21a\"></iframe>","width":"100%","height":180,"duration":4640,"description":"In this episode, I talk with Kelton Noyes, a senior technical communicator who started his career in tech support and gradually built his way into documentation. We discuss how to choose documentation tools, practical strategies for making the business case for investing in documentation, and how Kelton successfully advocated for technical writing as a valuable full-time discipline within his organization.—Kelton and I discuss his journey from tech support to technical writing, which began with his frustration at answering the same questions repeatedly. He started creating documentation between support calls to fill gaps he noticed, sharing these resources with coworkers who found them valuable. His managers appreciated the work, but nobody initially recognized documentation as a full-time role. We explore how he eventually made the transition by demonstrating concrete value through metrics like reduced support volume and faster training ramp-up times and shifting the conversation from advocating for the importance of documentation to advocating for himself as the person to do that documentation.We dive deep into Kelton's approach to choosing documentation tools, including how to develop a hierarchy of needs based on customer feedback, organizational requirements, and author workflow. He shares the importance of taking advantage of demos and free trials to explore features hands-on, explaining how requirements often evolve during this exploration process as you discover capabilities you didn't know you needed.We also explore red flags that indicate it's time to reevaluate your tooling, the challenge of finding tools that serve multiple departments, and how to navigate the collaborative aspects of getting organizational buy-in for documentation initiatives.About Kelton Noyes:Kelton Noyes is an English major with a love of technology who spent years trying to find a way to blend the two. He started his career working technical support jobs across a variety of...","thumbnail_url":"https://img.transistorcdn.com/JlP4_zZATprOmI0COWYcSJZswo0AzjaOmxyE_M5gX6M/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kNTdh/ZjBlMjA5ZmEwZDhh/NTNjZWFiOWM2NWY1/ZDAzNS5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}