I Asked 30 Founders What does a new Hire do when they need to find something.
I asked 30 software founders where new hires go to find answers. The resounding majority answered with "They ask someone". Here's the ranked list of how co
I have been researching the Institutional Knowledge Crisis that has been plaguing companies since their inception. To that end, I have started to interview business owners and startup founders to reach the root cause of the issue. Since the past few weeks, I have interviewed close to around 30 COO, CEO, and Startup Founders. During my conversations with these accomplished individuals I found that for a specific question about “What does a new hire do when they need to know how something is done?”, the astounding majority answered with “They ask someone”.
Follow-up analysis revealed that they were aware that this does impact the performance of high performers since they have to halt their current tasks to answer the question, or it creates a fear in near hires to only ask questions when said individuals are free which hampers their productivity. This was a straight contradiction to what we expected to hear, only half a dozen responded with “they check the wiki” while almost everyone had one. Naturally the question becomes why is that the case?
What I actually asked
The objective of these questions was to understand how knowledge propagates in an organization, the main question that I was looking to get answers on was:
When a new hire needs to find out how something is done in your organization, where do they look first?
Very specific, and very personal, this was the ideal question to ask instead of beating around the bust and asking “do you have a knowledge problem?" or “would you use a tool that fixed it?” Although relevant, these questions did not reveal the core problem that these organizations were silently facing.
Where company knowledge actually lives, ranked
From my conversations, I was able to essentially qualify and rank on the bases of frequency how organizations answer this very question:
- They ask someone. The most popular answer by a huge margin, and the most logical as well since none of us think too deeply about occupying someone’s time as long as it solves our immediate issue.
- They check Slack. The second logical, and specific to organizations that actively log everything on their communication tools, unconsciously creating a heavy reliance on its accuracy and accessibility.
- They check Notion. The third more unique, yet foundational answer however in the same sentence negated its usefulness due to it being set up once and never updated properly.
- They just google it. A fanatical approach in theory but it worked where knowledge on the problem was readily available on the internet, or enough was present to make an educated guess.
- The official wiki. This was an answer that I only heard a couple of founders say, yet it struggled with the same issue as the notion where periodic updates once a year make the wiki mostly outdated during Q2 onwards.
The pattern nobody names
Just by going through the answers outlined above, you notice immediately that there isn’t a specific system that anyone has in place that reliably works, every time, for everyone.
All options, though completely standard for how organizations operate, are either unreliable, or break the momentum of the person who knows the answers, essentially punishing them for their exceptional knowledge.
After these conversations, the most valuable insight that I got that I still think about from time to time is:
These teams weren’t missing information layer, they were missing a standardized and easy to use access point to reach that information layer.
Think about it this way, the knowledge that the new hire needs isn’t something new, its something that has already been done or is often followed as a rule of thumb, but they aren’t able to get to that knowledge as easily as they should be without interrupting someone.
Yet that information has no inherent value, in plain terms it useless sitting in an years old slack thread because stored isn’t the same as accessible, and accessible isn’t the same as findable. When institutional knowledge checks all three of the above boxes it can be considered as useful.
Why the wiki keeps losing
What I least expected was that companies that had a Notion workspace or org wiki would be somehow better off. Yet that was not the case at all. New hires still preferred to ask someone if they are available instead of just checking existing guides, or rulebooks.
This was mainly due to the fact that wiki’s themselves are only useful if there is a culture of referring to them built in the organization. But most of the times, wiki’s are built as a task required to be considered as a “modern organization”, with beautify Notion workspaces or detailed rulebooks. Instead of it being built to be helpful, the process of building it becomes and excuse of being productive, the same way scrolling LinkedIn during working hours is considered productive. This creates a deadly loop where employees pride themselves on the number of SOPs they have written instead of measuring how many employees they have helped with their SOPs’ instead.
What the gap actually costs
Now this doesn’t directly drop a company's stocks by 10% in weeks. So no immediate impact on P&L statements, yet that is exactly why it continues to fester for longer until the company is only resignation away from looking at 40% of their knowledge on processes. The effects become notable when:
- A new hire takes weeks to ramp up because they need to constantly refer to an individual for answers.
- Talented and High Performers start losing momentum and have declining stats due to constantly being interrupted.
- When people leave, they take context and information that was never written down with them.
All of these are real costs that companies have to bear almost every quarter. The inherent nature of the problem not seeming urgent is why it festers until too much information is lost for anyone to do anything.
What I'd do about it this week
From my conversations I realized that it’s not anyone’s fault for overlooking this concern, and fixing it can be done easily. Run this exercise with your team if you feel like you have them problem:
- Check in with your most recent hire and ask them “what was the hardest answer you had to find in your first month?”
- Check in with your frequently interrupted employee “what is the question you have to answer over and over again?”
- Your new hire tells you what SOP is missing, and your new hire tells you what Process is missing.
I’m stilling having these conversation to get a better understanding of how deep this problem goes and how business owners tackle it. That is why I’m building Lynxient to close this gap and hopefully make accessing institutional knowledge easier for businesses.
If you run a team of 10-60 employees and you think you have this problem, I’d genuinely love to have a discussion with you to hear your version of it. DM me at Huzaifa Bin Saif on LinkedIn.