The Art of Good Design: Elements and Principles for Creating Beautiful and Functional Products

Design is all around us, from the clothes we wear to the products we use in our daily lives. But have you ever stopped to consider what makes a design successful? The art of good design involves much more than simply making something aesthetically pleasing; it also requires consideration of functionality, usability, and the user experience. In this article, we’ll explore the key elements and principles of good design and how they can be applied in the product design process. Whether you’re a designer or simply someone interested in the world of design, understanding these concepts can help you appreciate and create beautiful, functional products.

Each of us interacts with products in our everyday lives in a variety of ways. From preparing our morning coffee to setting up the alarm before going to sleep at night. These products have become part of our lives and help us go through our day in a much more efficient and pleasant way. 

 

Countless are the products out there hoping to be the ones selected to help us accomplish these tasks, but with a limited number of tasks that a human performs in a day, the competition is quite high. 

 

So, what makes us choose one product over the other? Below I’ll share with you the product design process that is proven to help business to create successful products. 

What is Product Design?

Product design refers to the process of creating a new product or service, taking into account the user’s needs, the business objectives and the technical constraints. The product design process usually includes researching, ideating, prototyping and testing. The goal of product design is to create a product that meets the user’s needs and solves their problems, while also being profitable and feasible to produce.

Designed by G2

What is a Design Process?

The Design Process is a series of steps that product teams follow during the formulation of a product from start to finish. The process varies depending on the type of design, but typically involves several key steps:


 1. Define the product vision. Defining a product vision and strategy involves understanding the problem that you are trying to solve, the needs of your target audience, your unique value proposition, and your long-term goals for the product. 

 
2. Research: Conduct market research, user research, and competitor analysis to understand the problem you are trying to solve and the needs of your target audience.

3. Define: Defining the design problem and creating design briefs, user personas, and user stories that represent the target audience.

4. Ideate: Generating ideas and creating concepts for the product, such as sketches, wireframes, and mockups.

5. Prototype: Creating a physical or digital representation of the product to test and validate design concepts.

6. Test and validate: Conducting user testing and gathering feedback to validate the design and make improvements.

7. Implement: Developing the final product and launching it to the market.

8. Monitor and maintain: Continuously monitoring the product and gather feedback to make improvements and resolve any issues that arise.

When starting the process it is important to be able to answer:

  • What problem are we solving?
  • Who has this problem?
  • What do we want to achieve?

Answering these questions allows designers to understand the user experience of a product as a whole and not simply the interaction (feel) or visual (look) part of a design. 

 

Finding an innovative solution requires following a design process that varies depending on the type of design.

Image credit: Unichrone

Design Thinking Approach in Product Design

If you want your product that meets the needs of users, is easy to use, and provide value to the customer, it is important to keep your user in mind in each part of the design process. For this reason, one of the most popular approaches to Product Design is Design Thinking. 

 

Design thinking is a problem-solving approach that emphasizes empathy for the user, a deep understanding of the problem, and rapid prototyping to test and iterate on ideas. It is a human-centered approach to innovation that can be applied to a wide range of problems, from creating new products and services to improving existing ones.

 

The design thinking process typically consists of five phases:

  1. Empathise: This phase is about understanding the user and the problem. It involves conducting research to gather information about the user’s needs, goals, and behaviors.
  2. Define: This phase is about defining the problem and identifying the key insights from the research. It involves synthetizing the information and identifying key themes and patterns.
  3. Ideate: This phase is about generating a wide range of ideas for possible solutions to the problem. It involves brainstorming, sketching, and creating low-fidelity prototypes.
  4. Prototype: This phase is about creating a tangible representation of the ideas generated in the previous phase. It involves creating a mockup, a simulation or a model of the solution, and testing it with users.
  5. Test: This phase is about evaluating the prototype with users and gathering feedback. It involves testing the solution with a small group of users, analysing the results and iterating on the design.

The end goal of a Design Process is create solutions that are desirable, feasible, and viable, and that effectively solve the problem at hand.

Empathise

Empathising with users is an important step in the design thinking process, as it allows us as designers and developers to understand the user’s needs, wants, and pain points.The best way to achieve this by conducting user research.

Image credit: Interaction Design Org

User Research

User research is the process of studying and understanding the needs, behaviours, and attitudes of users in order to inform the design and development of products and services. This can include conducting surveys, interviews, usability tests, and other forms of qualitative and quantitative research in order to gather data about how users interact with and experience a product or service. The goal of user research is to make sure that the final product or service meets the needs and expectations of its intended users.

