From owner-dependent to process-run: building standard operating procedures in a small company

Many small businesses share a quiet problem: they only work properly when the owner is there. Quality slips when the owner takes a week off. Customers ask for the owner by name. Key steps live in one experienced employee’s head, and everyone holds their breath when that person is sick. The business is busy, but it is not scalable, saleable or restful.

The underlying issue is the difference between a personality-run business and a process-run business. In the first, results depend on particular people being present and remembering how things are done. In the second, the way work is done is captured, shared and improved, so that capable people can produce consistent results whether or not the founder is in the building. Global franchise chains are the extreme example. Customers often do not know who founded them, because the system, not a person, delivers the product.

Most small businesses do not need to become a franchise. They do need enough process to stop depending on memory and heroics. The main tool for that is the standard operating procedure (SOP). This article explains why SOPs matter, which processes to document first, and a practical seven-step method for writing SOPs that people actually use.

Why SOPs matter more in small businesses

It is tempting to see documented procedures as bureaucracy for large companies. In fact, small businesses often benefit more, for five reasons.

1. Consistency. When everyone follows the same method, output quality stops varying with who is on shift. Customers notice consistency more than occasional brilliance.

2. Efficiency. A documented best method removes the small inefficiencies that creep in when each person invents their own approach. Searching for information, redoing steps and asking colleagues “how do we do this again?” all drop.

3. Fewer miscommunications. Many errors start with assumptions: “I thought you were ordering the material”, or “I didn’t know that customer needed a certificate”. A procedure that states who does what, and when, removes much of that ambiguity.

4. Faster scaling. A second site, a second shift or a new product line is far easier to start when the first one runs on documented processes. You copy the system rather than trying to clone the owner.

5. Protection against knowledge loss. This is the most underrated benefit. In many small firms, critical processes such as how to set up a particular machine, how to quote a complex job or how to reconcile a supplier account exist only in one person’s experience. When that person leaves, retires or is unwell, the knowledge goes with them. A written, tested procedure turns individual expertise into a business asset.

There is also a training benefit. When a new person joins, a procedure manual lets them learn the process far faster than shadowing someone who is too busy to explain. A short check after they have read it, followed by supervised practice, can get a new starter productive in days rather than weeks.

Document execution, not strategy

A useful distinction is between strategy and execution. Strategy covers where the business is going, which markets to pursue and which big bets to make. It requires judgement and usually stays with the owner and leadership team. It is not the place to start with SOPs.

Execution means the repetitive, day-to-day work that delivers the product or service. Quoting, order entry, purchasing, setup, production, inspection, dispatch, invoicing and following up on payments all fall under it. Execution is where SOPs give the biggest return, because these tasks happen often, involve several people and suffer most from variation.

To decide where to start, list the activities that are:

• Frequent: done daily or weekly.
• Repetitive: done broadly the same way each time.
• Error-prone: a frequent source of mistakes, rework or complaints.
• Person-dependent: currently understood by only one person.
• Customer-visible: directly affecting what the customer receives or experiences.

Activities that score highly on several of these are your first SOP candidates.

A seven-step method for writing an SOP

Step 1: Start with the problem and the goal

Begin with a department or activity where something keeps going wrong: quality, productivity, accuracy, delivery, billing or sales follow-up. Write down the problem in plain terms, for example “about one in ten quotes goes out with a pricing error”, and then the goal, such as “every quote checked against the current price list and margin rule before sending”. A clear goal gives the procedure a purpose and a way to judge whether it works.

Step 2: Set the process boundary

Define where the process starts and where it ends. For a quoting process, it might start when an enquiry is received and end when the quote is sent and logged for follow-up. For a production job, it might start when the job card is released and end when the finished goods are packed and labelled.

Clear boundaries stop SOPs from sprawling into everything. They also make hand-offs visible. The end of one process is the start of another, and the hand-off is where many errors happen. At this stage, also define the output, meaning what “done correctly” looks like, and the inputs needed along the way, such as information, materials, approvals and tools.

Step 3: Capture the best current practice with the team

Do not write procedures alone at a desk. Gather the people who do the work and walk through the activity step by step. Find the person who gets the best results and observe exactly what they do: the settings they use, the checks they make, the order of steps and the small tricks that experience has taught them. Write it down in sequence.

This step does two things. It captures real know-how rather than an idealised version, and it builds ownership. People are far more likely to follow a procedure they helped write.

As you list the steps, note the resources each one needs: how many people, which skills, which equipment and roughly how long it takes.

Step 4: Draw the flow and assign roles

Turn the sequence into a simple flowchart or swim-lane diagram showing:

• Roles: who performs each step (use role titles, not names, so the SOP survives staff changes).
• Sequence: the order of steps, including decisions such as “if the part fails inspection, go to step 9”.
• Hand-offs: where work passes from one role to another.

Then review the flow with everyone involved, together. This integrated review often reveals duplicated checks, missing steps, unclear decisions and bottlenecks, and it agrees who contributes what.

Step 5: Anticipate failures and assign accountability (RACI)

