<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Xinran Wang</title>
    <description>The latest articles on DEV Community by Xinran Wang (@xinranw).</description>
    <link>https://dev.to/xinranw</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F5802%2Fd8d51682-c35b-4d53-b449-1948ce46447b.JPG</url>
      <title>DEV Community: Xinran Wang</title>
      <link>https://dev.to/xinranw</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/xinranw"/>
    <language>en</language>
    <item>
      <title>Professional communication skills - identify your audience</title>
      <dc:creator>Xinran Wang</dc:creator>
      <pubDate>Sun, 01 Mar 2020 21:56:45 +0000</pubDate>
      <link>https://dev.to/xinranw/professional-communication-skills-part-2-1hia</link>
      <guid>https://dev.to/xinranw/professional-communication-skills-part-2-1hia</guid>
      <description>&lt;p&gt;Welcome back to my series on professional communication skills. In part 1, we established &lt;a href="https://dev.to/xinranw/professional-communication-skills-2kh7"&gt;the importance of growing your communication skills&lt;/a&gt;, especially within a tech-focused career. In this article, I'm going to discuss the first skill that can help improve your communication abilities.&lt;/p&gt;

&lt;h3&gt;
  
  
  Identify your audience
&lt;/h3&gt;

&lt;p&gt;The first step is to consciously identify who you're communicating with.&lt;/p&gt;

&lt;p&gt;The way different groups of people communicate between themselves can be vastly different. Think about the common discussions between engineers vs managers vs directors; the problems they discuss, the terminology they use, even the tools they rely on for communicating, are all quite distinct. &lt;/p&gt;

&lt;p&gt;By default, after a few weeks on a job, you get used to talking with other engineers on your team. But what does "getting used to" mean? Why are you able to communicate relatively easily? Why might talking to a non-engineer or non-team member seem harder?&lt;/p&gt;

&lt;p&gt;With people you work with on a regular basis, sure you get used to their personalities and ways of talking, but you also inherently share underlying context: goals, tools, languages, acronyms etc. All of these factors affect effectiveness of your communication style. By identifying who you're talking to, you can start adjusting for those differences and vary the information, terminology, and style of your communication.&lt;/p&gt;

&lt;p&gt;For example, if you're a frontend engineer, talking about your problems with javascript, react, html, css, webpack, npm etc. might cause a lot of confusion with the backend engineers on the team, bu they can still probably provide input on technical design issues or help talk through a bug.&lt;/p&gt;

&lt;p&gt;Moving a bit farther away from the tech stack, designers and product managers won't really care about the technical problems you're having but would be happy to talk through product and design level questions and feedback.&lt;/p&gt;

&lt;p&gt;Moving another level away, directors, marketing, legal etc. might all be so far removed from the projects you work on that there won't be many commonalities in your day to day work, especially at a larger company. So even when talking about the same projects, you'll have to find ways to communicate in a way that's relevant to them. This might sound more like user research, metrics, or alignment with company goals. &lt;/p&gt;

&lt;p&gt;So in the future, try being more conscious of your audience, especially when you're working with people outside of your immediate team. Think about the words you use and adjust for your audience. These small changes can have a big impact in how you are able to communicate outside of engineering.&lt;/p&gt;

&lt;p&gt;This is part 2 of my series on professional communication skills. Stick around for future articles in this series!&lt;/p&gt;

&lt;p&gt;Professional Communication Skills series:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://dev.to/xinranw/professional-communication-skills-2kh7"&gt;Professional communication skills intro&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/xinranw/professional-communication-skills-part-2-1hia"&gt;Identify your audience&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Figure out what your audience actually cares about&lt;/li&gt;
&lt;li&gt;Adjust the information and terminology you use for your audience&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>career</category>
      <category>communication</category>
      <category>growth</category>
    </item>
    <item>
      <title>Professional communication skills - Intro</title>
      <dc:creator>Xinran Wang</dc:creator>
      <pubDate>Tue, 11 Feb 2020 08:40:58 +0000</pubDate>
      <link>https://dev.to/xinranw/professional-communication-skills-2kh7</link>
      <guid>https://dev.to/xinranw/professional-communication-skills-2kh7</guid>
      <description>&lt;p&gt;For most of us, talking to people within our realms is relatively easy. We all care about similar things, use the same tools, solve similar problems. But when we need to break out of our bubble to collaborate with other functions (design, product, marketing, business, etc.), communication gets harder and harder. &lt;/p&gt;

&lt;p&gt;Part of what makes this difficult is that these communication skills are often not emphasized early in our careers. It's usually after we've caught up on the technical skills that these &lt;del&gt;soft&lt;/del&gt; professional skills become more important.&lt;/p&gt;

&lt;p&gt;As junior engineers, our day-to-day work often requires hours of continuous individual focus, solving new technical problems, and communicating via Slack with our peers. Occasionally we'll have a 1-on-1 with a manager or participate in team meetings. Most of these interactions involve largely similar communication styles. &lt;/p&gt;

&lt;p&gt;After a few years, as you try to level up and start leading projects, you'll immediately start running into problems if you use the same communication styles as before. At first, you'll work with engineers outside of your team, who won't have the same technical background and goals as you. Then more closely with the engineering and product managers, who care about entirely non-technical problems. Eventually you'll scale out of the product org to working with business and legal, who basically speak a different language. How you're used to communicating with fellow engineers on your team is probably not going to work very well when you're working with these other groups of people. &lt;/p&gt;

&lt;p&gt;Yet being able to communicate effectively is incredibly important. You have to be able to work across teams and organizations to solve the really big problems. You have to talk to all kinds of different people and convince them to believe in you and trust in you. All of that requires effective communication skills.&lt;/p&gt;

&lt;p&gt;In these upcoming articles, I'll do some deep dives into some of the skills that have helped me improve. Stick around!&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://dev.to/xinranw/professional-communication-skills-2kh7"&gt;Professional communication skills intro&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/xinranw/professional-communication-skills-part-2-1hia"&gt;Identify your audience&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Figure out what your audience actually cares about&lt;/li&gt;
&lt;li&gt;Adjust the information and terminology you use for your audience&lt;/li&gt;
&lt;li&gt;Change your communication medium for your audience&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>career</category>
      <category>communication</category>
      <category>growth</category>
    </item>
  </channel>
</rss>
