What defines a great product designer?
Is it clarity of vision? The efficiency of iteration? A sixth sense for involving the right people at the right time?
We can speculate endlessly. Instead, we spoke with 10 experienced designers from a variety of backgrounds and industries to collect their thoughts on how to become a better designer in 2016.
We learned about their successes, their failures, and their new perspectives on design. From enterprise UX to travel sites and design agencies, here is their top advice for improving your skills within a larger product team.
Table of Contents
- 1. Kick formalities to the curb
- Austin Knight, UX Designer at HubSpot
- 2. Craft product personality before beauty
- Jessica Phan, Founding Designer at Zugata
- 3. Scalable design systems are the future
- Drew Thomas, Chief Creative Officer at Brolik
- 4. Evangelize UX through a common language
- Justin Mifsud, UX Designer & Founder of UsabilityGeek
- 5. Pick your battles patiently
- Alina Bochkacheva, Product Designer at Duo Security
1. Kick formalities to the curb
Austin Knight, UX Designer at HubSpot
This year, I paid a guy to get drunk and run a user test of HubSpot.com. Then I toured the country talking about the results.
I had the time of my life. But perhaps more importantly, I was able to change the way that my team (and many teams around the country) approach qualitative user research.
We ran an unorthodox usability test (originally as a joke), ended up gathering surprisingly valuable feedback, applied that feedback to our design, generated measurable results, and ultimately learned something new about how user testing should be conducted. None of this would have been possible without the support of the awesome, forward-thinking company that I work at.
Don’t be afraid to test everything you know about “the way design is done”. I am realizing how critical it is to work with people that are open-minded, humble, and truly motivated to make something great.
When meeting designers, I pay little attention to education or certifications, and much more attention to experience, passion, and demonstrated ability. This year, I experienced the heightened success and satisfaction that comes from working with people who focus less on formalities and more on creativity, agility, open-mindedness, and ultimately having fun along the way.
In 2016, I urge more companies and product teams to rethink the ways that they work and experiment more with new concepts and ideas.
2. Craft product personality before beauty
Jessica Phan, Founding Designer at Zugata
As the solo and founding designer at an early stage startup, I learned it is crucial to focus more on the brains and personality rather than the face and beauty of the product.
Because speed is a startup’s best friend, we have to execute quickly, sometimes at the expense of few misplaced pixels, icon inconsistencies, and type crimes.
And as much as it’s painful to lower design standards, the sacrifice must be made. We learned that what we are essentially building is still a prototype. But once we discover that product stickiness, we return and focus on the face and beauty of the product.
For new features we launch in 2016, we will continue to iterate scrappily and test quickly. And when we nail the engagement and retention for existing features, we will go back and polish up the aesthetics.
3. Scalable design systems are the future
Drew Thomas, Chief Creative Officer at Brolik
In 2015, I learned that the only way to be future-friendly is to separate everything into its most basic and versatile form.
Things are changing fast– frameworks, networks, devices, even the “Internet of Things”. The things we make today need to do a lot more tomorrow. It’s not too hard to be prepared, though. Content can be separate from front end code and accessed via API. We can create many component-specific stylesheets to be rearranged and used anywhere. UX can be built with UI kits or pattern libraries to be reused in many different places across different applications.
The point is that in 2016 and beyond, it won’t be possible to keep up with all of our digital tasks in a cost efficient way unless we standardize, organize, and see “digital” as a single system with many versatile and reusable parts.
The biggest way it’s going to affect us is we’re pushing content APIs for all of our clients. Basically, we’ll build them a “standalone” CMS that has no specific front end (website, app, whatever). We started doing this already, but we decided to build out our platform this way and make it official.
Other than that, it’s mostly atomic design-like stuff. We don’t go full on atomic and use the same terminology and everything, but we’ve been building more and more that way for each project.
We recently started creating “live” UI kits instead of a full visual design. So we combine UXPin prototypes with the UI kit elements and the design just happens. It’s much faster than creating a high-fidelity mockup from scratch.
4. Evangelize UX through a common language
Justin Mifsud, UX Designer & Founder of UsabilityGeek
While UX evangelization has remained a core aspect of the UX Designer’s role, you need even more skills and knowledge now.
For example, as a UX consultant, I have witnessed many company owners stress the importance of conversions as a result of design changes
If a UX designer is not familiar with conversion and how to implement it in their design (e.g. more prominent CTA, content design that enables the reader to focus) etc. etc. then that is a serious problem. Also, more than ever, the UX designer also needs to communicate with other stakeholders using their jargon and be able to present their ideas using notation that they can understand.
Long story short: the UX designer needs to evangelize through common knowledge. You’re better able to sell the ROI of UX when you’re able to incorporate theories from other fields such as marketing, SEO and general business strategy.
5. Pick your battles patiently
Alina Bochkacheva, Product Designer at Duo Security
In 2015, I joined the best and biggest team I have ever worked with at a 200+ person company.
When working on enterprise products, I had to learn how to make decisions and reach common ground with much bigger groups of people. What do you do when you disagree?
Sometimes you just have to step aside, look at everything as a whole and ask yourself “Is it that important? Will it make a big difference to the user?”. On the other hand, sometimes we feel very strongly about our decisions.
How do we bring our team members to the same page?
My answer is by walking them through, step by step, how we got here. And before you react to any feedback, just give it 5 minutes first.