How to conduct user research?

User Interviews

User interviews are a qualitative research method used to gather information about users and their needs, behaviours, and attitudes. They are typically conducted one-on-one, in-person or remotely, and involve asking open-ended questions to a representative sample of users.

During a user interview, a researcher or designer will typically ask questions related to:

  • The user’s background and demographics
  • The user’s experiences and behaviours related to the product or service
  • The user’s needs, goals, and pain points
  • The user’s attitudes and perceptions about the product or service
  • The user’s feedback and suggestions for improvement

User interviews can be conducted early in the design process to inform the development of personas and user stories, or later in the process to validate design concepts and gather feedback on a prototype or MVP.

User interviews can be conducted in different ways, such as:

  • In-person interviews: conducted face-to-face with the participants
  • Remote interviews: conducted remotely, through video conferencing or phone
  • Self-administered interviews: conducted through online surveys or questionnaires

The goal of user interviews is to gain a deeper understanding of the users and their needs and behaviours. This information can then be used to inform the design of a product or service, and to validate design decisions throughout the development process.

Online Surveys

Online surveys are a type of research method used to gather information from a large number of users. They are typically conducted through an online platform, such as a website or mobile app, and involve asking a set of pre-determined questions to a representative sample of users.

Online surveys can be used to gather a wide range of information, such as:

  • Demographic information about the users
  • User attitudes and perceptions about a product or service
  • User needs and pain points
  • User satisfaction and engagement with a product or service
  • User feedback and suggestions for improvement

Online surveys can be used at different stages of the design process, from early-stage research to validate design concepts and gather feedback on a prototype or MVP.

There are different types of online surveys, such as:

  • Closed-ended surveys: which ask questions that have pre-determined answer options.
  • Open-ended surveys: which ask questions that allow users to provide written responses.
  • Likert scale surveys: which ask questions that measure user agreement or disagreement on a scale.

Online surveys can be a cost-effective and efficient way to gather data from a large number of users. However, they do have some limitations, such as the possibility of biased responses or low response rates. It’s important to make sure that the sample is representative of the target population and that the questions are well-designed to minimise bias.

Contextual Enquiries

Contextual inquiry is a user research method that combines direct observation of users in their natural environment with semi-structured interviews. The goal of contextual inquiry is to understand the user’s work or home environment, their tasks, and their goals in order to create a product or service that is better suited to their needs.

Contextual inquiry typically involves the following steps:

  1. Planning: Identifying the users and tasks to be studied, and planning the logistics of the study.
  2. Fieldwork: Conducting direct observation of users in their natural work or home environment, typically accompanied by semi-structured interviews.
  3. Data analysis: Analyzing the data collected during the fieldwork and identifying patterns and insights.
  4. Report: Creating a report of the findings that includes recommendations for design and development.

Contextual inquiry is particularly useful for understanding the context of use and can provide valuable insights into the users’ workflow, pain points, and opportunities for improvement. It’s particularly useful for understanding the day-to-day work of users and how the product or service fits into their work or home environment.

It’s important to keep in mind that contextual inquiry is a qualitative research method, meaning that it provides rich and detailed information but might not generalize to the whole population. It’s also important to have a clear methodology and plan and to have the right resources to conduct the research.

Market research

Conducting market research involves gathering and analysing data about a specific market, industry, or target audience.

Competitive research

Competitive research, also known as competitive analysis, is the process of gathering and analysing information about competitors in order to understand their strengths, weaknesses, and opportunities. The goal of competitive research is to gain a competitive advantage by identifying areas where the company can improve its products, services, or strategies.

A competitor is a company that shares your goals and that fights for the same thing that your product team wants. There are two types of competitors:

Image credit: venngage.com

Direct competitors: Direct competitors are companies that offer similar products or services to the same target market as your company. They are businesses that are in direct competition with yours for the same customers, revenue, and market share.

For example, if your company sells athletic shoes, your direct competitors would be other companies that also sell athletic shoes, such as Nike, Adidas, and Puma.

Indirect competitors:

On the other hand, indirect competitors are companies that offer products or services that can be used as an alternative to your company’s offerings. They may target a similar market, but the products or services they offer are not identical to yours.

 

For example, if your company sells athletic shoes, your indirect competitors would be companies that sell other types of footwear such as, sandals, casual shoes, boots, and so on.

