> For the complete documentation index, see [llms.txt](https://www.pmguidebook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pmguidebook.com/people-skills/communication/knowing-your-audience.md). # Knowing Your Audience Understanding your audience is fundamental to effective communication. This skill involves recognizing the audience's characteristics, such as their roles, cultures, backgrounds, goals, motivations, and communication styles. ## Example When collaborating with a Product Designer (PD) on reviewing a new design for an existing feature at a music streaming service, such as Apple Music, the PD usually leads the meeting. The Product Manager (PM) carefully examines the new design and actively listens to the PD's rationale. Throughout the design review, the PM raises any concerns and provides detailed explanations to support their thinking. For example, suppose the search bar is not easily accessible despite previous user analysis indicating its importance. In that case, the PM waits for the discussion on the search area and then articulates the issue, explains the underlying reasoning, and potentially suggests a solution. The process often involves allowing space for collaborative or individual exploration to find the best solution. This communication style is well-suited for cross-functional collaboration with teams like development and marketing. On the other hand, when engaging with a Data Scientist (DS) or any other research collaborator, the PM employs a precise and detailed communication approach. Suppose the DS is analyzing the PM. In that case, the PM ensures clear communication of the business use case, hypotheses being tested, suggested approaches, and any specific requirements for deliverables such as file format, data points, or graphs. This level of communication also applies when working with Data Analysts, UX Research, or other team members involved in research. In contrast, the PM adopts a more concise approach when discussing a problem with C-Level executives (e.g., CEO or CFO). They provide a high-level overview of the problem, potential solutions, and their recommendations. The PM typically delves into specifics only when prompted or requested for further information but can bring up areas deemed important by the PM. ## Pain Points Challenges include understanding diverse audience needs and avoiding assumptions about audience knowledge or perspectives. Miscommunication can occur if the message isn't tailored to the audience's understanding. ## Practical Exercise Think of three different audiences you communicate within your role. How would you adapt a product update message for each of them? ## Related Research Topics * Audience analysis techniques \[ [Google](https://www.google.com/search?q=Audience%20analysis%20techniques%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Audience%20analysis%20techniques%20in%20product%20management) ] * Cross-cultural communication \[ [Google](https://www.google.com/search?q=Cross-cultural%20communication%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Cross-cultural%20communication%20in%20product%20management) ] * Communication styles \[ [Google](https://www.google.com/search?q=Communication%20styles%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Communication%20styles%20in%20product%20management) ] * developer-speak \[ [Google](https://www.google.com/search?q=developer-speak%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=developer-speak%20in%20product%20management) ] --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.pmguidebook.com/people-skills/communication/knowing-your-audience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.