What Knowledge Management Overlooks Classic knowledge management thinks in SECI cycles, cubes and levels: useful, but blind to design. Thoring and colleagues state it plainly: without an understanding of what makes design knowledge distinct, a company’s capacity to innovate declines (Thoring et al., 2022). Sticky-note intuition as a KM illusion (“the designers somehow know”) is no substitute for a typology. It merely administers invisibility.
Four Types, Not One Gut Feeling Their model distinguishes four ways in which design knowledge exists. In the thing (Artifact Knowledge): the bottle opener carries the solution in its form, Velcro the lesson of the burr. In the person (Design Intuition): knowledge without words, trained through experience and observation. In signs (Design Language): sketch, diagram, technical term, software. In theories (Design Theories): condensed, testable models, standards and patterns. Between them lie the transitions: filtering and adjusting filters between thing and intuition, externalising and internalising between intuition and language, theory building and deriving concepts between language and theory.
Qualities Across the Grid Orthogonal to these lie Situatedness (context-bound to transferable), Expertise (novice to expert), Diffusion (individually to collectively accessible) and Content (technical, human-centred, procedural, declarative). Anyone who knows only “explicit vs. tacit” misses Artifact Knowledge, precisely the level that makes Radermacher’s model (Radermacher, 1996) useful for design, and the one SECI leaves out. Design knowledge sits in the thing, not only in the head and not only in the wiki.
Why Management Would Rather Not Hear It Artifact Knowledge cannot be neatly copied into the intranet. Intuition evades the checkbox. Design Language seems “soft” until a missing term paralyses an entire critique. Theories and patterns seem too slow for quarterly reporting. KM systems optimised for documents and tickets reward the diffusion of Design Language snippets and penalise the care of Artifact Knowledge and Design Intuition. The illusion is that intuition fits on a sticky note. The consequence is that knowledge transfer fails quietly and innovation thins out.
Consequences for the Studio For practice, the model means deliberately generating new design knowledge, not merely filing what already exists. For teaching: exercises along the eight dimensions and three transitions. For theory: taking artefacts seriously as stores of knowledge and systematising their extraction into Design Language; researching “ways of seeing” as the transition from artefact to intuition. None of this is studio cosmetics. It is infrastructure for the ability to critique.
Literature Chaos as a Symptom Thirty sources, eight categories, inconsistent terminology: Object Knowledge, Artifact Knowledge, Precedents: often the same thing under different names. Thoring and colleagues do not turn this into a niche glossary project but into a warning for management. Redundancy and the lack of a comprehensive classification are not academic pedantry. They are the reason KM teams and design studios talk past each other: one looks for tickets, the other already sees knowledge in the prototype that never made it into text.
Transitions as Innovation Work The three transitions are the operative core. Whoever adjusts filters sees problems and opportunities others miss (“ways of seeing”). Whoever externalises makes intuition open to critique. Whoever builds models (journey maps, 2×2s, personas as practical frameworks, not as general laws of nature) synthesises. Innovation happens in these transitions. A KM that stores only the end products of Design Language cuts off exactly where design knowledge comes into being.
Between as Knowledge Work Between and the probes in the studio work precisely at these transitions. Writing down the criterion before the specification exists makes intuition open to discussion while it can still move. Fixing the material early keeps the knowledge in the thing tangible: the form carries knowledge about use that no ticket replaces. Which leaves a question for every studio: what of what you know lies today only in the prototype, and who would notice if it were cleared away?
Sources
Radermacher, F. J. (1996). Cognition in systems. Cybernetics and Systems, 27(1), 1–42. https://doi.org/10.1080/019697296126651 (abstract only)
Thoring, K., Mueller, R. M., Desmet, P., & Badke-Schaub, P. (2022). Toward a unified model of design knowledge. Design Issues, 38(2), 17–32. https://doi.org/10.1162/desi_a_00679 (full text)