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.
We can easily imagine from our own experience why fire might be used as a symbol of the life of a house and the family that lives there. The fire was certainly the most lifelike element of the house: it consumed food and left behind waste; it could grow and move seemingly by its own will; and it could exhaust itself and die. And most important it was warm, one of the most fundamental qualities that we associate with our own lives. When the fire dies, its remains become cold, just as the body becomes cold when a person dies. Drawing a parallel to the concept of the soul that animates the physical body of the person, the fire, then, is the animating spirit for the body of the house.