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,019, Comments: 0

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

Posted by dhiraj 3 years 1 week ago

Cyn.in 3.1.3 release is now available. This is a bugfix release. Major changes in the translation mechanism are included, please read the notes in the Translations section, for more info. Cyn.in Community Edition users should read the note on removal of legacy products before upgrading their Cyn.in instances.

Key Fixes

  • The "Who" section of an Event item when viewed singularly was not coming up when only the Attendees field was filled. It would not show up unless the Contact Name field was also filled - the section now shows up correctly.
  • Downloading of only .zip files was broken only in IE8. Any zip file when downloaded from Cyn.in in IE8 would show as a corrupted download, while it would work in all other web browsers. Fixed.
  • Discussion URLs will now be much shorter, maximum width is now reduced to 80 characters. Note: This will affect only new discussions, old discussions' URLs will continue un-changed to preserve existing links. This feature has been requested in the Cynapse Community, by @everythingability, @ybizeul and others.
  • Plone base has been upgraded to latest stable version, Plone 3.3.5.
  • Proxy Server Support: HTTP Proxy server support for Internet connections has been tested and fixed to work correctly for update checking and future server-side Internet features.

Minor Improvements

  • Recycle Bin now directly shows Manage Contents view, this allows bulk management and can be used to delete all items, in an easier way.
  • Performance improvements: Minor performance improvements and deprecated methods removal is included in this release. Cyn.in server startup time has improved, and you should hopefully see faster page-loads. We are continuing to work towards improving performance, stay tuned for more updates.

Translations and Community Contributions

This release brings many changes in the translation and i18n front. We have finally been able to shift to the locales folder based layout for translations files. This is the recommended way of including translations in products and allows Cyn.in to choose the correct translation to load without depending upon (potentially) incorrect values in language file headers. We have also switched to using tagged svn versions of translations - every Cyn.in version from now on will have a concrete translation version, to rule out update mishaps from untested translations. Salient points:

  • Updated French, Italian and German translations. Community Contributions section, below, has notes.
  • New translations layout: The i18n folder in <buildout>/src/ubify.policy/ubify/policy/i18n has been replaced with <buildout>/src/ubify.policy/ubify/policy/locales.
  • Space selection dropdown list in quick adder bar will now respect unicode characters in Space names. This has been tested to work properly with Cyrillic and other non-English languages.
  • New translation strings: There are new translation strings available, we have added missing i18n translations for places reported by the Cyn.in Community. More strings are going to be added soon.
  • Translators should now consult the Cyn.in Translations Wiki pages before commencing work on translations. From now on, which branch of the subversion checkout you work on will matter, we will no longer be using CyninTranslations trunk for translations files.

Community Contributions

  • LinguaPlone: Cynapse Community user @millie contributed a patch to make Cyn.in work better with the Lingua Plone product, which allows each content item to be written in multiple languages and shows the appropriate content to visitors based on their selected languages. This fix has been included in this release, thanks @millie! :)
  • New translators/languages are always welcome! Community user @ybizeul has contributed a French translation. Redomino s.r.l. have contributed an Italian translation. Both new translations have been included in this release.
  • Thanks go out to @gogobd, @mdebusfor updates on the German translation, included in this release.

Removal of Legacy Products

For maintainability reasons, several non-used plone products have always been included in Cyn.in releases. These legacy / non-used products have now been removed from the Cyn.in buildouts and are no longer included. The following products have been removed:

  • kss.plugin.jquery  - This product was internally used initially in early 3.x versions for bridging KSS and jQuery, but was unused in subsequent public releases
  • Products.Ploneboard - Only used in legacy (Pre Cyn.in 2.x deployments)
  • Products.PloneFlashUpload - Only used in Cyn.in 2.x deployments
  • python-cjson - has been replaced with jsonlib which provides better Unicode support for JSON
  • archetypes.schematuning - has been removed, it is now included in archetypes.schemaextender with caching.zcml flag
  • collage - Only used in legacy (Pre Cyn.in 2.x deployments)
  • clouseau - Only used in development

Potentially this can be a breaking change for existing installations, especially if you have installed any of these products and left them installed or in limbo. When the new Cyn.in update is applied to your Cyn.in instance you may run into problems if you fall into these cases. We recommend at the least manually uninstalling any of the above products if you had them installed prior to installing the update. If you are unable to get the Cyn.in 3.1.3 update to work properly on your existing installation, please start a new discussion on Cynapse Community. This problem only affects existing installations, new installations should remain unaffected. Please test the update on a test system if you are running a production Cyn.in and want to upgrade to the latest.

Links

Cyn.in Server Download page on Cynapse.com: http://www.cynapse.com/downloads/cynin-community-edition

Subversion Tag Checkout URL: http://odn.cynapse.com/svn/cynin/tags/cynin_3_1_3

Source Code Snapshot URL: http://odn.cynapse.com/attachments/download/127/cynin_3_1_3-source.zip

Closed Issues Log: http://odn.cynapse.com/projects/cynin/issues?query_id=13

Views: 4,936, 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,434, Comments: 0

Posted by romasha 3 years 5 weeks ago

Imagine a world where your customers handle the bulk of your customer support issues, gladly sell (and upsell) your products, and identify any problems your products or services are having before a crisis occurs. Through the use of web community software, you don't have to imagine this any longer.

Customer Community

According to a survey by Deloitte, the greatest value of online communities is they increase word-of-mouth (35%), increase brand awareness (28%) and increase customer loyalty (24%). Every company knows that word of mouth advertising is the strongest form of advertising available. Regular people telling regular people about the benefits of your business will go farther than some of the largest marketing budgets. With the popularity of social networks such as Facebook, Twitter, and Myspace, savvy businesses are eagerly taking notes on how online communities can increase sales, marketing ROI and customer satisfaction.

Customer support can be one of the most challenging aspects of any business. With information traveling at the speed of light, disgruntled customers can quickly become negative online billboards when their concerns are not promptly addressed. Online communities allow others to shed light on customer concerns before they become real issues. When you allow satisfied customers to provide advice, aid new customers, and share their experiences through an online community, you can often times avoid PR nightmares that may spawn otherwise.

Online communities can also help to alleviate costs and decrease staff workload in this area. Communities focused on facilitating peer-to-peer support can deliver a customer service win-win by not only lowering support costs but by also by responding more rapidly than your customer support team may be able to. When calls that would typically be handled through the higher cost phone channel are deflected to the community your customer support staff can focus on improving current products and services while avoiding having to answer the same questions repeatedly.

Online communities foster an organizational culture centered on customer-driven innovation and co-creation. Engage employees who would not normally interact with customers - people from shipping, logistics, purchase, finance or HR and make them customer ambassadors.  They can take back a customer centered viewpoint to their departmental colleagues. As a result, the organization as a whole gets closer to the customer than even before, inturn inspiring the staff to adapt.

By adding an online community to your organization's current means of satisfying customers, you will not only increase customer sastifaction, reduce overall costs, and improve the productivity of your support staff, but you'll gain valuable salespeople in the form of every customer's favorites sales reps - their peers.

If you wish to setup an online community for your company and would like to understand how Cyn.in can help, leave us a message. The Cynapse Community is an excellent example of how Cyn.in is being used to power an online support community.

Views: 2,697, Comments: 0

Syndicate content