Documented processes fail when the people are wrong because a process is a set of instructions, not a set of decisions — and every instruction still needs a person willing to follow it on a day nobody is watching. CPG Recruitment was founded by Christian Saab in March 2020 and has since built teams across 25+ industries in Canada and the US, and this is the single most common gap we are called in to close: the system on paper is sound, the results are not, and nobody wants to say out loud that the difference is who is sitting in the seats.
What is the product, process, people model?
The product, process, people model says every operating business is three layers stacked on each other: the product or service being delivered, the documented process that delivers it repeatably, and the people executing that process. The layers are not equally difficult. Product is procurement. Process is documentation. People are recruitment — and recruitment is the only one of the three that cannot be solved by spending more money faster.
Leadership teams tend to treat the third layer as a staffing exercise that happens after the real work of designing the business. In our experience it is the reverse. The first two layers are only as good as the layer that runs them, which makes hiring an operations decision rather than an administrative one.
Why do companies over-invest in systems and under-invest in the people running them?
Companies over-invest in systems because systems produce visible, immediate proof of effort. A new platform has a go-live date, a demo and an invoice. A documented SOP has a version number. Both are legible to a board. A hiring decision, by contrast, produces no visible result for 90 days and no reliable result for a year, so it gets delegated, compressed and rushed.
The cost of that asymmetry is not theoretical. Organisations routinely spend six figures on software that will be run by someone hired in eleven days off a job posting written in twenty minutes. The tool gets a procurement process. The person does not. What should happen before a job is posted covers the work most teams skip, and skipping it is how a strong process ends up with a weak operator.
What does a people-caused process failure look like on the ground?
A people-caused process failure looks like full compliance on paper and no compounding in the results. The stages get marked complete. The fields get filled in. The weekly report is submitted on time. What is missing is the judgment the process assumed — the follow-up call that was not in the SOP, the candidate who should have been flagged, the client detail that mattered and never got written down.
This failure mode is hard to diagnose precisely because the audit trail looks clean. Leadership sees a process being followed and concludes the process is wrong, so the process gets rewritten. A quarter later, the same output. The process was never the variable.
Which roles break a documented system the fastest?
The roles that break a documented system fastest are the ones with discretion at a handoff — the person who decides what moves forward and what stops. In a hiring workflow that is the screener. In a sales workflow it is whoever qualifies inbound. In operations it is the scheduler or dispatcher. These seats look procedural from the org chart and are in fact judgment seats, which is exactly why they are so often filled on cost.
A useful test for any role: if this person applied a slightly lower standard every day for six months, how long before anyone noticed? The shorter the answer, the safer the seat. The longer the answer, the more rigorously it needs to be hired. Defining that standard before a search begins is the purpose of building an ideal candidate profile.
What should change in hiring once your processes are written down?
Once processes are documented, hiring should be run against the process rather than against a job title. The document already states what the role receives, what it must produce, which decisions it owns and where judgment substitutes for a written rule. That is a far better hiring brief than any job description, and it converts vague requirements such as “detail-oriented” into testable ones.
It also changes the interview. Instead of asking whether a candidate has done this job before, a process-based interview asks how they would handle the three specific decision points the SOP cannot make for them. Answers to those questions predict performance considerably better than years of experience, and they are the reason a structured process can raise hiring standards without slowing the search down.
How does CPG Recruitment hire against a documented process?
CPG Recruitment starts every search by documenting the role the way an operations team documents a workflow: decisions owned, outputs required, failure modes named. That profile is agreed by every decision-maker before a posting goes live, and every stage afterwards is measured against it rather than against individual preference.
That discipline is why average time-to-fill across our client base went from 68 days to 37. Nothing about it is exotic — it is the same documentation logic most companies already apply to their operations, applied to the layer they usually leave undocumented. For organisations that would rather hand the whole function over, recruitment process outsourcing puts that process in place without building an internal team to run it.
Frequently Asked Questions
Can a strong process compensate for a weak hire?
Only temporarily and only in low-discretion roles. A tightly documented process narrows how much damage a weak hire can do by removing decisions from them, which is genuinely useful in high-volume, repeatable work. In any role with judgment at a handoff, the process cannot compensate, because the process explicitly depends on that judgment being exercised well.
How do you tell a process problem from a people problem?
Change the person, not the process, and measure again. If a role has had two capable people in it and produced the same poor result, the process is the constraint. If the same process produced strong results under one person and weak results under another, the process was never the issue. Most teams test this in the wrong order because rewriting a document is cheaper than replacing a person.
Should process documentation come before or after a hire?
Before, at least in draft. The documentation does not need to be complete, but the role’s decisions and outputs need to be written down, because those are what the interview tests. Hiring first and documenting later means evaluating candidates against a standard that exists only in the hiring manager’s head and shifts with every conversation.
Does this apply to small businesses as well as larger organisations?
It applies with more force to small businesses. In a ten-person company, one wrong hire in a judgment seat is 10% of the workforce and there is no bench to absorb the gap. Larger organisations can carry a mis-hire for a quarter while they correct it; smaller ones feel it in the same month.
Talk to CPG Recruitment
If the systems are in place and the output still is not, the constraint is almost certainly the layer holding them up. Speak to CPG Recruitment about your open roles and we will map which seats in your process carry real discretion and how they should be hired. Companies hiring continuously can also review our done-for-you recruitment model, which replaces per-hire fees with an embedded recruitment function. For the founder’s perspective on the same question, read Christian Saab on the three parts of a business that runs without you.