💡 Core Concepts & Executive Briefing
Understanding Brain-Dumping and SOPs
If you’re a business consultant, your “product” is your thinking: how you diagnose issues, design fixes, run workshops, write proposals, and guide teams through change. The problem is that a lot of that knowledge lives in your head. When it does, your delivery quality depends on you showing up—every time.
That’s what SOPs and brain-dumping solve.
SOPs (Standard Operating Procedures) are the step-by-step instructions that let your team deliver your work consistently without you hovering over their shoulder. For a consultant, SOPs aren’t just about administrative tasks like scheduling. They should also cover repeatable client-facing work like intake, discovery structure, analysis templates, stakeholder interviews, workshop facilitation flow, recommendation write-ups, and proposal production.
The goal: 80% effective on day one
A strong SOP should be clear enough that a trained teammate can hit about 80% of the outcome on their first day using it. Not “perfect,” but reliably good. When you hit this standard, you stop being the single point of failure.
Example: If you regularly run a “Process and Profit Leak Audit,” you shouldn’t have to re-explain the same sequence every time. A contractor should be able to start the audit, collect the right inputs, produce the first draft, and bring you only the missing pieces.
The Importance of Brain-Dumping
Brain-dumping is the practice of pulling your expertise out of your head and turning it into something other people can use. In consulting, that often means recording what you do when you:
- prepare for a discovery call
- ask the right questions
- analyze notes into themes
- turn findings into recommendations
- structure a proposal so it wins
If you don’t brain-dump, your knowledge stays “locked” in your habits. Then growth becomes slow and expensive because every new hire has to learn by trial and error—or by interrupting you.
Creating Effective SOPs (for consulting work)
Use this simple structure for every SOP:
1. Why: Start with the reason this task matters.
- For example: “Why we run discovery this way: it prevents us from recommending solutions that don’t fit the client’s constraints.”
2. What: List the exact steps.
- Break it down into checkable actions, like: “Confirm agenda and stakeholder list,” “Collect last 90 days of metrics,” “Ask for prior attempts and what failed,” “Summarize risks and assumptions.”
3. Outcome: Define what success looks like.
- For example: “A completed Discovery Summary that includes: key problem statements, top 3 constraints, decision-maker map, evidence links, and open questions.”
This turns your experience into a measurable deliverable.
Organizing Your SOPs (so people can actually use them)
Store SOPs in one place your team can search fast. If your SOPs are scattered across emails, folders, and chat threads, they won’t get used.
A practical setup: create a “Consulting SOP Vault” with folders for:
- Client Intake
- Discovery
- Research & Analysis
- Workshops
- Deliverable Drafting
- Proposal Production
- Client Communication
Add a short naming standard like: “DISC-01 Discovery Call Prep” or “PROP-03 Proposal Outline.” When someone needs help mid-project, they should be able to find the right doc in under a minute.
The Loom-First approach (because consulting work is visual)
For many consulting tasks, writing first is painful and slow. Recording first is faster.
Use Loom to capture yourself doing the work on your screen. Examples:
- recording how you turn messy discovery notes into a clear problem statement
- recording how you fill in your analysis template (and what you look for)
- recording how you build a proposal outline from a discovery summary
Then convert those Loom recordings into SOPs. This creates “video truth” plus a searchable written guide.
A good SOP isn’t a wall of text—it’s a clear path. Loom shows the path; the written SOP makes it repeatable.
Building a Culture of Self-Reliance
Your team should know that SOPs are the first stop, not the last resort.
Set the expectation: “Before you ask me, check the Vault.” When someone gets stuck, they should tell you what they tried and which SOP they followed (or couldn’t find). That keeps you from being interrupted for predictable tasks.
Over time, this builds a team that can deliver consistent client outcomes—while you focus on higher-leverage work like client strategy, deal shaping, and improving your consulting offers.
When you brain-dump and document, you stop “carrying” the business in your head and start building a delivery system your team can run.