After work, the usual design presentations are mostly business-related, mainly B-side design, and the methodology of traditional interaction design is a bit rusty. So I organize my notes again, and if there is something wrong, we can communicate more.
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
At work, when designers communicate with upstream (product managers) and downstream (development), they are all based on needs. We need to b2b data understand the real business demands and user demands behind each demand.
For demand analysis, it can be analyzed from the following three points:
Business needs;
User needs;
Break down the key factors.
1. Business needs
First of all, the entire product has a comprehensive goal. For example, the highest goal of Mobike and ofo bicycle products is to become the largest shared bicycle platform. Some students may think that this goal is nonsense. In fact, this is not the case. Sometimes this goal can show the final trend and business model of the product. We can see that Mobike is profitable and realized through the sharing economy.
Secondly, each small module you accept has its own business needs, such as: registration and login modules, which are convenient for user management and enhance user stickiness. To be more realistic, your user activity is high, go out Financing is very simple (of course, there must be a certain liquidity).
Here is a GSM model that can be applied: Goal, which is the business goal of your module; Signal, what kind of behavior you want users to produce; metric measurement, which is quantified to a specific indicator (on C-side products, it is often click rate and conversion rate, etc.).
Combined with specific examples, the module I am currently working on is advertising traffic diagnosis. The comprehensive purpose of the entire platform is to help operations better convert traffic and improve profitability. Combined with the GSM model, the goal of this module is to quickly analyze and diagnose abnormal sources such as fluctuations. , so that a correction can be made.
The signal of this module is that operators use this module to locate related problems, and the metric indicators of this module are related indicators of advertising traffic (such as ecpm) that use this module to improve.
Under this module, every small function can be thought in this way. Combined with the examples in my own hands, the diagnostic analysis results have several parts. What is the function of each part? What problem does the operation solve with this part?
We should all think about the use of scenarios that can be simulated in the process. Of course, it is not necessary to list every function point like this, just make it clear in your mind. After all, every module, whether it is a large module or a small module, has a role and meaning. If not, why make it?
2. User needs
User needs are what products and designers need to keep in mind at all times. After all, the most realistic dimension to evaluate a product is the number of users and activity of the product, but sometimes user needs and business needs will be contradictory to a certain extent.
The simplest example: Many software use advertising, the simplest monetization model, but from the user’s point of view, the fewer advertisements, the better, and advertising does damage the user experience to a certain extent. At this time, products and design are required. Teachers make a good balance.
User needs can be confirmed from the following two steps: clarifying the target users and clarifying the needs of the target users.