1. What you will learn
This lesson helps you define what resilience should mean for your business in measurable terms and to diagnose your present exposure. You will build an outcome map of three to five results, work out what a day of disruption costs you, and find your main constraint: whether it is a single point of failure, thin cash, weak data protection, poor communication or untested plans.
2. The idea explained
An outcome of resilience is a change in how the business behaves under stress: activities that restart faster, losses that are smaller, customers who are told early, cash that lasts longer. An activity is something you do, such as buying a generator or writing a policy. Owners often set activity goals because they are easy to tick, and then discover in the first real incident that nothing works as expected. The outcome map starts with results and works backward to the preparations that could produce them. For a small business, resilience outcomes fall into five families: recovery time, loss size, cash runway, information and people.
Recovery time is how quickly critical activities return, compared with their tolerable downtime. Loss size is the money lost per incident, which depends on how long you are down and how much you can still do. Cash runway is the number of weeks you can pay essential costs with little or no income. Information covers data safety, records you can retrieve and contacts you can reach. People covers whether someone else can do each critical task and whether staff know what to do. A business can be strong in one family and weak in another: a well-run shop with excellent records and no second person, or a team that is well trained but holds all data on one laptop.
The diagnostic asks three questions for each family: what number describes it, what is it now, and what would good look like for a business like yours. Use your own tolerable downtime and your own numbers. A key figure is the cost of a day of disruption: the contribution you lose per day when critical activities stop, plus the extra costs of coping. Multiply by realistic durations to see what different incidents would cost. Then find the constraint: the family where a modest improvement would cut the largest loss. Do not aim to prevent every event; aim to lower the impact and shorten recovery. Nothing here predicts events or guarantees outcomes, and most businesses cannot eliminate risk.
Apply it
3. How to apply it in your own business
Write a page called outcomes in ninety days with no more than five lines, each with a measure, today's value and a target. Examples: time to restore the order records from backup from 70 minutes to 30; contacts reachable on a call test from 70 per cent to 95 per cent; second person able to perform three critical tasks, from zero to three; cash runway from three weeks to six; incident checklist walked through by all staff, from none to all. Rank the lines and mark the top one.
Run the diagnostic from your baseline. Compute your daily contribution: monthly contribution divided by working days. Estimate the cost of typical incidents: a two-day power failure, a five-day absence of a key person, a week without your main supplier, a day of lost data. Multiply the daily loss by duration, and subtract what you could still do. Rank the incidents by cost and likelihood. Note the dependency behind each.
Find your constraint by asking four questions in order. If my premises were unavailable tomorrow, what could still happen? If my key person were absent for two weeks, who would do their work? If my data were lost, how much could I restore and how fast? If my main customer or supplier failed, how many weeks could I last? The first weak answer is your constraint for this quarter. Write one sentence and one small, cheap action, and place it first in your plan. Keep the outcomes realistic and tied to tests, not to feelings. Where an outcome relies on insurance or legal duties, confirm the facts with your insurer or adviser.
Worked example
4. Worked example
Consider Aarohi, who runs a small dental supplies distribution business with five staff. Monthly sales are 1,500,000 rupees and contribution is 20 per cent, so 300,000 rupees a month. With 25 working days, daily contribution is 12,000 rupees, since 300,000 divided by 25 is 12,000.
Incident costs. A two-day power failure with no workaround: 2 times 12,000, which is 24,000 rupees. A five-day absence of the person who handles orders, where orders drop by half: 5 times 12,000 times 0.5, which is 30,000 rupees. A week without the main supplier, which provides 60 per cent of products, with substitutes for a third of them: lost daily contribution about 12,000 times 0.6 times 0.67, which is 4,824 rupees a day, over 6 working days, about 28,900 rupees. A one-day data loss with a weekly backup: up to five days of orders to re-enter, about 40 hours of work at 200 rupees an hour, 8,000 rupees.
Her outcomes: restore time for order data from 3 hours to 30 minutes; second person able to process orders from none to two; runway from 4 weeks to 8. Cash on hand is 400,000 rupees and monthly fixed costs are 350,000, so runway is 400,000 divided by 350,000, about 1.1 months, or 4.9 weeks. Doubling would need about 800,000 rupees, a large step, so she sets 6 weeks as a first target, about 490,000 rupees.
Constraint: the person who handles orders is a single point of failure, at an estimated cost of 30,000 rupees per event. Action: write a one-page instruction and train a second person for one hour a week. All figures are hypothetical.
She dates the page and shares it with her accountant, who reminds her to check her insurance for business interruption cover.
5. Common mistakes and how to fix them
The first mistake is setting activity goals such as buy a generator. Restate each as a tested result, like time to restore or tasks a second person can do. The second mistake is guessing the cost of disruption; compute your daily contribution and multiply by realistic durations.
The third mistake is choosing many outcomes. Keep at most five and rank them. The fourth mistake is trying to prevent every event; aim to shorten recovery and reduce impact, and confirm insurance facts with your insurer.
Key takeaways
6. Board summary
Resilience outcomes are changes in behaviour under stress: recovery time, loss size, runway, information and people. Compute your daily contribution and the cost of typical incidents. Use your own tolerable downtime and numbers. Find the constraint by asking four scenario questions. Keep at most five outcomes and confirm insurance facts.
Check your understanding
7. Practice and self-check
Q1. Name the five resilience families. Answer: Recovery time, loss size, cash runway, information and people. Q2. Daily contribution, 300,000 over 25 days? Answer: 12,000 rupees. Q3. Cost of a two-day power failure? Answer: 24,000 rupees. Q4. Cost of a five-day absence with orders halved? Answer: 30,000 rupees. Q5. Data re-entry, 40 hours at 200 rupees? Answer: 8,000 rupees. Q6. Runway, 400,000 over 350,000? Answer: About 1.1 months, 4.9 weeks. Q7. Cash for six weeks of runway? Answer: About 490,000 rupees. Q8. What was her constraint? Answer: The single person who handles orders. Q9. What was her first action? Answer: A one-page instruction and weekly training of a second person. Q10. Should you aim to prevent every event? Answer: No; aim to shorten recovery and reduce impact.