Organizational Knowledge

Organizational knowledge is the study of what firms know, how that knowledge is created, stored, moved, and lost, and why it sometimes makes a company valuable and sometimes slips away.

11 frameworks, from 1911 to today · Management · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Organizational knowledge is the study of what firms know, how that knowledge is created, stored, moved, and lost, and why it sometimes makes a company valuable and sometimes slips away. Its central puzzle is simple to state and hard to solve: the most important things an organization knows—how to make a product well, how to serve a customer, how a team actually gets work done—are often not written down anywhere, are held unevenly across people, and are difficult to copy or transfer even inside the same firm. The field grew up asking why some companies outperform others when they buy the same machines, hire from the same labor markets, and read the same management books. The answer, increasingly, was knowledge: what people collectively know and how well the organization puts that knowledge to work.

Scientific Management and the First Attempt to Capture Know-How

The story begins with Frederick Winslow Taylor, whose The Principles of Scientific Management appeared in 19111. Taylor's problem was the gap between what skilled workers knew and what managers could see. Machinists and laborers held craft knowledge in their hands and heads; management ran the shop on rule of thumb. Taylor proposed to extract that knowledge: study each task with a stopwatch, break it into motions, find the "one best way," and encode it in written instructions and standardized tools. In his famous account of pig-iron handling at Bethlehem Steel, workers were taught a prescribed sequence of lifts and rests that raised daily output severalfold.

Taylorism was the first large-scale codification project in management—an attempt to turn tacit craft skill into explicit, transferable procedure. It worked well enough for repetitive physical tasks to spread through factories worldwide, and it provoked the counter-movement that followed. Its limitation was built in: it assumed knowledge could be fully captured by an outside observer and imposed downward, and it treated the worker's own understanding as an obstacle rather than a resource.

Human Relations and the Discovery That People Hold Knowledge

From the late 1920s, experiments at the Hawthorne plant of Western Electric, associated with Elton Mayo and Fritz Roethlisberger, turned attention to the social side of work. The researchers found that output and satisfaction depended heavily on group norms, attention, and informal relationships—not just on physical conditions or pay. The "Hawthorne effect," the tendency of people to change behavior when they know they are being studied, became a cautionary tale about research method, but the broader finding held: workers form informal groups with their own rules and their own practical knowledge of the job.

The human relations movement that followed did not use the word "knowledge," but it established a premise the field would later build on: the organization's real operating knowledge lives partly in social relationships and group culture, not only in formal instructions. Chester Barnard's The Functions of the Executive (1938) made a related point from the top: executives chiefly manage communication and shared purpose, and much of what makes an organization function is informal and unplanned.

The Information-Processing Organization

After the Second World War, the rise of computing and cybernetics gave management a new metaphor: the organization as an information-processing system. Herbert Simon's work on bounded rationality—the idea that decision-makers have limited attention and computing capacity—and his 1947 book Administrative Behavior reframed organizations as devices for simplifying decisions through routines and standard operating procedures. James March and Simon's Organizations (1958) developed the picture of firms as systems that search for, store, and retrieve information.

This tradition made "knowledge" visible as something organizations process, but it tended to equate knowledge with data and rules. The gap it left was the tacit, embodied, socially held knowledge that Taylor had tried to capture and Hawthorne had shown to be social. That gap became the field's central subject in the 1990s.

The Resource-Based View: Knowledge as a Source of Advantage

In 1984 Birger Wernerfelt published "A Resource-Based View of the Firm," arguing that firms should be understood in terms of the resources they control, not just the products they sell. The idea matured through the 1980s and 1990s, notably in Jay Barney's 1991 paper on firm resources and sustained competitive advantage, which specified the conditions under which a resource yields lasting advantage: it must be valuable, rare, hard to imitate, and hard to substitute2.

Knowledge fit these criteria unusually well. A rival can buy the same machines, but not the accumulated know-how of a workforce, the routines that coordinate it, or the relationships that make it flow. The resource-based view gave the field its economic rationale: knowledge matters because it is the kind of asset that is difficult to copy. It also set the agenda for the next question—if knowledge is the advantage, how does it actually get created and moved?

Knowledge Creation: Tacit and Explicit

