Design/UX Team Structure

over 9 years ago from Matt Felten, Design System Lead at YouCaring

  • Joshua SortinoJoshua Sortino, over 9 years ago (edited over 9 years ago )

    Edit: Some people suggested I compile my comment into an article... so I published it here:

    I helped build the design team at Disqus and now I'm helping build the design team at Teespring.

    Always make sure you're hiring exceptional people (that applies to all departments, not just design). People who have a passion to create and build will be your smartest employees. It's better to hire someone who has a problem solver's mindset but lacks a specific skill than to hire someone who has that skill but lacks a problem solver's mindset.

    Ask yourself, "what does this person do better than I can?" Make sure each designer brings a unique skill to the team. When everyone is good at something different, everyone settles into projects that fit their strengths and they won't run into ego battles.

    "Unicorns" can be great, especially when the company is small. Unicorns can code and design, but don't forget the more designers are coding the less they're designing.

    As a company grows, you want hire more specialists. Unicorns who are "T" shaped (i.e. they have a broad skill set but are still very good at one thing) will experience fewer growing pains.

    With a few exceptions, I have often found Unicorns to be slightly less skilled in the artistic and visual department (myself included). Sometimes it's useful to have one person who is just really good at branding, visuals and interaction design without knowing how to code.

    Don't make exceptions. Even if you're extremely desperate for help, a bad employee will cost you more time and money than what they temporarily saved you.

    “Steve Jobs has a saying that A players hire A players; B players hire C players; and C players hire D players. It doesn't take long to get to Z players. This trickle-down effect causes bozo explosions in companies.”

    This leads me to my conclusion for how to structure your team. You've hired the best possible employees you could find. Everyone brings unique skills to the table. Do you really need to structure the company like a traditional agency? A flat organization structure keeps egos in check and shows your employees you value them equally. If you really did hire the best, let them know they can use whatever external title they want (Senior, Lead, etc...) after they move on from the company.

    Last, don't be intimidated. Building a strong team is time-consuming, tedious work. But let me tell you, it's some of the most satisfying work you'll ever have.

    27 points
    • Jad LimcacoJad Limcaco, over 9 years ago

      Great advice Josh!

      0 points
    • Tony GinesTony Gines, over 9 years ago

      You should just copy paste this response into a Medium article. Good stuff.

      0 points
    • Ryan Hicks, over 9 years ago

      Best advice I've read on the subject. Well put.

      1 point
    • Matt FeltenMatt Felten, over 9 years ago

      Thanks Joshua. Immensely helpful. It's hard to look past short-term needs (Holy crap! I need help) to make sure you're hiring the best people.

      Did you have front-end developer specialists on your team(s) or did you only have designers and "unicorns"?

      Aside: Is there really not a better term for "unicorn" yet?

      2 points
      • Joshua SortinoJoshua Sortino, over 9 years ago

        I really hope there's a better term than unicorn! I only use it because its meaning is recognized throughout the tech industry.

        0 points
        • Matt FeltenMatt Felten, over 9 years ago

          Yeah, not a slight against you at all. It's pretty ubiquitous now. I just can't help thinking I'm saying "UI Rockstar!" or something.

          0 points
      • Joshua SortinoJoshua Sortino, over 9 years ago

        And to answer your question... we hire both. Some designers on the team code, some do not. If they're good at what they do, you'll find (or they'll find) where they fit in.

        Like I said, the more a designer codes, the less they design. If you really need help and you can't find a "unicorn", maybe you should consider hiring both a front-end engineer and a designer? If you don't think there's enough design work to go around, hiring a design contractor (and a full-time front-end engineer) might be a better route.

        0 points
    • John OatesJohn Oates, over 9 years ago

      Great post! We've been currently having a lot of discussion about our structure and process, do you have any suggestions for reading materials, books/articles? Thank you for your insight!

      0 points
    • Brandon FinnBrandon Finn, over 9 years ago

      Ya Josh!

      0 points