KM Principles
In his article, Thomas Stewart discusses ten principles of Knowledge Management - or Intellectual Capital. Such capital can be extremely beneficial to a corporation if used correctly, and Stewart makes some suggestion as to how knowledge can be managed in the best possible way for any type of company.
According to Stewart, intellectual capital is not owned by any one person - its value comes from sharing it among people. In order to enable such sharing, it is important to foster teamwork and other social forms of learning. (My personal experience tells me that friendship and cooperation between teams is helpful to everyone involved.)
If a company can recognize its KM assets, only then can it invest in them. It isn't an easy investment - the product of good KM is visible only to the company's employees - and not to its customers. However, such investment is critical for company success.
CIO Background
In class, the lecturer asked an open question - when choosing a CIO for a company, what sort of credentials should he have?
The CIO would have to have a good grasp of the technology available for his work, but this doesn't mean that he needs to come from a technical position. On the contrary, the person who is in charge of company knowledge should be a person who knows how company knowledge is used - meaning that it should be someone who has worked on the factory floor, so to speak. Ideally, I think, this person should spend time working with every team in the company, to see exactly what knowledge they need for their daily work.
Wednesday, March 29, 2017
Tuesday, March 21, 2017
Post 1: KM ISO; Company Blog
The Case for KM Standards
For class, we read an article that discusses the need for standards in knowledge management. Nick Milton, the writer, lists several reasons for such standards to be determined by ISO.
First, KM doesn't have one clear definition. Different companies may mean different things when they say "knowledge management." Each company may not have the authority to decide what the term means, but ISO might - so it would be helpful to have an ISO standard for companies to refer to.
Second, KM may be a complicated subject with different applications in different environments, but there are common mistakes that everyone should be able to avoid. Having a standard could reduce the number of failed KM projects.
Third, a standard is a good way to judge not only yourself, but also other companies that provide KM services - in the event of KM outsourcing, to tell whether the company does a good job.
The author mentions also that a standard can be used as a guideline and doesn't have to have strict rules, and also that this is exactly the sort of thing that ISO does.
Company Blog
In search for a company blog, I began with companies that I've gotten to know through interviews. Having spent the last few months job hunting, finding company blogs has become a hobby of mine.
PayPal, for instance, has a blog called "PayPal Stories" (which can be found at https://www.paypal.com/stories/us).
PayPal's blog includes articles relating to several categories. Of course there are news stories about the company's achievments and new technologies, but the blog also includes articles that could be helpful to average PayPal users - like people who have their own businesses. Some of the articles relate to community work, and some relate to people who work at the company. The blog is clean and pretty and easy to navigate.
The blog's target audience can be both professionals and just average joes who want to learn more about the company. Such a blog does two things: 1. It shows the technology side of PayPal, which is helpful for a business that is considering using PayPal's services; 2. It shows the human side of PayPal - this is specifically important because PayPal's customers are entrusting PayPal with their money and credit card information.
Naturally, the blog also offers other ways to follow PayPal on social media, which speaks to any sort of customer.
For class, we read an article that discusses the need for standards in knowledge management. Nick Milton, the writer, lists several reasons for such standards to be determined by ISO.
First, KM doesn't have one clear definition. Different companies may mean different things when they say "knowledge management." Each company may not have the authority to decide what the term means, but ISO might - so it would be helpful to have an ISO standard for companies to refer to.
Second, KM may be a complicated subject with different applications in different environments, but there are common mistakes that everyone should be able to avoid. Having a standard could reduce the number of failed KM projects.
Third, a standard is a good way to judge not only yourself, but also other companies that provide KM services - in the event of KM outsourcing, to tell whether the company does a good job.
The author mentions also that a standard can be used as a guideline and doesn't have to have strict rules, and also that this is exactly the sort of thing that ISO does.
Company Blog
In search for a company blog, I began with companies that I've gotten to know through interviews. Having spent the last few months job hunting, finding company blogs has become a hobby of mine.
PayPal, for instance, has a blog called "PayPal Stories" (which can be found at https://www.paypal.com/stories/us).
PayPal's blog includes articles relating to several categories. Of course there are news stories about the company's achievments and new technologies, but the blog also includes articles that could be helpful to average PayPal users - like people who have their own businesses. Some of the articles relate to community work, and some relate to people who work at the company. The blog is clean and pretty and easy to navigate.
The blog's target audience can be both professionals and just average joes who want to learn more about the company. Such a blog does two things: 1. It shows the technology side of PayPal, which is helpful for a business that is considering using PayPal's services; 2. It shows the human side of PayPal - this is specifically important because PayPal's customers are entrusting PayPal with their money and credit card information.
Naturally, the blog also offers other ways to follow PayPal on social media, which speaks to any sort of customer.
Industrial Engineering student, pleasure to meet you.
This is it. I've finally reached my last year of university. It's been a rollercoaster, and I'm down to my last few courses. It's a wonderful feeling.
One of those courses is Knowledge Management, or KM. In requesting that we create blogs, the professor has made it clear that this course is meant to be practical and not just academic, which I hope will make for a pleasant experience.
I'm not new to blogger.com - I created my first blog when I was sixteen and wrote in it periodically until a few years ago. Blogging is a wonderful concept, I'd like to get back into it.
The field of KM isn't new to me either - in the army, my team had to put extra effort into efficient knowledge management for two main reasons: 1. Many tasks had to be completed within a few hours, even at night, so any information needed in order to complete a task had to be readily accesible; 2. One-third of the team members were replaced every six months - one group of soldiers would complete their service and a new group would take their place - meaning that training had to be quick and easy, and also that no one really had the chance to become truly professional. Knowledge was stored in a shared file and in old emails.
One of those courses is Knowledge Management, or KM. In requesting that we create blogs, the professor has made it clear that this course is meant to be practical and not just academic, which I hope will make for a pleasant experience.
I'm not new to blogger.com - I created my first blog when I was sixteen and wrote in it periodically until a few years ago. Blogging is a wonderful concept, I'd like to get back into it.
The field of KM isn't new to me either - in the army, my team had to put extra effort into efficient knowledge management for two main reasons: 1. Many tasks had to be completed within a few hours, even at night, so any information needed in order to complete a task had to be readily accesible; 2. One-third of the team members were replaced every six months - one group of soldiers would complete their service and a new group would take their place - meaning that training had to be quick and easy, and also that no one really had the chance to become truly professional. Knowledge was stored in a shared file and in old emails.
Subscribe to:
Posts (Atom)