This series of interaction design articles extracts the core steps required in the work. It is estimated that there are 6 articles, and the following contents are tentatively drafted:
Interaction design process one needs analysis
Architecture Design of Interaction Design Process II
Interaction design process three process design
Interaction design process four page layout design
Interaction design process five interactive document output
Interaction Design Process Six Design Testing and Evaluation
The full name of architecture design is information architecture design, and the quality of architecture design can determine the usability of the entire product for users. In daily life, everyone must have heard the complaint "how can this function be in it, I couldn't find it for a long time", and the reason for this is probably due to the problem of architectural design.
Why do we need information architecture b2b data design? Because if not, the entire product will be chaotic, allowing users to see the first time the product has a general feeling about the entire product and what it can achieve.
For example, for content social platforms, users have been educated by platforms such as Weibo, Douyin, etc. The core function point is "publishing", and other first-level navigations are homepage/discovery/personal page, etc. Even if there are deviations, it does not matter. There will be big differences, so if a new content social platform challenges this information architecture at this time (provided that this information architecture is very mature and has been tested by users and the market), then it is very likely to fail. .
1. Preliminary work of architectural design
The preliminary work includes the following four points:
Understand the usage scenarios and characteristics of target users
Understand business needs
Information architecture for research products
card sorting
1. Understand the usage scenarios and characteristics of target users
This does not need to be introduced too much, especially for C-end products, product managers and designers need to always put users in the first place, fully understand the needs and habits of users, and do not easily challenge user habits. Here is a method. Everyone should have heard of the Persona construction. It sounds relatively tall. The simple point is to visualize a target user (as shown below, the picture is taken from everyone is a product manager), he has a name , there are companies, they have their own current operations and goals, etc. Such a method will make the target users truly land, more "flesh and blood", and allow products and designers to better consider user scenarios and needs.
2. Understand business needs
Different products have different profit models, so you must fully understand the business needs of your own products. For a simple example, an app mainly generates profits through user payment, so in the design process, you must use appropriate guidance to encourage users to pay. At the same time, the importance level of payment should also be reflected in the information architecture. This process is of course a loss to the user experience, but all products need to have their own way of survival.
3. Competitor Information Architecture
This should be the most used method by everyone, it saves time and effort, and the effect is very good. Mature competitive product analysis can help us a lot. It cultivates user habits, educates users for us, and steps on a lot of pits. When I conduct competitive product analysis, I will mainly focus on two points. The first common point is the function that this type of product must have, and the second difference point is the characteristic function of each product.
In terms of tool use, all kinds of brain map software can be used, don't be too rigid, I personally like to use Baidu brain map, online at any time, other mindmap/xmind/mindmanager and so on.