One of the most common things I notice in growing businesses is this:
The founder keeps getting the same questions.
“Can I approve this?”
“What should I do with this customer?”
“Who should handle this?”
“Where do I update this?”
“Should I go ahead?”
Sometimes the founder gets frustrated.
They may think:
“I have already explained this several times. Why are they still asking me?”
But before blaming the employee, I think it is worth asking a different question.
Where does the answer actually live?
Because very often, the answer lives in the founder's head.
When the founder becomes the knowledge base
In the early days of a business, this is completely natural.
The founder knows the customers.
The founder knows the processes.
The founder knows what decisions were taken and why.
The founder remembers what happened the last time a similar situation came up.
So employees ask.
The founder answers.
The business moves.
But as the team grows, this model becomes difficult.
The founder cannot continue being the company's internal search engine.
Yet that is exactly what happens in many businesses.
Someone needs an answer.
They don't know where to find it.
So they ask the person who always knows.
The founder.
The employee may not actually need another explanation
This is something I have learned over time.
When someone asks the same question repeatedly, the first instinct is often:
“I need to train this person better.”
Sometimes that is true.
But sometimes the person has been trained perfectly well.
The problem is that there is nowhere to refer back to.
Maybe the process was explained verbally.
Maybe it was discussed in a meeting.
Maybe it was shared on WhatsApp.
Maybe someone sent a message six months ago.
Maybe there is an SOP somewhere in Google Drive.
The employee remembers part of it, but not enough to act confidently.
So they ask again.
Repeated questions are often a systems signal
I would pay attention to repeated questions.
They can tell you:
The process isn't clear.
The ownership isn't clear.
The decision authority isn't clear.
The information isn't easy to find.
Or simply:
The process exists only in someone's memory.
That is useful information.
Instead of asking, “Why are people asking me this again?”
Ask:
“Why do they need me to answer this?”
That question usually takes you much closer to the real problem.
What can a founder do?
Start with the questions you answer most frequently.
Don't try to document everything.
Pick the top ten.
For each one, ask:
Who normally handles this?
What is the standard answer?
What exceptions can occur?
When should the employee escalate it?
Where should the information be recorded?
Then create a simple reference.
It could be an SOP.
A checklist.
A decision tree.
A process map.
Even a simple FAQ can help.
The format is less important than the accessibility.
Give people authority, not just information
There is another reason employees keep coming back.
Sometimes they know what to do.
They just don't know whether they are allowed to do it.
For example:
An employee knows the customer qualifies for a particular resolution.
But they don't know whether they can approve it.
So they ask the founder.
That isn't a knowledge problem.
It is an authority problem.
If you want employees to make decisions independently, define the boundaries.
What can they decide?
What needs approval?
What requires escalation?
That clarity can eliminate a surprising number of interruptions.
The goal is not zero questions
I don't think a healthy business is one where employees never ask the founder anything.
That would be unrealistic.
Some decisions should absolutely reach the founder.
Strategic decisions.
Major financial decisions.
Important customer relationships.
Sensitive people matters.
New opportunities.
The goal is different.
The goal is to ensure that routine questions don't constantly consume leadership time.
My thought
If employees keep asking you the same questions, don't immediately assume you have a people problem.
You may have an information problem.
Or an ownership problem.
Or an authority problem.
Or simply a process that has never been properly documented.
The founder's knowledge is one of the business's greatest assets.
But if all of that knowledge stays inside one person's head, it also becomes a dependency.
A growing business should gradually move knowledge from people's heads into the way the business works.
That is how you create a team that can think, decide and act without waiting for the founder every time.
Vinitaa Vinod
Founder, ORGOOK Solutions