If you are like most tech writers, your team sometimes designs products and features that are difficult to use, and they depend upon you to make them usable through user assistance. You are an expert at communicating to users and have a strong understanding of how the designs could be improved to reduce the need for extensive documentation. All you need to do is get your team on board. Good luck with that!
In this talk, you will learn how to quickly identify when you are documenting around design flaws, and give more persuasive feedback to your designers and developers to fix them. (Hint: personal opinion and hypothetical, subjective arguments are rarely persuasive.) You will learn why team dynamics sometimes work against you, and how to make your case using “lighthouse” examples, which are objective, tangible, data-driven–and require much less documentation. Better to show than to tell.