Discover
The Not-Boring Tech Writer
The Not-Boring Tech Writer
Author: Kate Mueller
Subscribed: 52Played: 640Subscribe
Share
© 2016-2026 KnowledgeOwl
Description
Some people hear the phrase "technical writing" and think it must be boring. We're here to show the full complexity and awesomeness of being a tech writer.
This podcast is for anyone who writes technical documentation of any kind, including those who may not feel comfortable calling themselves tech writers. Whether you create product documentation, support documentation, READMEs, or any other technical content—and whether you deal with imposter syndrome, lack formal training, or find yourself somewhere in the gray area between technical communications and general writing—there's a place for you here.
Each month, we publish two episodes: an interview with an amazing guest focusing on useful skills or tools that can help you improve your tech writing skills, and a behind-the-scenes solo episode with host Kate Mueller about what she’s working on, struggling with, or thinking about in her daily tech writing life.
The Not-Boring Tech Writer is generously sponsored by KnowledgeOwl, knowledge base software built for people who care, by people who care.
This podcast is for anyone who writes technical documentation of any kind, including those who may not feel comfortable calling themselves tech writers. Whether you create product documentation, support documentation, READMEs, or any other technical content—and whether you deal with imposter syndrome, lack formal training, or find yourself somewhere in the gray area between technical communications and general writing—there's a place for you here.
Each month, we publish two episodes: an interview with an amazing guest focusing on useful skills or tools that can help you improve your tech writing skills, and a behind-the-scenes solo episode with host Kate Mueller about what she’s working on, struggling with, or thinking about in her daily tech writing life.
The Not-Boring Tech Writer is generously sponsored by KnowledgeOwl, knowledge base software built for people who care, by people who care.
91 Episodes
Reverse
In this solo episode, I share my latest progress on content updates and reflect on my takeaways from Sharon Burton’s interview (S3:E48). I share some thoughts on the importance of curiosity in our industry and the ways that AI usage can feel like managing others (and why I’m bad at that).—This month I got another dozen or so article editor pages updated. My article editor punchdown list is now somewhere between 50-60 articles remaining. More importantly, I finally finished the Microsoft Teams app docs and the App Store submission for that app, including recording a short explainer video. The Wisdom Wednesday sessions I’ve been leading have prompted a lot of docs work, too. My session on optimizing search had me digging deep into the ways that our search combines keyword and semantic search, which our current documentation didn’t at all address. I did a first pass at updating those docs based on my research, but they likely still need more work. I’m also making updates to our documentation on different login and authentication options as I prep for that session.I also reflect on my interview with Sharon Burton and the book she edited, Women in Technical Communication. I need to learn more about our own history, as my technical writing knowledge is very heavily skewed toward the last decade. Sharon’s passion for capturing and sharing women’s stories in our field is palpable, and she’s really embracing that role. I especially appreciated her focus on how curiosity isn’t teachable but is so essential to being successful as a tech writer. While I may have uncertainty about my own place in the field, I have no uncertainty about my own curiosity.In the episode, Sharon and I spent quite some time discussing the ways she used AI to vibe code some automation scripts in Google Drive to make managing contributions from over 60 writers more manageable, and how this helped her manage some very tedious, unenjoyable tasks so she could focus on the pieces she enjoyed more. This mirrors my own preference for using AI in my work: automating things I don’t like or that are tedious. But a lot of the folks I know using it heavily are basically turning into AI managers, and I spend some time musing on that and the fact that I hate being a manager. Perhaps this explains much of my resistance to using AI; who knows?In this episode:[00:00:58]: My progress update on article editor docs and Microsoft Teams app docs[00:04:42]: Reflecting on Sharon’s episode: I need to read more of the writers she shared[00:05:32]: Reflecting on Sharon’s episode: Her passion and belief in capturing and sharing these stories[00:06:32]: Reflecting on Sharon’s experience and perspective on curiosity[00:08:28]: My reflections on using AI as a form of managing others and my own preference for doing work myself[00:11:36]: Why I don’t want to be a manager, of people or of AI[00:15:07]: Sharon’s perspective on how much our field changes, and why the basics won’t[00:16:55]: This month’s goal: feeding webinar work back into the docsResources discussed in this episode:KnowledgeOwl Support Teams notification feature overview documentation“Women in Technical Communication” edited by Sharon BurtonRelated TNBTW episode: S3:E48: Telling the stories of women in technical communication with Sharon BurtonJoin the discussion by replying on Bluesky
—Contact The Not-Boring Tech Writer team:We love hearing your ideas for episode topics, guests, or general feedback:Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyGuest suggestions formContact Kate Mueller:knowledgewithsass.comLinkedInBlueskyContact KnowledgeOwl:knowledgeowl.comLinkedIn
In this episode, I talk with Sharon Burton, a technical content strategist who has taught technical communication to engineering students at the University of California, Riverside, for 22 years and edited the book Women in Technical Communication. We talk about how a $10-an-hour job writing computer manuals took her from cultural anthropology into a field that gave her permission to be curious, how a scam anthology and a friend’s terminal cancer diagnosis led to the book, why the people who did the work should tell the history of technology themselves, and how she used AI to write the Google Drive scripts that kept dozens of contributors’ stories organized.—Sharon and I start with how she fell into tech writing in the early 1990s as a single mom and cultural anthropology graduate student, when someone she knew in the computer science department mentioned a company that needed computer manuals written for $10 an hour. We talk about why she can teach writing but not curiosity, why breaking a product on purpose is part of documenting it, and how saying yes to things she didn’t know how to do led to 22 years of teaching at UC Riverside.The heart of our conversation is Women in Technical Communication, the book Sharon edited. The idea came from a scam anthology that asked contributors to pay $500 and give up their copyright, and her friend Char James-Tanny’s terminal cancer diagnosis made her start it right away. Sharon makes the case that the people who did the work need to tell the history of technology themselves, and that these stories show a field that has always been about change, which makes AI just the latest one.We spend the second half on how Sharon managed the project. She vibe coded Google Drive scripts with AI to create a private folder and Google Doc for each writer, copied in their submissions, and tracked word counts to show who had made edits. She sent the writers weekly status emails and edited lightly so each woman’s voice stayed her own. Sharon recommends books by Karen Schriver, Susan Weinschenk, and Ginny Redish, and closes with advice someone once gave her, act as if you belong, and the hardest lesson in following it: it’s okay to ask for help.About Sharon Burton:Sharon Burton is a technical content strategist, educator, author, and editor based in Riverside, California. She has taught technical communication to engineering students at the University of California, Riverside, for 22 years, and she edited “Women in Technical Communication: From Typewriters to Touchscreens: A History by the Women Who Did the Work” (XML Press). She came to tech writing in the early 1990s from graduate studies in cultural anthropology.In this episode:[00:01:44]: Sharon’s origin story: from cultural anthropology graduate student to writing computer manuals[00:05:55]: Why Sharon can teach writing but can’t teach curiosity[00:08:04]: Breaking things on purpose, and customers who use products in ways nobody designed[00:13:36]: Writing her own career story, and appointing herself “general manager of the universe”[00:15:05]: Falling into 22 years of teaching tech comm to engineers at UC Riverside[00:17:37]: Saying yes to things you don’t know how to do yet[00:18:28]: How a scam anthology sparked “Women in Technical Communication”[00:24:01]: Char James-Tanny’s diagnosis, and why the book couldn’t wait[00:30:48]: Writing her own story last, and realizing she’d made a difference[00:32:09]: Teaching “clear writing” and plain language to thousands of people[00:33:02]: A field that’s always changing, and why AI is just another change[00:36:59]: The next book: from women in engineering to women in technology[00:39:19]: Why the people who did the work need to tell their own stories[00:42:04]: Coming full circle to cultural anthropology, and stories as primary sources for historians[00:44:36]: Managing submissions: a Google Form, a spreadsheet, and a private folder for each writer[00:47:36]: Vibe coding Google Drive scripts to create the folders and docs[00:53:23]: More room for each story, and weekly status emails to every writer[00:55:11]: Getting a yes or no from each writer, and editing lightly so each woman’s voice stays her own[00:57:24]: From modest origins to editing Ginny Redish’s piece in tears[01:00:53]: Automating the parts of the job you don’t like[01:03:36]: Sharon’s recommended reading: Karen Schriver’s “Dynamics in Document Design”[01:05:08]: Susan Weinschenk’s “100 Things Every Designer Needs to Know About People”[01:07:20]: Ginny Redish’s “Letting Go of the Words,” and learning to think in pictures[01:08:46]: Advice Sharon has lived by: act as if you belong, and ask for helpResources discussed in this episode:Women in Technical Communication edited by Sharon Burton - The book Sharon edited, a history of the field told by the women who did the workBooks:Dynamics in Document Design by Karen Schriver - Based on Karen’s PhD research; Sharon goes back to it every four or five years100 Things Every Designer Needs to Know About People by Susan Weinschenk - Sharon keeps the second edition on her desk for brainstormingLetting Go of the Words by Ginny Redish - Which Sharon turns to when she needs to think in pictures instead of wordsJoin the discussion by replying on Bluesky
—Contact The Not-Boring Tech Writer team:We love hearing your ideas for episode topics, guests, or general feedback:Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyGuest suggestions formContact Kate Mueller:knowledgewithsass.comLinkedInBlueskyContact Sharon Burton:Email: [email protected] KnowledgeOwl:knowledgeowl.comLinkedIn
In this solo episode, I share my latest content updates progress and reflect on my takeaways from Jenna Jennissary’s interview (S3:E46). I share some thoughts on the collaborative work process she outlines and provide updates on some solo episode themes from 2025.—This month I ignored the article editor docs updates in favor of helping with pre-release testing and docs for our new file import tool, which supports importing PDFs and Word documents into KnowledgeOwl or converting them to articles within KnowledgeOwl. It handles other file types, too, but these were what I focused on in the documentation. This change also renamed our top-level menu item from “Articles” to “Pages,” so I did some work on reviewing and replacing occurrences of “Articles” with “Pages” when it was referring to the navigation (and not when it was referring to the concept or collection of articles, which are still valid).I also reflect on my interview with Jenna Jennissary and our discussion of audio description writers and resources, sharing a few additional resources I found. Jenna’s distinction between collaborative work rather than “group project” work was interesting, as it focused on things like style guide adherence and knowledge management, documenting, and sharing as you go, which feel like key concepts in a lot of lines of work.I close by sharing updates on a few key themes from my 2025 solo episodes, including updating you on how my experiment with Kate Pond’s Google form for daily check-ins is going and my house’s mouse infestation.In this episode:[00:00:46]: My progress update on pre-release docs for the file import tool[00:03:44]: Updating “Articles” in navigation to “Pages” and my find and replace adventure[00:06:43]: My recent and upcoming Wisdom Wednesday sessions[00:09:33]: My reflections on Jenna Jennissary’s episode and the work and resources of audio description[00:12:18]: Reflections on good collaborative work in audio description, as opposed to group project work[00:16:04]: Updates on my daily check-in Google form usage (thanks, Kate Pond!)[00:19:02]: Updates on my mouse infestation (TL;DL: seems to be going well)[00:21:27]: My goal for this month: keep on keeping onResources discussed in this episode:KnowledgeOwl Support Knowledge Base: Import PDF documentsKnowledgeOwl Support Knowledge Base: Import Word documentsKnowledgeOwl’s Find and replace featureOwlcademy Upcoming webinarsScripting audio description for film, TV, and video games with Jenna Jennissary (S3:E46) The ADNA Presents podcastThe Audio Description Project's Training Sessions and MaterialsSelf-documentation for career growth with Kate Pond (S3:E24)Kate sounds off on self-documentation (S3:E27)Join the discussion by replying on Bluesky
—Contact The Not-Boring Tech Writer team:We love hearing your ideas for episode topics, guests, or general feedback:Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyGuest suggestions formContact Kate Mueller:knowledgewithsass.comLinkedInBlueskyContact KnowledgeOwl:knowledgeowl.comLinkedIn
In this episode, I talk with Jenna Jennissary, a producer at Descriptive Video Works who specializes mostly in video games and still gets to write and perform audio description herself. We talk about how a Reddit post about a scene in “God of War” led her from regulatory affairs into audio description, where the field’s standards come from when no central body sets them, how tight timing makes writers experts at saying the same thing in fewer syllables, and what it takes to break in as a new audio description writer.—Jenna and I start with what audio description is: a scripted narrator who speaks between the existing dialog to describe the visuals for blind and visually impaired viewers. She came to it from regulatory affairs at a pharmaceutical manufacturer after SightlessKombat asked on Reddit for someone to describe an emotional, dialog-free scene in “God of War.” Jenna thought she could do better than the first attempt, and the two of them ended up audio describing the whole game as a fan project, which led to her job at Descriptive Video Works.The heart of our conversation is why Jenna calls audio description tech writing and creative writing smooshed together. No central body sets the rules; standards come from the biggest studios and clients like Netflix. Most of the constraints come down to timing: the narrator can only speak in the gaps, so you become an expert at finding synonyms with fewer syllables. We also talk about working past a sighted writer’s biases, including why, given the choice, it’s slightly better to describe an action just before it happens, so the listener has time to process it.Jenna covers what makes a good audio description writer and what makes an excellent one, the tools and security measures behind the work, how blind players play video games, and how new writers break in, including practicing on YouDescribe. She recommends Netflix’s audio description guidelines and the American Council of the Blind’s Audio Description Project, and closes with her own life advice: if something in your day-to-day bugs you, change it.About Jenna Jennissary:Jenna is a Producer at Descriptive Video Works, the largest Audio Description studio in North America, and the leading studio for video game Audio Description. She has written many of the current industry standards to adapt AD writing to the unique constraints of video games, and advocates for quality above all for her oft-underserved audience. Thankfully, she still often gets to write or perform AD herself for live events.In this episode:[00:01:16]: Jenna’s role: a producer at Descriptive Video Works, specializing in video games[00:02:24]: What audio description is, how it differs from captions, and a few samples[00:03:43]: Pre-scripted, live, and video game audio description, and where to find it[00:05:35]: Jenna’s origin story: regulatory affairs, disability advocacy, and helping blind gamers[00:08:28]: Audio describing all of “God of War” as a fan project, and landing at Descriptive Video Works[00:11:54]: A producer’s day-to-day: wrangling contractors, client review, and live describing gaming events[00:16:24]: No central body: where audio description standards come from, including Netflix’s guidelines[00:18:35]: The shift toward describing characters’ ethnicity and racial appearance[00:20:52]: Picking the synonym with the right vibe, and whether audio description can be standardized[00:21:56]: An advisory committee of blind film critics, and client guidelines that work against accessibility[00:26:00]: Is audio description tech writing? Timing constraints and synonyms with fewer syllables[00:27:59]: Avoiding tongue twisters, voicing subtitles, and casting extra narrators[00:31:48]: Overcoming sighted bias, and describing an action just before it happens[00:35:43]: The skills of a good audio description writer, and what makes an excellent one[00:40:12]: The tool stack: ADR software, captioning tools, and clients’ proprietary platforms[00:42:33]: Security: on-site writing, watermarked proxies, and preventing leaks[00:45:00]: How blind players play video games: text to speech, haptics, and sound effects[00:47:30]: Accessible fighting games, the Blind accessible games wiki, and player-made mods[00:49:02]: Breaking into audio description: surveys, writing tests, and training[00:51:40]: Joining the writer roster, and training programs to diversify the field[00:54:26]: Practicing on YouDescribe[00:55:29]: Resources: Netflix’s guidelines and the American Council of the Blind’s Audio Description Project[00:56:46]: Jenna’s best advice: if something bugs you, change itResources discussed in this episode:The American Council of the Blind’s Audio Description Project: Jenna’s pick for finding movies and TV shows with audio description and the platforms they’re onVideo games with audio description: The list from the ADP’s video gaming subcommittee, which Jenna serves onThe “God of War” audio description fan project: SightlessKombat’s #TranscribingGames guide to the game, with links to the audio described videos Jenna wrote and voicedNetflix Audio Description Style Guide: Netflix’s public audio description guidelines, which Jenna recommends as a publicly-available style guide you can accessBlind accessible games: The wiki Jenna mentions for finding games that blind players can playYouDescribe: A site where blind viewers request audio description for YouTube videos and anyone can add it, which Jenna recommends for practiceJoin the discussion by replying on Bluesky
—Contact The Not-Boring Tech Writer team:We love hearing your ideas for episode topics, guests, or general feedback:Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyGuest suggestions formContact Kate Mueller:knowledgewithsass.comLinkedInBlueskyContact Jenna Jennissary:Email: [email protected]
In this solo episode, I share my latest content updates progress and confess to finally jumping on the Claude Code bandwagon. I also reflect on my takeaways from Katie Cox’s interview (S3:E44) and some of the instructional design concepts she shared that most resonated with me.—I finally finished my Minimum Viable Docs (MVD) list from the article editor layout release, four months later. I also finally gave in to using Claude Code when I needed to overhaul and update our OpenAPI spec file for our API documentation. My usage began innocently enough, trying to catch issues upgrading from version 2.x to 3.0 of the OpenAPI spec, but eventually included upgrading to version 3.1, updating Redoc, and overhauling a lot of the structure. Along the way, I still relied a lot on human expertise, in the form of API docs feedback from our developer Sue and OpenAPI technical expertise from Lorna Mitchell. I ultimately created a Claude skill that checks for valid YAML, validity against the OpenAPI spec file, validity against the Redoc linter CLI, and a few style guide choices.I also reflect on my interview with Katie Cox, noting that there are a ton of ways that instructional design and technical writing overlap in terms of the skillset, the day-to-day work, and the focus on end-user needs. The primary difference, to me, lies between what a reader expects versus what a learner expects. I appreciated Katie’s focus on encouraging self-directed learning and not gating content behind clicks and required interactions. And I’m most looking forward to pairing learning objectives with a compelling narrative, one of the key tricks she uses in her work.In this episode:[00:00:28]: Kate’s progress updates[00:01:42]: Kate’s long tangent about using Claude Code to update her OpenAPI spec file[00:16:48]: Kate’s reflections on Katie Cox’s episodeResources discussed in this episode:KnowledgeOwl’s API endpoint reference documentationDeveloper collaboration with Lorna Mitchell (S3:E2)KnowledgeOwl’s API keys documentationMaking the leap from tech writing to customer education with Katie Cox (S3:E44)The Accidental Instructional Designer by Cammy BeanJoin the discussion by replying on Bluesky
—Contact The Not-Boring Tech Writer team:We love hearing your ideas for episode topics, guests, or general feedback:Email: tnbtw@knowledgeowl.comthenotboringtechwriter.comLinkedInBlueskyGuest suggestions formContact Kate Mueller:knowledgewithsass.comLinkedInBlueskyContact KnowledgeOwl:knowledgeowl.comLinkedIn



