In 1935, the U.S. Army Air Corps held a fly-off competition to choose its next long-range bomber. The favorite was Boeing's Model 299 — faster, more powerful, and more capable than anything else in the field. On the day of the demonstration flight, it climbed beautifully, stalled, and crashed. The pilot, one of the most experienced in the service, had simply forgotten to release the elevator lock before takeoff. A step he'd done a hundred times. A step that, under the pressure and complexity of a new aircraft with four times the controls of its predecessor, he skipped.
The Army didn't scrap the plane. Instead, a group of pilots put together a simple pre-flight checklist. The Boeing Model 299 went on to become the B-17 Flying Fortress — the backbone of Allied air power in World War II — and logged nearly 1.8 million flight hours without a single accident attributable to pilot error of that kind.
That story is the heart of Dr. Atul Gawande's book The Checklist Manifesto. And I think about it constantly when I'm working on your operations.
The Problem Isn't Incompetence. It's Complexity.
Here's what I want you to hear clearly: checklists are not for people who don't know what they're doing. They are for people doing work that is complex enough that even experts, under real conditions, miss steps.
Financial advisory work is exactly that kind of work. You are managing dozens of client relationships simultaneously, each with its own nuance, timeline, and emotional weight. You're tracking compliance deadlines, investment reviews, document expirations, fee billing cycles, meeting follow-ups, and prospect touchpoints — all while being the only person in the room who holds the full picture of any given client's life. The cognitive load is enormous. The stakes are high. And the conditions are rarely ideal.
In that environment, the question isn't whether you'll ever miss a step. It's whether you have a system that catches it before it matters.
"The checklist gets the dumb stuff out of the way so your brain is free for the work that actually requires judgment."
Two Kinds of Checklists — and Why the Difference Matters
Gawande distinguishes between two types. Understanding which one fits a given situation is part of building checklists that actually get used.
The DO-CONFIRM checklist
You do the task from memory and experience — the way you always have — and then you pause and run through the checklist to confirm nothing was missed. This works well for experienced practitioners on familiar processes. Think: end-of-quarter billing review, or closing out a client onboarding. You know the work. The checklist is the safety net, not the script.
The READ-DO checklist
You read each item and complete it before moving on. This is better for less familiar processes, high-stakes one-time events, or anything being delegated to someone new. Think: setting up a brand-new client in your CRM for the first time, or walking a staff member through an unfamiliar compliance filing. The checklist is the process.
The mistake most firms make is trying to use a READ-DO checklist for everything — and ending up with a 47-step document no one reads. Or using a DO-CONFIRM checklist for something that actually requires step-by-step guidance, and missing the point entirely. Part of what I do when we build your SOPs together is figuring out which type actually fits.
What Good Checklists Do for Your Firm
Beyond catching errors, well-designed checklists do something quieter but just as valuable: they move knowledge out of your head and into your systems. That matters for a few reasons.
It protects your clients when you're at your worst. Tired, distracted, dealing with something personal, overwhelmed with a difficult client situation — you still have to serve the rest of your book. A checklist means your clients get the same quality of process regardless of what kind of week you're having.
It makes delegation possible. You can't hand off a process that lives only in your head. You can hand off a checklist. Whether that's a future hire, a part-time assistant, or just your future self returning to a task you haven't touched in eight months, documented processes are what make other people's help actually useful.
It reduces the mental load of running the business. When you trust that the process will catch what you might miss, you stop white-knuckling every workflow out of fear of forgetting something. That's not just efficiency — that's actual breathing room.
- CRM record created with all household members and relationships linked
- Welcome email sent within 24 hours of signed agreement
- Account opening paperwork sent via DocuSign; task set to follow up in 48 hrs
- Client added to appropriate segmentation tags and communication lists
- Kickoff meeting scheduled; agenda template pulled and customized
- Data gathering questionnaire sent with deadline noted in CRM
- Compliance file started; KYC documentation logged
That list above isn't revolutionary. Every step is obvious — in isolation, on a good day, when you're fresh. But under real conditions, with three other things happening at once? Missing step four means a new client never gets your quarterly newsletter. Missing step seven creates a compliance gap you won't discover until it's inconvenient. The obvious things are exactly the things checklists protect.
Why I'll Keep Building These With You
When we work together on your SOPs and workflows, the checklists we build aren't busywork — they're the infrastructure. They're what makes everything else we build actually hold. A beautiful CRM pipeline is only as reliable as the steps someone reliably takes at each stage. An automation only fires correctly if the right information is in the right fields. And the right information only gets there consistently if someone has a clear, simple process they trust enough to actually follow.
Gawande's conclusion after years of research was simple: in complex work, expertise isn't enough. The best surgeons, pilots, and engineers in the world still use checklists — not because they need reminding of the basics, but because the basics are too important to leave to memory.
Your firm isn't different. Neither are you. And that's not a criticism — it's just how complexity works.