Before releasing the procedure, ask what could go wrong. A step may be skipped. A wrong material may be used. An approval may be missed. A defective product may reach the customer. For each risk, add a check, a mistake-proofing step or a clear escalation.

A RACI matrix helps make accountability explicit for each key activity:

The most common failure in small businesses is having no “A”, or several, so that everyone assumes someone else is checking. One accountable person per activity removes that gap.

Step 6: Write it clearly and visually

Good SOPs are short, specific and easy to follow at the point of use. Practical guidelines:

• Use numbered steps and start each with a verb: “Check”, “Enter”, “Tighten”, “Record”.
• Include photos or screenshots for anything visual: correct setup, acceptable finish, the right form field.
• State acceptance criteria clearly, such as “gap no more than 0.5 mm”, instead of “check it looks right”.
• Put safety warnings and critical-to-quality steps where they apply, not in a separate preamble.
• Keep each SOP to one process. Link to others rather than combining them.
• Add a header with the title, owner, revision number, date and approval, so people know they have the current version.

Step 7: Train, observe and hand over

A document alone does not change behaviour. Use a structured handover often described as “I do, we do, you do”:

1. I do: an experienced person demonstrates the process while the learner watches and follows the SOP.
2. We do: they perform it together, with the learner taking more of the steps.
3. You do: the learner performs it independently while the experienced person observes and gives feedback.

Then reduce supervision gradually. At first the learner reports back after each completion. Later they report on a routine schedule. Record who is trained on which procedures in a simple skills matrix.

Keeping SOPs alive

The fastest way to kill a procedure system is to write documents once and never update them. Within months the procedures no longer match reality, people stop trusting them, and the business is back to memory and habit. To keep SOPs alive:

• Assign an owner to each procedure, responsible for keeping it current.
• Review on a schedule, such as annually, and whenever the process, equipment or customer requirement changes.
• Make suggesting improvements easy. If an operator finds a better way, the SOP should be updated, not ignored.
• Control versions. Remove old printouts from the floor and keep one master copy, usually in a shared folder or simple document system.
• Use SOPs in performance conversations. When expectations are written down, it becomes fairer and easier to compare performance with the standard and to spot where coaching is needed.

How SOPs connect to automation and performance management

Once a process is documented, it becomes much easier to improve and automate. You cannot sensibly automate a process nobody can describe. A clear SOP reveals which steps are pure data entry or copying, and those are good candidates for templates, forms, integrations or software. It also reveals which steps genuinely need judgement.

Documented processes also make performance management fairer. When the expected method and outcome are written down, you can see whether results fall short because of the person, the training, the tools or the process itself. Without a standard, every performance conversation becomes a debate about expectations nobody recorded.

A realistic rollout plan

Trying to document the whole business in one go usually fails. A staged approach works better:

1. Month 1: list all recurring activities and score them on frequency, error rate, person-dependence and customer impact. Pick the top three.
2. Months 1–2: write, test and train the first three SOPs using the seven steps above. Measure the problem you set out to solve.
3. Month 3: review the results, refine the procedures and agree a simple template and storage location for all future SOPs.
4. Months 3–6: document the next five to ten processes, prioritising person-dependent knowledge.
5. Ongoing: review and improve, and add procedures when new products, equipment or customers arrive.

Within six months, most small businesses find that the owner is pulled into fewer routine questions, new staff learn faster, and the number of avoidable errors drops.

Example: documenting a machine setup

A small machining business relies on one senior setter for a complex multi-operation part. When the setter is on leave, setups take twice as long and scrap rises. Using the seven steps, the supervisor and setter document the setup: the boundary runs from receiving the job card to first-off approval. They photograph each fixture position, list the tool numbers and offsets, note the three settings that most often go wrong and add a first-off inspection checklist with the critical dimensions. Two other operators are trained using “I do, we do, you do”. The next time the senior setter is away, the setup takes only slightly longer than normal, and no parts are scrapped.

Common mistakes

• Writing the ideal, not the real. Procedures that describe how work “should” happen, without observing how it does, are ignored.
• Too much text. Long paragraphs are not read at a workstation. Use steps, photos and criteria.
• No owner. Unowned SOPs go out of date within months.
• Using names instead of roles. People change. Roles persist.
• Skipping training. Handing someone a document is not the same as teaching them the process.

Summary

A business that depends on the owner’s presence is fragile and hard to grow. Standard operating procedures turn individual know-how into shared, repeatable practice. Start with frequent, error-prone, person-dependent activities. Define the problem and the boundaries, capture the best current practice with the team, map roles and hand-offs, assign clear accountability, write clearly and visually, and hand over with “I do, we do, you do”. Keep procedures owned and current. The result is a business that delivers consistent quality, trains people faster and keeps working when you are not there.

If you would like help documenting processes or turning shop-floor knowledge into clear work instructions, GoCore offers SOP and work instruction packages.

---

Sources: small-business training notes on developing business processes, SOPs, the RACI matrix and structured handover, together with established operations-management practice. Examples are illustrations.