On the one hand he is looking for inspiration and wants to find something original, to mark the product with himself. On the other hand, there are standards, processes and repetitive actions.
Below you will find the process when I start the new project.
My Desegn & Research Workflow
To solve a problem, you need to understand the product, its context and business expectations. Without this knowledge you rely only on experience and assumptions, and these can often lead you to bad decisions. So you gather information like a seasoned detective and try not to understand what's going on here.
Know the product, business expectations and what the customer problem this product solves
Trying to understand the available data and what questions are not answered
Our first Milestone
The information you collect is like collecting data during an investigation. You check various sources, analyze data and try to find connections. You connect the dots and get to the point where you can "feel" the situation, the product and its problems.
We launched Zense UI Kit
By understanding the context and the available data, you can prepare the product structure and indicate its improvements and simplifications. The risk of missing an important element is less when you have so much product knowledge in your head.
Preparing a product structure that is simple, logical and expected
Product wireframes and test planning
We hit our first 1,000 client
While working on specific screens, a lot of questions will appear in your head. "Will it work?", "Will they notice it, understand?" That is why for me it is also a perfect moment to prepare a list of questions and doubts, from which you can create a User Testing scenario.
Zense UI makes the difference
Once we know what and how it is going to be built, we can focus on how it is going to look. At this stage we can also build a prototype, which will be useful not only for testing with users, but also for presenting progress inside the company.
Product design close to target
Testing (if possible) of the project and the target product version after improvements
We hit our first 1,000 client
Testing and Research are critical to the success of the product. Not only do they give us confidence that something is built correctly, but they also reduce the cost of unnecessary development. In practice, however, many companies are in a hurry to release a live product and skip tests or want to do them later. At this stage, communicating the risks and possible costs of corrections is one of the main tasks I have in mind.
Example use cases
This case shows the process of creating a new version of the product, including research, rebuilding the information architecture and adjusting the features to the needs of a specialised group of customers.
This case describes the stage of a product's life from the moment it appears on the web to the moment it undergoes significant changes resulting from intensive research and attempts to understand human behaviour and expectations.
I am a Designer who have done a lot of usability tests and research since 2009. This means that I can be active throughout the whole design process, from gathering information and planning the concept, through testing it and delivering the final design.
I have extensive experience in working with clients from Europe (mainly Germany, Switzerland, and England) and Asia (UAE and Bali). I have helped to create e-commerce, e-travel, e-learning products as well as for many specialist customers.