Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall
A few days ago, the best products are not satisfied with the demand, but "requirements", we mentioned "to try to meet the user's requirements, so that they hopelessly fall in love with your products." "The article distinguishes between the" requirements "and" requirements "of the user, a lot of friends reply to the news is quite enlightening, but I also noticed that some entrepreneurs still have questions: since I want to do everything possible to meet the requirements of users, but the user's requirements are endless, and the difference is also larger, then what should I do?
I can never impersonate an expert, I'm just saying what I think.
Friends who are involved in software development may know that software development is more common in two models, one is the waterfall model, the other is the agile model. In fact, the thinking logic behind the two models is also common in entrepreneurial processes.
Waterfall model divides software development into various stages, requirements analysis, definition of elements, basic design, detailed design, coding, monomer testing, combined testing, system testing, and so on, each stage has a strict definition of input and output, if not the output requirements, then the next stage will not expand. After the system test is completed, the software is delivered to the user, and the whole process is completed.
The waterfall model's thinking pattern is a very receptive pattern, and it feels natural to know what the user wants first, and then step by step until delivery. This pattern has been widely used. However, it has its drawbacks, the biggest problem is that it cannot be timely. A project is short for a few months and a year or two, and user requirements are likely to change during this period. Just like the user to order a fit clothes, you give him a measure of size, and then silent for several months, the results found that a few months later, the user gained weight, this time the cost of rework is too big.
Then there was the agile model. The core of the agile model is iteration, and the ultimate goal is to satisfy the customer so that it can proactively accept changes in requirements. It's a manifesto I agree with: individuals and interactions outperform processes and tools, software that works is better than all documents, customer collaboration trumps contract negotiation, and responding to change is better than following a plan. In particular, the last sentence of "response changes" is also the essence of our lean entrepreneurship.
In the agile development process, the general two weeks will be a version, each version and the previous version will add several features, the user's request if there is change, can be in the latest version of the timely response. In this way, users do not have to wait a few months to see the final version directly, but can continue to participate in the process, which is very important for the product to meet the user's requirements.
Or take a just custom-made clothes as an example, in the agile development of thinking, the tailor may first make a sample of clothes, the cloth may be coarse, even the top is marked, and then let you try the size, whether it fits; after a few days, let you try again, when you have used the formal fabric, you may feel that the collar style is not appropriate; In a few days, you try again, so you can interact with each other until you get the clothes you like.
The development of micro-letters is a good representation of agile models, every time we upgrade a version, we will find that the function of micro-letter has some changes, voice intercom is in the 2.0 version out, "Shake" function is out of the 3.0 version, to the 5.0 version, and the subscription number did a folding process. This kind of iterative development way, enables it to grasp the market feedback in time to make the response.
The user's requirements are endless, so we need to learn from the agile model, constantly adjust the product, the entire life cycle of entrepreneurship, is constantly receiving feedback, and constantly meet user requirements.
So don't worry about the user asking too much, what you have to do is start at 1.1.
We often contact with some entrepreneurial projects, entrepreneurs are easy to enter a misunderstanding. They planned all the details of the product in the first place, and then paid a lot of time and effort to get the details done. The money burned a lot, the market time also delayed, the results of a listing, the reaction is very general. This is the waterfall mode of thinking, trying to perfect, want to meet all the requirements of users, the results found that the reality is not perfect, the change has been too late.
Do not try to satisfy all the requirements of the user at once, because even the user himself, does not necessarily know all his requirements, let alone the user's requirements will change over time.
Well, a lot of people might ask, "Where do I start?"
My advice is to start with the most basic "available", micro-letter 1.0, but also only instant messaging, sharing photos and replacement avatar and other simple functions. Tailor-made clothes for the guests, the first step to ensure that they can wear into, and then consider whether the dress is comfortable, the appearance of the beauty of the problem.
In layman's parlance, the user's requirements for the product are as human beings are alive. People live to eat, to wear clothes, to the car, to the house, to the spouse, to see the film, to listen to music, and even to land on the moon, so many requirements, how to do? Very simple, from the solution to food and clothing began.
After solving the "available" problem, how do you add it to the user's "easy to use" thing? I think it's time to ask the user instead of torturing yourself in the office. Products and software, as well as iterative forward progress, the last version of the market after the push, listen to what the user said, especially the most words, then, you may know what you should do.