Ask a business owner running a five person operation whether they have standard operating procedures, and the honest answer is usually a laugh, followed by "we're too small for that." I want to push back on that instinct, because it is exactly backward. The smaller your team, the more damage one absent staff member, one resignation, or one bad day can do to your business, and SOPs are the cheapest insurance you can buy against that risk.
What an SOP Actually Is, Stripped of the Corporate Jargon
A standard operating procedure is simply a written instruction for how a task gets done, consistently, regardless of who is doing it. It is the answer to "what exactly happens when a customer complains," or "what are the exact steps to close the shop and lock up at night," written down instead of trusted to memory.
You do not need software, a template from a Fortune 500 company, or a consultant to write one. You need a document, even a shared Google Doc or a printed sheet on the wall, and enough honesty to admit that important knowledge currently exists only in someone's head.
The Real Cost of Not Having SOPs
Consider what actually happens without them. Your most experienced staff member calls in sick, and the person covering does not know the exact steps for processing a refund, so a customer waits, gets frustrated, and leaves a bad review. You hire a new employee, and training them takes three times longer than it should because every instruction is delivered verbally, once, with no reference document to check back against. A long serving staff member resigns, and takes with them the only working knowledge of how a critical supplier relationship, a pricing exception process, or a monthly reconciliation actually works.
None of these are hypothetical. They are the specific, recurring failure points that show up in Nigerian small businesses far more often than founders expect, precisely because the business runs on institutional memory rather than documentation. A business with three staff members has three single points of failure. A business with fifteen staff and no SOPs has fifteen.
"We're Too Small" Is Exactly Backward
Larger companies survive gaps in documentation because they have redundancy, multiple people who can cover any given task, formal training departments, and slack in the system to absorb a mistake. Small businesses have none of that cushion. When your logistics coordinator is the only person who knows which rider service is reliable for which part of Lagos, or your one salesperson is the only one who knows which clients need special payment terms, your business is not lean. It is fragile.
Writing SOPs early, while your business is still small enough that documenting a process takes an afternoon rather than a month long project, is far cheaper than trying to retrofit documentation onto a business that has already grown chaotic. This is precisely the size of business that benefits most, not the size that can afford to skip it.
Where to Start: Pick Your Highest Risk Processes First
You do not need to document everything on day one. Start with processes where a mistake is expensive, customer facing, or where you personally are the only person who knows how it works.
Common starting points for Nigerian small businesses include opening and closing procedures, cash handling and reconciliation, customer complaint and refund handling, order fulfillment from payment to delivery, and new staff onboarding.
For each, write down the trigger, what starts this process, the steps in order, who is responsible for each step, and what "done correctly" looks like. Keep the language simple enough that someone on their first week could follow it without needing you to explain it out loud.
SOPs Are Not About Removing Judgment
A common objection is that SOPs turn staff into robots who cannot think for themselves. This misunderstands the purpose. A good SOP handles the routine ninety percent of situations so your team's judgment is reserved for the genuinely unusual ten percent that actually needs it. Your best staff member should not be spending mental energy remembering the standard refund process. They should be applying their judgment to the one customer situation that does not fit the standard case.
Documented processes also make it easier to delegate with confidence. Founders who try to hold every process in their own head end up as the bottleneck for every decision, which is exactly the trap that keeps a business from growing past its founder's personal bandwidth.
Keep SOPs Alive, Not Frozen
The mistake many businesses make once they finally write SOPs is treating the document as finished. Processes change as your business grows, new tools get adopted, and problems that were not anticipated the first time around show up in practice. Review your key SOPs every few months, and update them the moment you notice staff working around a documented process because it no longer matches reality. An SOP nobody follows because it is outdated is worse than no SOP at all, because it teaches your team that documentation is not to be trusted.
The Bottom Line
If your business currently depends on specific people remembering specific things correctly, every single time, you do not have a system. You have a bet, and eventually that bet loses, usually at the worst possible moment, a busy season, a key resignation, an unexpected absence. Writing SOPs is not corporate bureaucracy imported from businesses ten times your size. It is how a small, resource constrained business protects itself against its own fragility. Start with your riskiest process this week. Write it down. You will likely be surprised how much clarity the exercise forces, even before a single new staff member reads it.
