Sep 17, 2020 | by Budi Tanrim

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

Update: My view on this topic has changed. Take this with a grain of salt. I felt this model is not intuitive enough and a bit too narrow.

Have you ever wonder what area to improve as a product designer?

I want to introduce the key skill areas of what makes a product designer. I will refer to throughout the series. Using this model, we’ll explore how a product designer can improve. It consists of five areas: Creative mindset, framework thinking, craftsmanship, collaboration, communication.

I’d argue that the strong product designer must 1) have a creative mindset to guide their actions and attitudes, 2) expanding framework thinking to structurize thinking and connect the dots, 3) have a strong craftmanship to produce artifacts, 4) able to collaborate so your team can move as a unit, and 5) be an excellent communicator to articulate your decision or thinking.

Key skill areas for product designers


You can refer to this model to plan on which area you’re interested in improving, which I will unpack and dive deeper into each skill area.

The stronger the product designer in these five areas, the bigger the influence area would be and, eventually, to solve more complex problems than before.


Creative mindset

The first area will be the creative mindset – that is, a perspective a product designer has toward a specific condition and respond it with the proper attitude.

For example: whether the product designer can adapt in the environment, comfortable navigating through ambiguity, the eagerness to learn from the mistakes, or how persistence she will be in the situation.

A creative mindset is what sets a senior product designer apart from a junior product designer. When a product designer has this creative mindset, she will be able to have the proper attitude, which will help her grow other skill areas continuously.

There are many mindsets we will uncover as we go in this series. In the first chapter, we touched that a strong product designer doesn’t think linearly in the sense of steps to give you an example.

Framework thinking

After you work as a product designer, you will realize how messy the process to build and iterate a product or an experience for a customer.

That’s why framework thinking is essential – that is the ability to analyze and synthesize the information, assess your own thinking, and connect them together with your team.

The more framework you’re exposed, the more abstract or complex problem you can.

The strong designer will not only understand the framework but able to apply it practically with the right tools or techniques. On top of that, I always observe the strong product designer is not only exposing themself to the design-specific frameworks but also absorbing frameworks from the other discipline, such as product, tech, or business.

The more lenses you have, the more you can see.

When you observe yourself struggle to have an abstract discussion, it is one indication that you want to consider to improve this area.

Collaboration

Collaboration is the ability to move with the team toward the desired outcome as a unit. The collaborative product designer can take a wide multidisciplinary perspective to bring alignment to the team so that they can move faster.

The inexperienced product designer will work alone or have a lot of walls throughout their process. They are resulting a slower pace of working and higher misalignment of the work from the objectives. In contrast, a strong product designer will break those walls. They co-create with various stakeholders or even users intensely to move as a unit toward the desired outcome.

Collaboration can benefit the organization to have more successful innovations or to increase the chances of customers to be more satisfied (Steen, Manschot, & De Koning, 2011).

Craftsmanship

Craftsmanship is an essential area for all product designers – that is, the ability to translate abstract ideas into a tangible output – known as artifacts.

It includes interaction and visual design, prototyping to communicate or validate ideas, or research skill.

A strong crafter would be able to iterate their work quickly to help the team translate their product ideas into a tangible working product or an experience used by the end-user. Most people think that craftsmanship is what design is all about.

Also, a strong crafter doesn’t fall in love with their artifacts. They understand that every work is a prototype that can continuously be improved.

Communication

Last but not least. The communication – which is the ability to articulate your thought or thinking, so the other person you’re working with can get your point.

We’ll unpack a lot of techniques like storytelling or expressing your disagreement. The communication will greatly influence your presence as a product designer within the team.

That’s the overview of the model that we’ll explore throughout this series. Stay tuned for the next chapter!

Continue reading
Newer post: Entering product design – Chapter 5: Soloist product designers
Older post: Entering product design – Chapter 3: Misunderstanding of business
ask me question illustration
Book a 50 minutes chat

