Process improvement for Alberta companies
that run on people, not paperwork

Our processes aren't written down. Is that a problem?

Not on its own. It is how most companies get to your size. A few capable people solved problems as they came up, and the way they solved them became the way things are done. That got you here, and nobody should be made to feel it was a mistake.

It starts to cost you in three situations. When you grow, because new people can only learn by watching someone who is already too busy. When you want to step back, because the business still needs you to remember how things work. And when someone leaves or retires, because what they knew leaves with them. That one is coming whether you plan for it or not. In Alberta construction alone, BuildForce Canada expects 43,400 workers, about a fifth of the 2024 workforce, to retire by 2034. In a company where nothing is written down, everything those people know about how the work gets done goes with them.

Documentation is still not where we start. A binder of procedures nobody follows is worse than none, because it looks like the problem is solved. We start by following one real job through your operation with the people who touch it. What gets written down comes out of that, short and in their words, and only for the steps that break when the usual person is away.

Why do process changes fail in companies our size?

Rarely because the new way was wrong. A 2024 review of 49 studies on why process improvement projects fail found the main causes were resistance to cultural change, weak support from leadership, inadequate training, poor communication and lack of resources. Not one of those is about the process itself. They are about how the change was handled.

In owner-led companies it usually looks like this:

• People were told, not asked. The new way was designed in an office and handed to the people who do the work, who could have pointed out what it missed.
• The change landed on top of a full workload. Nobody's day got lighter to make room for learning something new, so the old way won by default.
• Nobody explained why. The owner knew the reason. The crew, the office and the field heard only that things were changing again.
• Pushback was treated as an attitude problem. When experienced people resist a change, they are usually telling you something true about the work that the plan did not account for. We treat that as information, not as an obstacle to push through.
• The answer to resistance was more pressure. Mandates and incentives can get people to comply on the surface while they quietly stop telling you what is going wrong. That is how a change looks finished on paper and gets worked around on the floor.

When does the change management part happen?

From the first conversation, not at rollout. Getting people to use a new way of working is not a final step you add once the design is done. Whether people adopt a change is decided by how it was built: who was asked, what they were told, and whether the new way fits the work as they actually do it.

So the people who do the work help shape the change before anything is decided. We try it on one small piece of the operation first, with the people involved, adjust what does not fit, and only then widen it. It is slower at the start. It is faster after, because nothing has to be forced and nothing has to be redone.

What about the people who know how everything works?

Every company your size has them. The estimator who knows which customers always change their minds. The office manager who knows where every file is. The superintendent the crews call before they call anyone else. They are among the most valuable people you have, and a process change can feel like a threat to them, because what they know is part of why they matter.

So they come in first, not last. Their judgment goes into the new way of working rather than being written around it. The goal is not to make them replaceable. It is to stop them being the bottleneck for questions anyone could answer, so their time goes to the work only they can do. And a map of how work moves is never used to judge an individual. It shows where the work waits and gets retyped, which is almost always about how the pieces connect, not about who is doing the job.

Will our people think this is about cutting jobs?

Some will wonder, and they deserve a straight answer early rather than a rumour later. Our work is aimed at the hours lost to waiting on answers and retyping the same information into different places, so the people you have can spend that time on work that needs them.

That matches what Canadian businesses report. When Statistics Canada asked businesses that had started using AI what happened next, 89.4 percent reported no change in their employment levels, and the most common change they did make was developing new workflows. The change that mattered was in how the work flows, not in who does it.

Where does the owner fit in?

In more than forty conversations with operators, one sentence came up again and again, usually said plainly:

"I don't trust these people to run my company the way I can, I stay involved to ensure it stays on track."

That is not a flaw. It is often the only reliable way the business has had to stay on track. But it means everything routes through you, and past about five direct reports a leader's day goes to coordinating other people's work rather than running the business.

A change needs you visibly behind it. Your team will watch whether you hold to the new way when it is inconvenient. What it cannot do is depend on you for every decision, or you end up as the bottleneck in the new process too. Part of the work is deciding which calls stay with you and which can move to someone else, and then letting them make those calls. That is often the hardest part for an owner, because being the person who solves every problem is how the business was built. When a leader stops answering every question first, other people start stepping forward with answers of their own.

How fast can we change how things work?

At the pace your team can absorb, which is usually slower than an owner wants and faster than the team expects. We change one thing at a time, start where the payoff is clear, and avoid your busiest season. We aim to have the first bottleneck solved within 60 days, because people believe in a change once they have seen one work, not when they are told it will.

Where do software and automation fit?

After the people and the process, never before. Once the work is mapped and the handoffs that should not exist are gone, some of what is left is worth automating. Often the answer is a setting in a system you already pay for. Sometimes it is a new system, and our pages on choosing an ERP and on implementations that went live without getting faster cover that decision.