Most organisations have a lot of documents and data floating around that hardly ever gets revisited or used. They all have research, reading, and relevant information collecting dust.
Stuff that should be informing the decisions and strategies of the company. Some of it sits unread in a knowledge base or a wiki. Some of it lies in the drives of individual employees who don’t have a way to share it productively.
So much knowledge not being applied!
Except that’s not how we work as human beings. If you haven’t read it, experienced it, and contextualised it, then it isn’t knowledge to you. Knowledge is a quality that people possess, not documents, and the only way to transfer it from one place to another is for people at both ends to apply themselves and make it their own.
A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use.
Customer dependence is more profitable than customer education.
What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers.
Keep your contact information in a prominent location.
Write for yourself and for posterity.
Write pertinent field information with every new entry. You should enter the date, time, and location at the top of every page.
Add information on your location.
Record your methods.
Make backup copies.
If you use abbreviations, make sure there is a key in your field notebook.
Don’t leave home without it.
Form a writing habit. Thomas Jefferson was such an inveterate chronicler of daily events in his notebooks that he even took the time to record the weather four times on the day he helped write the Declaration of Independence. So unless you have something far more pressing than writing the Declaration of Independence, you have no excuse for avoiding your field notebook!
Set up a structure for your field notebook.
Create an index.
Treat your field notebook like a scrapbook. You should view your field notebook as a central clearinghouse for miscellaneous information that is relevant to your research project. If there are related bits of information that you will find useful later on, sketch them, write them down, photocopy them, and staple or tape them in your notebook.