1. What you will learn
This lesson shows how to diagnose whether a business really needs change, what is causing the pain and what outcome you want. You will separate symptoms from root causes, price the cost of doing nothing and write a first draft of a change charter with a measurable outcome.
2. The idea explained
Change usually begins with a complaint. Deliveries are late, customers are leaving, costs are rising, staff are tired, a competitor has launched something new. The owner feels the pain and reaches for a solution: a new machine, new software, a new manager, a reorganisation. Many such solutions fail, not because they were poorly executed but because they answered the wrong question. The complaint was a symptom, and the real cause lay somewhere else.
Diagnosis is the discipline of finding the cause before choosing the cure. A symptom is what you see and feel: late orders. A cause is what produces it: the cutting section starts jobs before fabric has arrived, so half-cut orders wait. A root constraint is the cause that, if fixed, would most improve the whole system. Every operation has one, and it is not always the loudest problem. Improvements elsewhere give little relief until the constraint moves.
A simple method is repeated why questions. Why are orders late? Because stitching finishes late. Why? Because the stitching lines wait for cut panels. Why? Because cutting has a queue of about two days. Why? Because there is one spreading table and all orders pass through it. Each answer must be checked with evidence, not accepted from opinion. Ask the people who do the work, look at the records, count and time.
Before designing any change, record the baseline: how the system performs now, measured for a few weeks. Without it you cannot tell later whether the change helped. Also name the stakeholders affected, the evidence available and the cost of leaving the gap unresolved. That cost, in rupees a month, is the first measure of how much effort the change deserves.
The outcome should be stated in measurable terms, with a date and an owner: on-time delivery from seventy to ninety per cent in six months. It should say what will not change, so that the change does not sprawl. A charter records these choices on one page.
Diagnosis will not guarantee that a change succeeds. Most change efforts fall short of some goals. What it does is reduce the chance that you invest in the wrong thing.
Apply it
3. How to apply it in your own business
Write the pain in plain words, with numbers: what happens, how often, to whom and since when. Avoid diagnosis in the description; stay with what you can observe. Check the records for at least four weeks to see how often it occurs.
Run the repeated why exercise with the people who do the work. Gather three or four of them for an hour with a whiteboard. Write the symptom, ask why and record each answer. For each answer, ask what evidence would show that it is true, and go and look. Stop when you reach a cause you can act on, usually after four or five whys.
Identify the constraint. Trace one order or one customer through the system and time each step. Note where work waits. The longest queue in front of the slowest step is usually the constraint. Test it: if you could double the capacity of that step for a week, would the overall output rise? If not, look elsewhere.
Price the cost of inaction. List the direct losses per month: penalties, rework, lost customers, overtime, expedited freight. Add the value of the time of people who spend it firefighting. Annualise. Compare with the likely cost of solutions.
Draft the charter: the problem, the baseline, the root cause with evidence, the outcome with measure and date, the scope, what is out of scope, the stakeholders, the assumptions still to be tested and the owner. Share it with two people who know the work and ask them what is wrong with it.
Worked example
4. Worked example
Farhana runs a garment unit with 25 workers. Each month she takes about 60 orders from export buyers. Eighteen of them are late, which is 18 divided by 60, or 30 per cent. Buyers deduct four per cent of order value for late delivery, and the average order is 2.5 lakh rupees, so each late order costs 10,000 rupees. Eighteen late orders cost 1.8 lakh a month. She also pays about 0.6 lakh a month for air freight to recover lost days. The cost of the problem is 2.4 lakh a month, or 28.8 lakh a year.
She had planned to buy two more sewing machines. The repeated why exercise, done with her line supervisor, cutting master and merchandiser, goes like this. Orders are late because stitching finishes late. Stitching finishes late because lines wait for cut panels. Panels are late because cutting has a queue. The queue is there because all orders use a single spreading and cutting table, and it is used for about eleven hours a day, with fabric often waiting for the table.
She tests it with a week of records. Average waiting time at cutting is 2.1 days; the stitching lines are idle for about 14 per cent of their time waiting for panels. Adding machines would not help, as stitching is not the constraint. Cutting is.
Her charter: problem, 30 per cent of orders late costing 2.4 lakh a month; baseline, four weeks of data; root cause, single cutting table; outcome, on-time delivery from 70 to 90 per cent within six months; scope, cutting and its scheduling; out of scope, stitching capacity; assumptions to test, that fabric arrival is not a second constraint and that a second table pays back. She shares it with her merchandiser and the cutting master, who add that fabric often arrives late from one supplier. She records that as an assumption to test.
5. Common mistakes and how to fix them
The first mistake is buying a cure before diagnosing. Trace the process and find the constraint first.
The second mistake is accepting opinions as causes. Check each answer with records and observation.
The third mistake is skipping the baseline. Measure for a few weeks so you can later prove what changed.
The fourth mistake is a vague outcome. State a measure, a date and an owner, and say what is out of scope.
Key takeaways
6. Board summary
Separate symptoms from causes and the root constraint. Use repeated why questions, each checked with evidence. Record a baseline and price the cost of doing nothing. State the outcome as a measure with a date and an owner. Write a one-page charter and ask others to challenge it.
Check your understanding
7. Practice and self-check
- 12 of 50 orders are late. Late rate? Answer: 24 per cent.
- A late order costs 8,000; 12 late orders. Monthly cost? Answer: 96,000 rupees.
- Annual cost of that? Answer: 11,52,000 rupees.
- What is a root constraint? Answer: the cause that, if fixed, would most improve the whole system.
- Why record a baseline? Answer: so you can show later whether the change helped.
- How did Farhana price her problem? Answer: 1.8 lakh in deductions plus 0.6 lakh in freight, 2.4 lakh a month.
- Where did she find the constraint? Answer: at the single cutting table.
- Why not buy machines first? Answer: stitching was not the constraint.
- What assumption did the merchandiser add? Answer: late fabric from one supplier might be a second constraint.
- Can diagnosis guarantee that the change will succeed? Answer: no; it reduces the chance of investing in the wrong thing.