The number of modules and pages that need to be designed for the product deviates greatly from the expected, and the jump relationship and development function points in the product are constantly changing. I feel that the product team is always overturning their original conclusions. As designers, It’s really tiring, so I follow them around. I always feel like I’ve been working overtime and drawing, but I haven’t made any substantial progress in my busy schedule. I really don’t want to do this kind of design.”
The author is quite understandable to hear this complaint from the designer's friends; no matter who, everyone hopes that their efforts will phone number list have a good result, rather than being busy.
So, if we can't change the status quo, how should we respond? I think this is what designers need to think seriously about.
Below, the author attempts to answer the above doubts for the designer partners from an objective point of view, and give some advice to designers phone number list who encounter the same situation.
1. Four life cycles of product development
First of all, the author first introduces the four life cycles of product development for everyone, which is a relatively unanimous definition of product life cycle in the industry; from the life cycle of product development, we can understand why each position of the product team is doing this when dealing with products, and why Not so.
Whether it is a B-end product or a C-end product, it usually goes through the process from preparing to enter the market to being eliminated by the market, that is, the four life cycles of introduction, growth, maturity, and decline.
1. Introduction period
The introduction period refers to the stage when the product team has finally completed the development of the core functions of the first phase of the product and officially launched after a long development cycle.
During the introduction period, the function of the product will definitely not meet all the needs of users, and it cannot completely cover all business situations, and there may be some bugs; Iterate to adjust the direction of the product.
The working status of the product team: According to market feedback, quickly promote necessary requirements into functional implementation.
Designer's work status: The design requirements received are relatively clear. Although the work is busy during this period, the design work is rhythmic and results are obtained.
2. Growth period
After a period of promotion, the product has been widely known and accepted in the market, and when the speed of product promotion is getting faster and faster, the product can cover more and more markets, and the product can also meet more and more abundant requirements. Business needs, and thus the value that products bring to the enterprise, are also increasing.
That is to say, at this time, the product planning has gradually become clear and definite, and the market share continues to rise. The product has been relatively stable in the growth period after adjustment and running-in during the introduction period.
The working status of the product team: Precipitation of reusable functions, special treatment of personalized functions, and continuous adjustment of products to meet the needs of a wider range of user groups.
Designer working status: The received design requirements are clearly divided, the source of the requirements and the problems that need to be solved are clear, and the design work is getting better and better.
After the steady growth or rapid explosive growth of the product in the growth period, the product already has relatively stable and comprehensive product functions, and the number of customers and customer repurchase rate are also relatively stable, creating stable business value for the enterprise; at this time, it is revealed that the product entered the mature stage.
The working status of the product team: The product functions are relatively comprehensive, and the product team will consider expanding the product ecology and stabilizing the current product.
Designer working status: The design requirements received will be less and less, if there are, most of them are based on the experience optimization on the original basis, and the design tasks of large modules are rarely carried out.