Should designers be generalists or specialists?
We look for generalists when we hire
We need people who have a wide range of skills. One day they can be doing user research — interviewing customers, writing surveys, analyzing results, etc. — and the next day they’ll be doing interaction work and visual design. At some point they’ll also be working closely with frontend developers, and they may even write code.
“A team built from generalists can handle any design task.”
If we hired specialists to cover each of these roles, we’d have some problems:
- Less efficiency — designers would wait around for the next task that required their speciality
- Loss of context on projects during handoffs
- A weakened relationship with the development team
Most designers have one skill they’re better at than others. We share these specialities to mentor our teammates and level any gap in skills. A designer with great research skills will work with the other designers to help them become better researchers. We don’t give all the research work to the person with those skills.
Exceptions
We have a UI design team that works on our Design System — they’re specialized in visual design, which we like to refer to as UI design. They’re expected to learn new skills like Framer.js.
Information architecture (IA) and copywriting is another exception. We have a great IA and UX writer (she opened World IA Day 2016) who works closely with our designers. Since we have such a complex IA in our product, and because we have a global audience, this is the one area that we need a true specialist.
Generalists are in demand
In a product environment, it’s essential to be a generalist. You need to be surrounded by other generalist designers who can share their skills and experience.
A team built from generalists is a team that can handle any design task.That’s the kind of team we need at Envato.
More to come in part 2...