In many growing businesses, daily operations continue because someone simply knows what to do.
A quotation gets prepared because one employee remembers the usual format. A purchase request moves forward because a senior team member knows who should approve it. A delivery issue gets solved because one person knows the workaround. A report is completed because someone knows where the numbers are stored, which file is updated, and who to ask when something does not match.
For a while, this can feel efficient.
The business moves because experienced people know the work.
But when a process depends too much on one person’s memory, availability, or personal habits, that process becomes fragile.
If only one person knows the process, that is a risk.
The Hidden Risk Behind "Tanong Mo Kay..."
Many businesses run on informal knowledge.
People say, “Tanong mo kay…” because that person has been there the longest, handled the issue before, or knows how the workflow really happens.
This is common in small and growing companies. It is also understandable. When teams are busy, documenting the process often feels less urgent than completing the work.
But the risk appears when the business starts asking important questions:
- What happens when that person is absent?
- What happens when that person is busy?
- What happens when that person leaves?
- What happens when the business grows, and more people need to follow the same process?
When the answer is unclear, the business may not have a process. It may have dependency.
Experience Is Valuable, But It Should Not Be the System
Experienced people are important to any organization. They carry context, judgment, and practical knowledge that no software can automatically replace.
The problem is not the person.
The problem begins when the person becomes the only source of truth.
When a process lives only in someone’s head, the business becomes dependent on availability instead of structure. Work slows down when that person is unavailable. New employees take longer to learn. Teams repeat the same questions. Managers struggle to see whether the process is being followed consistently.
Over time, this creates operational risk.
The organization may appear functional, but the workflow is not easy to transfer, improve, or scale.
A Good Process Should Be Clear Enough to Transfer
A strong process should not depend on one hero.
It should be clear enough for the team to follow, improve, and scale.
That does not mean every process needs a long manual. It means the business should have a shared understanding of how work moves from one step to the next.
A clear process should answer basic questions:
- Who owns the step?
- What information is needed?
- What triggers the next action?
- Where is the source of truth?
- What approval is required?
- What happens when there is an exception?
When these questions are not answered, teams rely on memory, chat messages, repeated follow-ups, and informal workarounds.
That may work for a small team. It becomes harder as the business grows.
Why Undocumented Processes Slow Growth
Growth adds pressure to informal processes.
More customers mean more transactions. More employees mean more handoffs. More locations or departments mean more variation. More decisions mean greater need for visibility and control.
If the process is not documented, repeatable, or easy to transfer, growth can expose weaknesses that were previously hidden.
The same task may be done differently by different people. Approvals may depend on habit rather than policy. Reports may vary depending on who prepared them. New employees may learn through trial and error. Managers may spend more time correcting, clarifying, and following up.
This is where business process improvement becomes important.
Improvement does not always begin with automation. Often, it begins with making the process visible.
Process Standardization Comes Before Digital Transformation
Many businesses look at digital transformation because they want faster operations, better reports, stronger controls, or less manual work.
Those are valid goals.
But technology works best when the process is already clear.
If the workflow is unclear, business automation may only automate confusion. If ownership is unclear, a system may send tasks to the wrong person. If data rules are inconsistent, reports may still be unreliable. If approvals are informal, the digital version of the process may still create bottlenecks.
This is why process standardization matters.
Before a business digitizes, it should first clarify how work should be done.
Standardize before you digitize.
What Process Clarity Looks Like
Process clarity does not need to be complicated.
It can start with one recurring workflow that causes delays, repeated questions, or dependency on one person.
For example:
Sales inquiry to quotation.
Purchase request to approval.
Inventory request to delivery.
Invoice preparation to collection.
Customer concern to resolution.
Monthly report preparation to management review.
The goal is to understand how the work actually moves today, then identify what should become clearer.
Who owns each step?
Where does the work wait?
Which information is often missing?
Which decisions depend on one person?
Which steps should be documented or standardized?
These questions help the business move from informal knowledge to shared operating discipline.
The Role of Systems and Automation
Once the process is clear, systems can help make it more consistent.
A system such as Odoo can support shared data, approval flows, transaction visibility, reporting, and business automation. It can help reduce manual follow-ups and make work easier to track across teams.
But the system should support a better way of working.
It should not simply copy unclear habits into a digital platform.
This is why digital transformation should align people, processes, and systems. People need to understand the new way of working. Processes need to be clear and practical. Systems need to enable the workflow with visibility, control, and continuity.
When these three are aligned, technology becomes more than a tool. It becomes part of a stronger operating model.
Start With One Process That Depends Too Much on One Person
A business does not need to document everything at once.
The practical starting point is to identify one process that depends too much on one person.
Look for signs such as:
People always ask the same person for instructions.
Work stops when that person is unavailable.
New team members find the process difficult to learn.
The same exceptions are handled each time differently.
There is no clear reference for how the work should be done.
Reports, approvals, or updates depend on personal follow-up.
Once the process is identified, the business can begin to document the flow, clarify ownership, define required information, and agree on the standard way of working.
That is where sustainable improvement begins.
Final Takeaway
Every business has people who carry valuable knowledge.
But valuable knowledge should not stay locked inside one person’s head.
When a process is clear, documented, and repeatable, teams can follow it more confidently. Leaders can improve it more intentionally. New employees can learn it more quickly. Systems can enable it more effectively. The business can scale with less dependency and more control.
That is the foundation of better ways of working.
Because digital transformation does not start with tools.
It starts with process clarity.
📩 Let’s Continue the Conversation
Ready to explore what better processes, greater visibility, and an integrated ERP system could unlock for your organization?
Start Somewhere with Something Somewhere Consulting and begin building a practical path toward sustainable business transformation.