Table of contents
- What Is Product Design?
- Product Design Strategy
- UX Research
- Ideation & Design
- Prototyping & Testing
- Deployment - the end of the Product Design Process?
Product Design definition
Let’s start from the very beginning by explaining what Product Design actually is. That’s the comprehensive approach of creating a product based on both - the target clients’ needs and business goals. The idea of placing the user in the center of the design process reaches the ‘80s so it’s still quite fresh but not exactly new. From that time thousands of companies decided to implement this approach into their business strategy and a lot of new theories, techniques and frameworks appeared around it. The IT industry, as a typical early adopter seeking for innovations and open for new solutions, introduced Product Design quickly and broadly. It has had a vast influence on the rapid popularization of technologies among non-tech users. Today most of the best IT companies develop their own Product Design Processes to limit the risk of market failure, clearly expose the values and distinguish from the competitors.
Product Design methodologies
As it was mentioned Product Design is user-centered but also should be business-driven so its development paths are determined by evolving requirements of the target group as well as by the remaining trends in the company’s management. The Product Design methodologies help to systematize the process and equip with the particular tools and solutions to keep the right workflow.
One of the most commonly used in companies although less and less applied in technology-related industries. It assumes the transparent process in which every stage should be finished to start another one. This way we can keep the apparent order and prepare a formal plan from the research through design and development to the product release.
The problem with the waterfall approach the IT companies particularly met is its inflexibility and difficulties in introducing modifications when the specific stage has already ended. For the enterprises performing in constantly and briskly changing the environment, the process is often too rigid and jeopardizing the project success in terms of remaining its up-to-dateness.
Established in 2001 Agile was the answer to peculiar requirements of creating digital products and to the defects of the waterfall approach. It makes software development more effective and responsive by cutting it into the small, repeated parts - iterations (sprints). Every each of them is run within the process including elements like planning, dailies, reviews, retros, and refinements. That ensures everyone is up to date with the project’s progress, the workflow is maintained, and that necessary modification can be deployed at a very early stage. Agile also assumes working in multidisciplinary, self-organized teams which creates a great space to exchange opinions of experts from different fields. For Product Designers, it provides the conditions of close collaboration with software engineers and an opportunity to gain fast, technical feedback about their ideas.
- Lean Startup
This methodology is focused on creating the MVP (Minimum Viable Product) - the basic version of the product consisting of the most important features. Building it requires prioritization of functionalities and sometimes resigning from some of those which are not essential to meet users’ needs and achieve business purposes. This approach will above all speed up releasing the product and introducing it to the first clients which is crucial in innovative projects and in highly competitive markets. MVP provides a chance to verify the assumptions and the idea with the real users and then improve the particular areas.
- Design Thinking
Design Thinking is one of the most in-demand design methodologies established more than 25 years ago by IDEO, product development company. So what it is about?
Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.
— Tim Brown, CEO of IDEO
To achieve above-cited results teams should be interdisciplinary so members can look at the issue from different perspectives. The whole Design Thinking work needs to be oriented on creative problem solving, experimenting, and testing ideas. The Product Design Process starts with “empathize” stage within which we try to get to know (but not judging!) the users by interviewing and observing them. Based on this research we define particular needs and insights to clarify the problem we want to solve. Then there comes the brainstorming in which even the most extraordinary ideas should be generated as the selection will come later. When we choose the most proper ones we can start prototyping phase. With the physical form of our idea, we are able to test it, get feedback and refine the solution.
Design Thinking offers great fundamentals and the general philosophy of conducting the Product Design Process so it’s no surprise that companies like IBM, Apple or SAP broadly implemented it and created a lot of successful solution based on it. It also inspires to further explore methodology and developed it as Google has had with building the Design Sprint.
This framework captures the IDEO’s methodology in a 5-day sprint to run the process quickly and effectively. Although it provides a very detailed plan, it can be adjusted to project’s specification and abilities.
Why product design is important in business strategy?
Product design isn’t just about a fancy look, impressive features or user-friendly interface. It’s a comprehensive approach which should put the users in the center of the process to create a product fitting their needs and expectations. But no company is building a solution just to satisfy a group of people - their goal is to achieve it to simply make money on selling the product. That’s so obvious, right? So the vital mission of Product Design is to support reaching business goals.
To make it happen UX Designer should be engaged in the project from the very beginning to validate the first assumptions and ideas. At the later stages of development, this role will modify and Product Designer will control the results with set requirements and advice on what should be changed and how. This constant UX support can significantly limit the risk of appearing the faults so at the end also save money and time put into designing and developing the product.
This step should be made even before the whole Product Design Process will start. The vision sounds quite subtle and fuzzy but it needs to be highly tangible and clearly define what kind of product you want to create and who will use it. Answers to these questions should be based on in-depth analysis of the target audience including their needs, insights, and also the problems they face and which can be solved with your product features. But user profile is not the only issue that needs to be studied at the very beginning of your trip. The equally important fields are an environment and a context so - competition, market conditions, law requirements, etc. All of them should be reflected in your business strategy, marketing, and sales plans and taken into consideration in the Product Design Process. They are also a groundwork to create Unique Value Proposition - the main benefit for choosing your product, making it stand out from other, similar ones and encouraging to pay for yours.
How do you know if your project succeed? Without setting goals first, you won’t be able to judge it accurately. Reaching particular markets, gaining a specific gross profit or a number of clients - these are measures showing how do you perform and what should be changed to achieve success. They are also essential for Product Designers to follow up the results of their work so does the project meet users’ needs and business goals you established.
Why UX research is an essential part of the Product Design Process?
The 1:10:100 rule established in quality management by George Labovitz and Yu Sang Chang is applied across many fields including digital project development. It illustrates in a very vivid way the real cost we need to bear in a particular stage of the process to react for the defects. So what it is about? In short: 1 dollar spent on prevention will save us 10 dollars on correcting errors and 100 dollars on a failure caused by the poor quality of preparation and analysis. Implementing this rule in UX shows the great role of research in the whole Product Design Process.
Entrepreneurs, especially in startups, often have a very strong belief that their products will meet the users needs and their enthusiasm might distort their viewpoints on some matters detected during the development. Subtle but meaningful premises found then are belittled or misinterpreted because of confidence of own knowledge of the user and the market circumstances. With this attitude, even engaging Product Designer who would conduct the most effective workshops won’t fully exploit the potential of the UX process. So research is vital not only for companies that have barely an outline of their business but also for these which prepared some analysis and are looking for a second opinion to verify them.
Benefits of conducting UX research:
- discovering the real expectations, needs, and requirements of users,
- fresh, external look at the product, ideas, and already gathered information and knowledge,
- detecting potential weak spots to prevent making errors in the design and development stages,
- verifying the business model and particular features
- a better understanding of the product and preparing for situations entrepreneur would not foresee on his own.
UX research methods
There are numerous techniques used by Product Designers in UX research. Choosing a particular one depends on the specifics and profile of the project, business goals and strategy and of course budget. To name some of the most popular and effective ones:
- Card sorting - a way of building proper information architecture of a digital product based on users’ categorization of words or phrases which the researcher has put on the cards.
- In-depth interview - time-absorbing method but worthwhile as the interview provides comprehensive and detailed information about the user, his needs and behaviors.
- Focus groups - opinion exchange along with a group of users run by UX researcher. There are more dynamic but also unpredictable so it’s essential to properly moderate them and interpret the information gained from participants.
- Field studies - a range of UX research techniques which allows you to observe users in their everyday life and specific situations. They ensure the insides of how the product might be used in a particular context and environment which is natural for the person.
- Concept testing - confronting the very early stage prototype with users to verify basic ideas and concepts.
How to run a successful brainstorming and get great ideas?
When all of the necessary information about users and the business environment will be gathered, Product Designer has to turn this knowledge into particular ideas. Conducting this part effectively requires proper moderation and organization. To achieve that there are numerous techniques which support running the brainstorming sessions. Here are some of the widely used on this stage of the Product Design Process:
- Value Proposition Canvas (VPC) - a powerful yet accessible tool which helps to check if two parts of this model: Customer Profile and Value Proposition fit each other. The first block is dedicated to the user’s expectations, needs but also negative issues and problems. The second element of the VPC focuses on the product and validates if it corresponding with information defined in Customer Profile by providing the value (Gain creators) and/or overcome the difficulties (Pain relievers).
- Customer Journey Map - it's a detailed list of the interactions between a customer and company. The map visualizes the path of user experiences and shows the steps he/she needs to take to buy a product with the emphasis of the touch points we need to pay attention within the design process.
- User stories - these are scenarios written from a user perspective and describing the features of the product. User stories contain 3 elements: persona, action, and value proposition expressed in a different kind of sentences with gaps to complete like: “As a ..., I want to ..., so I can ...”. Commonly applied in the Agile approach to software development.
When the designs are created?
Well, just right now. We know what we want to create, we are aware of the market circumstances and we got to know users inside out. So now is the time to translate this great knowledge into an aesthetic and user-friendly design. The amount of UI Designer work differs according to the stage of development which product is at the moment. Wherever it’s a mature project with defined visual identity or a startup which doesn’t even have a logo, the key to success in building a delightful user interface is the constant and close collaboration between UX and UI Designers and the client. Product profile and business goals are one more again crucial as this part of the process is not only about the eye-catching look of an app. UI Designer has to consider if the interface will be based mostly on images like in e-commerce or maybe dashboards presenting data in an easy way for the users of some Fintech system? Or maybe a client perform in the digital signage industry so adapting to DOOH requirements will be vital? All these have to be taken into account right at the beginning.
In creating UI the first issue which needs designing is the basic structure of a digital product. One of the most commonly used methods of building it is wireframing which shows a layout, vital elements, and main pages of the website or app. Even if wireframes are just sketches this is a way better form to present ideas and user flow than discussing them without any particular image.
How to prepare a prototype for tests?
The prototype delivered to tests doesn’t have to be highly advanced but it needs to include some important aspects of the work that has been already done and require validation. It can be prepared with paper or using e.g. Adobe XD or Axure. Both methods have their pros and cons and should be used in terms of the stage of the product's design. Evaluating the project part by part will gain you time to correct errors before the development phase will start and help to keep the effective workflow. The prototypes will become more and more advanced with the progress of the project so it’s crucial not to wait to build them when we will have an almost fully-fledged product. Introducing modifications at that moment will cost more time, work and of course money.
Testing in the Product Design Process
After a discussion (or rather few of them) with a client about prepared design projects and prototypes there comes a moment of gathering the first feedback. In software houses, the development team usually includes QA specialists who are responsible for detecting bugs and technical problems. The range of their duties is growing and the good practice is to entrust them e.g. usability test.
Whichever scope of services you will choose to develop your project, sooner or later the product will face the moment of users testing. That’s always a great challenge so be prepared for rather plenty remarks and that a great part of them will be unexpected. Tests can change not only a particular feature or element of the app but sometimes the whole strategy we’ve established within other stages of Product Design Process. Users will provide you with bugs reports, some fresh observations, opinions about the interface, information about a particular context in which they used the app and did it help or fail. To fully exploit this valuable feedback Product Designer should select the accurate form of testing fitting the project specification and the stage of its development.
Testing techniques and tools
- Usability testing - verification of functionality and intuitiveness of the product. It provides a broad evaluation containing data on how potential clients experience it, is it understandable and easy to use for them, do they find it attractive, are they able to reach clue information, what’s their opinion of particular features and much more. The testing session can be conducted in a formal environment or more casual circumstances. There’s no need to engage numerous users but Product Designer should clearly define the information he wants to obtain.
- Heatmaps - used in design surveys to check which part of e.g. website users pay attention too, for how long and in what order. It’s based on tracking the movements of eyes, mouse or /and clicks.
- A/B testing - helpful when Product Designer wants to check which of solutions will be more effective. It assumes introducing two versions of elements to the users and analyzing their reactions for each of them.
Of course not. Realizing the product shouldn’t be considered as a final step of the Product Design and Development Process and the end of the collaboration with software supplier wherever it’s an outsourcing company or in-house team. The digital products perform in the competitive and dynamic conditions so there’s always something you can improve or completely change. Observing customers’ behavior when they use your solution and analyzing gathered data should be a permanent part of running the business as well as planning refreshments and reaching for post-implementation expert support.