1. What you will learn
This lesson gives you the outcome map for the programme and a diagnostic showing where you stand against it. You will learn the eight areas assessed here, how to score each with evidence rather than impression, how to tell a weakness from the constraint that is actually costing you, and how to convert low scores into actions completable within a week.
2. The idea explained
An outcome map states what you should be able to produce at the end. Here the outcomes are a costed conflict baseline, a statement of your process faults, one process change running, your triggers named by others, a measured result, and a ninety-day plan.
The diagnostic scores eight areas: customer complaint handling, staff disagreement and task clarity, supplier and payment disputes, clarity of promises and terms, your own self-awareness, de-escalation practice, repair and follow-up, and prevention through process.
Two features keep it honest. Evidence: each score rests on something you can point to, a count, a document or a specific incident. Forced distribution: at least two areas must score two or below.
Then the harder question: which weakness is actually costing you. In this subject the answer is almost always found by counting rather than by feeling, because the incidents that feel worst are rarely the ones that occur most. An owner may score one on de-escalation, having handled a single confrontation badly, while the real cost sits in eleven quiet delivery misunderstandings that never raised anyone's voice.
There is also an ordering rule. Prevention through process is almost always the cheapest area to improve and the one with the widest effect, because it removes incidents rather than handling them better. Self-awareness and de-escalation are valuable and slower, since they depend on changing a reaction. Where both score low, start with prevention.
The knowledge check that follows corresponds to decisions you will face. A question you cannot answer points to a lesson worth revisiting before the capstone.
Apply it
3. How to apply it in your own business
Score each area from one to five with one line of evidence. Where you have no evidence, score one, because an unmeasured area is an unmanaged one.
Apply the forced distribution; the usual hiding places are clarity of promises and prevention through process.
Count rather than feel. Beside each area, write how many incidents in the last two months belong to it.
Name the constraint as the area carrying the most incidents or the most cost, not the one carrying the worst memory.
Write one corrective action per low score, each completable within a week, each with a date, and start with prevention where prevention is low.
Worked example
4. Worked example
Ismail runs a wholesale vegetable supply business with six staff, delivering to about forty small restaurants.
He scores himself. Customer complaint handling, three. Staff disagreement and task clarity, two: loading disputes happen most mornings. Supplier and payment disputes, three. Clarity of promises and terms, two: quantities and prices are agreed verbally at four in the morning. Self-awareness, two: he has never asked anyone. De-escalation, three. Repair and follow-up, two: he rarely returns to an incident once it passes. Prevention through process, two: he has no written anything.
Five areas at two, so the distribution passes easily.
He then counts the last two months. Customer incidents: nineteen, of which fourteen concern a quantity or price disagreement. Staff incidents: twenty-three, of which seventeen concern who was supposed to load what. Supplier incidents: four.
Cost. Of the fourteen customer quantity disputes, nine were settled by giving free produce, which he estimates at about six hundred rupees each, so five thousand four hundred rupees. Two restaurants stopped ordering; at about four thousand rupees a week each, that is about eight thousand rupees a week, or roughly four hundred and sixteen thousand rupees a year if permanent, which is by far the largest number on the page. The staff disputes cost time rather than money, about fifteen minutes each across seventeen incidents, so about four and a quarter hours.
Now the constraint. His worst memory is a shouting argument with a supplier, which scored his de-escalation concern. But the counting says clarity of promises is the constraint: fourteen customer disputes and seventeen staff disputes both trace to things agreed verbally in the dark at four in the morning and remembered differently by eight.
His first action, completable in a week, is a carbon-copy order book: quantity, price and name written and signed at the point of order, one copy to the restaurant. Second, a loading sheet listing what goes on which vehicle. Neither requires him to behave differently; both work when he is tired.
5. Common mistakes and how to fix them
The first mistake is scoring from impression. Fix it by counting incidents per area over two months.
The second is naming the constraint from your worst memory. Fix it by naming the area with the most incidents or the most cost.
The third is starting with self-awareness because it feels like the serious answer. Fix it by starting with prevention, which removes incidents rather than handling them better.
The fourth is scoring everything in the middle. Fix it with the forced distribution.
The fifth is writing corrective actions that are really projects. Fix it by requiring completion within a week.
Key takeaways
6. Board summary
The outcomes are a costed baseline, a process-fault statement, one process change running, triggers named by others, a measured result, and a ninety-day plan. The diagnostic scores eight areas with evidence and requires at least two scores of two or below. Name the constraint by counting incidents and cost, not by remembering which one felt worst. Prevention through process is usually the cheapest improvement with the widest effect, because it removes incidents rather than handling them better. Every low score earns one corrective action completable within a week, and the best changes work when you are tired.
Check your understanding
7. Practice and self-check
One. Name the eight areas. Answer: customer complaint handling, staff disagreement and task clarity, supplier and payment disputes, clarity of promises and terms, self-awareness, de-escalation practice, repair and follow-up, and prevention through process.
Two. Why count rather than feel? Answer: because the incidents that feel worst are rarely the ones that occur most or cost most.
Three. Ismail had nineteen customer incidents; how many concerned quantity or price? Answer: fourteen.
Four. Nine disputes settled with about six hundred rupees of free produce each. What is that? Answer: five thousand four hundred rupees.
Five. Two restaurants at four thousand rupees a week. What is the annual figure if permanent? Answer: about four hundred and sixteen thousand rupees.
Six. What was the common cause behind both customer and staff disputes? Answer: agreements made verbally at four in the morning and remembered differently later.
Seven. Why did he start with an order book rather than with self-awareness? Answer: because prevention removes incidents rather than handling them better, and it works regardless of his state.
Eight. What makes a corrective action valid here? Answer: that it is completable within a week and works when you are tired.