User collaboration is the magic weapon of information technology in the 21st century. Some companies are now aware of this and are moving quickly to implement better collaboration practices. We will learn that the enterprise wiki is part of the ideal solution for this effect. What corporate challenges need to be addressed by corporate wikis? Improve staff capabilities and integrate cutting-edge knowledge in recruiting \/ training all staff to match the business world and agility. Building a consistent enterprise wiki with well-documented processes and providing services to customers is essentially the memory of modern enterprises. It can serve as a reservoir of all knowledge and become the most valuable resource for enterprises in 2020, second only to people. Bran was king for a reason. He is the memory of the world. The
Now let’s talk about how to plan and implement enterprise wikis. This article will help you access, plan, select, implement and maintain enterprise wikis in 2020. Enterprise wiki program: enterprises or key enterprises also have many activity parts \/ decision makers. Therefore, we need a comprehensive plan to implement the enterprise Wiki and use practices to improve it. There are several planning methods according to employees’ productivity, influence on happiness and return on investment, preference for risk-taking and management style. Top down approach: plan and implement the knowledge management of the top team and top management, and work from top to bottom. This is probably the most difficult to achieve, especially in creating cultural change. Top down approach: start from yourself, expand to the team, expand to the team group, and so on. This is also easy to achieve in large enterprises. Isolated team access: select the team, you, or your following teams to experiment with and expand knowledge sharing and knowledge management principles. If you have a team full of energy and enthusiasm in the new attempt, or you have a team full of leadership style, you’d better start from here. Isolated project method: select a project and set up a knowledge sharing process for the project that all relevant personnel must follow. If you have a new project to start and can use it to bring about cultural change, it will work well. Enterprise wiki realization: 1) cultivate wiki culture: in the androg planning method, we know that your vision to realize the knowledge sharing system based on enterprise knowledge is culture. The
I’ll tell you what to consider. Management support: obviously, management support is needed to implement large-scale efforts to change the way the company works. As mentioned earlier, you can discuss pilot projects initiated in a top-down, team, or project approach with management. When they see the offer, it will help them move forward. Reward: reward should be provided for anything that people need to pay attention to. For those who produce the best content for the company’s wiki site, including bonuses and reviews is unprecedented. The
However, rewards must be provided for correct measurement items. Good indicators: click through rate, reader group and reference \/ use times are good indicators. Invalid indicators: number of words created \/ length of video (for video content), number of articles \/ videos published. Recognition is also a good bonus. Collaborative style: the larger the wiki, the more important it is to maintain the quality of the content. Old documents are not worth the loss. This is why special attention should be paid to how to set up collaboration. Here are some ideas for role collaboration: Topic recorder participants edit audience employment policies: employment policies should also reflect the need for a more cooperative culture. The
The era of taking talent as the first standard has passed. Humility is now the key factor. Modest enough to learn from others, others
Find a generous person who can teach and share. Open policy: an open culture is a necessary condition for prosperity in the knowledge economy. Enterprises should make efforts to this end and take it as a part of culture. From the top to the top: if the people at the top don’t accept this culture, it’s useless. If you are a person at the top, please give up your fear and accept the culture of openness and cooperation. You are the boss. It doesn’t matter if you don’t know everything. It doesn’t matter if you don’t know everything. The
You can learn from those who want to help you. They can also teach each other, so it doesn’t matter. 2) The second most important thing to pay attention to is to realize the best platform for wiki. Factors to be considered include: Integration into existing workflows: if people and teams can integrate well with existing workflows, it is much more likely to adopt enterprise wikis and knowledge sharing processes. The less homework, study and cumbersome courses, the higher the adoption rate. Cost: you must also find a viable solution based on the allocated budget. Here is one. The
Accessibility: the company’s wiki must be able to access any location where the team and personnel are located. Unless you have very sensitive data, you must allow the Internet, all devices, browsers, etc. to access the company wiki. Ease of use: adding, editing, and queuing km content must be simple and user-friendly. Technical requirements: are there a large number of concurrent users? Are there many documents to maintain? Pay attention to the requirements in the technical field. 3) Support user participation: in addition to creating a culture that integrates wiki use into the authorization of all individuals and teams in the organization, other steps should be taken to actively involve people in the organization in these efforts. The
User training: training users through wiki video \/ content, one-on-one conversation, group conversation, etc. Feedback: receive users’ feedback on content quality and knowledge sharing effect, and measure participation. Feedback can also be achieved by allowing users to evaluate, comment on, share, and connect to documents. 4) Maintenance: I know that old documents are more harmful than useful, so I need to plan to maintain wikis. Pruning: the technique of pruning is to know when to delete what, what to change, and what to leave behind. You can access the cleanup using content unreal when a particular document is unused or updated. Or, monitor which parts of the process have changed recently. The
Discipline: wikis need discipline. Make sure you have it and assign resources \/ people to perform as needed. Use measurement item: measure all the contents to be improved. Maintenance objectives: set specific objectives for maintenance, including click through rate, session time, number of references, process or support ticket usage, latest articles, maximum participants, queue managers, etc., and measure the success rate of maintenance activities. The goal may be to improve the freshness of articles, increase the use time of wikis, and improve the use of processes. 5) Method of composing Wiki: Male
Understanding how to organize information is similar to understanding how to organize employees. a) Domain knowledge structure: Elon Musk of reddit AMA said: \
You can use multiple projects as a parallel configuration method. The
c) Frequency of use: according to the frequency of use, there is a need for an easy way to obtain information. Helpiekb provides the ability to do this. d) Layering: to reduce information complexity, you can use multi-level layering to organize dense topics. If you want to implement such an enterprise wiki, it is recommended to use the text printer’s own wiki plug-in helpI KB (helpie KB). Helpiekb is a wiki plug-in for WordPress. It integrates with other plug-ins and topics. Without it, you can almost create a powerful and customizable enterprise wiki at an amazing cost. If you are new to the WordPress world, a guide on how to use WordPress and helpie to create wiki sites will be useful. Free use of helpie