Understanding the difference between direct and indirect competitors is important because it can help you identify the areas where you need to differentiate your product or service to stand out in the market.

It can also help you understand which competitors are more of a threat to your business, and where you can find opportunities to innovate and grow your business.

Define

The Define phase in design thinking is the second step in the design thinking process, following the Empathise phase. The goal of the Define phase is to synthesise the information gathered in the Empathise phase and to define the problem or opportunity that the design thinking process will address. This phase typically includes the following steps:

Image credit: Uptech

  1. Synthesise the research findings: Review the research findings and organise the information in a way that makes it easy to understand and communicate.
  2. Define the problem or opportunity: Identify the problem or opportunity that the design thinking process will address, based on the research findings and insights.
  3. Develop a point of view: Develop a point of view that clearly communicates the problem or opportunity and the user’s needs.
  4. Create a problem statement: Create a problem statement that clearly defines the problem or opportunity and the user’s needs in one or two sentences.
  5. Create a design brief: Create a design brief, which is a document that summarises the problem or opportunity and the user’s needs, and provides guidance for the next steps of the design thinking process.

It’s important to keep in mind that the Define phase is crucial as it helps to ensure that the design thinking process is focused on solving the right problem or opportunity and that it aligns with the user’s needs. It’s also important to involve a diverse group of stakeholders and users in the Define phase, to ensure that the problem or opportunity is clearly defined and that it aligns with the project’s goals and the user’s needs.

User Research Analysis

Analysing data from user research involves interpreting the information gathered during the research in order to identify patterns and insights. Here are some steps that you can take to analyse data from user research:

  1. Review the data: Review the data collected during the research, such as surveys, interview transcripts, and notes from observations.
  2. Organise the data: Organise the data into categories and themes, such as demographics, behaviours, and attitudes.
  3. Identify patterns and insights: Look for patterns and insights in the data, such as common themes, trends, or areas of concern.
  4. Create user personas: Create user personas that represent the different types of users and their needs.
  5. Create a report: Create a report of the findings that includes recommendations for next steps.
  6. Validate the findings: Validate the findings with other research methods and with the team, stakeholders and users to ensure the accuracy of the insights.

Data analysis can be conducted using different techniques such as:

  • Qualitative data analysis: which involves analysing and interpreting non-numerical data, such as interview transcripts, observations, and open-ended survey responses.
  • Quantitative data analysis: which involves analysing and interpreting numerical data, such as survey responses and user behaviour data.

Ideation

Image credit: Mural

The Ideation phase in the design thinking process is the stage where ideas and concepts are generated to solve the problem defined in the previous stage, the Empathise stage. In this phase, the goal is to generate a wide variety of ideas and concepts, without worrying about their feasibility or practicality. The idea is to generate as many ideas as possible, to later evaluate and select the best ones.

This phase typically involves the following steps:

1. Brainstorming

Conducting brainstorming sessions with a diverse group of people, such as team members, stakeholders, and experts, to generate a wide variety of ideas.

2. Sketching and prototyping

Creating rough sketches and mockups of the ideas generated during brainstorming.

3. Idea generation tools

Using different ideation tools such as, SCAMPER, Mind mapping, Crazy 8’s, and so on, to generate new ideas. 

4. Feature Prioritisation

Prioritising ideas is the process of evaluating and selecting the most promising ideas generated during the ideation phase.

Feature prioritisation is the process of evaluating and organising the features of a product or service based on their importance and priority.

The goal of feature prioritisation is to ensure that the most important and valuable features are developed and delivered first, while less important or lower-priority features are deferred or eliminated.It’s important to involve the team, stakeholders, and users in the prioritisation process, to ensure that the ideas selected align with the project’s goals and the user’s needs.

5. User stories

Prioritising features based on their alignment with user stories and user needs.

A user story is a simple, concise description of a user’s experience or goal, written in natural language. It is used in Agile development methodologies, such as Scrum, to capture the requirements of a product or service from the perspective of the user.

A user story typically follows this format:

“As a [user], I want [goal] so that [reason].”

For example: “As a frequent traveler, I want to be able to book my flights and hotels on the same website so that I can plan my trip more easily.”

User stories are used to capture the requirements of a product or service from the perspective of the user. They are typically written by product owners or business analysts, but can also be written by users themselves or other stakeholders.

User stories are useful for several reasons:

  • They are easy to understand and communicate, which helps to ensure that everyone on the team is on the same page about the requirements of the product or service.
  • They help to focus on the user’s needs and goals, rather than on specific features or technical solutions.
  • They are flexible, and can be easily updated as the project progresses, or as user needs or business priorities change.

