I like repeatable processes. To me, it’s a waste of time to do the same thing more than once. I’m also reminded of this when I start repeating answers to the same questions. When considering knowledge companies, virtually everything valuable to us are our people and information, not physical assets. As I said in “Fire your Best People…”, if information is locked inside someone’s head, they are a less valuable resource. It’s all about sharing: files, knowledge, pertinent information from emails and so on. If the asset only exists on one person’s machine, or worse: their head, and is relevant to others, your company has a problem.
When considering software, if all of the assets necessary to create working software haven’t been committed to the version-control repository, the software doesn’t exist. Sounds simple doesn’t it? Then, why do so many projects and companies fail to follow this simple rule? If I was cynical, I might think it’s because some think that by harboring this information, they can essentially hold the organization “hostage” - and increasing job security. In my experience, this is no longer the primary reason in the organizations I’ve seen (although there are always a few exceptions). I think the main problem is leadership. It takes discipline for each person in an organization to ask themselves after they’ve sent instructions on how to do something in an email…
Is this something I want to keep permanent for all current and future employees?
Other examples include:
- Realizing that a configuration file used to deploy the software should be checked into the version-control system so that the software can be built in any target environment, not just on their machine.
- The workaround for that strange bug in your Content Management System should be posted to the Wiki
- That pointing to a file in a version-control repository may be preferred over sending email attachments with every change .
- The email that documented the steps that Human Resources performs when a new employee starts with the company, should be published to the company’s Intranet .
Here are some possible tools where you might capture these assets:
- Version-control repository
- Corporate Intranet
- Hosted Wiki
- Electronic Corporate bulletin board
- Company blog
Leaders in knowledge organizations understand their most vital assets are their people and the information produced by these people. When people leave, you need to have a way to continue to leverage this knowledge. Leaders understand that this philosophy of sharing information must be institutionalized. Just remember…
If it’s not in the System, it doesn’t exist
Originally authored by Stelligent at testearly.com
Comments