vci-ebm-papst-knowledge-management provider logoOpen for submissions

Knowledge Management: Making Employee Expertise Visible

ebm-papst is seeking a solution that creates transparency on the expertise and experience of its employees across all global sites. Employees share their know-how with minimal effort and retain control over their data, enabling fast identification of the right internal experts. The solution will be validated in a Venture Client PoC.

#KnowledgeManagement#ExpertiseDiscovery#VentureClienting

Context 

ebm-papst operates globally with sites and teams in Europe, Asia and the Americas. Within R&D, a dedicated knowledge management function is responsible for the methods, tools, formats and processes the company uses to manage its knowledge. 

Much of this knowledge is tied to people: what employees have worked on, which topics they dealt with in earlier projects, and the reasons behind past decisions. This knowledge is particularly relevant for: 

  • Product development: understanding which ideas were explored in the past and the rationale for pursuing or discontinuing them 
  • Staffing of new or cross-functional projects: identifying employees who can contribute, even if their current role does not indicate it 
  • Onboarding and cross-site collaboration: identifying relevant contacts without an established personal network 

Every employee has an intranet profile today, but it only shows data from the HR directory and cannot be extended with experience or expertise. For R&D, there is an expert database listing officially appointed experts, as well as former experts who can still be contacted as backups. It has been in use for about three years (previously an Excel list), is maintained manually and only covers this group. 

Problem Definition 

ebm-papst currently has no way to make the broader expertise of its employees visible and searchable. The main issues are: 

  • Expertise is not visible: Experience from earlier projects, roles or employers is not documented and is unknown to colleagues. 
  • Profiles are static: Intranet profiles only show HR master data and cannot be extended by employees. 
  • Limited coverage: The existing expert database only includes officially appointed R&D experts and has to be maintained manually. 
  • Dependence on personal networks: Access to expertise relies on personal contacts, which is limited across global sites. 
  • Maintenance effort: Solutions that require employees to spend a lot of time documenting their background are unlikely to be used. 

The company is not looking for a digital twin of its employees or a comprehensive knowledge base. The objective is to create transparency on internal expertise and to enable targeted networking between employees.