Every company has a knowledge problem. It just doesn't look like one until someone leaves.
The answer to "how does the 401k vesting work?" lives in one person's head. The answer to "who do I contact when the expense system is down?" lives in a Slack message from 2022 that nobody can find. The answer to "what's the actual policy on remote work during school holidays?" was explained in an all-hands eighteen months ago and has been re-explained by three different managers since.
This is institutional knowledge. It belongs to the organization, but the organization doesn't have it. The people do — until they don't.
Why knowledge bases don't get built
The standard answer is a wiki. Create a Confluence space. Start a Notion page. Assign someone to document the processes.
This works until it doesn't. Documentation projects stall because the people who know the answers are the busiest people in the building, writing documentation feels like admin rather than work, nobody knows what to document until someone asks about it, and the person who'd benefit most from the documentation isn't the person being asked to write it.
The fundamental problem is that knowledge base maintenance is voluntary. It requires someone to proactively convert tacit knowledge into written knowledge — before they know anyone needs it.
Most of the time, that doesn't happen. The question gets answered verbally. The knowledge stays tacit.
What anonymous Q&A actually surfaces
Anonymous questions are different from survey responses or feedback forms. They're specific. They're timely. They're real problems someone is currently having and is willing to ask about — just not with their name on it.
"Does the company match pension contributions in the first year, or only after the probation period?"
"If I'm working from a different country for two weeks, do I need to tell anyone?"
"Is there a formal process for raising a concern about a colleague's behaviour, or does it all go through my manager?"
These are not questions people ask in team meetings. They're not questions that appear in annual engagement surveys. They're questions that sit unanswered, or get answered incorrectly through informal channels, or — in the worst case — lead someone to make the wrong decision because they didn't feel safe asking.
When you create a safe channel for these questions, you find out what your team actually needs to know. And when those questions get answered, you have something valuable: a documented exchange between a real question and an authoritative answer.
That's the raw material for a knowledge base. It just needs a place to land.
How HushAsk + Notion turns answered questions into permanent records
When a public thread in HushAsk is answered and ready to close, the admin has the option to archive it to Notion with a summary title. One click opens a modal. You type a clear, searchable title — "How does pension matching work in year one?" — and HushAsk creates a page in your Notion Hush Library with the question, the answer, the routing, and the date.
The next time someone has the same question, there's a record. Not a policy document that's three years out of date. A real question with a real answer, given by someone in HR or operations who knew what they were talking about.
Over time, the pattern becomes visible. Repeated questions point to gaps in onboarding documentation. Clusters of questions around specific topics point to policy confusion. The knowledge base builds from what employees actually needed to know — not from what HR assumed they needed to know.
What this looks like in practice
A few months into using HushAsk, a People Ops team at a 120-person company has a Notion database with 40–50 entries. Questions about benefits, remote work policy, performance review process, expense claims. Each entry has a clear title, the full Q&A, and a status. New employees get pointed to it during onboarding. Managers link to it when the same question comes up in 1:1s.
Nobody wrote the documentation. It emerged from conversations that were already happening — just below the surface.
The anonymous format matters for this. Some of those questions couldn't have been asked with a name attached. The pension question. The remote work question. The one about the colleague. They surface through HushAsk because the asker didn't have to identify themselves. They end up in Notion because the answer was worth keeping.
One thing to be clear about
The Notion archive is optional and intentional. HushAsk doesn't automatically log every message — each archive entry is a deliberate choice by an admin after a question has been answered. This keeps the library useful rather than becoming a dump of every anonymous message the tool has ever processed.
Not every question needs to be archived. The ones that do are easy to identify: if you'd explain the same thing to the next person who asks, it's worth saving.