Dec 04, 2018

Essential skills for Product Designers

What does it take to be a good Product Designer?

Product designers are solving complex problems these days. We’re working every day to understand the users, the problems and trying to come up with a solution that we iterate over time. But, what does it take to be a good one?

Fortunately, I have invited a few friends of mine to pick their brains and wisdom. So, I poked a few of them and ask them a cliché question: If you can pick one, what is the most important skill to have as a Product Designer?

Let’s hear what they have to say.

Bill: “Empathy baked into communication.”

Communication is the secret sauce. And not just that. Empathy baked into communication. A designer can have all the raw talent in the world but without great communication, they fall short of the bigger picture. Why, you say? Well, part of designing for a client is also selling your work. You do that by telling a story, communicating your thoughts and ideas in a compelling way. Communicating. After a certain phase in your career, no longer can you just wow people with pretty visuals. They need the why. They need solid communication.
What happens when the clients start to lose faith as you explore endlessly to please them. What happens when times get hard. Communication is just about all that will solve this. Throw some empathy in there and you are now making headway. Clients often need to be heard, understood, and comforted. Queue up good communication skills and you have a MUCH better chance at navigating the harder waters.
Communication helps from start to end. Setting expectations, describing your needs, sharing your insights, etc. Get your communication skills down and you are really set up for success! Bill S. Kenney, Co-Founder of Focuslab

Bady: “Endurance is rare.”

I’d say it would be Grit. I think It’s not only about talent, or passion but also being able to stay focus on your end goal in a long shot. If you want to make some changes in the industry that has been around for centuries, it will require a good amount of effort and patient. Passion/enthusiasm is common but endurance/patient is rare. Bady QB, Design Lead at DBS Bank

David: “Listen.”

When you receive a new project, listen to your manager. Ask for requirements, historical information, the definition of done, timelines, etc. When you show your designs, listen to your design team. Ask follow-up questions. Consider every piece of feedback even if you disagree with it. Try their suggestions. Make a few more iterations. When you show your prototypes, listen to your users. They will surprise you by interpreting interfaces in ways you did not expect. Ask why. Ask what they’re thinking. Ask what they expected.
When you hear concerns and clarifications, listen to your engineers. They need to solve problems you most likely didn’t consider. If they have a tough sprint they may need to find ways to simplify your proposal. Cooperation and compromise are key to building strong relationships. David Klein, Lead Product Designer at Salesforce

Scott: “Make sure nothing gets interpreted differently than how I intended.”

Making sure the other people understand your ideas exactly as you do. A lot of times when talking to designers you just assume the other person knows what you’re thinking. Unfortunately, this isn’t always true. The more complex the problems and solutions are, the more ways someone can incorrectly interpret what you’re proposing. This issue is even trickier working for a remote company like InVision. Making sure people understand your ideas requires an extra layer of communication and choosing the right medium to share your work through. I try not to share static mockups or links to prototypes that people can use as there’s always a lack of context to the problem you’re trying to solve or how exactly your solution will work. Instead, I usually create high-fidelity prototypes and do a screen recording of me using it while I explain things overtop. I find this gives me the chance to make sure nothing gets interpreted differently than how I intended. Scott Savarie, Principal Product Designer at InVision

Russell: “Able to take multiple opposing pieces of feedback.”

One of the things I’ve learned as a designer, is that the more experience you have, the more you are able to take multiple opposing pieces of feedback, whether it be constraints, or objectives of the project, and find a way to design a solution that reconciles all of them. For example, a user experience stakeholder might say that this experience should feel snappy and quick, where another technical stakeholder might say that although they’d like that to be possible, they are heavily constrained, and so technical performance will be limited. Initially it sounds like both groups can’t get what they want, but I think a skilled designer embraces the constraints and objectives, and finds a way to make both of those things happen. This is not to say that this will always be possible, and it’s crucial to weigh the importance of those pieces of feedback, to make sure you are making the right tradeoffs, but by embracing an opposable mind, you can often achieve much more than what you initially thought possible. Take those two opposing thoughts and put them against each other. Ask yourself, how might we enable a snappy experience, while we are technically constrained? By opening your mind to what you want to be true, and not focusing on what’s not possible, you can find so much more. One of my favourite books that explains this idea of opposable ideas, and the opposable mind in general, is A Technique For Producing Ideas by James Webb Young. Russell Baylis, Senior Designer at Shopify

Aleš: “Communication is necessary skills if you want to be a professional.”

