Details to be noted for website revision

In the rapid development of the Internet era, the continuous emergence of new technologies, the site is constantly updated, or perhaps because of the changing rules. Whatever the cause, the proper revision is very important. Make sure that the new design will give you more advantages in front of your competitors, and discuss the details of the website revision.

We do not want to spend money on the site revision. The reason for the revision is because we feel that the site needs to be visually improved, and our visitors want to see something new from a visual perspective. We should consider the revision comprehensively from the user's angle. Users should be our focus when considering creating a new identity for our blogs, publications, and any other forms of web pages.

The larger and more important the site, the greater the likelihood of its revision failure. Why? Because you have to take thousands and even millions of users into account, it's hard to please all users-frankly, it's impossible. I once left a website I like, just because it did a facelift. If I leave this site permanently, I wonder how many other users have done the same thing.

To increase the likelihood of a successful website revision, here are some points to note.

Make sure your site needs to be revised

When your site has a back up visitor, most of them want to add some functionality; they know where the navigation is, where the search box is, how to find the document, and so on. Through the revision, you are most likely to change these things.

If you're lucky enough to have a live-more community, you can do an online poll and ask if they need a website revision. If you do not have such a community, the decision will be made by you. Try to ask the designer of Daniel for advice and see how they think about it.

Get your users involved in this.

The second step in the revision process is to get community users involved, which will help the site better suit your users. Because you get feedback from them and use the feedback in the web design.

It's a good idea to try to keep the main elements in the same place, at least to make sure that the functions at the same location are similar. The first time you move the toolbar from the left to the right, it often creates confusion. The same is true for navigation bars-if the previous navigation bar is a drop-down menu style, let it keep the style, or simplify the navigation. It is important to ensure that the user does not feel that the navigation bar is more difficult to use than the previous version when using the new site. To avoid the overall revision of the site. More importantly, let the user participate in the process.

Test Web site

Do not close the door to do site testing, so that users also participate in. Provide users with the option to test the new site-make it visible. Then, let the user submit the feedback to you through the form, questionnaire, and keep track of it. This is another way to get users involved. As I said, users are always the focus of our attention. You are not doing your own website revision, but for the user. Letting the user test the new design before the job is done will also give you a chance to fix it. It's difficult to think about this process, and you have to start with some new ideas and end up with a different website--anyway, make sure your visitors appreciate the changes you've made to the site, and they'll come back.

Don't change the layout right now.

This is a strategy used by most social media sites. Whenever they change the layout, they will either allow the user to continue using the old version for a predetermined period of time, or let the user switch to the new design first, and give the user the option to return to the previous version. Why would they do that? The answer is simple. Not everyone has time to use the new layout. Using a new style layout takes time, and if users don't want to spend time on it right away, give them the right to do so.

Allow users to switch to new designs (especially when the site is still in beta), and give an option to allow them to revert to a previous version. Of course, you can't do this forever, let's take a look at Facebook's approach. Only they will force the user to update to the new layout within a month or two after determining that the new layout can be used.

Some users have decided to turn to Facebook's new "Timeline" page. I like the previous layout, so I decided to keep the layout. Also, I don't want to get the timeline page, and Facebook doesn't allow me to go back to the previous version, so my Facebook stays the same. But in fact, it won't be long before Facebook will update my layout to timeline when the old layout is no longer in use.

This is a very interesting strategy and is well implemented in social media. So you can consider this strategy in your website revision.

When the website is finished, it also allows users to provide feedback

Your website has been revised and completed. The user cannot go back to the previous version and can only accept the new version. In fairness, users should be allowed to provide feedback.

There are many tools on the Internet to help you achieve it. In this way, you can make sure that once an error occurs, the user can point out to you that if you have an active community to support this site, this is easiest to implement. It's worth a try.

If many users feel that something is wrong, modify it as quickly as possible. Their opinions are valuable and considered, and users will feel like they are part of the community and will be happy to stay on your site.

Make sure you make every decision for a specific reason.

It is wise to tell the user why you are making a revision to the site. Some users have little knowledge of design changes, usability, or new technology, and I'm afraid they don't care about it-they just want to continue using the site in the way they used to. In a certain amount of time, users may not be accustomed to the design changes until they get used to the new layout, so at first some users may be able to resist the popularity of new styles.

So, explain to the user why you think the revision is important. Using some basic theories, explain to them that adopting new technology will make the site more functional and even faster to access the site. When you hear this, most users will be excited about the new design.

Develop instructions for new layouts

If you have a large-scale revision of the site, it is helpful to guide users through pictures, text or video. I'm sure the users who know what to do next will appreciate the guidance, which allows them to quickly adapt to the new design. It also makes them feel like you care about them-and it also prompts them to visit your site again.

Picture Source

In case your website fails, there is still a solution. This only happens when you hear a lot of complaints from the community that you don't want to spend money on new designs, but want to do something to improve the site.

About your mistakes.

If the mistake happens, it's probably your mistake as a designer. You have done the wrong thing in the development process, or you may not have communicated with the user. If they are not satisfied with the new design, it is a place where the design is wrong, and this is where you should focus on solving.

This is a great time to show your intimacy with the community. It can be on Twitter, on Facebook, or on your website, to give users a real sense of the urgency you want to fix your mistakes. Ask them to tell you where there is a mistake and it will be easier when you are sure of the solution.

Use their feedback

When the user sends feedback, use it as much as possible. Acknowledge some of these complaints and show the community that you want to do everything better. It will also make your life easier, and you will get some conclusions, ideas and possibilities from all the feedback and the discussions involved. When you have the support of the community, it becomes easier to modify an error.

If necessary, revert to previous version

Accept the website revision failure, nothing embarrassed. If the community strongly requests, you can return the site to the previous version. Of course, going back to the previous version means you still need to use the resources to make a website revision, which at least waits until you have a new strategy in place to ensure that the number of visitors is not reduced.

It is really important to make the community happy, and to do that is to allow them to go back to the previous site style. Don't force it on the user. Provide only one option so they can choose the style they like. This will solve the problem in a short time and also provide you with the time to better prepare for the new design.

Keep track of feedback

Whenever you release a new design, the most important thing is to listen carefully to the community and their behavior. Google Analytics is a good tool that allows you to have a deep view of the time users spend on your site. If the number of visitors to the site soon after the update quickly, this may be due to the new web design.

Pictures from Claymor

At this point, you have to interact more with your visitors and ask where the error is. The conclusion is that if the designer is interested and willing to participate in the user, many users would rather stay on a bad page than to stay in an excellent page that the designer doesn't care about. So you have to show your community that you care about them.

Another way to track feedback advice is to keep a close eye on social media blogs. When talking about such changes, most users prefer Twitter and Facebook, so stay focused. This also shows the website's revision is for their benefit.

Conclusion

The conclusion is that the revision of the website is not as simple as it sounds. In this important decision, not being able to participate in your community is likely to cause the project to fail and force the user to leave. Keeping a close relationship with the community, using their feedback and suggestions, at least considering their recommendations, is a smart choice. So you will be closer to success. (Compile: Chen)