Knowledge creation and architecture.

Knowledge creation is the make-or-break stage in knowledge management because organizations can’t compete without generating new knowledge. The process depends primarily on people: knowledge ultimately resides in individuals, and even “explicit” knowledge becomes available only after tacit experience is transformed into documented form. That means organizations need a system and culture that make it easy—and worthwhile—for people to capture what they know, write down experiences, and share them so others can reuse it.

Technology plays a supporting role rather than driving knowledge creation. A knowledge management system can store, archive, and retrieve information, but people still decide how knowledge is applied in real work. In this framing, knowledge management is not a technology project; people and processes account for roughly 80% of the impact, while technology contributes about 20% by enabling access to what has been captured.

New knowledge is created through teamwork and collaboration. Teams pool resources and compare job experiences with job outcomes, translating what worked (or failed) into reusable knowledge. As team members internalize each other’s methods, they collectively refine how tasks should be done. Over time, this cycle of sharing, feedback, and reapplication matures into expertise—whether someone becomes a stronger programmer, analyst, assessor, or other specialist.

Once knowledge is created, documenting it helps carry learning forward to future teams and similar projects. The transcript illustrates this with software development and HR-related software: programmers, analysts, evaluators, and assessors share knowledge during development, testing generates feedback, and that feedback drives further iteration. The resulting knowledge becomes an asset for the next project, improving performance and reducing repeated mistakes.

Barriers to knowledge sharing are largely cultural and motivational. People may refuse to share—sometimes even with supervisors—because they fear threats to their position or perceive personal risk. Overcoming this requires organizational climate and culture that reward openness. HR practices are central: compensation and recognition tied to knowledge sharing (such as a “knowledge champion” award), opportunities to apply knowledge, support for creativity and innovation, and job design that grants autonomy within a broader framework. Job security, advancement, skill variety, and recognition of achievement are also presented as motivators that encourage people to contribute.

Individual differences matter too. Personality and attitude influence willingness to share; extroverted people may share more readily, while introverted people may hold deeper knowledge. The transcript also highlights the role of cognitive and affective attitude: positive attitudes increase sharing, while negative attitudes lead to withholding. Organizational norms and values can further either enable or block cross-level sharing.

Finally, knowledge architecture is presented as a three-part structure—content, people, and technology. Content is organized by functional needs (examples include sales data like competition and sales volume; HR policy details like openings and benefits; marketing strategy and R&D effects; and customer service metrics like compliance and satisfaction). The technical layer is then broken into stages: user interface, access control, collaborative intelligence and filtering, expert systems, knowledge-enabling applications, transport and middleware, and a repository layer that includes data warehouses and legacy applications. The architecture also raises practical decisions about building versus outsourcing systems (e.g., ERP), emphasizing cost-effectiveness and the need for expertise, along with ongoing maintenance responsibilities.