Episode 298 | The Strategic Entrepreneur Podcast
By Cindy Gordon, selective visibility strategist and business mentor
🎧 Listen to Episode 298 on The Strategic Entrepreneur Podcast
Most business owners are told to document everything before they can scale. The advice sounds reasonable, but it is wrong, and it is one of the most common reasons experienced women in business get stuck right before the growth they were planning for.
I am Cindy Gordon, selective visibility strategist and business mentor. I have built and sold four businesses, and I have made every version of the SOP mistake. The skill of selective systematization is one I learned the hard way, and it is the one that actually separates the businesses that scale cleanly from the ones that stall right before they take off.
This article gives you the selective approach to SOPs. What actually needs to be documented. What does not. The test to run before you spend another hour writing a process nobody will read. And how to know when the time is right.
The Trap of Documenting Everything
When you try to document everything, three things go wrong.
The first is bloat. You start with the genuinely important processes. Then you start documenting things that are obvious, things that are rare, and things that might matter someday. By the time you are done, you have a wiki nobody can navigate.
The second is that the documentation does not match how the work actually gets done. Most of the things you do in your business have variations you have not consciously named. You think you have one process for client onboarding. You actually have three, depending on the client. The document captures one of them and the other two are now wrong. The new person you hire follows the document and gets it wrong, and you cannot figure out why.
The third is the most expensive. The time you spent documenting too much is time you did not spend on the actual work that grows your business. Documentation is a tool. Treating it as the work itself is the most common form of busy that looks like progress.
Two Questions Before You Write Any SOP
Before you spend another hour documenting something, run it through two questions.
Does This Truly Repeat?
The first question is about repetition. Does this truly repeat in your business right now? Not “could it repeat someday” or “if I scale it might repeat.” Right now, in your current business, does this exact task or decision come up over and over again in a substantially similar way?
If the answer is no, do not SOP it yet. Things that do not repeat consistently are still decisions. You cannot systematize a decision until it has been made enough times in similar ways that the pattern is clear.
This is where most premature documentation comes from. You imagine a process will need to be systematized once you scale, so you write the SOP in advance. The problem is that the imagined process almost never matches the real one when the time comes. The actual repetition reveals variations and edge cases your imagined version did not anticipate. You end up rewriting the document after the work has already taught you what it actually needed.
Does This Actually Matter?
The second question is about impact. Does this actually affect the outcome? Some things repeat constantly but do not actually affect whether the business runs well. The exact format of your weekly to do list might repeat every week, but the format does not matter for how the business actually runs. The relationship work behind your top three client relationships might be inconsistent every time, but you do not need an SOP for it because the texture of those relationships cannot be systematized.
The intersection of “yes, it repeats” and “yes, it matters” is what gets documented. Everything else stays fluid until you have evidence that it needs to harden.
What Belongs in Your SOP Library
These are the categories where SOPs reliably pass both tests in established businesses.
Visibility and Content SOPs
Your content publishing workflow. Where you post, how often, in what format. This repeats. It matters.
Your repurposing pipeline. How one piece of content becomes the next three or five. The mechanics of this are worth locking in once you find a rhythm that works.
Your email sending process. The cadence, the segmentation, the technical execution. The cleaner this gets, the more reliably your list compounds.
Your lead magnet delivery and welcome sequence. The exact path a new subscriber takes through your world. This is the one most business owners underinvest in, and it pays off the most when it is done well.
Operations and Growth SOPs
Your client onboarding. The first thirty days of a new client relationship. The single document that does the most work in most service businesses.
Your sales or discovery call structure. The repeatable shape of the conversation. This protects you from having to reinvent the wheel every time and keeps your conversion rate consistent.
Your offboarding and refund process. The exit path that protects the relationship even when things end.
Your hiring and contractor process. How you bring people in, what they get, what is expected.
Your financial review cadence. The numbers you check, how often, in what format.
These categories repeat in almost every established business, and the way you handle them materially affects how the business runs.
What Does Not Belong in Your Documentation
The list of what does not belong in your documentation is usually longer than the list of what does.
Your thinking work. Strategic decisions, judgment calls, the exercises of judgment that change based on context. These do not belong in an SOP because they are not processes.
Your voice work. The actual content you produce, including the emails you write and the conversations you have with clients. These require you and cannot be systematized without losing the thing that makes them yours.
One time decisions. Anything you have done once or twice and may never do again. Documenting these is the most common form of premature optimization.
Anything not yet actually repeating. Just because you have decided you will do something repeatedly does not mean it has started repeating. Wait for evidence before you document. The first three iterations of any process usually look very different from how the process eventually settles.
Relationship work. The texture of your specific client relationships, peer relationships, and team relationships. These are not processes. They are ongoing exercises in human attention.
Common SOPs Women in Business Try to Write Too Early
If you have been making a list of SOPs you “should” write, some of the most common ones on those lists are also some of the ones most worth deferring until later. Run these through the two question test honestly.
A content calendar SOP for a content strategy you are still testing. If your content strategy has shifted twice in the last six months, the underlying pattern is still developing. Writing an SOP for it now is writing an SOP for a strategy that will not exist in three months.
A hiring SOP before you have hired anyone. The first hire will teach you what your actual hiring process needs to include. Write the SOP after, not before.
A discovery call SOP after one or two discovery calls. A handful of calls is not enough evidence to systematize the shape of the conversation. Run thirty calls. Then write the SOP based on what actually repeated.
A complete client onboarding SOP for a service you are still iterating. The onboarding flow for a service that is still being refined will need to be rewritten with every iteration. Wait until the service itself is stable.
A full social media SOP across every platform. Most business owners are showing up inconsistently on three platforms and a polished SOP for all three will not fix that. The SOP cannot create discipline that does not yet exist.
Each of these passes the repetition or impact test in theory but fails in practice because the underlying work is not actually settled yet. Document the things that are stable. Leave the things that are still being figured out as decisions, not processes.
When the Right Time to Document Actually Is
The most common question after this framework lands is “okay, but when is the right time to actually write the SOP?”
The right time is when you have evidence that the process has settled into a recognizable pattern. That usually means you have done the task at least five to ten times in substantially similar ways, you have noticed the variations and decided which ones are real and which were one offs, and you can describe what you would tell someone else to do if you had to hand it off tomorrow.
If you can describe the process out loud cleanly without making it up as you go, it is probably ready to document. If you find yourself qualifying every step with “well, sometimes…” or “it depends on…”, the pattern has not settled yet.
The timing question gets easier when you stop trying to document in advance of need. Document just behind the curve, not just ahead of it. The processes that are working in your business now have already taught you what they need to be. The processes you are still figuring out will keep teaching you, and you can lock them in once they have done the teaching.
One of the women I have worked with across multiple strategy sessions wrote about this in her Google review. Her quote names what the selective approach actually produces:
“I’ve had multiple strategy sessions with Cindy and every time I felt stuck or had no clue where to start, she helped me map out exactly what to focus on next. Instead of feeling overwhelmed, I left each session with clear, actionable steps I could implement right away. They didn’t just work, they truly moved the needle forward in my business.”
— Debbie Todd, Google Review
My Story and a Client Working Through This Right Now
In my earlier businesses, I made every version of the SOP mistake before I learned the selective version.
In one of my businesses, I wrote a process document for almost every recurring task. The folder was beautifully organized. The procedures were thorough. And almost nobody, including me, ever opened them. The work got done from memory and habit. The documents existed for the comfort of having documented, not for the practical use of running the business.
In another, I went the opposite direction. I documented almost nothing, planning to capture it all once the business was bigger. Then I tried to hand off pieces and realized I had not figured out my own processes well enough to explain them. The handoff failed. The team member left. The work came back to me.
What I learned across those experiences is that selectivity is the entire skill. Once I started documenting only the things that genuinely repeated and genuinely mattered, the documentation actually got used.
I am working with a client right now who is scaling her business at an incredible pace. The numbers prove it. And her instinct, like almost everyone’s instinct in this position, was to document everything in preparation for the next stage.
We spent the first part of our work together on selectivity instead. The core question we are working through is what her business actually needs documented to support the growth she is in right now, versus what she is imagining she will need based on a future shape of the business that has not arrived yet. Some things can stay fluid for now. Other things genuinely need to be locked in. The work is telling the difference.
She is moving faster as a result, because she is not buried under documents that do not yet have a purpose.
The Unmistakable Mastermind: A Small Room on Purpose
The mastermind I am building this fall is a small room on purpose.
The Unmistakable Mastermind starts September 2026. I started by sending private invites to a carefully chosen group of women I have already worked with closely. Women I knew would fit this kind of room. Two said yes within days and put their deposits down for September spots. Before there is a public sales page. Before any formal launch announcement. Just the right women recognizing the room they had been waiting for.
If this post landed and you want to be in a room where the work of selectivity gets thought through alongside other women doing the same kind of work, DM me on Instagram at @exclusivelycindy. The next round of details is coming soon
What to Do With This This Week
The selective approach to SOPs is the difference between documentation that supports your business and documentation that becomes its own work.
Here is the assignment for this week. List your current SOPs or the ones you have been meaning to write. For each one, ask two questions. Does this actually repeat in my business right now? Does this matter for the outcome? If both answers are yes, keep it on the list. If either answer is no, take it off.
You will probably end up with a shorter list than you started with. That is the right outcome. Selectivity is what makes the documentation usable, and usable documentation is what actually supports scaling.
About Cindy Gordon
This post on what to document before you scale a service business is from Cindy Gordon, selective visibility strategist and business mentor for female entrepreneurs.
Cindy Gordon is a selective visibility strategist and business mentor for female entrepreneurs. A 6x founder who has built and sold four successful businesses, she holds a Masters in Special Education with a focus in Behavior Analysis and brings the discipline of individualized assessment to visibility work. She helps women diagnose what is breaking their content, where their visibility actually belongs, and how to show up with clarity instead of noise. Cindy is the founder of Exclusively Cindy and the host of The Strategic Entrepreneur podcast, where she explores the trust recession, the sameness epidemic, and what it takes to become unmistakable.
Save this post. Share it with a business owner who has been overdocumenting in preparation for growth that is not quite here yet.
