Knowledge Management: Difference between revisions

From Secure Group Wiki
Jump to navigation Jump to search
 
(54 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''The Secure Group knowledge management strategy enables our organization to create, apply, and share information, breaking down silos and increasing the usage of valuable data.'''
'''The Secure Group knowledge management strategy enables our organization to create, apply, and share information, breaking down silos and increasing the usage of valuable data.'''
</br>
</br>
</br>


It's a no brainer that knowledge enables us to grow and innovate. But, it's a fact also that this is easier said than done. Before we reached our ideal Knowledge Management strategy, we faced some problems:
In Secure Group, we developed a culture in which people feel independent and autonomous when working. We believe traditional rigid management structures do not create a supportive environment, but cause unnecessary stress and distracts employees, which jeopardizes performance. Because of that, we respect our people's skills and knowledge and support them to pursue the company’s goals in their own way. This mutual respect between parties is essential to our Knowledge Management strategy and we can only afford this level of trust in our people if we know they are fully capable of doing their work and can fill any knowledge gaps quickly and efficiently.


* It was inefficient when serving only individuals: Information needed by many was often shared from individual to individual in conversation or email.
It's a no-brainer that knowledge enables us to grow and innovate. But, it's a fact also that this is easier said than done. Before we reached our ideal Knowledge Management strategy, we faced some problems as the old way we managed information at Secure Group was inefficient. Information was shared in a fragmented way, through email and messaging apps. When people needed information, they’d go to an expert and ask them, which not only wasted time but would only benefit one person. It was difficult for the person to retain the new information, especially if it was shared in passing conversation or buried among emails. The process was also not being overseen, so embellishments and inaccuracies could slip through, which could jeopardize the information. Finally, when a knowledge gap formed, we had no way to fill it, as the one-to-one nature of knowledge sharing was impossible to scale, and the gap would remain.
</br>


* It was repetitious and time-wasting: Often a few Subject Matter Experts are heavily relied upon to verbally provide information, and they spend their time repeating the same information rather than doing value-added work.
After learning from these past mistakes, we then decided where knowledge should NOT be. We realized our knowledge should be easily accessible by our employees. It should not be stuck in someone’s head, where it is of no use to anyone but the person - it would even be unhelpful since people would constantly interrupt their work with questions. It should also not be chaotically thrown around emails and messages, where it is impossible to track and collect. Nor should it be dumped in guides and manuals and be forgotten about, becoming obsolete and misleading.


* It was impermanent so ineffectual: Research shows it is difficult for people to retain information, especially when it is transferred verbally.
To ensure the effectiveness of our knowledge management strategy we also defined knowledge sharing as criteria in the Levels of our Frameworks so to progress with us, individuals must demonstrate the capability of sharing knowledge in a structured way.


* It had no accountability or control: When no one was held accountable, the data shared could be inaccurate and out of date, and this was a problem that was difficult to fix.
= Knowledge Categories =
There are three basic forms of knowledge to consider when it comes to knowledge management: explicit, implicit, and tacit. Knowledge management is such a complex process that there are numerous terminologies, solutions, and techniques. Knowledge-driven businesses like ours have the advantage to drive efficient business activities by applying readily-available knowledge from a comprehensive, well-managed knowledge base. Knowledge in a business setting refers to the development of an organization's abilities, experiences, capabilities, and insight.
All this is created, managed, and stored in the form of explicit knowledge, which is the focus of Individual Contributors, and tacit knowledge, which is the manager's focus.


* It was a self-fulfilling prophecy that recurs: The knowledge transfer process stopped when the information was shared, but the knowledge gap still existed in the wider organization, leading to problem recurrence.
[[File:KNOWLEDGE.png|500px|center]]
</br>
</br>
To make it clearer, we separated the data and information into Extensive Knowledge, Realms Knowledge, and Secure Group Knowledge.


And after learning from our past mistakes, we then decided where knowledge should NOT be:
== Extensive Knowledge ==
Also known as KAI of the framework, this is about understanding the usage and configuration of a diverse set of tools/software/platforms, languages, protocols, etc. which affect your performance within the company. They are related to the scope of your position and employees should grow this knowledge and hard skills on their own, while the company will provide context on the application of the tool/software/platform within defined processes.


* In inaccurate published content: Information may be published in manuals or on the intranet, and this may be outdated, inaccurate and hard to find, wasting time. 
== [[Secure Group Knowledge|Secure Group Knowledge]] ==
This is all about understanding the company’s products, the processes and tools/software/platforms related to their execution, the way all teams work, the concepts that are part of their scope, and how they contribute to the overall corporate strategy. It includes technical knowledge for non-technical people and business knowledge for technical people. For this category of knowledge, we provide pieces of training because this way we can ensure that everyone has the complete knowledge set to be a high-performer in our company.


* In somebody’s head: Information only held in someone’s head is only of use to that person. Worse, they will be interrupted frequently with questions about it.  
[[File:Problems-Solution.png|800px|center]]


* In the cloud: Information may be recorded informally such as in emails, but this too is hard to find and often badly explained.  
== Realm Knowledge ==
We have categorized the concepts that are present in our business and operations into domains of knowledge or activity. When addressing business leadership, each management framework requires proficiency in one or more of such domains, which are called Realms. You can check them all [[Realms|here]].


We also knew that each of the generations has a different way of learning, advancing and collaborating. We recognized this by sharing knowledge in two formats. These are reading and face to face courses with a practical application.


Knowledge sharing is also built into the Levels in our Framework. To progress, individuals must demonstrate the capability of sharing knowledge in a structured way and the capability of applying Tech Sessions.


We share knowledge through our internal wiki Confluence. Our wiki acts as a single source of all knowledge for our organization which can be created, edited and modified by any employee.
Another thing we realized is that person has different ways of learning, advancing, and collaborating. We recognized this and decided to share knowledge in two formats: reading and face-to-face courses with a practical application. Therefore, we share knowledge through our internal wiki Confluence and through our Learning Day.
Confluence functions as a central repository for managing and distributing all company knowledge and information. Here, all co-workers can store internal documentation about company policies, processes, how-to guides, projects or products they are building, common workflows, procedure checklists, and more.


In our Management Model and structure of the Career Framework, we are currently assessing knowledge regarding the following categories:
= Confluence =
</br>
Our wiki acts as a single source of all knowledge for our organization which can be created, edited, and modified by any employee. Confluence functions as a central repository for managing and distributing all company knowledge and information. Here, all co-workers are responsible and accountable for storing internal documentation about company policies, processes, projects or products they are building, common workflows, procedure checklists, and more.</br>
* General Knowledge: a list of indispensable software, tools, platforms and more, for Secure Group, that employees need to know (it can be a little bit out of the scope of their position). If it’s an item described in this category, employees should learn the subject matter on their own and share their knowledge amongst the company. We will provide context on the application of the tool/software/platform within a defined process.
We currently have [[Team_Management#Department|Departments]] spaces composed of standard operation procedures, playbooks, how-to-guides and processes documentation, [[Team_Management#Team|Teams]] spaces composed of operational artifacts and [[Team_Management#Division|Divisions]] spaces hyperlinking all the content.
* Specific Knowledge: a list of concepts, tools, software and etc., that are indispensable for them to develop under the scope of their position. If it’s an item described in this category, employees should learn the subject matter on their own and share their knowledge amongst the company. We will provide context on the application of the tool/software/platform within a defined process.
* Secure Group Knowledge: a list of products, company profile and features that they need to know in order to succeed in Secure Group. It’s part of the Learning Day.
* IT Knowledge: a list of essential concepts that we consider to be basic for our Frameworks and that we expect employees to master. It’s part of the Learning Day.
</br>
== Learning Day ==


The Learning Day is our knowledge-driving initiative and it occurs on the last Tuesday of each month. It is a whole day dedicated to Learning. We start with breakfast at 9h00 filled with brain booster food and after that, we start the training according to the following formats:
= Learning Day =
The Learning Day is our knowledge-driven initiative and it occurs on the last Tuesday of each month. It is a whole day dedicated to Learning. We start with breakfast at 9h00 filled with brain booster food and after that, we start the training according to the following formats:
* Tech Challenges: consist of a presentation with an instructor that will act as a facilitator for the employee to assimilate the knowledge. After the training, employees receive a Tech Challenge to prove that they are capable of completing tasks relating to what they just learned.
* Tech Challenges: consist of a presentation with an instructor that will act as a facilitator for the employee to assimilate the knowledge. After the training, employees receive a Tech Challenge to prove that they are capable of completing tasks relating to what they just learned.
* Tech Sessions: consist of a collaboration activity or open format seminar. It can be given by an external training and it also comes with a task to be completed that varies from topic to topic.
* Tech Sessions: consist of a collaboration activity or open format seminar. It can be given by an external trainer and it also comes with a task to be completed that varies from topic to topic.


=== Subjects that we provide training ===
After the completion of a training session, you will receive a challenge to prove you are capable of completing tasks related to what you just learned. They are usually short exercises to test you. 
* Secure Group Knowledge because it's an internal category and it affects the KAI of every position. We provide training regarding our products and Management Model.
* Processes defined in the RACI, because it's internal knowledge and it affects the Level Chart of every position.
* Basic IT Concepts for non-technical people and Basic Business Concepts for technical people, because it provides Context regarding our industry.


Please note, if you attend training regarding some of these topics you need to score a grade 3 in the KAI related to the topic.
= Knowledge Accountability Index =
 
Secure Group is all about accountability: and that includes accountability in knowledge. Once information is systemized and available to all, it becomes measurable and this allows it to be considered within the employees’ performances. In order to manage the existing knowledge in the company and to promote such accountability, we created a Knowledge Accountability Index a.k.a. KAI.
=== Subjects that we don't provide training ===
We don't provide training regarding topics that belong to Specific Knowledge or General Knowledge of any framework. We understand that this should be developed by our employees on a daily basis and it's a good practice that shows adherence to our value "Devotion to Learning" shown in the Culture Code.
 
=== What's like to be a trainer/trainee in Secure Group?</br> ===
Knowledge sharing it's part of the Levels in our development path. In order to progress, employees must demonstrate the capability of sharing knowledge in a structured way and applying Tech Sessions.  
</br>
</br>
[[File:Trainer_trainee.JPG|center]]
=== Responsibilites ===
{| class="wikitable"
! style="text-align: center; font-weight:bold;width: 33%" | Instructor's responsibilities
! style="text-align: center; font-weight:bold;width: 33%" | Manager's responsibilities
! style="text-align: center; font-weight:bold;width: 33%" | Management Model Expert's responsibilities
|-
|
* Plan the sessions carefully in advance.
* Prepare the material for the Session.
* Prepare the Session/Challenge before the training.
* Complete sessions neatly, promptly and correctly
* Inspect all equipment and classroom in advance.
* Arrive for the session on-time and prepared.
* Never mock or make fun of a student in or out of class.
* Answer any questions thoughtfully.
* Apply received feedbacks
|
* Assign trainings (Challenges or Sessions).
* Approve/disapprove the content/format.
* Create new sessions requests.
* Evaluate each training accordingly to the Seniority of the position.
* Assess the subordinates KAI based on the trainings.
* Create content and provide Tech Sessions/Challenges as an Instructor.
|
* Set up training in LMS.
* Set up Tech Challenge in the platform.
* Provide insights to managers regarding the performance of instructors and students (match with the KAI and Levels assessment)
* Score the Tech Challenge and provide the results.
* Manage Feedback forms.
|}


== Knowledge Accountability Index ==
To help us measure competency in a skill, the index describes the grades of everyone’s ability and competency in a specific occupation. It is separated into six grades, each outlining the capabilities and value to be delivered by the person, and allowing them to plan their learning journey. These range from “Fundamental awareness” to “Expert”. The index can be used by an individual to compare their current level of proficiency to top performers in the same occupation and it enables us to:
We already established that we keep “good” processes that promote accountability. The same applies to knowledge. In order to measure, manage the existing knowledge in the company and to promote accountability we created a Knowledge Accountability Index aka KAI
</br>
The KAI is an instrument used to view everyone’s ability and competency in a specific occupation. It also measures all the technical skills and knowledge sets a person needs to progress. The KAI is divided into four categories: General Knowledge, Specific Knowledge, Secure Group Knowledge, and IT Knowledge.
</br>
The index captures a wide range of abilities and organizes them into five grades. These range from “Fundamental Awareness” to “Expert”. The index can be used by an individual to compare their current level of proficiency to top performers in the same occupation and it enables us to:


* Centralize effort to understand technology trends from a holistic view
* Centralize effort to understand technology trends from a holistic view
Line 104: Line 57:
In Secure Group, the effective management of knowledge aids competitive advantage. When people are accountable for knowledge it can be shared more efficiently and productively. We have put in place systems and good processes to achieve this so armed with knowledge, our employees are better able to innovate in their work.
In Secure Group, the effective management of knowledge aids competitive advantage. When people are accountable for knowledge it can be shared more efficiently and productively. We have put in place systems and good processes to achieve this so armed with knowledge, our employees are better able to innovate in their work.


=== Company Knowledge Centricity Level ===
== Knowledge Grade Description ==
Our current situation is represented by  '''Grade 1''' and '''Grade 2''' depending on of individual and department.
</br>
</br>
'''Goal'''</br>
'''Our strategic goal is to achieve Grade 3 till spring and Grade 5 by next year'''
</br>
</br>
{| class="wikitable"
!colspan="5"|'''Secure Group Centricity Grade'''
|-
!rowspan="1"| '''Knowledge Centricity Grade'''
!'''Grade Description'''
!'''Capabilities'''
!'''Value Delivered'''
!'''Knowledge Footprint'''
|-
!rowspan="1"| '''Grade 1'''
|Inability to generate actionable knowledge
|
* Required skills not existent internally.
* Lack of organizational will.
* Focus only on basic transactional functionality.
|Understanding on an ad hoc, post-mortem basis as to why it happened.
|Little Knowledge infrastructure.
|-
!rowspan="1"|'''Grade 2'''
|Knowledge silos within the organization.
|
* Business unit / function-centric knowledge creation.
* Lack of vision to action / compete on knowledge.
* Little or no information sharing across business units/functions.
|Understanding of business and issues which must be addressed to improve individual business units/functions.
|Analytical resources embedded in local functional teams.
|-
!rowspan="1"|'''Grade 3'''
|Aspire to leverage knowledge.
|
* Desire to leverage knowledge driven from the top.
* Efforts underway to integrate / better understand internal knowledge capabilities.
|Ability to capture current conditions, attempt to understand future trends model in place.
|Local knowledge delivery Model in place.
|-
!rowspan="1"|'''Grade 4'''
|Knowledge-Driven Business
|
* Centralized effort to understand business trends holistically.
* Knowledge creation, capture, and management key driver for people performance.
|Ability to anticipate I adapt to changes in external/internal environments to obtain/retain competitive advantage analytical structure.
|Central enterprise-wide knowledge structure.
|-
!rowspan="1"|'''Grade 5'''
|Industry Knowledge Leader
|
* Knowledge-driven innovation driving business growth.
* Employees are passionate and committed to analytics.
|Generate consistent business value through insights to obtain competitive advantage established analytical processes embedded in over competition organization.
|Well established knowledge process embedded in the organization.
|}
 
==== Why is it failing ====
'''1. Inefficient when it serves only individuals.''' When an employee or a prospect gains information from another person – say, via email or through a conversation, this knowledge has been transferred to a grand total of one person. It takes time and diligence to convey knowledge – and to go through that effort for one person alone is completely inefficient. There are likely dozens, if not hundreds or thousands of other stakeholders who might be in need of the exact same information. That’s a lot of emails or phone calls.
</br>
</br>
'''2. Reckless with employees’ time because it’s repetitious.''' In most cases, stakeholders will get answers and information in a one-on-one conversation. (For instance, an employee asks a colleague a question or a prospect visits the location to talk with a staff member.) This knowledge transfer process is hardly even a process; it’s disruptive and time-consuming. When a handful of Subject Matter Experts are heavily relied upon to provide information verbally, they’re interrupted frequently to answer the same questions over and over by different people – they spend their time repeating the same information when they could be doing more value-added work.
</br>
</br>
'''3. Ineffectual because it’s impermanent.''' According to the latest research, it’s extremely difficult for humans to remember information they learned even just a few days ago. This problem – illustrated in the Curve of Forgetting – is exacerbated if the person learned this information verbally. That’s just a reality of the human brain. So not only was the process to acquire the information time-consuming and wasteful, it wasn’t even effective. The person probably has forgotten some or most of the knowledge and will be forced to seek it out again.
</br>
</br>
'''4. Uncontrolled because no one is accountable.''' A non-existent or ill-thought-out knowledge transfer process means that no one can be held accountable to be sure the information they have is accurate and up-to-date. When managers and company leadership don’t know:
 
* What they need their team to know
* What their team already know and if it is correct
* What their team do not know
* If the accurate information is readily available to all relevant members of the team
No one can hold employees accountable to own the correct knowledge and to leverage it appropriately. This means staff can be wasting time looking for answers, providing incorrect, incomplete, or outdated information to prospects and customers, not following the wrong processes and guidelines – and there’s no proper way to assess their work, correct them, or monitor their improvement afterward.
</br>
</br>
'''5. A self-fulfilling prophecy''' that's bound to reoccur. Though stakeholders may be willing to go to some effort to find and learn the knowledge they need, when the process stops after they’ve got the information they want, the organization misses out on a key opportunity to streamline their process, reduce repetition, and better serve others. Aside from the knowledge giver and recipient, no one else is aware of the gap that existed in the first place – thus, no one can prevent this situation from reoccurring.
 
==== Where knowledge should not be ====
'''1. In previously published content:''' For example, Ivan might dust off his old training manual or search on the company intranet to look for the answer. The problem? This is time-consuming – especially since the information may not even be there, or could be outdated. Worse, the information might actually be present in other materials of which Ivan isn’t aware or to which he does not have access.
</br>
'''2. In somebody’s brain:''' Ivan fastest option is to ask one of his colleagues. He might email, call, or have a conversation with a co-worker. But if the particular expert he needs is out sick, too busy to talk, or simply makes a mistake, Ivan either has an incorrect answer or no answer at all. In addition, he has also disrupted that employee from his or her tasks.
</br>
'''3. In the cloud:''' Sometimes, the knowledge exists in a sub-space that isn’t formally published content, but has been recorded. For instance, Ivan might find the answer sifting through his archived emails, memos, company updates, or notes. Chances are its obscure, ill-explained, and hard to find.
 
=== Knowledge Level Description ===
This scale serves as the guide to understanding the expected proficiency in each grade.
This scale serves as the guide to understanding the expected proficiency in each grade.


{| class="wikitable"
[[File:KAI.png|800px|center]]
!colspan="1"|Grade
!'''Name'''
!'''Description'''
!'''Focus'''
|-
!rowspan="1"| '''1'''
| Not Applicable.
|You are not required to apply or demonstrate this competency. This competency does not apply to your position.
|
|-
!rowspan="1"| '''2'''
| Fundamental Awareness (basic knowledge).
|You have a common knowledge or an understanding of basic techniques and concepts.
|Focus on learning.
|-
!rowspan="1"| '''3'''
| Novice (limited experience)
|
* You have the level of experience gained in a classroom and/or experimental scenarios or as a trainee on-the-job. You are expected to need help when performing this skill.
* You understand and can discuss terminology, concepts, principles, and issues related to this competency;
* You utilize the full range of reference and resource materials in this competency.
|Focus on developing through on-the-job experience.
|-
!rowspan="1"| '''4'''
| Intermediate (practical application)
|
* You are able to successfully complete tasks in this competency as requested. Help from an expert may be required from time to time, but you can usually perform the skill independently.
* You have applied this competency to situations occasionally while needing minimal guidance to perform successfully;
* You understand and can discuss the application and implications of changes to processes, policies, and procedures in this area.
|Focus is on applying and enhancing knowledge or skill.
|-
!rowspan="1"| '''5'''
| Advanced (applied theory)
|
* You can perform the actions associated with this skill without assistance. You are certainly recognized within your immediate organization as "a person to ask" when difficult questions arise regarding this skill.
* You have consistently provided practical/relevant ideas and perspectives on the process or practice improvements which may easily be implemented;
* You are capable of coaching others in the application of this competency by translating complex nuances relating to this competency into easy to understand terms;
* You participate in senior level discussions regarding this competency;
* You assist in the development of reference and resource materials in this competency.
|Focus is on broad organizational/professional issues.
|-
!rowspan="1"| '''6'''
| Expert (recognized authority)
|
* You are known as an expert in this area. You can provide guidance, troubleshoot and answer questions related to this area of expertise and the field where the skill is used.
* You have demonstrated consistent excellence in applying this competency across multiple projects and/or organizations;
* You are considered the “go to” person in this area within Secure Group and/or outside organizations;
* You create new applications for and/or lead the development of reference and resource materials for this competency;
* You are able to diagram or explain the relevant process elements and issues concerning organizational issues and trends in sufficient detail during discussions and presentations, to foster a greater understanding among internal and external colleagues and constituents.
|Focus is strategic.
|}


=== KAI Categories ===
[[File:Grade_Description.jpg|center|900px]]
In our Management Model and structure of the Career Framework, we are currently assessing knowledge regarding the following categories:


* General Knowledge: a list of indispensable software, tools, platforms and more, for Secure Group, that they need to know (it can be a little bit out of the scope of their position).
= Company Knowledge Centricity Level =
* Specific Knowledge: a list of concepts, tools, software and etc., that are indispensable for them to develop under the scope of their position.
Our current situation is represented by  Grade 2 and Grade 3 depending on the department. '''Our strategic goal is to achieve Grade 5 by the middle of next year'''.
* Secure Group Knowledge: a list of products, company profile and features that they need to know in order to succeed in Secure Group.
[[File:Knowledge_Centricity_Grade.jpg|900px|center]]
* IT Knowledge: a list of essential concepts that we consider to be basic for our Frameworks and that we expect employees to master.

Latest revision as of 08:47, 1 August 2022

The Secure Group knowledge management strategy enables our organization to create, apply, and share information, breaking down silos and increasing the usage of valuable data.

In Secure Group, we developed a culture in which people feel independent and autonomous when working. We believe traditional rigid management structures do not create a supportive environment, but cause unnecessary stress and distracts employees, which jeopardizes performance. Because of that, we respect our people's skills and knowledge and support them to pursue the company’s goals in their own way. This mutual respect between parties is essential to our Knowledge Management strategy and we can only afford this level of trust in our people if we know they are fully capable of doing their work and can fill any knowledge gaps quickly and efficiently.

It's a no-brainer that knowledge enables us to grow and innovate. But, it's a fact also that this is easier said than done. Before we reached our ideal Knowledge Management strategy, we faced some problems as the old way we managed information at Secure Group was inefficient. Information was shared in a fragmented way, through email and messaging apps. When people needed information, they’d go to an expert and ask them, which not only wasted time but would only benefit one person. It was difficult for the person to retain the new information, especially if it was shared in passing conversation or buried among emails. The process was also not being overseen, so embellishments and inaccuracies could slip through, which could jeopardize the information. Finally, when a knowledge gap formed, we had no way to fill it, as the one-to-one nature of knowledge sharing was impossible to scale, and the gap would remain.

After learning from these past mistakes, we then decided where knowledge should NOT be. We realized our knowledge should be easily accessible by our employees. It should not be stuck in someone’s head, where it is of no use to anyone but the person - it would even be unhelpful since people would constantly interrupt their work with questions. It should also not be chaotically thrown around emails and messages, where it is impossible to track and collect. Nor should it be dumped in guides and manuals and be forgotten about, becoming obsolete and misleading.

To ensure the effectiveness of our knowledge management strategy we also defined knowledge sharing as criteria in the Levels of our Frameworks so to progress with us, individuals must demonstrate the capability of sharing knowledge in a structured way.

Knowledge Categories

There are three basic forms of knowledge to consider when it comes to knowledge management: explicit, implicit, and tacit. Knowledge management is such a complex process that there are numerous terminologies, solutions, and techniques. Knowledge-driven businesses like ours have the advantage to drive efficient business activities by applying readily-available knowledge from a comprehensive, well-managed knowledge base. Knowledge in a business setting refers to the development of an organization's abilities, experiences, capabilities, and insight. All this is created, managed, and stored in the form of explicit knowledge, which is the focus of Individual Contributors, and tacit knowledge, which is the manager's focus.


To make it clearer, we separated the data and information into Extensive Knowledge, Realms Knowledge, and Secure Group Knowledge.

Extensive Knowledge

Also known as KAI of the framework, this is about understanding the usage and configuration of a diverse set of tools/software/platforms, languages, protocols, etc. which affect your performance within the company. They are related to the scope of your position and employees should grow this knowledge and hard skills on their own, while the company will provide context on the application of the tool/software/platform within defined processes.

Secure Group Knowledge

This is all about understanding the company’s products, the processes and tools/software/platforms related to their execution, the way all teams work, the concepts that are part of their scope, and how they contribute to the overall corporate strategy. It includes technical knowledge for non-technical people and business knowledge for technical people. For this category of knowledge, we provide pieces of training because this way we can ensure that everyone has the complete knowledge set to be a high-performer in our company.

Realm Knowledge

We have categorized the concepts that are present in our business and operations into domains of knowledge or activity. When addressing business leadership, each management framework requires proficiency in one or more of such domains, which are called Realms. You can check them all here.


Another thing we realized is that person has different ways of learning, advancing, and collaborating. We recognized this and decided to share knowledge in two formats: reading and face-to-face courses with a practical application. Therefore, we share knowledge through our internal wiki Confluence and through our Learning Day.

Confluence

Our wiki acts as a single source of all knowledge for our organization which can be created, edited, and modified by any employee. Confluence functions as a central repository for managing and distributing all company knowledge and information. Here, all co-workers are responsible and accountable for storing internal documentation about company policies, processes, projects or products they are building, common workflows, procedure checklists, and more.
We currently have Departments spaces composed of standard operation procedures, playbooks, how-to-guides and processes documentation, Teams spaces composed of operational artifacts and Divisions spaces hyperlinking all the content.

Learning Day

The Learning Day is our knowledge-driven initiative and it occurs on the last Tuesday of each month. It is a whole day dedicated to Learning. We start with breakfast at 9h00 filled with brain booster food and after that, we start the training according to the following formats:

  • Tech Challenges: consist of a presentation with an instructor that will act as a facilitator for the employee to assimilate the knowledge. After the training, employees receive a Tech Challenge to prove that they are capable of completing tasks relating to what they just learned.
  • Tech Sessions: consist of a collaboration activity or open format seminar. It can be given by an external trainer and it also comes with a task to be completed that varies from topic to topic.

After the completion of a training session, you will receive a challenge to prove you are capable of completing tasks related to what you just learned. They are usually short exercises to test you. 

Knowledge Accountability Index

Secure Group is all about accountability: and that includes accountability in knowledge. Once information is systemized and available to all, it becomes measurable and this allows it to be considered within the employees’ performances. In order to manage the existing knowledge in the company and to promote such accountability, we created a Knowledge Accountability Index a.k.a. KAI.

To help us measure competency in a skill, the index describes the grades of everyone’s ability and competency in a specific occupation. It is separated into six grades, each outlining the capabilities and value to be delivered by the person, and allowing them to plan their learning journey. These range from “Fundamental awareness” to “Expert”. The index can be used by an individual to compare their current level of proficiency to top performers in the same occupation and it enables us to:

  • Centralize effort to understand technology trends from a holistic view
  • Define knowledge as a key component in high performance
  • Anticipate and adapt to changes in external/internal environments to obtain/retain a competitive advantage in a quantifiable structure

In Secure Group, the effective management of knowledge aids competitive advantage. When people are accountable for knowledge it can be shared more efficiently and productively. We have put in place systems and good processes to achieve this so armed with knowledge, our employees are better able to innovate in their work.

Knowledge Grade Description

This scale serves as the guide to understanding the expected proficiency in each grade.

Company Knowledge Centricity Level

Our current situation is represented by Grade 2 and Grade 3 depending on the department. Our strategic goal is to achieve Grade 5 by the middle of next year.

Retrieved from "https://managementmodel.info/index.php?title=Knowledge_Management&oldid=3428"