1. What you will learn
This lesson produces the outcome map for your transformation and the diagnostic that decides what it should contain. You will learn how to convert a vague ambition into a measurable outcome, how to run a diagnostic that identifies where the business actually loses value, and how to choose the one or two outcomes worth pursuing this year.
2. The idea explained
An outcome map states what will be different, in numbers, and by when. It is short — one page, three or four outcomes at most — and each outcome must be measurable from records you either have or will create.
The discipline is converting ambitions into outcomes. "Grow the business" is an ambition. "Raise contribution per job from sixteen to twenty-two per cent by the end of the year, measured from real invoices monthly" is an outcome. The second can be reviewed; the first cannot.
The diagnostic decides what belongs on the map, and it has six areas.
Money per sale: contribution per unit on each major line. Where is value being lost per transaction?
Volume and demand: enquiries, conversion, orders. Is there enough demand for the business you have?
Delivery: throughput, backlog, on-time, rework. Can you produce what you sell?
Cash: cycle, working capital, receivables ageing. Does the business consume cash faster than it generates it?
Structure: concentration, repeat rate, the mix of lines by contribution. Is the business dependent on something fragile?
Owner: how much of the business passes through you, and what that costs.
Run all six and rank the findings by rupee value. That ranking, not your preference, decides the map.
One further discipline. Choose no more than two outcomes for the year. An owner pursuing four will achieve none, because each requires sustained attention over months and small businesses have one person's attention to allocate.
Apply it
3. How to apply it in your own business
Run the six diagnostic areas with arithmetic. Where you cannot compute, write "not captured" and make it an action.
Rank every finding by rough rupee value per year. Do this before forming any opinion about what to do.
Choose the top one or two by value, provided each is something you could actually change. A finding you cannot act on — a market change, a regulatory requirement — is context, not an outcome.
Write each as a measurable outcome with a number, a measurement method and a date.
Write what would tell you the outcome is not achievable, so the map can be revised rather than defended.
Put the map on one page where you will see it weekly.
Worked example
4. Worked example
Satish, in Coimbatore, runs a small business manufacturing and supplying industrial trolleys and racks, with twelve staff and revenue of about sixty-eight lakh.
His diagnostic findings, with values.
Money per sale: contribution on trolleys is about twenty-four per cent and on racks about eleven per cent. Racks are about forty per cent of revenue, so about twenty-seven lakh at eleven per cent. If racks matched trolleys, that would be about three lakh fifty-one thousand more contribution a year. Value: three lakh fifty-one thousand.
Volume: enquiries about fourteen a week, conversion about thirty-one per cent. A fifth better conversion would be about two more orders a month at an average contribution of about nine thousand, so about two lakh sixteen thousand a year. Value: two lakh sixteen thousand.
Delivery: backlog about seven weeks against a quoted three; rework about seven per cent, costing roughly one hundred and forty hours a year at a fully-loaded rate of about two hundred rupees, which is twenty-eight thousand, plus the material at about sixty thousand. Value: about eighty-eight thousand.
Cash: cycle about forty-four days, working capital about seven lakh; receivables beyond sixty days about two lakh forty thousand, of which he judges about eighty thousand doubtful. Value: eighty thousand at risk, plus interest cost on the delay.
Structure: one customer at twenty-nine per cent of revenue. Not a rupee value but a risk.
Owner: he personally quotes every job, about eighteen a week at twenty-five minutes each, which is seven and a half hours a week, or about three hundred and ninety hours a year. Value: not a direct saving, but the largest single block of his time.
Ranked: racks margin at three lakh fifty-one thousand, conversion at two lakh sixteen thousand, rework at eighty-eight thousand, doubtful receivables at eighty thousand.
His preference had been to attack conversion, because selling feels like growth. The ranking says racks margin, by a wide margin.
He examines racks before committing. Recomputing from three real rack orders, he finds his steel usage per rack is about eleven per cent above his own drawing specification, because standard lengths are being cut wastefully rather than nested. That single cause accounts for about two-thirds of the margin gap, and it is a production change rather than a pricing one.
His outcome map, two outcomes only. First: raise rack contribution from eleven to eighteen per cent by the end of the year, measured monthly from real invoices, primarily by reducing steel wastage. Second: reduce backlog from seven weeks to four by the end of the year, measured weekly, because a three-week quoted lead time against a seven-week backlog is damaging conversion and he cannot fix conversion without it.
His revision condition: if rack contribution has not reached fifteen per cent by month six, the wastage explanation is wrong and he will recompute the cause.
5. Common mistakes and how to fix them
The first mistake is an outcome that cannot be measured. Fix it by attaching a number, a method and a date.
The second is choosing outcomes by preference. Fix it by ranking findings by rupee value first.
The third is choosing more than two outcomes. Fix it by accepting that one person's attention cannot sustain four.
The fourth is acting on a symptom before finding its cause. Fix it by investigating, as with the steel wastage.
The fifth is a map with no revision condition. Fix it by writing what would show the diagnosis was wrong.
Key takeaways
6. Board summary
An outcome states what will be different, in numbers, by when, and measured how. Run six diagnostic areas and rank every finding by rupee value before forming an opinion. Your preference will usually point at selling; the ranking usually points elsewhere. Investigate the cause before designing the change; a margin gap is often a production fault, not a pricing one. Two outcomes a year at most, because one person's attention cannot sustain four.
Check your understanding
7. Practice and self-check
One. Racks at twenty-seven lakh and eleven per cent, versus twenty-four per cent. What is the gap worth? Answer: about three lakh fifty-one thousand rupees a year.
Two. Two more orders a month at nine thousand contribution is worth how much a year? Answer: about two lakh sixteen thousand rupees.
Three. Which finding ranks first, and which did he prefer? Answer: racks margin ranks first; he had preferred conversion.
Four. What caused two-thirds of the rack margin gap? Answer: steel usage about eleven per cent above specification, from wasteful cutting.
Five. Why is that important? Answer: it makes the fix a production change rather than a pricing one.
Six. Why did he include backlog as his second outcome? Answer: a three-week quote against a seven-week backlog damages conversion, which he cannot fix otherwise.
Seven. How many outcomes should a year carry? Answer: no more than two.
Eight. What is his revision condition? Answer: rack contribution not reaching fifteen per cent by month six, meaning the wastage explanation is wrong.