THE KNOWLEDGEBASE THAT WON'T SIT STILL

Week 6 · Blog Post 10 · Web 2.0-Based Learning and Performance · Summer 2026

AI-Generated Image | ChatGPT

Listen to this post:

6:10

THE FILING CABINET PROBLEM

I have a confession about corporate knowledgebases: most of them are where good information goes to be politely ignored. You know the type — a shared drive, a wiki nobody edits, a "single source of truth" that's true exactly once, on the day it ships, and then quietly drifts out of date while everyone goes back to asking the one person who actually knows. I read two articles recently about how knowledge really moves through organizations, and together they helped me name why the filing-cabinet model keeps failing — and what to build instead.

The root problem is a bad metaphor. Hemsley and Mason (2013) describe a "knowledge as object" view that treats knowledge like a thing you pour into a container, store, and retrieve unchanged — inert, sitting there, waiting. Tidy picture. Also wrong about how people learn, because knowledge that just sits there doesn't teach anybody anything. (The stat that gets quoted to death: roughly 90% of corporate learning happens informally, nowhere near the official LMS — Carr, 2011, as cited in Jarrahi & Sawyer, 2013.)

WHERE THE LEARNING ACTUALLY LIVES

Jarrahi and Sawyer (2013) studied knowledge workers in consulting firms and found the real action is stubbornly social. They mapped five informal practices — locating expertise, finding the right expert, reaching out, socializing, and broadening your horizons — and showed how tools like wikis, forums, internal social networks, and plain old email scaffold each one. That word matters: scaffold. The knowledge isn't in the tool. It's enacted the moment someone uses the tool to solve an actual problem.

Which quietly reframes what a knowledgebase is for. Not a vault — a venue. A place where questions get asked out loud, answered in public, and left lying around for the next person to trip over. Jarrahi and Sawyer call the whole messy pile an "assemblage" — email plus wiki plus chat plus the human conversations stitching them together. No single tool wins; they cover for each other.

THE ACCIDENTAL SPACING EFFECT

Here's the part that made me sit up: Hemsley and Mason (2013) trace how information travels across social platforms and clumps into what they call interest networks — clusters of people who keep circling the same topic because they actually care about it. Over time, those networks can harden into real communities of practice. And the thing about a community that keeps circling a topic is that its members keep re-encountering the material. Not once. Over and over, spaced out across weeks and months, in the ordinary rhythm of work.

If you've spent any time with learning science, you can see where this is going. The spacing effect — and its hardworking cousin, retrieval practice — tells us we remember things we revisit at intervals far better than things we cram once and abandon. Most of us try to manufacture that with flashcard apps and drip campaigns. But an active community does it for free, as a side effect of simply being a community. Every time a topic resurfaces in the channel, every time someone reaches out with a related question, every time an old thread gets bumped back to the top — that's a retrieval cue. Learning doesn't stick because we filed it well. It sticks because we kept bumping into it.

DESIGNING FOR THE COMEBACK

The catch — and there's always a catch — is that none of this runs on autopilot. Hemsley and Mason are blunt that this knowledge ecosystem is dynamic, evolving, and not subject to direct control. You can't schedule virality or mandate a community into being. What you can do, as a designer, is build the conditions: make contributing nearly frictionless, keep threads searchable and easy to resurface, seed the recurring questions on purpose, and fight the instinct to lock everything behind approval workflows that strangle the very recirculation you're counting on. You're not filling a cabinet. You're tending a habitat, and hoping the right things keep coming back around.

So I'll put it to you — if you've worked somewhere with a knowledgebase that genuinely kept teaching people over time, what made it come alive instead of going stale? I keep trying to work out how much of that is design and how much is just culture.

---

Resources