The pivotal figure was Ikujiro Nonaka. Drawing on Michael Polanyi's distinction between tacit knowledge (what we know but cannot easily articulate—how to ride a bicycle, recognize a face, or judge a customer's mood) and explicit knowledge (what can be written down and transmitted), Nonaka argued in the early 1990s that organizations create knowledge by converting between the two. His model, developed with Hirotaka Takeuchi in The Knowledge-Creating Company (1995), described four modes: socialization (tacit to tacit, through shared experience), externalization (tacit to explicit, through metaphor and model), combination (explicit to explicit, through documents and databases), and internalization (explicit to tacit, through learning by doing).

The concrete case that anchored the theory was Japanese product development: engineers at Matsushita struggling to design a home bread-making machine, and the insight—arrived at partly by watching a hotel baker knead dough—that the machine needed a particular twisting motion. The design problem was solved not by a specification but by embodied observation converted into a mechanism. Nonaka's model made tacit knowledge a first-class management concern and gave the field its most widely taught framework.

Knowledge Transfer and Stickiness

If knowledge is valuable, why is it so hard to move? Gabriel Szulanski's research in the mid-1990s on "stickiness" studied the transfer of best practices inside firms and found that knowledge often failed to travel even between units of the same company. He identified sources of stickiness at each stage: the knowledge itself may be causally ambiguous (people cannot say why it works), the source may lack motivation to share, the recipient may lack absorptive capacity (the ability to recognize and use new knowledge, a concept from Wesley Cohen and Daniel Levinthal's 1990 work), and the relationship between the two may be poor.

The practical implication was that transferring knowledge is not like copying a file. A classic illustration is the difficulty firms have replicating a successful factory or retail format in a new location: the routines that make the original work are partly embedded in people, layout, and local relationships, and the copy underperforms until those are rebuilt. This line of work turned knowledge management from a storage problem into a relationship and context problem.

Communities of Practice and the Social Turn

In 1991 Jean Lave and Etienne Wenger introduced the concept of legitimate peripheral participation—the idea that people learn a practice by joining a community at its edges and gradually moving toward full participation34. Wenger's later work, especially Communities of Practice (1998), described these groups as defined by mutual engagement, a shared repertoire, and a joint enterprise. In organizations, communities of practice are the informal networks through which practitioners actually share tricks, standards, and judgment—often without management's knowledge.

The concept mattered because it explained where a great deal of organizational knowledge actually lives and how it is reproduced: not in databases but in the ongoing relationships of people who do the same work. It also warned that knowledge cannot simply be commanded into existence; managers can support communities but cannot manufacture them to order.

Codification and Personalization: Two Strategies

By the late 1990s, consulting firms and their researchers had begun to distinguish two ways of managing knowledge. In Working Knowledge (1998), Thomas Davenport and Laurence Prusak described knowledge as a mix of experience, values, and expert insight, and argued that managing it required attention to culture and trust as much as technology. The sharper strategic contrast came from Morten Hansen, whose research on consulting firms distinguished a codification strategy—capturing knowledge in documents and databases so it can be reused by many people—from a personalization strategy—investing in networks and person-to-person contact so that expertise is shared directly.

Hansen, Nitin Nohria, and Thomas Tierney's 1999 Harvard Business Review article made the point that firms should choose one strategy as primary rather than trying to do both equally. The codification approach suits standardized, reusable solutions; the personalization approach suits novel, judgment-heavy problems. The distinction gave managers a vocabulary for a real trade-off: documenting knowledge makes it scalable but can strip away the context that makes it useful.

Intellectual Capital Measurement

A parallel strand asked how to put knowledge on the balance sheet. In the 1990s, with the gap widening between firms' market value and their book value, researchers and practitioners developed frameworks for measuring intellectual capital—the intangible assets of an organization, often divided into human capital (people's skills), structural capital (processes, databases, intellectual property), and relational or customer capital (relationships and reputation). Karl-Erik Sveiby, Leif Edvinsson at Skandia, and Thomas Stewart, whose Intellectual Capital appeared in 1997, were central figures.

The measurement project had real appeal: if knowledge is the main asset, investors and managers need to see it. But the frameworks struggled with the same problem that made knowledge valuable in the first place—it is hard to observe and hard to compare across firms. The field's center of gravity shifted from counting knowledge to understanding how it is created and used.

