You've written the SOP. You've shared it with the team. You may have even held a training session. And yet — somehow — every person on your staff seems to have their own interpretation of how client onboarding actually works. Sound familiar?
The problem usually isn't your team. It's the SOP itself. Most procedures are written to document what should happen, not designed to make it easy for a real human being — stressed, distracted, or brand new — to do the right thing every single time.
The Rider, The Elephant, and the Path
In their book Switch, Chip and Dan Heath describe human behavior through a memorable metaphor: a rider on an elephant, traveling down a path. The rider is our rational mind — careful, deliberate, and good at making plans. The elephant is our emotional, instinctive side — powerful, but prone to taking shortcuts when the route feels hard. The path is the environment around them.
Most SOP failures happen because we spend all of our energy trying to train the rider — writing detailed instructions, hosting meetings, sending reminders — while ignoring the path entirely. But here's the truth: if the path is clear, smooth, and easy to follow, even the most distracted elephant stays on course.
"Your SOP should be so well-designed that whether your employee is having a great day, a horrible day, or their very first day — they can't help but follow it correctly."
That is the standard to hold your procedures to. Not "good enough to follow when things are going well," but robust enough to guide your team even on the hard days. The goal is to build the path — and then make it nearly impossible to veer off of it.
Build In the Guardrails
A great SOP isn't a list of suggestions — it's a sequence of guardrails. Each step should lead naturally and inevitably to the next, so that skipping or reordering becomes harder than just doing it right.
In practice, this means structuring your procedures so that a later step literally cannot be completed until the earlier one is done. If your team uses a workflow tool like Wealthbox, Redtail, or Hubly, this might mean building a workflow where Task 2 doesn't appear until Task 1 is marked complete. If you're working from a checklist, it means the checklist is the source of truth — not a loose document floating in a shared drive that someone has to remember to find.
Design principle: If your SOP can be completed out of order without consequence, it isn't structured tightly enough. Each step should act as a checkpoint — confirming that the previous step happened before the next one begins.
Break It Down and Assign It Out
One of the most common SOP mistakes is writing a procedure from the firm's perspective rather than the individual team member's. A long, multi-page document that covers every role in a single flow is nearly impossible for any one person to own — so no one fully does.
Instead, break your SOPs into clearly separated tasks, and assign each task to a specific role. Not just "the team" — a specific person or position. When accountability is diffuse, things fall through the cracks. When every task has a name attached to it, there's no ambiguity about who is responsible when it doesn't get done.
Equally important: include a realistic timeframe for each task. How long should this step take? Is it a 5-minute action item or a 2-day turnaround? Timeframes set expectations, help managers identify bottlenecks, and give team members a clear sense of pace.
"Every task in your SOP should answer three questions: Who does it? When does it need to be done? And where do they go if they get stuck?"
Link to the Answer Before They Have to Ask
Even well-trained employees hit moments of uncertainty. The onboarding checklist references a form they've never seen. A step involves a system they only use once a quarter. A new hire doesn't know the firm's naming conventions yet.
When those moments happen, the path forks — and the elephant will almost always choose the easier route, which is often "skip it and figure it out later" or "ask someone" (if they can find them). The fix is simple: embed the answer directly in the SOP before they have to go looking for it.
Every task that requires specialized knowledge should include a direct link to the relevant training material, reference document, or recorded walkthrough. Not a link to a folder — a link to the exact resource. The fewer clicks between confusion and clarity, the more likely your team stays on the path.
Automate the Path Where You Can
The best version of an SOP isn't one that relies entirely on human memory and discipline. Wherever possible, build automations and templates directly into the workflow so that the "right way" is also the easiest way.
This might look like:
- An email template that auto-populates with client data, so the right language gets used every time
- A workflow trigger that automatically creates the next task when the previous one is marked complete
- A document generation tool that pulls client information directly from the CRM, eliminating manual entry
- A recurring calendar reminder that prompts a team member to initiate a quarterly review process
Automations reduce cognitive load, minimize the chance of human error, and make the client experience more consistent — regardless of which team member is handling a given task that day. They also free your team up to focus on the high-touch, relationship-driven work that actually requires a human.
The Bottom Line
A well-designed SOP is one of the highest-leverage investments you can make in your firm. It protects the client experience, reduces your dependence on any one person's memory, and creates the operational foundation your firm needs to scale.
But it only works if people actually follow it. So the next time you sit down to write or revise a procedure, ask yourself: have I built the path? Is it clear, sequenced, assigned, time-bound, and supported? Would a brand-new employee know exactly what to do — and exactly where to look if they got stuck?
If the answer is yes, you've built an SOP your team will actually follow.