The Resource Library Fallacy

It is a strange kind of comfort. The act of gathering material creates the impression of intellectual movement — of staying curious, staying sharp, staying engaged. But, even though internalising it took me longer than I wish to admit, accumulation is not engagement. Saving is not reading. Bookmarking is not understanding.

The moment you mistake one for the other, you have already stopped learning without noticing.

This pattern is fairly easy to spot in personal habits, but it is somewhat harder to recognise when it operates inside organisations.

A lot of organisations maintain some version of a knowledge library. A shared drive with templates. A folder of standard operating procedures. A hub with recorded webinars, onboarding guides, how-to documents. These are built with genuine care, often by people who have thought deeply about the content inside them. And once they exist, they carry an implicit assumption: the information is available, therefore people will use it.

This assumption is remarkably persistent. I think we all would love for it to be true. When someone does not know a process, the first reaction is often surprise. "It was covered during your onboarding." "It's all in the shared drive." When a tool is misused, the reflex is the same. "There's a guide for that." The logic feels right — the resource exists and it was shared, therefore ignorance is a choice. But this confuses availability with absorption. Unfortunately, the contents of a document sitting in SharePoint do not get magically imprinted into anyone's mind — just as the book that has been sitting on your bedside table for the past eight months does not enter your brain while you sleep. Though if Microsoft ever figured out that technology, they could claim having solved organisational learning once and for all. (A terrifying thought, but an oddly plausible one?)

A similar pattern plays out with training. A lot of professional development, when it happens at all, takes the form of a webinar, a slide deck, or a short session squeezed between other priorities. These work well enough for compliance — the kind of training you click through because a labour regulation requires it. But for anything that demands a genuine shift in behaviour, skill, or understanding, the format is hopelessly mismatched to the goal at hand. Yet organisations keep reaching for it, because it is visible, scalable, and easy to report on. We trained two hundred people. The board members smile.

There is a deeper issue beneath the logistics, though. Learning requires mental capacity. Mental capacity requires time. It requires enough real estate in your cognitive realm to build anything solid. I do not know about other professional environments, but in my field neither is readily available. There is always more work. Outputs are always more urgent than professional development. Even well-intentioned professionals — people who genuinely want to learn — find that their bookmarks go unvisited, their saved resources untouched. Not because they do not care, but because the structure of their work makes sustained learning nearly impossible. Self-development will always lose to revenue growth.

Resource libraries serve a clear purpose for a certain kind of knowledge — compliance standards, branding guidelines, procedural references, legal frameworks, instructions for how to use internal systems. These are stable, factual, and designed to be looked up when needed. Nobody needs a workshop on what the correct logo dimensions are. You check the brand guide and move on.

But organisations routinely use the same tool for an entirely different category of problem. They create a guide on how to effectively manage virtual meetings and expect it to produce better facilitators. They record a webinar on cross-functional collaboration and assume teams will now regularly keep in touch. They build a resource hub for project management and wonder why projects still go sideways. The tool is being asked to do something it was never designed to do: change how people think, decide, and behave.

A how-to guide does not build a skill. Skills require repetition, failure, adjustment, and the scarce, precious resource of time. A recorded presentation does not develop judgment. Judgment develops through navigating real ambiguity with real consequences. And a shared folder full of frameworks does not create shared understanding. It creates the illusion that everyone is on the same page, while in practice people carry vastly different interpretations of the same material. Or, more likely, have not opened it at all.

This is where the unevenness becomes structural. The people who engage with shared resources will most likely be junior staff — those with more time, more willingness to comply, and fewer competing demands on their attention. Alternatively, those who naturally nerd out about the topic at hand (they are probably the ones who created the resource in the first place). Senior staff, meanwhile, are the least likely to engage. Not necessarily because they think they know better, though that happens too. More often, they simply lack the bandwidth. They are making decisions constantly, and the cognitive load of leadership does not leave much room for a twelve-page guide on a new process. The more senior you get, the more confident you become — and the less time you have to check whether that confidence is still warranted. There is also an assumption that runs in the other direction: if someone has risen to a senior position, they must already know these things. Knowledge is expected to trickle downward. If a junior officer needs to learn something, surely the director already has it covered. This means senior staff are rarely challenged on gaps they may not even be aware of. They are given slack for not engaging with the same materials everyone else is expected to review — not because anyone decided they were exempt, but because nobody thought to question it.