Knowledge Loss and Retention

The final strand concerns what happens when knowledge leaves. As the workforce aged and turnover rose, researchers studied knowledge loss—the disappearance of expertise when people retire, quit, or are laid off—and knowledge retention, the practices meant to prevent it. Techniques included exit interviews, mentoring and apprenticeship, documentation of critical procedures, and succession planning for expert roles.

The recurring finding was that the most valuable knowledge is often the hardest to retain, because it is tacit and held by a few people whose departure is not noticed until the work starts to fail. The field's history thus came full circle: Taylor tried to capture craft knowledge in instructions, and a century later the problem of capturing what people know before they leave remained unsolved in general, even as the tools for addressing it had multiplied.

Where the Field Stands

Today organizational knowledge is studied through several overlapping approaches. The resource-based and knowledge-based views of the firm remain the economic backbone, explaining why knowledge is a source of advantage2. Nonaka's tacit–explicit framework and the communities-of-practice tradition remain the standard accounts of how knowledge is created and shared53. The stickiness literature and the codification–personalization distinction guide practical decisions about transfer and strategy5. Intellectual capital measurement persists in reporting and valuation work, and knowledge retention has become urgent as workforces age and as remote and hybrid arrangements change how knowledge moves.

The open questions are the old ones in new form: how much of what an organization knows can be made explicit without losing what makes it valuable; how knowledge moves across boundaries of culture, distance, and technology; and how firms can retain expertise that is held in people who will eventually leave. The field began by asking why some firms outperform others, and it still answers, in large part, with what those firms know and how well they keep it.

References

  1. The Principles of Scientific Management, Wikipedia
  2. Resource-based view (introduction, Origins and background), Wikipedia
  3. Community of practice, Wikipedia
  4. Situated learning (introduction, History), Wikipedia
  5. Knowledge management (Dimensions, Strategies), Wikipedia

The frameworks of Organizational Knowledge

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1911-1940

    Scientific Management

    How can managers find and enforce the one best way to do each task?

    Fly to its tower in Nousfarer

  2. 1930-1960

    Human relations movement

    How do social relationships and group norms shape how people work?

    Fly to its tower in Nousfarer

  3. 1947-1990

    Carnegie School

    How do organizations process information and make decisions under limits?

    Fly to its tower in Nousfarer

  4. 1984-Present
  5. 1990-Present

    Knowledge Stickiness and Transfer

    Why is knowledge so hard to move even inside one firm?

    Fly to its tower in Nousfarer

  6. 1990-Present

    Knowledge-Based View of the Firm

    Is knowledge the key asset that explains firm performance?

    Fly to its tower in Nousfarer

  7. 1991-Present

    Community of practice

    How do people learn and share know-how through informal groups?

    Fly to its tower in Nousfarer

  8. 1991-Present

    SECI model of knowledge dimensions

    How do organizations turn tacit knowledge into explicit knowledge and back?

    Fly to its tower in Nousfarer

  9. 1994-2010

    Intellectual Capital Measurement

    How can a firm measure the value of what its people know?

    Fly to its tower in Nousfarer

  10. 1998-Present

    Codification and Personalization Strategies

    Should a firm store knowledge in documents or connect people who hold it?

    Fly to its tower in Nousfarer

  11. 2000-Present

    Knowledge Loss and Retention

    How can a firm keep critical knowledge from walking out the door?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Scientific ManagementHuman relations movementCarnegie SchoolResource-based viewKnowledge Stickiness and TransferKnowledge-Based View of the FirmCommunity of practiceSECI model of knowledge dimensionsIntellectual Capital MeasurementCodification and Personalization Stra…Knowledge Loss and Retention

Beyond the field

Where Organizational Knowledge's ideas came from in other fields, and what they led to there: the strongest 12 of 34 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Organizational Knowledge is a planet in Nousfarer

Its city has a tower for each of these 11 frameworks. Land, walk in, and climb one concept at a time.

Land on Organizational Knowledge

Related fields

Fields its ideas are linked to

More in Management

See where Organizational Knowledge sits on the Map of Human Knowledge