I’d say it is communication and presentation skills. Straight-up. Besides doing good work you also need to know how to talk about it with confidence. It is important to learn how to explain your ideas, solutions, and decisions. Because only then you can bring other people on board. I always use a simple rule for this: you can do the best work of your life, but if you can’t explain it to your client, colleague or manager, it’s going to be useless and you’re never going to make it into a final product. Communication can be hard and be uncomfortable, especially for introverts (including myself), but it is necessary skills if you want to be a professional. If you master it or get better at least, it can really do wonders for you. Aleš Nešetřil, Creative Director at STRV

Mason: “A unique point of view is crucial-born.”

The most important skill a designer should possess is a strong point of view and look for this in every designer with whom I collaborate. While the technical or mechanical aspects of design can be mimicked, a unique point of view is crucial—born from a solid understanding of design fundamentals, good common sense and years of practice. With a strong perspective, your work with stand out from the crowd and people will take notice.
Some examples of designers who possess this? In Mixpanel’s case, I began consulting with them when they were in their infancy. Eventually, I officially joined the team and after the first year, it was the perfect time to add another designer. I had collaborated with Julien Renvoye on a few freelance projects and we kept in touch quite a bit. Julien has always had a voracious appetite for good design. He’s the kind of designer that puts so much love in every project that it compels me to keep pushing boundaries and improve my skills. What drew me to his work from the start was his unique perspective found in every project. There was always a level of polish that few designers achieve. He was the second designer that Mixpanel hired. Mason Yarnell, Previously Design Lead at Mixpanel

A closing chat with the reader

Aren’t these great? While it is not realistic to live with solely one skill, I hope this gives you different lenses about what important for Product Designers.

Some people tend to focus on the hard-skills and forget about the soft-skills. After talking to a few fellow designers, I couldn’t agree more. The communication and collaboration is often the top pick. If I may add though, I’d say the ability to articulate the design decision is also important because it’s a result of the combination of having an ability to understand of the problem in depth and the communication skill.

Step up your soft skills, be more aware of it.





Nov 24

About self-doubt

Nov 11

Don't confuse design with artifacts

Nov 06

What if you need to find another job tomorrow?

Oct 26

Making sense of your design project by writing

Sep 30

When was the last time you reflect?

Sep 29

Methods are tools

Sep 24

How can I get a bigger project?

Sep 23

Entering product design – Chapter 7: Craft and analysis

Sep 22

Entering product design – Chapter 6: Narrow collaborator

Sep 21

Entering product design – Chapter 5: Soloist product designers

Sep 17

Entering product design – Chapter 4: Product designer key skill areas

Sep 14

Entering product design – Chapter 3: Misunderstanding of business

Sep 11

Entering product design – Chapter 2: Principles over steps

Sep 10

Entering product design – Chapter 1: Silver bullet

Sep 10

Entering product design – Overview

Sep 04

SAR: A framework for concise storytelling

Aug 27

Start your design with outcome

Aug 24

New medium post: Collaboration ground for design systems

Aug 17

Action points

Aug 13

Pulse check: Listen to your team

Aug 11

You should actively apply for a new job

Aug 10

Design systems' area of influence: Service (3/3)

Aug 04

Design systems' area of influence: Offering (2/3)

Aug 03

Design systems' area of influence: Identity (1/3)

Aug 01

My mom ran me to the hospital

Jul 29

Reader question: Do we need to build MVP for every product?

Jul 27

Reader question: Do I need formal design education?

Jul 24

Recognize assumptions

Jul 21

Sandbox for your personal growth

Jul 20

Start your week with questions

Jul 17

Specificity in feedback

Jul 15

Don't sell the design. Sell the business impact

Jul 14

Overwhelming inspiration

Jul 13

The framing trap

Jul 10

Everyone vs. Specific

Jul 09

The blind horse designer

Jul 08

Set the context in your meeting

Jul 07

Let's just try and see what happens

Jul 06

Managing expectation

Jul 05

Low UX maturity company

Jun 17

A simple exercise for career reflection

May 31

The “Coach sheet” – A paper-based system for people management

May 26

Bring calm to your remote team

Feb 13

Workshops can be more efficient than meetings

Feb 07

3 questions designers should be asking

Feb 06

Walking 1on1: A refreshing way to connect


Nov 21

My hope for stubborn 'Innovators'

Jul 18

Five simple actions to help you gain more time

Apr 23

Evolving Product Experience Principles at Bukalapak

Mar 09

A framework to give better design feedback: Analyze, Discuss, Suggest

Jan 28

Making a decision is hard, here's my rule of thumb


Dec 04

Essential skills for Product Designers

Nov 16

Quick life update

Nov 06

Things I learned from working at Shopify

Oct 15

About design critique

Sep 17

Common icon design problems you should avoid

Sep 06

Preface: Welcome to