Knowledge as Knowing, Not Knowledge as Object

Definition

Real expertise is not a static body of stored information but an active, ongoing process — "knowing" as a verb rather than "knowledge" as a noun. A person applying expertise is continuously reading a specific, evolving situation and revising their plan in response, not retrieving and executing a fixed procedure.

In the Book

The book makes the point with a deliberately unsettling image: if a friend says he has read many books about surgery and is ready to operate on your skull, you would rightly decline. Real surgeons "do not blindly apply knowledge they have gleaned from books or procedures they have stored in their heads" — they consider the patient's history, monitor vital signs, look at tissue, make incisions, draw conclusions, and revise the plan as the situation evolves. The book calls this engagement "an active, inventive process that is just as critical as their store of knowledge itself," and notes that experts' knowledge is really an accumulated "residue" of past actions, thinking, and conversations that stays a dynamic part of ongoing experience — which is why neurosurgeons will travel long distances just to operate alongside a colleague, to refine technique through joint practice rather than reading about it.

Why It Matters

This reframing changes what counts as a knowledge-management failure. If knowledge is a stored object, the failure mode is an incomplete database. If knowledge is knowing, the failure mode is removing people from the situations where judgment gets exercised and refined — and no database, however complete, substitutes for that. It also explains why communities built around ongoing joint activity, rather than repositories built around document capture, are the right unit for managing expertise that has to keep adapting to new situations.