Notes for website Revision

Revision is a problem. More and more Internet company product staff are aware of this problem. Both the revision of Douban and the revision of Facebook have been frantically resisted by users.

Compared with traditional 1.0 websites, the power of 2.0 website users is infinitely magnified, which also means users have more and more voices in website development. Any so-called revision may affect the usage habits of existing users to a certain extent and may be attacked by users on a large scale.

This means that the website revision may require more wisdom and refined operations.

Why do we need a new version?

When a website was founded, it was always unfamiliar and ignorant. It was the most loyal embodiment of the core value of the website. At this time, the website can be called the initial stage of the product.

With the changes in user needs and business needs, we will gradually make some adjustments to the website to better adapt to the needs of the website's step-by-step development. When these small changes accumulate to a certain extent, the previous product interface design and website architecture can no longer meet the requirements. At this time, a new version is required.

This process is a bit similar to the operating system. We found it great when we first started to Access XP, but as time went on, XP became increasingly unable to meet our needs, at this time, Microsoft will patch it in large and small ways so that it can work better. However, if one day, XP really cannot meet the needs of users and the company's commercial value, then we need to launch the next version of the operating system, which is now popular in Windows 7.

Website revisions serve two things: user needs and business needs. Let's take a look at the key points worth attention for a smooth revision.

　　1. Make a requirement survey before the revision

Similar to the development of many products, the website is subject to constant changes in requirements, which means repeated work may be required in many cases, and some may need to be completely redone.

At this time, the importance of the Demand Survey for revision is highlighted. You need to collect user requirements for functions through user surveys, data mining, and other methods, at the same time, you also need to confirm the requirements for the overall development of the company with the management, and then summarize the requirements for the revision for use during the revision.

The comprehensive demand survey has two main positive significance for the website revision: first, let the product team be aware of the product design and development process; second, reduce the time and user losses caused by demand changes.

　　2. Do not change it if possible.

During the website revision process, user habits may be affected. Do not change it if possible. The website revision is to add, to make the website better and better, rather than to do subtraction.

The good and evil of users are an important criterion to test whether the website revision is successful. Therefore, if there are some well-received features, if they are different from commercial interests or high-level will, it is best to preserve the user's usage habits and give users enough time to adapt.

　　3. progressive evolution

With multiple website revisions, senior executives like to immerse themselves in the new joy of the entire site. However, such a thorough revision may lead to a large loss of users, and users who have worked hard to cultivate may be wiped out due to the fraudulent revision. The larger the website, the heavier the loss.

There is a famous experiment called "warm boiled frog". Our revision should also be carried out steadily step by step, giving users a period of time to buffer, so that users can learn and adapt to new features.

If you need to change the five channels, change them one by one. If you need to change the ten functions, change them one by one.

Before the revision, let the user know which functions will be changed and what will be changed. What are the benefits after the change. Then, in this process, you can receive various comments from users about the revision, and then judge the feasibility of the revision.

　　4. Going online does not mean that the revision is over.

Many of my friends are always relieved after the website is revised and launched.

However, revision is a means rather than an aim. It is the key to cater to users and meet business needs. This means that the launch is not the end point, but a new starting point.

Then, we should extensively collect comments from all parties on the revision. The sources of these views include but are not limited to users, colleagues, and industry friends, so as to screen out reasonable suggestions, then adjust and improve the website.