Most knowledge systems fail not because they’re poorly built, but because they ask too much from the people meant to use them. At Protogen Corp, years of investment in templates, folders, and formal documentation workflows produced very little usable knowledge. The insight was there, in conversations, quick notes, and problem-solving threads but it never made it into the system. That’s where Phlow made the difference. By meeting employees where they already work and making it effortless to contribute unstructured content, Phlow turned forgotten thoughts into searchable, connected knowledge, without changing how people worked.
Context
At Protogen Corp, leadership had invested in several knowledge management initiatives over the years. The problem wasn’t setting up systems. It was getting people to use them.
Employees avoided writing documentation unless it was mandatory. When they did, it was either lost in a drive or locked in a document template no one understood.
“We had templates, folders, guidelines — and no actual knowledge being captured.”
Meanwhile, important insight was shared in chats, emails, hallway conversations, or buried in long-format PDFs with no structure or context.
The Challenge
Every attempt to standardise knowledge contribution turned into a burden:
- Document templates were hard to find and harder to fill
- Contribution required a fixed format and approvals
- People had to “pause their work to write it down”, so they didn’t
- Everyone knew that what they wrote was buried in some document management system and that their time would be wasted
Knowledge that did get written often went unused, because it wasn’t linked to anything else. It sat in isolation, unconnected, unfindable, and forgotten.
What Phlow Did
Phlow flipped the model.
Instead of forcing structured contribution, it allowed people to write naturally, and then made sense of it automatically.
- Engineers started writing informal wiki-style articles and personal notes
- Teams used discussions to problem-solve and capture reasoning in the moment
- Project leads posted lessons learned without worrying about formatting
- External documents were simply uploaded and contextualised by Phlow
The system:
- Parsed and understood each input, whether it was a note, a doc, or a message
- Auto-related it to relevant projects, topics, and past work
- Made every contribution instantly searchable, referenceable, and connected
“Now it takes 2 minutes to write something, and the system makes it useful without us doing anything else.”
Outcome
- Contribution rates increased across the company, especially from ICs and frontline teams
- Meetings led to quick notes and decisions that didn’t disappear afterward
- Knowledge stopped being an afterthought and became part of the flow of work
- Managers began referencing employee insights in decisions, because they could find them
“We used to document for compliance. Now we write things down because it actually helps.”
Why This Matters
Most systems require you to format knowledge. Phlow lets you capture thoughts, and it formats the insight for you.
Most systems collect a huge amount of information, transforming it into more work for someone else. Phlow processes unstructured information and converts it into actionable knowledge, making it immediately available to everyone in the organisation.
It’s not about asking people to do more. It’s about making it easy enough that they don’t even notice they’re doing it, and powerful enough that the system does the rest.
More Articles
When Knowledge Lives Everywhere, You Can’t Trust Anything: Why Enterprises Need a Single Source of Truth
Nothing stalls a team faster than when things go wrong and no one can agree on why. A deadline slips, a project derails, or a customer gets the wrong answer, and suddenly the hunt begins. [...]
When Knowledge Speaks a Different Language, and No One Understands
In global enterprises, knowledge should flow freely across offices, teams, and time zones. In reality, it rarely does. One of the most overlooked reasons? Language. When a company has locations in Tokyo, Milan, São Paulo, [...]
The Problem with Tribal Knowledge
Every single company lose it every day. Most don’t know what to do about it. And very few realise how much it costs them. I’m talking about tribal knowledge. What the Hell is Tribal Knowledge? [...]
When Answers Take Days: The Hidden Cost of Not Knowing Who Solved It Last Time
You’ve been here before. A project stalls because a critical question doesn’t have an answer. Someone remembers it came up last year. The answer exists somewhere. But nobody remembers exactly where. Or who figured it [...]
The Hidden Cost of Management’s Endless Report Requests — and How to End It
Every product company has the same unspoken habit: When leaders can’t find the information they need, they go straight to the people who can. And too often, that means engineers. Executives are not handing investor [...]
Transparent vs Need-to-Know: Choosing the Right Knowledge Culture for Your Enterprise
Two Cultures of Knowledge – Transparent vs Need-to-Know In the modern enterprise, knowledge is power, but how that power is distributed defines the culture of an organisation. Broadly speaking, companies fall into two categories when [...]