It’s important to keep in mind that user stories are not detailed specifications, they are high-level descriptions of what the user wants to accomplish, and it’s important to break down the user stories into smaller chunks of tasks (epics, features, and user tasks) before starting the development process.

Structure of the product

Planning the structure of a product involves organising the features, functionality, and content of a product or service in a way that is logical, intuitive, and easy to use.

Here are some steps that you can take to plan the structure of a product:

 

  1. Understand the user’s needs: Conduct user research to understand the needs, goals, and pain points of the target audience.
  2. Define the product’s objectives: Define the product’s objectives and goals, such as increasing sales, improving user engagement, or solving a specific problem.
  3. Identify the key features: Identify the key features and functionality that are necessary to achieve the product’s objectives.
  4. Create a feature map: Create a visual map of the features and functionality of the product, including the relationships between different features and the user’s journey through the product.
  5. Organise the features: Organise the features and functionality in a logical and intuitive way, based on the user’s needs and the product’s objectives.
  6. Define the information architecture: Define the information architecture of the product, including the organisation, labeling, and navigation of the content.
  7. Create wireframes and prototypes: Create wireframes and prototypes of the product’s structure to test and validate the design.

Information architecture

Site map designed by Amy Shepheard for a online grocery delivery product in development

Information architecture (IA) is the practice of organising, structuring, and labelling content in a way that makes it easy to find and understand. It is the structural design of shared information environments. The goal of information architecture is to help users find the information they need quickly and easily, by creating a clear and intuitive structure for the content.

Information architecture typically involves the following steps:

  1. Define the content: Define the types of content that will be included in the product or service, such as text, images, videos, and audio.
  2. Organise the content: Organise the content into categories and subcategories, based on the user’s needs and the product’s objectives.
  3. Label the content: Label the content in a clear and consistent way, using terms and phrases that are familiar to the user.
  4. Create a navigation system: Create a navigation system that allows users to easily find and access the content, such as a menu or a search bar.
  5. Create a sitemap: Create a visual map of the structure of the content, including the relationships between different pages and sections.
  6. Test and Iterate: Test the information architecture with users, gather feedback and iterate to improve the design.

Information architecture is a critical aspect of user experience design and it is important to take into account the user’s perspective when creating the IA of a product or service. It is also important to keep in mind that IA is an ongoing process, and it should be reviewed and updated regularly as the product or service evolves.

Prototype

Prototyping is the process of creating a preliminary version of a product or service, used to test and validate the design before it is fully developed.

The goal of prototyping is to gather feedback and make improvements to the design before it is finalised.

There are different types of prototypes depending on the level of detail and functionality they provide, such as:

Credit: Moqups

  1. Low-fidelity prototypes: These are rough and simple representations of the product or service, such as sketches or wireframes, which are used to test the overall layout and structure of the design.
  2. Medium-fidelity prototypes: These are more detailed and interactive versions of the product or service, such as wireframes with clickable buttons or simple interactions, used to test the functionality and usability of the design.
  3. High-fidelity prototypes: These are highly detailed and functional versions of the product or service, such as interactive mockups or working models, used to test the design and user experience in a realistic environment.

Prototyping is an iterative process, it allows designers and developers to test and validate the design with users and stakeholders, gather feedback and make improvements to the design before it is finalised. It also allows to test and validate assumptions, and to identify and solve potential issues early in the development process.

 

It’s important to keep in mind that the level of detail and functionality of the prototype should be appropriate for the stage of the design process and the goals of the testing. Also, it’s important to involve a diverse group of stakeholders and users in the testing and validation process to gather feedback and ensure that the design aligns with the product’s objectives and the user’s needs.

Design Handoff

Designed by Gal Shir

A design handoff is the process of transferring the design of a product or service from the design team to the development team. It typically involves the sharing of detailed design specifications, such as wireframes, mockups, and style guides, as well as any necessary annotations, notes or instructions that explain the design decisions and the design rationale behind them.

The goal of the design handoff is to ensure that the development team has all the information they need to accurately and efficiently build the product or service according to the design.

