Posted by romasha 3 years 3 weeks ago

Wikis, like those used to power the "The Free Encyclopedia" Wikipedia, allow for the easy creation and editing interlinked pages via a web browser using user-friendly text editors. Enterprise wikis, are a great way to harness your organization's collective brain power and talents. Based on our experience of deploying Cyn.in in enterprises, listed below are some of the myths that we have encountered and demystified for our customers: 

Collaborative document editing with Enterprise Wikis

Myth #1 - Wikis pose a a security threat to my organization.

Today's wiki software incorporates several security features that make them secure virtual work areas. Not only is it easier to protect pages to viewers external to the organization, but it's also simple to protect pages to those internally. Pages can be grouped and secured, or secured individually at the press of a button.

Myth #2 - Wikis motivate employees to contribute content.

We'd love to think that the ability for an employee to contribute content "makes" an employee want to contribute, but it doesn't. One of the notions that comes up is that some of the people are afraid to share their knowledge in a collaboration system. This is because they think that if they share their knowledge, they will be no longer valuable to the orgnization and will be an expendable resource! On the contrary, the more a person shares, the more valuable they become to their organization. Why? Because others in organization will be aware of their expertise and are more likely to come to them for information. They become the "Go-to" experts.

Myth #3 - My company is too small to be able to take advantage of wikis.

Wikis aren't about company size, they're about the content that is contained within the organization. If your company has any content that more than one employee is expected to have access to, then a wiki is the perfect enterprise collaboration software for your company. Not only do wikis solve the "access" problem, but it also solves the "consistency of material" problem that plagues so many organizations.

Myth #4 - Employees know how to contribute.

It is important to seed a wiki to everyone started. Users need guidance to start contributing and a strucutred wiki defines a purpose. Start with a loose structure and modify content over time to define how the wiki is organized. Encourage contributors to add their own content in wikis and determine how to tie the wikis together stucturally once you understand how the content is shaping up.

Myth #5 - Wikis always provide the information employees need.

Wikis can only supply what you have designed it to provide. Proof of concept, through wikis such as Wikipedia, show that wikis can be as powerful as you make them. Adding useful content to the wiki should always be one of the main purposes of the wiki. Users should be encouraged to add information without worrying about making it perfect or polished.

Business Wikis, through a collaborative effort, enable creation of resources that are superior to anything that could be accomplished alone. If you are looking at implementing an enterprise wiki in your company, see how Cyn.in can help you build a secure, collaborative environment.

Views: 8,971, Comments: 0

Posted by romasha 3 years 8 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: 6,637, Comments: 0

Syndicate content