So what you end up with is fragmented knowledge. One person has read everything. Another skimmed the summary. A third did not know the resource existed. And yet the organisation operates as if everyone received the same information, understood it the same way, and is now equally equipped to act on it.

This is not a knowledge management problem. It is a fantasy.

If the goal is shared capability rather than stored information, the approach has to change. Not because resource libraries are bad, but because they solve for the wrong thing. They solve for access. What organisations actually need is adoption — and adoption requires something resource libraries cannot provide: a shared experience.

When people learn together, something happens that does not happen when they learn alone. They develop a common baseline. A shared vocabulary. A reference point they can return to later — not a document, but a memory. "Remember that exercise we did in the workshop." That sentence carries more organisational weight than a fifty-page guide, because it points to something people lived through together. It may not have gone deep. It may not have covered every edge case. But it established a floor that everyone stands on, and that floor makes future conversations possible without having to constantly re-explain the basics.

For now, this matters more than depth. An organisation where everyone holds a solid, shared understanding of fundamentals will outperform one where a few individuals have read extensively but the rest are guessing. Not because depth is unimportant, but because depth without a shared foundation creates a different problem: you spend your energy bridging gaps and resolving misunderstandings instead of moving forward. When basic standards, principles, and ways of working are genuinely adopted — not just documented — they stop being topics of debate. They become an obvious element of the organisational culture. And obvious is where productive work begins.

That said, shared experience alone is not enough either. An after-training happy hour does not automatically become a learning experience (sure can, though). What makes learning stick is struggle. Not suffering — struggle. The productive discomfort of trying something unfamiliar, getting it wrong, and having to figure out why. If you struggle with something, you remember it. If you remember it, you can do it differently the next time. If you simply follow instructions, you execute. Execution is fine for routine tasks. But for anything involving judgment, collaboration, or change, execution without understanding is just motion.

This is why simulated environments matter more than organisations tend to acknowledge. A sandbox, a practice scenario, a facilitated exercise — these allow people to interact with a new tool or process as something to explore rather than something to fear. They can test, fail, observe consequences, and try again. When mistakes happen in a learning environment, they are examined by the group. They become material for reflection rather than grounds for blame. This does more than build skill. It builds a culture where learning is expected to be uncomfortable, and that discomfort is treated as a signal of progress rather than a sign of incompetence.

There is this pattern I see showing up reliably with a colleague of mine. They discover a new framework — a model for understanding team dynamics, a methodology for strategic planning, a theory of organisational change. They get excited. They read about it, talk about it, maybe even present it to other team members. The energy is genuine. But then nothing happens. The framework stays in the realm of ideas. It is discussed in the abstract, admired for its elegance, and never applied to anything concrete.

This is not a failure of intelligence or motivation. It is a failure of translation. Frameworks exist in books in a clean conceptual space where variables are controlled and examples are curated. I would love for organisations to follow the playbooks outlined in top-ten leadership literature. They do not. Reality resists neat categories. People do not behave the way the model predicts. Systems push back, and the gap between what the theory promised and what the environment allows becomes a source of frustration rather than learning.

This is where organisational training could — and should, if I say so myself — intervene. But it rarely does. A well-designed learning experience would take that framework off the page and into practice. It would let people test it against real scenarios, discover where it holds and where it breaks, and develop their own sense of when and how to use it. Instead, what happens is… into the resource library you go. A PDF. A slide deck. Maybe a short explainer session. And then people are expected to figure out the application on their own — which, for anything involving judgment, collaboration, or behaviour change, is exactly the part that cannot be self-taught.

The skills that matter most in organisational life — leadership, delegating, managing conflict, communicating across teams, navigating ambiguity — are precisely the ones that resist documentation. You cannot read your way into being good at them. You can read about them, and that may give you language. But the learning happens in doing, in failing, and in making sense of what went wrong with other people in the room. That is not a resource library problem. It is a design problem. And until organisations treat it as one, they will keep building libraries and wondering why nothing changes.

Again, none of this means resource libraries are useless. They have a role, and it is a legitimate one. But it is a limited one. The mistake is not in building them. The mistake is in believing they can do something they were never designed to do.

Organisations invest heavily in storing knowledge and remarkably little in creating the conditions where people actually develop capability. The SharePoint licence gets funded, but capacity-building does not. The guide gets written. The practice may or may not happen. (It is not like we track the learning outcomes of staff anyway.)

Information can support learning, but it cannot replace it.

Yet, we're surprised when people do not know what they were supposed to have learned from a document they were supposed to have read.