The problem I keep seeing with “knowledge work”

Source: Dev.to

Publishing feels like the finish line

Once a report is written, reviewed, approved, and published, there is a sense of relief. Something concrete exists. The work has an endpoint.

From inside an organisation, this makes complete sense. Publishing is a familiar process. It is easy to track. It fits how teams are structured.

From the outside, it often falls apart. Most people are not looking for documents. They are looking for answers.

People do not think in PDFs

Readers arrive with questions, not with time. They want to know what an organisation actually recommends, how a position has changed, whether a claim still holds up, and where something came from.

Handing them a long document and expecting them to piece that together is asking a lot—especially on a phone, short on time, or trying to make a decision.

Search inside a document helps a little, but only if you already know what you are looking for and if the wording matches exactly. Most of the time, it does not.

The quiet cost of unread knowledge

When knowledge is hard to access, several things happen:

• People rely on summaries instead of sources.
• Outdated information stays in circulation.
• Different teams interpret the same work differently.
• Institutional memory slowly erodes.

None of this happens because the work lacks quality; it happens because the interface between the work and the reader is fragile. Over time, trust takes a hit—not because the organisation is wrong, but because clarity is missing.

Access is the real bottleneck

Most organisations do not have a knowledge problem; they have an access problem. They already know more than they can easily surface. Their insight is buried across years of reports, inconsistent language, and static formats.

The more they publish, the harder it becomes for anyone—including their own teams—to answer simple questions with confidence.

What I am trying to explore

I am thinking about what better access actually looks like:

• Not more dashboards.
• Not longer executive summaries.
• Not another place to upload files.

Instead, systems that let people ask questions in plain language, get grounded answers, and see exactly where those answers come from.

That line of thinking led me to start working on a project called Answerable, an attempt to rethink how research and institutional knowledge is accessed rather than just published. If you are curious, it lives here: .

This post is not about that product, but about a pattern I keep seeing and a belief that if we care about evidence and understanding, we need to pay far more attention to how people actually interact with knowledge once it leaves our hands.

Documents are not the enemy, but they cannot be the interface

PDFs and reports still have their place. They are useful records for accountability and depth.

However, they should not be the only way people are expected to understand complex ideas. When the interface fails, the knowledge gets blamed—a wrong conclusion.

If we want better decisions, better debate, and better use of research, access has to be treated as part of the work, not something that happens after it.