1. What you will learn
This lesson turns the wish to have proper procedures into three measurable outcomes for the next ninety days, and runs a diagnostic of your process inventory. You will finish with a one-page outcome map naming a baseline, target, owner and review date for each outcome.
2. The idea explained
Owners who decide to get organised often set goals such as document everything or make the business run without me. These are aspirations. They give no first step, and they hide the question that decides where to begin: which process is costing us the most? An outcome map replaces the aspiration with a few measurable results tied to specific processes.
The diagnostic starts with an inventory. List the processes in the business, from the moment a customer first contacts you to the moment you are paid, and the support processes underneath: purchasing, stock, hiring, maintenance, accounts. For each, note who does it, whether it is written down, how often it runs and how often it goes wrong. This need not be precise; it is a rough map to show where the trouble lies. Most owners discover that the processes with the most complaints are the ones with no written procedure, and that two or three processes cause most of the cost.
Then measure the top candidate. Choose the process with the most delay, error or complaint. For it, gather three figures: volume, lead time and error or rework rate, with the cost of an error. These are the baseline. From them you can set outcomes that are specific: reduce the error rate from a stated level to another, cut lead time by a stated number of days, and write and train a stated number of SOPs.
Good outcomes are small enough to reach in a quarter and tied to actions you control. Outcomes about customer satisfaction or profit are worth watching, but they depend on many things beyond the process. Prefer outcomes the process itself can move.
Write each outcome so that a stranger could tell, on the review date, whether it was met. Say who owns it. Include one outcome about people: for example, that every member of the team knows where the procedures are and has been trained on those that concern them.
Success is not guaranteed. Errors have many causes, and a good SOP reduces variation without removing it.
Apply it
3. How to apply it in your own business
List the processes in your business on one page, in order from customer contact to payment, then the support processes. Beside each, write the owner, whether a written procedure exists, the monthly volume and a rough count of problems in the last month.
Choose the process with the most trouble. Gather its baseline: monthly volume, average lead time from request to result, error or rework rate and cost per error. Use records where they exist and a two-week tally sheet where they do not.
Write three outcomes. One on quality, such as cutting the error rate. One on speed, such as cutting lead time. One on the system, such as writing, testing and training staff on three SOPs. For each, write the baseline, the target, the owner and the review date. Then write the first action for the coming month that most directly moves each.
Translate each outcome into rupees or hours, cautiously, with if the target is met beside it. Keep the map to a page and put it where the team can see it. Share it, and ask for each person's view on obstacles. Review it at the end of each month, and rewrite a target if the facts show it was unrealistic. If any outcome touches regulated activity, ask the relevant authority or a professional first.
Add a short risk note: what could spoil the quarter, such as a rush season, staff turnover or a supplier problem, and what you would do.
Worked example
4. Worked example
Consider Pallavi, who runs an online apparel brand from Ludhiana with six staff. All figures are invented. Her process inventory shows fourteen processes, of which two are written down. The returns process causes the most complaints.
Baseline for returns: 200 returns a month; average lead time from parcel receipt to refund is 12 days; the wrong refund amount or a missed refund occurs in 6 per cent of cases, which is 12 returns a month; each error costs about 400 rupees in staff time, goodwill and correction. The monthly cost of errors is 12 times 400, which is 4,800 rupees.
Her three outcomes. First, cut the error rate from 6 per cent to 3 per cent. Second, cut lead time from 12 days to 7. Third, write, test and train staff on three SOPs: returns, order confirmation and stock count.
In numbers: 3 per cent of 200 is 6 errors, so 6 fewer than 12, saving 6 times 400, which is 2,400 rupees a month, if the target is met. Cutting 5 days of lead time on 200 returns means customers wait 1,000 fewer refund-days in total, though the money value of that is harder to state and she does not try. Three SOPs are countable.
She assigns the returns outcomes to her operations lead, the SOP outcome to herself, and schedules monthly reviews on the last Saturday. Her risk note says that a festive sale will double returns in the following quarter, which could hide the improvement. She treats the numbers as targets and not forecasts. She asks her accountant how refunds should be recorded, and notes the question.
She also writes down what the outcome map will not do: it will not make customers order less, and it will not remove all mistakes. She shares the page with the team and asks each person to name one obstacle.
Pallavi also writes down what she will stop doing this quarter: replying to return queries individually by phone. She will move them to a standard message with a status link. The freed time is what she will use to write the SOPs. A programme that adds work without removing any becomes a burden, and choosing what to drop in advance keeps the outcomes achievable.
5. Common mistakes and how to fix them
The first mistake is setting an aspiration such as document everything. It gives no first step, so choose a process and measure it.
The second mistake is picking outcomes the process cannot move. Profit and satisfaction depend on much else, so choose error rate, lead time and SOP counts.
The third mistake is skipping the inventory. Without it, you may fix a minor process, so list all processes and count problems.
The fourth mistake is announcing outcomes without asking the team. People know the obstacles, so ask each person to name one.
Key takeaways
6. Board summary
Replace aspirations with three measurable ninety day outcomes. List processes and count problems to choose where to start. Baseline volume, lead time and error rate with the cost per error. Choose one outcome each for quality, speed and system. Add a risk note and review monthly.
Check your understanding
7. Practice and self-check
Question 1. How many returns a month does Pallavi handle? Answer: 200. Question 2. What is 6 per cent of 200? Answer: 12 errors. Question 3. What is the monthly error cost at 400 rupees each? Answer: 4,800 rupees. Question 4. What is 3 per cent of 200? Answer: 6 errors. Question 5. What saving would that be? Answer: 2,400 rupees a month. Question 6. How many days does she aim to cut from lead time? Answer: 5, from 12 to 7. Question 7. How many SOPs does she plan to write and train? Answer: Three. Question 8. Why might the improvement be hidden next quarter? Answer: A festive sale could double returns. Question 9. Who owns the SOP outcome? Answer: Pallavi herself. Question 10. Are the numbers forecasts? Answer: No, they are targets.