Contact us

🌍 All

About us

Digitalization

News

Startups

Development

Design

Product Designer’s role in the Product Life-Cycle

Damian Denis

May 06, 20204 min read

DesignUX designProduct design

Table of Content

  • What is a product?

  • So what's going on with that Product Design?

  • UX/UI vs Product Designer

  • Okay, but what is the role of the Product Designer?

  • Can anyone become a Product Designer?

What is a product?

“Anything that can be offered to a market for attention, acquisition, use or consumption that might satisfy a want or need. It includes physical objects, services, persons, places, organizations and ideas.”

– Kotler, Wong, Saunders, Armstrong

So what's going on with that Product Design?

Nowadays, we have a bunch of interesting new titles for various positions. We love to use these exquisite names — they sound strange and sometimes we don't know exactly what they mean (but they sure do look cool on our LinkedIn profiles).

Looking at it historically, just a few years ago we did not have a UX/UI differentiation. Everyone would be responsible for everything. It was just Design. You were a Designer and everything it entails was expected from you: user experience, mobile, desktop, all the way through. There weren’t as many categories and subcategories as there are now. The name Product Designer was mostly related to people who design everyday objects — from glassware, jewellery, furniture, telephones to cars and other machines.

However, for some time now, the term Product Designer has started to break into the online world, when our products of everyday use have started becoming digital. At that point, the role of designers began to evolve quite dynamically. As the number of systems, platforms and complex solutions grew, so did the possibilities for design. And with these opportunities, the number of responsibilities and processes influenced by designers has also increased.

UX/UI vs Product Designer

There’s one important record that needs to be set straight. A UX/UI Designer is not the same role as a Product Designer. Their responsibilities often vary greatly. Of course, there are as many theories on this subject as there are people, but there is one that is closest to my beliefs and in quite a simple way allows to distinguish between the two positions:

A UX/UI Designer is more focused on such aspects as research, testing, prototyping and designing.

The Product Designer, on the other hand, looks at the product more holistically. They have to take into account and focus on business aspects, which isn’t necessarily in a UX/UI Designer scope of work.

Okay, but what is the role of the Product Designer?

Recently, I was talking to a good friend of mine, Mathew Piatek (an ex-Product Designer @Contractbook), about this very topic. I took the liberty of asking him what he thinks is the role of the Product Designer in a product’s life-cycle? The fact that he had worked on developing a digital product provides him with a good insight into this subject.

Since our observations and thoughts were almost perfectly aligned, I have summed them up in a list of not so obvious key aspects.

A Product Designer can be the link between technological knowledge and solutions — they can be the first initiator of product activities and roadmap generation.

Their presence can be very helpful in unobvious processes, which normally we might think are independent of the design, such as the sales process. Creating a sales or recruitment process is also something that can be very nicely planned by the designer — as a process, not an interface.

Thanks to their experience, Product Designers know exactly how long it can take to implement a specific solution, both on the design and development side (at least in general). They are able to take on a decision-making role in the product, in terms of balancing the weight between small features and large ones, which. If properly included in the roadmap, they will allow for continuous progress of the project, without making huge breaks between making significant changes.

They can take on the role of a facilitator of meetings and processes. Because of their problem-solving skills, they are able to reconcile different perspectives.

A Product Designer can also impersonate a Support person — mitigate the effects of the unnecessary ‘telephone’ game by having direct contact with the product’s users. This will allow them to collect raw feedback from various sources, which is in no way filtered and disturbed. (Unfortunately, the Support often transforms such feedback, which gives unmeasurable results). Paul Van Oijen, a Senior Product Designer at Shopify at the Remote Design Week conference, had a very interesting speech about this particular problem.

They are able to conduct simple A/B tests, interviews with users and draw conclusions for further product development from the collected data.

We can say that nowadays the Product Designer is a core component of every development team, providing support, which can take different forms when needed, while keeping the product’s vision in mind. They can find themselves in any situation.

The role of a Product Designer is also different when working on developing a single product versus working in a software house. Each of these roles has its pros and cons. It all depends on how the Product/Software house operates, what processes are being used. But this is a topic for another next article. Stay tuned!

Can anyone become a Product Designer?

As a Designer would answer, it depends. We know that people are visual creatures. But if you only think about this aspect, the business side of things doesn't hold much of your interest, you just want to make beautiful things, then definitely not. On the other hand, if you're interested in every aspect of product development, you like talking to people, doing research, testing, checking, you’re patient and innately curious, the answer is definitely yes.

Being a Product Designer is a mix of skills that are used on many different levels, depending on your needs. This visual aspect is actually the cherry on the cake which, tastes great when you have influenced other pieces of the construction.

Do you have any Product Design-related questions? Drop us a line: . You can also check out our Dribbble account.


Recommended readings:

13 Roles of a Product Designer — UX Collective

The job of the ‘Product Designer’ and its importance in a startup — UX Collective

Product Designer’s role in the Product Life-Cycle

 
Product Designer’s role in the Product Life-Cycle

Published on May 06, 2020

Share


Damian Denis Head of Design

Don't miss a beat - subscribe to our newsletter
I agree to receive marketing communication from Startup House. Click for the details

You may also like...

Understanding Declarative Programming in UI Design: The Pros and Cons Explained
DesignProduct design

Understanding Declarative Programming in UI Design: The Pros and Cons Explained

Declarative programming simplifies UI design by focusing on what the interface should accomplish rather than how to implement it. This approach improves code readability, maintainability, and developer productivity. However, it also has drawbacks, including limited flexibility and potential performance concerns. This guide explores the pros and cons of declarative programming to help developers make informed choices in their UI design projects.

Marek Pałys

Mar 04, 20245 min read

Declarative UI Design: What It Is and Why It Matters for Modern Developers
Product designDigital products

Declarative UI Design: What It Is and Why It Matters for Modern Developers

Declarative UI design allows developers to focus on what the user interface should look like rather than how to build it. This method simplifies code, enhances readability, and improves maintainability, making it a popular choice among modern developers. Learn how declarative UI design can transform your approach to building dynamic and scalable applications.

Marek Pałys

Jul 09, 20249 min read

A Beginner's Guide to Creating Low-Fidelity Prototypes: Essential Tools and Techniques
Product design

A Beginner's Guide to Creating Low-Fidelity Prototypes: Essential Tools and Techniques

Low-fidelity prototypes are basic models used to explore design ideas and test functionality quickly. In this guide, we explore the tools and techniques necessary for building low-fidelity prototypes, helping you streamline your design process by identifying issues early and encouraging collaboration. Whether you're new to design or looking to refine your skills, this guide offers practical strategies to enhance your prototyping.

Alexander Stasiak

Jan 31, 202413 min read

Let's talk
let's talk

Let's build

something together

Startup Development House sp. z o.o.

Aleje Jerozolimskie 81

Warsaw, 02-001

VAT-ID: PL5213739631

KRS: 0000624654

REGON: 364787848

Contact us

Follow us

logologologologo

Copyright © 2024 Startup Development House sp. z o.o.

EU ProjectsPrivacy policy