A design handoff typically includes the following elements:

  1. Design specifications: Detailed information about the layout, typography, color, and other design elements of the product or service.
  2. Interaction design: Information about the user flow, interactions, and animations of the product or service.
  3. Style guide: Guidelines for the use of typography, color, and other design elements, including code snippets for developers to use.
  4. Design assets: All necessary design assets, such as icons, images, and other visual elements.
  5. Annotation and comments: Explanations of the design decisions and the design rationale behind them, as well as any necessary notes or instructions.
  6. User research and usability testing results: Any user research and usability testing results that were used to inform the design decisions.

5. Testing

Designed by Komodo

Testing in product design is the process of evaluating the product or service in order to identify any issues, validate assumptions, and gather feedback to inform future design decisions. There are different types of testing in product design, such as:

 

  1. User testing: Involves observing and interacting with real users as they use the product or service, in order to gather feedback on the usability and user experience.
  2. Usability testing: Involves evaluating the ease of use and the effectiveness of the product or service in achieving its intended goals.
  3. Accessibility testing: Involves evaluating the product or service to ensure that it can be used by people with disabilities.
  4. Performance testing: Involves evaluating the product or service to ensure that it performs well under different conditions, such as different devices, screen sizes, and network speeds.
  5. A/B testing: Involves testing two or more variations of the product or service to determine which one performs better in terms of user engagement, conversion rates, and other metrics.
  6. Beta testing: Involves testing the product or service with a group of real users before it is released to the general public.

 

It’s important to keep in mind that testing is an ongoing process, and it should be conducted regularly throughout the design and development process. It’s also important to involve a diverse group of stakeholders and users in the testing process, to ensure that the product or service aligns with the project’s goals and the user’s needs.

Why it's important to do testing?

The design process is a series of steps that product teams follow during the formulation of a product from start to finish. The process varies depending on the type of design, but typically involves several key steps:


  1. Identify and solve issues: Testing allows designers and developers to identify and solve potential issues with the product or service before it is released to the public. This can include issues with usability, accessibility, performance, and security.
  2. Validate assumptions: Testing allows designers and developers to validate their assumptions about the product or service, such as user needs and behavior, and make adjustments as needed.
  3. Gather feedback: Testing allows designers and developers to gather feedback from real users, which can help to inform future design decisions and improve the overall user experience.
  4. Improve the user experience: Testing allows designers and developers to identify and solve usability issues, and improve the overall user experience.
  5. Improve the product’s quality: Testing helps to ensure that the product or service performs well under different conditions, and that it meets the needs and expectations of the users.
  6. Meet compliance and standards: Testing can help to ensure that the product or service meets relevant compliance and standards such as accessibility standards, and security standards
  7. Save time and money: Identifying and solving issues early in the development process can save time and money, as it is much more expensive to fix issues after the product or service has been released.
  8. Improve the product’s marketability: Testing allows to validate the product’s value proposition and to improve the product’s marketability before it is released.

How to evaluate product performance?

Designed by Search Engine Journal

Evaluating product performance after launching involves measuring and analysing the performance of the product or service, in order to identify any issues or areas for improvement. Here are some steps that you can take to evaluate product performance:

  1. Define performance metrics: Define the metrics that you will use to measure the performance of the product or service, such as user engagement, conversion rates, and any other relevant metrics.
  2. Collect data: Collect data on the performance of the product or service, such as through analytics tools or surveys.
  3. Analyse the data: Analyse the data to identify any trends or patterns, and to understand the overall performance of the product or service.
  4. Compare to benchmarks: Compare the performance of the product or service to industry benchmarks or similar products, to understand how it performs relative to others.
  5. Identify areas for improvement: Identify any areas for improvement, such as usability issues, performance problems, or areas where the product or service is not meeting the user’s needs.
  6. Prioritise issues: Prioritise the identified issues based on their impact and the effort required to solve them.
  7. Address issues: Address the identified issues through updates, patches, or other solutions.
  8. Test and validate: Test the changes and validate that they improve the product’s performance.
  9. Keep an eye on the competition: Keep an eye on your competitors, and be aware of any new features or services they may be launching.
  10. Share with stakeholders: Communicate the performance results with the stakeholders, and share the roadmap for future enhancements.

More to explore

Giftano-for-business-cover

UX|UI Design

I bring products from idea to development using a User Center Design approach.
See my work
Cover-Search Page

UX Audits

I help businesses improve their products usability and performance with a UX Audit.
How it works
Wordpress-dev

Website Development

I build websites using WordPress/Webflow for small businesses and bloggers.
How I help

© 2022 Andrea Viflor

Linkedin-in Behance Instagram

Andrea Viflor | User Experience Designer