KAI: Difference between revisions

From Secure Group Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 8: Line 8:
* [[Android Development]]
* [[Android Development]]
* [[System Administration]]
* [[System Administration]]
* [[Automation QA]]
* [[QA Automation]]
* [[Quality Assurance]]
* [[Quality Assurance]]
* [[Product Owner]]
* [[Product Owner]]
* [[Digital Marketing]]
* [[Digital Marketing]]
* [[Community Management]]
* [[Community Management]]
* [[Design]]
* [[Graphic Design]]
* [[WebSite Development]]
* [[WebSite Development]]
* [[Enterprise Sales]]
* [[Business Development]]
* [[Support]]
* [[Support]]
* [[Product Marketing]]
* [[Product Marketing]]
* [[UX Design]]
* [[UX/UI Design]]
* [[Technical Recruitment]]
* [[Technical Recruitment]]
* [[Accounting]]
* [[Accounting and Finance]]

Revision as of 10:08, 8 October 2020

As mentioned in our Knowledge Management strategy In order to measure, manage the existing knowledge in the company and to promote accountability we created a Knowledge Accountability Index also known internally as KAI. The index is divided into 4 categories:

  1. General Knowledge – this is about understanding the basic functionality of a tool/software/platform that is not part of your position’s specific knowledge, but you need it to be able to communicate with other teammates on projects and tasks. It is something you should learn and understand by yourself.
  2. Specific Knowledge – this is regarding in-depth understanding and usage of a tool/software/platform that directly affects your performance within the company. Employees should grow specific knowledge and skills on their own, while the company will provide context on the application of the tool/software/platform within a defined process.
  3. Secure Group Knowledge – this is all about understanding the company’s strategy, products, and processes
  4. IT Knowledge – this is about understanding technology and also business people understanding basic IT concepts

To access the KAI of each framework, refer to the relevant page: