<?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>Forem: Jacob Eubanks</title>
    <description>The latest articles on Forem by Jacob Eubanks (@jacobeubanks).</description>
    <link>https://forem.com/jacobeubanks</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%2F211757%2F65c6d067-7f1a-48c7-9c0b-74abd655e997.jpeg</url>
      <title>Forem: Jacob Eubanks</title>
      <link>https://forem.com/jacobeubanks</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jacobeubanks"/>
    <language>en</language>
    <item>
      <title>2 Effective Methods for Managing People Who Are Smarter than You</title>
      <dc:creator>Jacob Eubanks</dc:creator>
      <pubDate>Mon, 19 Aug 2019 18:58:50 +0000</pubDate>
      <link>https://forem.com/jacobeubanks/2-effective-methods-for-managing-people-who-are-smarter-than-you-2o9f</link>
      <guid>https://forem.com/jacobeubanks/2-effective-methods-for-managing-people-who-are-smarter-than-you-2o9f</guid>
      <description>&lt;p&gt;&lt;sup&gt;Cover Image: &lt;a href="https://www.pexels.com/photo/close-up-photo-of-grape-fruit-197907/"&gt;Close Up Photo of Grape Fruit&lt;/a&gt; by &lt;a href="https://www.pexels.com/@henriguerin"&gt;Henri Guérin&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;

&lt;p&gt;Part of my responsibilities as Lead UX Engineer at the company I work for is to manage a small UI/UX team made up of 3 brilliant people and myself. I've learned a lot so far and I have two solid tips that may help if you're ever in a similar situation.&lt;/p&gt;

&lt;h2&gt;
  
  
  1) Ask questions
&lt;/h2&gt;

&lt;p&gt;Asking questions is a great way to learn together as a team and encourage collaboration. This comes to mind when there is a particular piece of a design or software that doesn't quite function the way it &lt;em&gt;should&lt;/em&gt; or isn't the pattern you would have implemented.&lt;/p&gt;

&lt;p&gt;Asking how the user would feel when interacting with the problem area vs expressing dislike or suggesting a change is going to produce a more collaborative and ultimately better result.&lt;/p&gt;

&lt;p&gt;At the same time, they more than likely have spent more time in that area trying to figure out a solution so often they have perfectly good reasoning that you may not have found out about if you didn't ask first. &lt;strong&gt;Acting on assumptions will underutilize your team&lt;/strong&gt;, ask questions instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  2) Encourage pushback
&lt;/h2&gt;

&lt;p&gt;When members of a team are encouraged to express their opinions and give pushback when they see fit the whole team benefits.&lt;/p&gt;

&lt;p&gt;Using one person's opinion isn't usually the right way to build things, especially in the UI/UX world. Want to implement something but the team thinks it's a bad idea? Guess what, it's probably a bad idea and enabling your team to pushback on it just saved tons of time and money.&lt;/p&gt;

&lt;p&gt;Take your team members seriously and thank them when they do pushback. &lt;strong&gt;Creating a safe environment is critical&lt;/strong&gt; if you want to get the most out of your team.&lt;/p&gt;

&lt;p&gt;One thing that seems to always ring true: &lt;strong&gt;Collaboration to produce a better solution is essential when working with smart people.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ui</category>
      <category>ux</category>
      <category>management</category>
    </item>
  </channel>
</rss>
