I spent a while trying to come up with a title for this article that truly established one of my least-favourite things in public relations, and I\u2019m still not happy. I keep thinking back to my first job in PR, where one of my managers (who isn\u2019t even in PR anymore) actively made fun of me for knowing how the very tech we were working on actually functioned. In future roles, I\u2019d have management actively worry about people who played too many games in a scenario where, ostensibly, we were talking to games journalists about video games.<\/p>\n
To really drill this home, I want to specifically say that if you make someone in PR feel bad because they actually know their subject matter, you are worse than scum.<\/strong><\/p>\n I have heard a lot of PR people \u2013 managers especially \u2013 say that they have domain expertise in, say, consumer tech or business. What they actually mean is that they\u2019ve learned the definitions of a few things, and that they can, when prompted, tell you what these things mean and roughly how you\u2019d put them in a sentence. What they\u00a0cannot<\/strong>\u00a0do is synthesize this information into further meaning, or have a particularly meaningful conversation around the subject. These are the same people that will also say to young PR people that actually know a subject to \u201cnot know too much\u201d about it, because it \u201cgets in the way.\u201d<\/p>\n Domain Expertise actually means having knowledge of a subject, how it works, and the larger industry,\u00a0and does not just mean remembering the right words and the right people.<\/strong><\/em>\u00a0For example, if you\u2019re doing PR for a gaming company, this means having played a meaningful chunk of recent releases, and completed at least, say, one major game. If you\u2019re working for a major PC manufacturer, especially one that\u2019s focused on performance, this means likely having built and still being able to build a PC, knowing what particular things do, why, say, a person may need multithreaded processing, if that\u2019s a part of said chip you\u2019re working on.<\/p>\n What pisses me off is the large crystallization of PR people who believe that having a surface level knowledge of stuff is enough to do a good job, and that having too much knowledge makes you unable to communicate the core value of a product. If you\u2019re reading this and saying \u201chaha, that ain\u2019t me,\u201d please interrogate if you actually know your ass from your earhole when it comes to your industry. While it\u2019s not possible to know everything, you should be able to understand and bathe in the industry that you claim to know\u00a0at least half as well<\/em>\u00a0as the reporters you\u2019re talking to.\u00a0And mark my words, they will notice.<\/em><\/p>\n Reporters hate this too, because they have to deal with PR people from giant agencies that have held onto big technology accounts for years due to people having varying levels of both confirmation bias and revealing photos on the right people in power. When a big agency gets an email about, say, a tech product\u2019s ability to X or Y, this is oftentimes routed through a manager, which goes to a PM, which goes to another person, which goes back to the manager to approve the content of. Would this not be easier if the PR person could not simply look in their brain and answer the question?<\/p>\n Similarly, when you\u2019re pitching a reporter, knowing what you are talking about actually allows you to pitch better. If said reporter is a consumer tech producer, perhaps they\u2019re not the ideal target for a high-end graphics card \u2013 even if they build PCs, there\u2019s not a high likelihood their viewers do. Conversely, when you find a reporter and show them that not only do you know your stuff, but you can actually converse about said stuff with them and help them understand why the thing you\u2019re pitching is good, and they\u2019ll be far more likely to write about your product. It\u2019s just that easy.<\/p>\n To conclude, if you have derisively referred to having knowledge as \u201ctoo much,\u201d if you have rolled your eyes at a colleague that has said something technical and claimed it\u2019s irrelevant, or if you\u2019ve felt self-conscious because someone has known more than you and made them feel bad for it, please learn more, or quit this industry. Get out. I don\u2019t want you here anymore.<\/p>\n","protected":false},"excerpt":{"rendered":" I spent a while trying to come up with a title for this article that truly established one of my … <\/p>\nWhat Domain Expertise Actually Means<\/h2>\n