Reflection on the cause of the difference

When I first saw this picture, also think can produce this incredible, because at that time is in the entrepreneurial company, and before the experience of even large companies are entrepreneurial products, small team is the benefit of diligent communication, often exchanges, from design to development stage, everyone in the participation and thinking, the goal is consistent, So I always feel that this image is exaggerated exaggerated the message, until today there is a lesson to start thinking. In fact, the problem is not so big, but for such problems, would rather enlarge the thinking.

The above result must be the worst and most people don't want to see it.

~ ~ The product itself is a failure

~ ~ Waste a lot of manpower and resources

It's a big blow to everyone.

~ ~ Delayed time, wasted the market opportunity

But how? I began to ask myself, calm down to think of a few reasons, of course, the purpose of recalling the reason is to better solve the problem, from avoid to eliminate the emergence of such problems.

1, the early thinking is not in place: in a single page complex interaction, simple static demo can not complete the full display of all the logic, including a variety of branches. In the past when making products for complex pages will be a single page of the logic diagram, used to verify the overall logic design, interactive design. But now look at how much more complicated the interaction might be.

2, information expression is not in place: How to show the interactive logic in a reasonable way is still a question worth thinking and trying, in time through axure can achieve partial interaction, but in more complex circumstances is not satisfied, while a large number of production and maintenance costs can not adapt to the rapid adjustment and change of the design rhythm. There is still a need to consider more effective ways to behave.

3, information transmission is not in place: the product design can only be completed 50%, the setting is less than 50%. Other gravity is the development and implementation phase. The way in which this phase is implemented and the quality of care is particularly important. The real realization of the product's functional logic, at the same time need to consider the future expansion of product functions, the operation of the market and other activities such as support, need many considerations. At the same time how to effectively communicate the logic of the function is to be considered.

4, requirements change after the verification: changes in requirements and adjustments are bound to exist, remember one word: The only constant is change. Change can not be completely avoided, but after the change, after the adjustment of the product still need to complete and meticulous re-examine the new design, in meeting the change, whether or not to increase or complex mode of operation.

5, the lack of front-end skills: Although the basis of some front-end skills, but the understanding of Ajax is still not deep enough and the system, otherwise it should be in the asynchronous synchronous data processing methods as early as possible to find some problems and hidden dangers, early to avoid problems.

6, not early input to the test: the product personnel need to put into the test of the product as soon as possible, in the development of the need for close communication with the developers, especially affecting the key parts of the product

7, multi-project parallel: Multi-project parallel causes the content and mode of thinking in the constant conversion, the middle is easy to produce "limbo", resulting in inconsistent ways and means of thinking, and ultimately affect the quality of output. Although sometimes "the product is numb, you can put some time back to see, can find problems", but this approach is generally the product of the overall process or a single "static" point is effective.

To sum up, it is found that the ideal link is: Design-> verification Design (self)-> expression Design-> validation design (development/product/other related)-> development-> validation Design-> test. It is critical and necessary to improve the frequency of the verification design and to adjust the verification design, at the same time with the improvement of the front-end skills.

Finally to the hard end of the classmate salute and apology, thank you ...