Get career advice or portfolio review. You can book a group session too. More details →

ask me question illustration
Ask a question

Send your question about the most recent post. If I can, I'll answer it on the blog. (This will open your email client)

ask me question illustration

Subscribe to newsletter

Get the post right into your inbox every time a new post is published or get a weekly email, you choose.

2021

May 05 Confusing popularity and value
May 04 Objective, strategy, and tactic
May 03 Self-learning
May 01 Small actions for self-improvement
Apr 30 Slow thinker
Apr 28 Mindset in the new job
Apr 27 One-on-one guide for individual contributors
Apr 26 Team player
Apr 23 'It looks good to me'
Apr 21 Why do you work?
Apr 20 The Steve Jobs' Error
Apr 19 Design is like riding a bike
Apr 16 See your life as an experiment
Apr 14 Lead with respect
Apr 13 Lead with trust
Apr 12 My reflection on leadership
Apr 07 Five years from now
Apr 06 Design Thinking allergy
Apr 05 What should design managers do with OKR?
Apr 04 When was the last time you talked to users?
Apr 03 Three core questions for product team
Apr 01 Inspecting interface design — Exercise with heuristic
Mar 30 Inspecting interface design — HE vs. UT
Mar 29 Inspecting interface design — Overview
Mar 27 Modern product design principles for Millenials designers.
Mar 25 A confusing interface that creates fire.
Mar 23 If F1 drivers get a trophy, what's our trophy?
Mar 22 Getting it right for the first time
Mar 19 Use Peltzman effect to communicate risk
Mar 17 Be the best version of yourself
Mar 16 If you coach a designer, do you need to know all the answers?
Mar 13 Show up and practice
Mar 11 Reader question: How to deal with promotion rejection?
Mar 10 Reader question: How to measure success?
Mar 09 Product design leadership - Managing and leading
Mar 07 How to draw an owl
Mar 05 Product design leadership — Persevere
Mar 04 Product design leadership — Establish urgency
Mar 02 Product design leadership — Strategic focus
Mar 01 Product design leadership — Setting direction
Feb 26 On GUI history, learning, and writing.
Feb 25 Product design leadership — Create changes
Feb 24 Product Design Leadership series
Feb 22 Documenting is a good team’s habit
Feb 18 Have a hard time getting design feedback?
Feb 18 I'm writing a book.
Feb 16 A manager cried in front of me.
Feb 15 Should I move to the managerial role?
Feb 12 Friday diary 01: On personal development, being senior, and breaking small task.
Feb 11 Evangelizing the human-centered practice
Feb 09 Human-centered team vs. Feature-centered team – Strategic insight
Feb 08 Human-centered team vs. Feature-centered team – Strategic relationship
Feb 08 Human-centered team vs. Feature-centered team – Overview
Feb 05 Dealing with top down request
Feb 03 Every team has its unique challenges.
Feb 02 Business aware designer – Recognize your competitors
Jan 29 Business aware designer – Job to be done
Jan 27 Business aware designer – Value proposition
Jan 26 Business-aware designer - overview
Jan 25 What do product designers do?
Jan 22 Announcement for mentorship program
Jan 21 Community story: impostor syndrome
Jan 20 Should startups build a design system?
Jan 18 How I overcame my impostor syndrome
Jan 17 User metrics - Signals and Metrics
Jan 15 User metrics - Vision
Jan 14 User metrics - Overview
Jan 13 Give back to the community
Jan 12 4P: framework for choosing job
Jan 11 Take things with a grain of salt
Jan 09 Principles of good portfolio design
Jan 07 An effective product design portfolio – Constraint
Jan 06 An effective product design portfolio – Structure
Jan 05 Connect user and business with AARRR framework
Jan 05 My blog in 2021
Jan 03 Should I build the feature request from customers?

2020

Dec 30 Feature requests are stupid business activity
Dec 21 The benefit of creating a design portfolio
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

2019

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

2018

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 yellowstroke.com