Think your plan is good, but it is always unacceptable? Such scenes can often be encountered in the workplace. What is wrong in the end? Is the solution really not good enough? In the article, the author combined his own experience to summarize three key points that are often overlooked in the product design process, and hope that the article can help you solve problems.
Have you ever encountered such a situation where you feel good, but others say that there is a problem with your plan, what is wrong? I am not convinced, why not do this, why do you want to do that. According to the reflection of the cabinet owner, the problem may lie in the following three points:
- The scene details are not fully considered;
- Ignore the APP environment and major premises;
- I am not very familiar with the business at all (I am not very familiar with the existing and will be designed).
The cabinet owner will use today’s work to explain these two points. The patron takes over the design task of a points system. After getting the task, the cabinet owner first went to understand the main functions of the points system that the company wants at this stage, and to what extent. Then look for some existing apps on the market as competing products for analysis, such as Alipay, Are you hungry, Taobao, Ctrip, Didi Taxi, and see what others do.
After reading it, I summarized several key points of the program design:
- Need to determine where the entry point of the points system is located?
- What are the constituent factors, points records, points earning methods, links to redeem products, are there any friend rankings?
- How to prompt users to get points on other pages of the APP?
So I opened a mouth on the profile page and made a mall-based page, as shown in the figure below.
The starting point of the cabinet owner is to tell users what benefits they can get when using this function, and then guide users how to get these benefits. Finally, because there are two behaviors of getting points and consuming points, they made a “point record” “Page. And the presentation page of the points is presented in the way of toast. The whole process does not seem to be a problem, as shown in the figure below.
It all makes sense in principle, and there is no major problem. However, when it is integrated in the overall APP environment, it is found that the design of the entire function is too heavy.
The positioning of the overall environment, the scoring system is similar to the way of coupons , which only appears when users make payments on the web, and the promotion method only appears in the official website introduction video for a few frames. The scenes that appear also appear when the user is viewing some game reports, browsing information, or shooting videos, and these scenes consume a lot of attention by the user himself, and they are also the places where the main functions of the APP are displayed.
Based on the above functional positioning and scenarios, the point positioning is actually a very weak function . It will not have a dedicated product exchange page like the competing products mentioned in the article. It is more like an automatic match when paying. “Coupons”, and when you get them, you can’t disturb the user’s main operation . So after the revision, it becomes the following plan.
The main page provides an entrance to the mall, which mainly introduces the benefits of points and how to obtain points, and the prompt to get credit is only displayed on the status bar (status bar) for quick digital display. This is much lighter. The plan is also more appreciated by the boss. This is the positioning of the function in the mind of the boss!
Therefore, in many cases, it’s not that we don’t know how to do it, but the understanding of the project is not yet in place. I have never thought about the proportion of the main function and auxiliary function of the entire APP, and I have never thought about the development team of this version. To what extent the resources can support the workload, how the boss wants to use the most cost-effective way to achieve maximum profitability, and so on.
Of course, the reason for this is that apart from the loss of information transmission, we also have to let go of the heart that wants to express ourselves. Every designer wants to be the leader on his own and make the most complete and most important functional block, so every At the time of design, a function will be biased towards enlargement and enlargement. It is very likely that it will lose its bias for a long time, resulting in a lack of objective analysis ability of the existing situation. You can only calm down, be broad-minded, and take the initiative to spend time and energy to inquire and communicate. Otherwise, there is no other way.
Repeat the first three points:
- The scene details are not fully considered;
- Ignore the APP environment and major premises;
- I am not very familiar with the business at all (I am not very familiar with the existing and will be designed).
Here also talk about recent experience. With the deepening of work experience, the understanding of the work content of interaction design is constantly updated and changed. When I first started, I felt that the interaction design was to perfect the functional process. The other things were the product manager and development team’s work. I just managed the flow chart myself; I gradually added the work of tracking the development and implementation of the project. To track the implementation of the product.
Now I think it is: Under the condition of understanding the commercial premises , perfect the user’s use of the product process (here is the process instead of referring to the flow chart), so that the user has a more pleasant experience in the use process , this is the task of interaction design . The required capabilities include the balance of various judgments, and various understanding of equipment and mobile phone systems, in order to know how to work in the least cost-effective manner and design the most suitable product that best meets the company’s current stage.
And some of the professional methods we know, such as A/B test, demo production, etc., are just to verify the feasibility of the plan. The more you know about these methods, the more you know, the better the plan you have adopted. More, but it does not mean that the ability to solve core problems is stronger. And the ability to solve core problems can only be continuously reflected in each case and practice again and again, trying to figure out the thinking of the people in each position, pondering their skills and gradually improving, and then one day, suddenly surprised, It turns out that I have been reborn from the fire!
Keep going~
