Posted by romasha 2 years 48 weeks ago

The centralized nature of wikis can transform your human resource department in a multitude of ways. The human resources department can utilize a business wiki in maintaining an up-to-date employee handbook, dispensing information about health plans, or making general office announcements.

For our purposes we'll focus on the document every company, large or small, has - the employee handbook. In all successful organizations, the employee handbook goes through several "rough" drafts before it is ever presented to employees. In addition to the final draft, updates are also made over time as company policies, dynamics, and needs change. The responsibility of the employee handbook rarely falls on one individual and is typically the responsibility of a core team in the human resource department. For this reason, we strongly suggest the use of an enterprise wiki to build and maintain employee handbooks (and all documents that are constructed collaboratively). Following are some of the advantages:

Collaboration is the key

Corporate wikis allow your HR department to see the changes being made to the employee handbook instantly. There is no need to wait on documents being passed and received via email, individual updates, or time spent working on collating the updates. Each contributor has access to the handbook, therefore work can be done collaboratively, faster.

Instant updates

No longer do you have to wait for typo or phrase corrections or updates that need to be made instantly. Each contributor can make changes when needed, ensuring a consistent document is presented to all viewers.

Reduce time wasted

It's rarely discussed how much time is wasted waiting on email responses. By managing the employee handbook with wikis, employees can ask non-confidential questions, get clarifications or suggest improvements through the comments. Anyone from the HR team can respond to the questions with appropriate answers. Another employee with a similar question, will already have her answer through the comments. This drastically cuts down on repetitive questions emailed to HR staff and time wasted in finding the right answers

Multiple inputs allowed

Getting the final document "perfect" takes contributions from several knowledgeable sources. The comments, questions and suggestions present in the form of discussions on the employee handbook wiki, act as direct inputs for the HR team to know what needs to be updated. Experts from the HR team can collaborate on the document to chime in without slowing down the overall flow of progress.

Reuse information

Reinventing the wheel always uses time that could be better spent on other tasks. By reusing information future versions can easily be created from old, trusted knowledge.

Easy access for daily reference

Publishing the employee handbook on the wiki provides employees with an up to date version while reducing confusion about which version of the handbook is the latest and refer to it for daily usage.

Final product faster

The above reasons are why it is highly recommend to incorporate wikis into the HR department's game plan. One major benefit of using wikis to manage the employee hand book is that your final product is completed in less time, which benefits your company in a multitude of ways (time, costs, and productivity are just the beginning).

If you are looking at implementing an enterprise wiki software for your company or HR department, see how Cyn.in can help you build a secure collaborative environment.

Views: 6,076, Comments: 0

Posted by romasha 3 years 4 weeks ago

For most successful businesses, the sales process can take a sequence of communications before the customer finally commits. From the initial contact to closing the deal, the more information your sales team can harness, the better the chances are of success.

sales wiki

One major component of the sales process is the creation of the sales proposal. Even though every client's proposal may start out with a template that includes some generic jargon that relates to all clients, successful sales proposals need to cater to specific client needs and they need to address the information gathered during each phase of the sales process. Starting with the initial client contact, sales teams can use company wikis to create client-centered, accurate proposals that can be updated iteratively by the sales force.

At each level of the sales process, your sales team can build upon previously entered information and can collaborate effectively using a single document as the foundation for discussions. The end result are higher quality proposals that addresses the client's concerns and needs simultaneously, are refined throughout the hierarchy, and facilitates collaboration throughout your sales team from start to finish.

Using collaborative wiki software for the sales process enables the following advantages:

  • Reduces confusion on the proposal versions by notifying collaborators of updates and by presenting those updates in real time.
  • Reduces proposal development time by allowing collaborators to work on the document simultaneously. This means that time spent waiting on emails and proposal updates is eliminated completely.
  • Incorporates remote contributors with ease by allowing anyone with permission to access the sales proposal, can add their feedback to make it more accurate.
  • Improves the quality of the final proposal by using a team of experts working to close the deal.
  • Increases your company's overall success rate by catering to each potential client while reducing the stress of your sales team.

If you would like to get started with a sales wiki or learn more about using Cyn.in for your sales teams, contact sales or check out the live demonstration.

Views: 4,468, Comments: 0

Syndicate content