Existing Systems & User Engagement
Why not using an internal wikipedia or repertory for employees to upload their interesting files?
Most employees are reluctant to share their files and knowledge because it takes and because they don´t see who will use it. This is why knowledge sharing systems are not up-to-date and only used by 14% of employee on average (according to PwC). On the other hand, when the request for sharing is coming from a particular employee, it becomes very hard to refuse to share.
Why not using a classic Q&A tool?
In classic Q&A, questions are not directed to specific people with answers but to large communities of people, making it easier to avoid answering. If the request is to a specific coworker who has the expertise and knowledgeme, it becomes almost impossible not to answer.
Technology & Implementation
How does Elqano know who is working on what and when?
Elqano uses custom enriched taxonomies, natural language processing and machine learning algorithms to automatically tag documents and correlate employees on a daily basis. With previous customers, Elqano was able to prove that its algorithm was correct 88% of the time.
What about data safety and connectivity?
Our team proposes two installation options: on the cloud hosted by AWS with SSO or directly installed on our client servers with containerization, both options are completely secured and safe. We can synchronize with SharePoint via REST API, with Shared Drive via a customer connector or with any kind of system upon request (G drive, Box, Salesforce …)
How long does it take to set up and implement the system?
Our team can implement the system in less than a month: we estimate one week for business mapping to prepare the taxonomy and map the existing systems, one week for set up and installation, two weeks of testing and adjustment before going live.