Comments on: Document your tribal knowledge.

By: knowledge adventure wiki

knowledge adventure wiki — Sun, 29 Oct 2017 07:28:54 +0000

Some organizations put their retirees by way of a process that
involves the transfer of knowledge in a period of time.
In today’s world while using technology boom and also the internet, we have been given an incredible number of
new methods for creating wealth and prospering in life.

It is only human beings who live lives of scarcity,
extreme competition, and imbalance, seemingly
against the laws of nature.

By: Jim Fallgatter

Jim Fallgatter — Mon, 08 Apr 2013 22:37:16 +0000

Excellent timing and excellent advice for my hoped for iPad app business Dave. At the end of the month we hit the App Store…and with some luck we will make some money. Thank you! This article made me sit down and think hard about a number of things that have taken the back seat to development and now could (we hope so) become very important. Springing to mind are software code escrowing, key man insurance, state of our documentation, Sweat Equity agreements that need to be formalized, Corporate Structure, Accounting practices, trademarks, etc. etc. All of which could bite hard if not thought through. Good wake-up call!

By: Paul Gogulski

Paul Gogulski — Tue, 02 Apr 2013 16:31:43 +0000

Agreed in principal, but unless the painful truth emerges from the mix, then it may lead to the wrong conclusions and therefor becomes meangingless, like so much of the current trend in obvsecure diversity training, anger management and advanced communications. Like one of my peers said at a recent seminar conducted in Qatar: “Why have a contract, when the owner tosses it back at you across the conference table and says: “Don’t give any of that.. I am the owner and I can do anything I want ” and attorneys on both sides nod in agreement, “Yes sir, yes sir.” If you speak even one more word or consider publishing what happened, you are terminated. Where does that fit in the tribal knowledge?

By: Harry Keller

Harry Keller — Tue, 02 Apr 2013 16:23:57 +0000

As a long-time professional software engineer, I can tell you that the comments in the code are more important than the code, although intelligent naming of variables and methods can help avoid extra commenting. Undocumented code is incomplete code.

As a professional scientist for a couple of decades, I can also tell you that the laboratory notebook is crucial to the advancement of science and must contain EVERYTHING that you do each day no matter how trivial.

For my three years in sales, I kept a bound notebook with every single contact time and notes along with a special column on follow up (no online in those days). This notebook was critical to my success and was passed on to my successor.

People who do not do these things are cowards who believe that they can make themselves indispensable by keeping secrets or are very lazy people. You should have neither in your organization and should not be one yourself.