I didn t do a demand analysis, how to do a good design

The starting point of design is demand. In the product life cycle, demand is a dynamic process, products can be divided into: introduction period, growth period, maturity period and decline period, products have different needs at different stages, and the types of needs are also different.

From the perspective of the object, the requirements are: basic needs, ease of use needs, and operability requirements;

From the perspective of product operation, the needs are: product operation needs, policy and legal needs;

From a system perspective, the requirements are: security requirements, performance requirements, maintainability and portability requirements;

The company has a mature demand collection, review and management mechanism. When judging the priority of requirements, the Kano model is used to determine whether it is a charismatic need, an expected need, a must-have need, an undifferentiated need, or a reverse need. For example, the folding screen mentioned earlier, taking photos on the front and back, and interaction between applications belong to the charm needs.

App splitting is an expected requirement. Folding reliability is a must-have.

So-called"Requirements analysis"It refers to a detailed analysis of the problem to be solved, and a clear understanding of the requirements of the problem, including what data needs to be input, what results to obtain, and what should be output. It can be said that "requirements analysis" in software engineering is to determine what the computer "does" and what kind of effect it wants to achieve. It can be said that requirements analysis is a must before making a system.

In software engineering, requirements analysis refers to all the work that is required to describe the purpose, scope, definition, and functionality of a new computer system when building a new or changing an existing computer system. Requirements analysis is a key process in software engineering. In this process, system analysts and software engineers determine the needs of the customer.

It is only after these needs have been identified that they are able to analyse and seek solutions for the new system. The task of the requirements analysis phase is to determine the functionality of the software system.

For a long time in the history of software engineering, requirements analysis was considered the simplest step in software engineering. But in the last decade, more and more people have recognized that requirements analysis is the most critical part of the process. If the analyst does not correctly recognize the customer's needs during the requirements analysis, then the final software will not actually meet the customer's needs, or the software project will not be completed within the specified time.

The first article of 2017 on needs analysis.

Before designing a solution, we analyze the business needs and user needs and clarify the design strategy. Then the business requirements include the business purpose (the business purpose is why do you want to do this feature?). and business goals (what kind of success does the product expect?).

The following is an attempt to discuss and analyze a specific requirement in my work, and how to do a requirements analysis before designing a solution.

a- Analyze business requirements.

Business purpose: to increase the number of users, user activity and policy promotion rate in the form of rebates;

Business Objective: Increase in policy enablement rate.

Metrics: Increase sign-up rates, increase engagement.

b- Analysis of user needs:

The target user is Lao Wang (white-collar workers, not bad for money, and has purchased insurance on this platform).

c- Decompose the key factors.

It is necessary to change from a business perspective to a user perspective, create motivation for users to be more willing to recommend, and eliminate users' worries before use, and be more willing to recommend friends and friends.

Solve the obstacles in the use of users, so that users can recommend and get rebates more quickly, so as to improve the user experience, but also can successfully achieve business goals and increase the registration rate.

Why do users recommend products to their friends? What are the concerns of users? What obstacles will I encounter during use?

These three questions are key to translating from a business perspective to a user perspective.

Create motivation for users to be willing to take the initiative.

Is it troublesome to refer friends? How do I get rebates after referrals? Would a friend be willing to buy it?

How do I know if the recommendation is successful and the purchase is successful? Is this campaign credible and does the rebate amount have an expiration date?

d-Summarize the design requirements and clarify the design strategy.

By analyzing the path of the user's body, find each contact point, understand the problems encountered by the user in the whole process, and propose appropriate solutions based on the analysis of key factors. and refine the individual steps in the process. In the actual process, you can also improve your product by comparing the user experience path of competing products.

2.Establish user experience paths and sentiment coordinates.

Display the "Referrer Entrance" in the personal center;

The recommendation rules should be as short as possible, placed at the bottom as much as possible, and do not occupy most of the user's visual center;

Click Share to give appropriate feedback and let the user know that the share has been successful. Or pop up the modal window "Share successfully!"

If the friend has successfully purchased the policy and the friend's policy has been activated, the rebate will be awarded.

To get rebates, in addition to congratulating users, you can also prompt users to "recommend and share" more pushes and more.

Summary Don't blindly draw wireframes, only before designing the plan, better understand and analyze the requirements, in order to serve users well and help users use the product. At the same time, only by analyzing and understanding the product from the perspective of users can we help the product improve the user experience and design needs from a global perspective, so as to create an excellent user experience.