# Letting Go of the Words **Readwise highlights:** [[3. Resources/Readwise/Books/Letting Go of the Words]] **Visual summary:** ![[Letting Go of the Words Visual.excalidraw]] ## Book Overview Janice (Ginny) Redish's *Letting Go of the Words* is a practitioner's guide to writing effective web content. The book's central premise is straightforward: people come to websites with specific questions and tasks, and your job as a writer is to make information easy to find, easy to understand, and credible. Redish draws on decades of usability research to argue that web writing isn't about what you want to say -- it's about what your audience needs to hear. The book walks through a content creation process that starts with understanding your audience and ends with maintaining and managing content over time. Redish emphasizes that good web writing begins long before you type a single word. You need to know who your readers are, what questions they bring, and what tasks they're trying to complete. She introduces personas as a practical tool for keeping real people at the center of content decisions. A recurring thread throughout the book is that content strategy and content creation are inseparable. Planning, coordinating, reviewing, and retiring content are all part of the job. Redish pushes back against the idea that writing for the web means dumbing things down. Instead, it means thinking clearly about purpose, audience, and structure -- then writing with enough discipline to serve all three. ## Key Themes and Highlights ### Audience-centered writing Redish grounds everything in the reader's perspective. She argues that too many organizations write for themselves rather than for the people who actually visit their sites. The foundation of good web content is knowing your audience -- not guessing, but actively researching. > "People come for information that answers their question or helps them complete their task. They want that information to be easy to find, easy to understand, accurate, up to date, and credible." > "Understand that your readers are not blank slates. We all interpret as we read, bringing the baggage of our past experience and our own understanding of what words mean." She provides a practical framework for audience research: gather data from analytics, social media, site visits, and usability testing rather than making assumptions. List key characteristics for each visitor group including their experience, emotions, values, technology context, and demographics. ### Content planning as conversation Redish frames content creation as a conversation between the organization and its visitors. Planning means answering three questions: Why? Who? What conversations? This framing shifts the writer's mindset from broadcasting information to engaging in dialogue. > "To have successful conversations, you have to know -- what you want to achieve through your content -- who you are conversing with -- what they want from your app, your site, your topic, your message; what task they want to accomplish." > "Planning your content is critical for apps, web sites, individual web topics, blogs, social media messages -- everything you write." The conversational model also drives her approach to personas: each persona is a composite of real people, not an invented character, built to represent a specific audience segment with real needs. ### Content strategy and governance The book makes a strong case that writing content is only part of the work. Content must be planned, coordinated, reviewed regularly, managed with someone in charge, and removed when it becomes outdated. Redish provides a seven-step process: inventory current content, decide on messages and style, create a style guide, design around content, audit existing content, test the strategy, and plan for the future. > "Content strategy means that all the content is not only created (or repurposed or revised); it is also planned, coordinated, reviewed regularly, managed and maintained with someone in charge, removed when it becomes outdated." She pushes organizations to think about their key messages, the mix of media they'll use, how formal or informal their tone should be, and how they'll handle different audiences across different channels. ## Analytical Reading - **Central Argument:** Web content succeeds when it's built around audience needs, planned strategically, and maintained with the same rigor used to create it. - **Key Evidence:** Usability research, persona methodology, content inventory and audit practices, real-world examples of content strategy implementation. - **Methodology/Approach:** Redish builds her case through practical frameworks -- personas, content inventories, style guides, audit processes -- grounded in user-centered design principles. The book is structured as a how-to guide rather than an academic argument. - **Strengths:** The emphasis on audience research over assumptions is well-supported. The seven-step content strategy process is actionable. Framing writing as conversation shifts the writer's mindset productively. - **Limitations:** The highlights suggest a focus on informational and task-oriented content. The book may underserve writers working on brand storytelling, persuasive content, or more creative web formats. Some of the tactical advice around character limits and platform specifics may date quickly. ## Personal Reflection The conversational framing of web content is the most transferable idea here. Most content problems I've encountered aren't really writing problems -- they're planning problems. Teams skip the audience research, skip the content strategy, and jump straight to drafting. Then they wonder why the content doesn't connect. Redish's insistence on starting with "Why? Who? What conversations?" is a corrective that applies well beyond web writing. The connection to developer relations work is direct. Developer documentation, tutorials, and guides all benefit from the same audience-centered approach. Knowing whether your reader is a beginner or an expert, what task they're trying to complete, and what questions they're bringing changes everything about how you structure and write content. The persona methodology translates cleanly to developer audience segments. The content governance piece is where most teams fall apart. Creating content is the easy part. Maintaining it -- auditing, updating, retiring outdated material -- is where the real discipline lives. Redish's framework for ongoing content management is a useful checklist for any content operation. ## Action Items - [ ] Apply the "Why? Who? What conversations?" planning framework before writing any new content piece - [ ] Build lightweight personas for the primary audience segments of current content projects - [ ] Set up a quarterly content audit process to identify outdated material that needs updating or removal