When an experienced sales manager leaves a manufacturing company, years of accumulated customer history, pricing negotiation notes and market observations walk out the door with them. The replacement starts from scratch, repeats the same mistakes with the same clients, and asks the same questions all over again. This is the familiar reality for many SMEs in Turkey. Knowledge belongs to the individual, and when the individual leaves, the knowledge goes too. Knowledge management addresses precisely this problem: transferring a company’s accumulated experience, expertise and hard-won lessons from individuals into a structured, independent system.
Knowledge management as a discipline distinguishes between two fundamentally different types of knowledge. The first is explicit knowledge — written procedures, technical documentation, project reports, client files and anything else that has been recorded and made accessible. The second is tacit knowledge — how a sales representative closes a reluctant client, how a production technician adjusts a temperamental machine, how a project manager makes decisions under pressure. This second category is embedded in experience and difficult to transfer. An effective knowledge management approach aims to make tacit knowledge visible too, converting it into explicit form through structured interviews, workflow documentation and mentoring practices.
Enterprise software systems provide the critical infrastructure for this process. When ERP systems, customer relationship tools and document management applications work together, company knowledge settles into a central, accessible structure rather than residing on individual hard drives or in individual heads. When decisions made throughout a project — from initial proposal to final delivery — are systematically recorded along with the problems encountered and the solutions found, a different team starting a similar project can draw on that accumulated experience. Repeated mistakes are avoided, learning curves shorten and productivity improves.
Customer knowledge management is one of the most tangible dimensions of this picture. Which products were sold to a given client in the past, what complaints were raised, which proposals were rejected, which payment terms were accepted — when all of this accumulates in the customer module of a CRM or ERP system, every member of the sales team shares the same institutional memory. A customer is no longer just a name and phone number; they become visible in full context, with history, preferences and potential. Entering this information consistently into the system requires discipline, but the long-term value it delivers to the company far exceeds the time invested.
Preserving and transferring technical expertise is another important dimension of knowledge management. In manufacturing companies, machine maintenance histories, fault logs and resolution methods; in software firms, technical documentation for developed modules; in consulting practices, methodology notes from completed engagements — all of these are reusable organizational assets. When common fault types and remediation procedures in a production facility are maintained in a knowledge base, even an inexperienced technician can access that information quickly. The company is no longer dependent on the presence of a single experienced specialist.
Building this kind of structure is not straightforward. The vast majority of Turkish SMEs allocate very limited time and resources to knowledge management. Under the pressure of daily operations, employees tend to move on to the next task rather than entering project notes into a system. Managers, unable to see the tangible return in the short term, rarely move the initiative up their priority list. There is also the question of what actually deserves to be recorded — capturing everything is neither possible nor useful, and an undifferentiated pile of information makes it harder to locate what genuinely matters. Making a knowledge management system work therefore requires both the technical infrastructure and the organizational habit of actually using it.
If you are an SME manager considering investment in this area, the right starting point is an honest assessment of where things stand today: where does your company’s critical knowledge currently live, whose departure would hurt the business most, which processes get reinvented from scratch every time they run? The answers to these questions will show you which knowledge needs to migrate into the system first. Before committing to a large and expensive software project, examine whether your existing ERP or accounting system’s document attachment and note-taking features are being fully used. In most cases the infrastructure is already in place; what is missing is the discipline to record knowledge systematically and the organizational commitment to make that discipline stick.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 18, 2005 and has been automatically translated into English and other languages using machine translation.