Standard operating procedures have a sweet spot: the third time you do the task. Write your first SOP when you do something for the third time. Not before because you do not know the process yet. Not after ten times because you have built bad habits. Keep it to one page. One page, steps and done-state, written while doing the task, not from memory after.
Evaluate tools with a thirty-day trial, not a demo
The demo is designed to sell you the tool. The trial is designed to let you discover if it actually works for your team. Never buy a tool based on a demo alone. Run a thirty-day trial with a specific use case, a small group of users, and clear success criteria. If the tool does not meet the criteria in thirty days, it never will.
The criteria should be measurable: did it save time, did it reduce errors, did the team actually adopt it? Adoption is the most important metric. A tool that is objectively better but subjectively annoying will be abandoned within ninety days. Choose the tool that the team will actually use, not the tool with the most features. The best tool is the one that disappears into the workflow.
Meetings are for decisions, not updates
If a meeting does not produce a decision, it should have been an email. Status updates, FYI announcements, and progress reports do not require synchronous time. They require a shared document that people read asynchronously. Reserve meetings for the things that genuinely need real-time interaction: decisions, disagreements, and brainstorming.
The test: before scheduling a meeting, write down the decision it should produce. If you cannot articulate the decision, cancel the meeting. If you can, send a pre-read twenty-four hours in advance so people come prepared to decide. The meeting itself should take half the time you think it needs. A thirty-minute meeting that produces a decision is better than a sixty-minute meeting that produces a follow-up meeting.
Build a decision framework, not a approval chain
Early-stage companies slow down when every decision requires founder approval. The fix is not to approve faster. It is to build a framework that lets the team decide without you. The framework has three parts: who decides, what information they need, and what constraints apply.
For most decisions, the person closest to the problem should decide. The founder's job is to set the constraints: budget limits, brand guidelines, strategic priorities. Within those constraints, the team decides. The framework should be written down and shared. When someone asks for approval, point to the framework. If the framework does not cover the decision, decide together and add it to the framework. Over time, the number of decisions that require you drops to near zero.
Automate the bottleneck, not the easy stuff
Most automation projects fail because they automate the wrong things. They automate the easy, visible tasks instead of the actual bottleneck. The result is faster busywork and the same overall throughput. Before automating anything, map the full process and find the step that limits throughput. Automate that step first.
The test for whether automation is worth it: multiply the time saved per instance by the frequency per month. If the result is less than ten hours per month, the automation probably costs more to build and maintain than it saves. Focus on high-frequency, high-time-cost tasks. Data entry, report generation, and notification routing are usually the best candidates. Creative work and judgment calls are the worst.
Scale operations by removing yourself from the loop
The goal of operations is to make yourself unnecessary. Not literally, but functionally. If every customer onboarding requires your involvement, you cannot scale past the number of onboardings you can personally handle. The fix is to document, delegate, and verify. Document the process, delegate it to someone, and verify the output meets the standard.
The transition from doing to managing is the hardest part of scaling operations. Founders are good at doing. They built the company by doing everything. The shift to building systems that let other people do everything is a different skill. Start with the process you do most often. Document it this week. Hand it off next week. Spend the freed time on the next process. Repeat until you are the bottleneck in nothing.
Frequently asked questions
When should I write my first SOP?
The third time you do something. Before that you do not know the process well enough. After ten repetitions you have built habits, including the bad ones, and the doc becomes archaeology.
What makes a good standard operating procedure?
One page: the goal, the numbered steps, and what done looks like. Written while doing the task, not reconstructed from memory. If a new person cannot follow it cold, it is notes, not an SOP.
What should a startup document first?
Whatever you do most often: onboarding, deployments, invoicing, support triage. Frequency beats importance for the first few. The SOP you use weekly pays for itself weekly.
How do I get the team to actually use SOPs?
Keep them one page, keep them where the work happens, and update them the moment a step changes. SOPs die from length and staleness, not from resistance. A wrong doc trains people to skip all docs.
Who should write SOPs?
Whoever does the task today. Managers writing procedures for work they no longer do produce fiction. The doer knows which step actually breaks. Review by a second person keeps them honest.