Successful technical documentation is clear, accurate, concise, helpful, and focused on real-world user goals. Almost as important is understanding what not to write. Think of it as opportunity cost. Time and effort spent writing unnecessary or duplicative content could be spent more productively on the many things we do need to document. Our 23-minute podcast discusses how you, the writer, should look at your requests and why you have the right and obligation to ask if you think the work may be unnecessary.