Some business processes look more established than they really are.
The work gets done. People know who to ask. Problems get resolved. Information ends up where it needs to go.
Then the person who normally handles it isn’t available.
Someone is on vacation. An employee is covering another role. A new person takes over a responsibility. Someone leaves the company.
Suddenly, a process that seemed routine becomes much harder to follow.
Not necessarily because the company doesn’t have a process.
Sometimes it’s because part of that process lives with the person who knows how to make it work.
That creates an important question:
Does the process belong to the company, or does it depend on the person who knows how to perform it?
A Working Process Isn’t Always a Repeatable Process
When the same person performs a task repeatedly, they develop knowledge that may never become part of the documented process.
They know where to look.
They know who needs to be involved.
They know which information matters.
They know which steps have to happen in a particular order.
They know what to do when the normal process doesn’t quite fit the situation.
Over time, those decisions can become so familiar that they don’t even feel like decisions anymore.
From the outside, the process appears to work.
But there’s a difference between a process that works because the company has established it and one that works because an experienced employee knows how to fill in the gaps.
The difference often becomes visible when someone else has to perform it.
The Written Steps May Not Tell the Whole Story
Documentation matters.
A checklist, procedure, template, or written set of instructions can make a process easier to repeat.
But documenting the steps doesn’t automatically capture everything someone needs to understand.
Consider something as routine as setting up a new construction project.
An experienced employee may know what information needs to be collected, where the project record belongs, who needs access, what needs to reach the project team, and what has to happen before the setup is complete.
A written instruction that simply says “set up the new project” doesn’t capture that knowledge.
Even a checklist can leave important questions unanswered.
How do you know whether the required information is complete?
Who needs access?
Who else needs to know the project has been created?
What happens when something required for setup isn’t available yet?
What changes when the project has a requirement that doesn’t fit the normal process?
The employee who regularly performs the process may know those answers without thinking about them.
Someone covering the responsibility may not.
Knowing the steps and understanding the process aren’t always the same thing.
Look for the Decisions Hidden Inside the Process
Some of the most important knowledge in a business process isn’t a step.
It’s a decision.
Think about someone covering for a project manager, project administrator, or another employee who normally handles a particular responsibility.
Finding the procedure may only be the beginning.
They may also need to recognize that a piece of information is incomplete, that someone else needs to be involved, that something has to happen before work can proceed, or that the normal process doesn’t fit the situation in front of them.
An experienced employee may make those decisions almost automatically.
That makes them easy to overlook when the company documents the process.
Instead of only asking:
What steps do you perform?
It can also be useful to ask:
What do you need to know to perform those steps correctly?
And:
Where do you have to make a decision?
Those questions can reveal parts of the process that otherwise remain dependent on individual experience.
Not Every Piece of Knowledge Needs to Be Documented
The answer isn’t to write down everything an employee knows.
That would quickly create documentation that is difficult to maintain and even harder to use.
Some knowledge comes from experience.
Some decisions require judgment.
Some situations genuinely need someone who understands the work.
The objective is not to remove people from the process.
It’s to understand where the company has become unnecessarily dependent on knowledge that only one person has.
Consider what another capable employee would need if they had to cover the responsibility tomorrow.
Could they find the process?
Could they find the information the process depends on?
Would they know who is responsible for what?
Could they recognize when the normal process doesn’t apply?
Would they know where to go when they need help?
Those questions are more useful than trying to document every possible situation.
The Information Around the Process Matters Too
Even good documentation has limits if the information needed to perform the process isn’t accessible.
A project administrator covering for someone else might understand the procedure but still need project records, previous correspondence, templates, contacts, shared files, or access to an application before they can actually perform the work.
If important information is scattered across personal folders, individual mailboxes, local devices, or systems that only certain employees understand, the written procedure can only help so much.
This is where process documentation and information management connect.
The company doesn’t only need to preserve the instructions.
It also needs to consider whether the information required to follow those instructions is available to the people who may legitimately need it.
A repeatable process depends on both accessible knowledge and accessible information.
Technology Can Make Knowledge Easier to Use
Technology can help reduce unnecessary dependency on individual knowledge.
Shared documentation can make procedures easier to find.
Consistent information locations can make supporting records more accessible.
Permissions can help make sure the appropriate people have access without giving everyone access to everything.
Templates and workflows can reinforce parts of a process that should happen consistently.
Automation may help with predictable steps when the business requirement is well understood.
But technology can’t capture operational knowledge the company hasn’t identified.
Moving an undocumented process into a new application doesn’t suddenly make the process understood.
Automating a workflow doesn’t answer questions the company hasn’t decided how to handle.
And storing documents in a shared location doesn’t guarantee that someone understands what those documents mean or what they should do next.
Technology can make established knowledge easier to access and use. It can’t replace the operational understanding that was never captured.
The Goal Isn’t to Make People Interchangeable
Experienced employees are valuable partly because of what they know.
The goal isn’t to make one employee interchangeable with another.
It’s to make sure routine parts of the operation don’t unnecessarily depend on one person’s availability.
A strong process allows experience to improve the way work gets done without requiring that same person to be present every time the process needs to work.
That can make it easier for another employee to cover a responsibility.
It can help a new employee understand how the company operates.
It can help maintain consistency when responsibilities change.
And it can allow experienced employees to spend less time answering the same basic questions.
The company still benefits from their experience and judgment.
It just doesn’t require every piece of operational knowledge to remain in someone’s head.
Operational Foundations Support the Construction Technology Framework™
The five pillars of the Construction Technology Framework™ depend on more than applications and infrastructure.
They are supported by Operational Foundations:
Documentation. Standards. Processes. Training. Governance.
Those foundations help turn individual knowledge into something the organization can depend on.
Documentation can preserve important knowledge.
Standards can establish what needs to happen consistently.
Processes can define how work moves through the company.
Training can help people understand more than just the individual steps.
Governance can establish responsibilities and help keep those processes current.
Technology supports those foundations, but it doesn’t replace them.
The objective is to create an operation where the company can benefit from individual experience without depending entirely on individual memory.
A Process Should Be Able to Outlast the Person Performing It
People will always bring experience, judgment, and knowledge to their roles.
That’s a strength.
The risk comes when important parts of the operation only work because a particular person knows what to do.
A useful test is simple:
If someone else had to perform this process tomorrow, what would they need to know?
The answer may reveal missing documentation.
It may reveal inaccessible information.
It may reveal an unclear responsibility.
It may reveal a process that was never fully defined.
Or it may confirm that the process is already working well and doesn’t need to change.
The goal isn’t to document everything or remove judgment from the work.
It’s to make sure the company owns enough of the process that the process can continue when the person performing it changes.
That’s Construction First. Technology Second.
Better Decisions Keep Projects Moving™.
Understand What Your Processes Actually Depend On
The Construction Technology Review™ looks beyond individual applications to understand how your people, processes, project information, and technology work together.
Using the Construction Technology Framework™ and its supporting Operational Foundations, M-Squared Networks looks at how important work gets done, what information people depend on, where knowledge or responsibilities may be concentrated, and whether technology is supporting the operation effectively.
The objective isn’t to document every task or eliminate the need for experienced people.
It’s to understand what your construction company depends on and where clearer processes, accessible information, appropriate standards, training, or technology could make the operation more reliable.
Take a closer look at whether important processes belong to the company or still depend too heavily on the person who knows how to make them work.