Skill #4: Understanding UX Design

📣 Special announcement: The Not-Boring Tech Writer team (Kate and Chad) will be at Write the Docs Portland in May. Thanks to KnowledgeOwl's sponsorship, they’ll be wearing KnowledgeOwl and The Not-Boring Tech Writer t-shirts and giving out The Not-Boring Tech Writer stickers. If you're attending WTD Portland this year, please say hi to Kate and Chad, let them know what you think of the show, and swing by the conference swag table to grab some free stickers so you can flaunt your not-boring tech writer status with the world!_____________________________________________Where should user experience (UX) design fit in the technical writer’s toolbox?Well, think about how your users experience your documentation:Are they following a workflow path, following a series of pages to complete a series of tasks sequentially?Are they following nav links, jumping around to find task-specific information?Understanding how your users experience your documentation is understanding UX design – which can make or break your docs’ usability.As our guest and UX designer Autumn Hood describes it: “You can’t have good technical communication without good UX design.”In this episode, you’ll learn how to think like a UX designer so you can create an effective documentation experience for your users.The Show Notes:Janice Redish’s Understanding ReadersSusan Weinschenk’s ROI of User Research webinarAutumn Hood on TwitterAutumn Hood on LinkedIn

Om Podcasten

All technical writers have one thing in common: their peers outside of the industry believe technical writing is a boring career. They think we lack creativity; they think we only eat tuna salad for lunch; and they think our work is reserved to instructional manuals that they don't even use. This podcast gives you the tools to prove them wrong! In each episode we talk to the humans behind the docs, sharing stories, experience and expertise to inspire, entertain, and give you knowledge and skills you can use in your life as a not-boring tech writer.