SMEs
Organisational Resilience Starts with Visibility, Not a Crisis Plan
See how visibility into cash, operations, dependencies and decision rights can help African organisations adapt when disruption arrives.
When disruption arrives, an organisation discovers more than an external event. It discovers its ability to see, decide and act. A power outage, late supplier, exchange-rate movement, cash squeeze, cyber incident or absence in a key role can become a crisis when nobody understands the dependencies, warning signs or fallback options. A less-than-perfect organisation can still limit the impact if it notices signals early and mobilises proportionate responses.
A crisis plan is useful, especially for major risks. But a document stored in a folder does not create resilience by itself. Everyday readiness depends on visibility: who holds critical information, which activities cannot stop for long, which supplier is difficult to replace, how long cash can support operations, and who can activate a continuity decision?
Map the dependencies that matter
Start with the services, deliveries or functions whose interruption would seriously affect customers, revenue, compliance or safety. For each one, identify the people, suppliers, systems, locations, data, equipment and funding it depends on. Separate primary dependencies from alternatives. A short map explaining how work can actually be blocked is more useful than a long list of generic risks.
Then identify signals that show deterioration: a delivery delay, concentrated receipts, a bank balance below an internal threshold, repeated IT incidents, missing spare parts or an overloaded employee. Thresholds should not be copied from another organisation without review. They depend on the business, sector, contracts and ability to respond.
Make cash and capacity visible
Operational and financial disruption often reinforce each other. A late customer payment may delay an essential purchase. Missing parts can postpone delivery and billing. Rapid expansion can increase working capital needs faster than receipts. Resilience therefore needs current information discussed together: expected cash in, upcoming payments, sales commitments, critical capacity, deliveries under way and open risks.
A frequent, short review can reveal a trade-off while options remain. The team may delay an expense, secure another supplier, adjust a schedule, redistribute workload or alert a customer. The AMOS Framework connects resilience with governance, execution and growth because these issues meet in an organisation’s real decisions.
The review rhythm should match how quickly a risk can materialise. An activity exposed to frequent supply interruptions may need a daily check of a few signals; a stable dependency may be reviewed monthly. Avoid two extremes: monitoring nothing until the incident, or demanding so many reports that teams cannot act. A useful rule states who checks the signal, when it is shared and which decision becomes available if the threshold is crossed. This turns monitoring into an operational choice rather than a compliance ritual.
Define continuity decisions
For each critical activity, state who may decide to pause, restart or use an alternative. Define the limits: what amount can be committed? Who informs customers? Which incident requires escalation? Where is essential information if the main system is unavailable? These decisions need simple exercises, not only meeting approval.
A tabletop exercise could simulate a supplier being unavailable for five days or the loss of access to the billing system. Ask participants what information they need, which decisions they make, what messages they send and which functions they protect first. Record delays, uncertainty and forgotten dependencies. The point is not to catch the team out. It is to find what needs clarification before a real event.
Fit continuity to available resources
Smaller organisations may not have a backup site, dedicated risk team or budget for duplicated systems. They can still identify a replacement contact, back up essential files, agree on another communication channel, keep alternative supplier details or document sensitive procedures. Resilience can improve through a series of proportionate choices, not only large investments.
Digital solutions can help track risks and share decisions, but they need to fit connectivity, skills, security and existing systems. A new platform cannot resolve unclear ownership. Explore the direction of the AMOS Digital ecosystem on its overview page and assess features against a defined need.
Learn after every disruption
After an interruption or near miss, record facts before drawing conclusions. What happened? When did the team know? Which action limited the impact? What delayed the response? Were customers informed in time? Which assumption proved wrong? A no-blame review does not remove accountability. It creates room to examine causes and assign corrections.
Then track a small number of useful measures: time to detect, time to restore, critical dependencies without alternatives, repeat incidents or overdue continuity actions. Interpret them carefully and compare them with a meaningful baseline. The AMOS Evidence and Assessment approach can help distinguish observations, interpretations and decisions.
Leaders should also communicate what a continuity decision means for staff, customers and partners. If the organisation changes service hours, delivery dates or access to a system, people need a clear explanation of what is affected, what remains available and when the next update will come. Communication is part of continuity because uncertainty can create additional disruption. Prepare short message templates for likely events and identify who is authorised to send them, while leaving room to adapt the message to facts as they emerge.
Resilience is a capability to maintain
Resilience does not promise that an organisation will never be affected. It is the ability to recognise disruption, protect what matters, adapt operations and learn while considering the people involved. It depends on repeated practices: accessible information, understandable decisions, aligned responsibilities and realistic review.
AMOS’s planned sector editions will need to translate these principles for different settings: higher education, healthcare, manufacturing, government, insurance, banking, agribusiness, logistics and supply chains, NGOs and SMEs. Continuity measures and scenarios will differ across sectors. The NGO edition is planned as a free offer for NGOs and their stakeholders; its timing and terms will be confirmed at launch. Sector editions can help organisations begin with risks closer to their work while keeping a shared language for discussing decisions, evidence and improvement. Their practical value should be assessed with users in each environment, including smaller organisations and stakeholders who may be affected by operating choices.
AMOS is currently in a pilot phase. Its usefulness and the durability of related practices still need assessment in different contexts. AMOS does not currently issue certifications. Organisations can explore the underlying thinking in the AMOS Manifesto and visit AMOS Resources to choose a next topic. Start with one critical dependency the team does not understand well. The best improvement is one the organisation can maintain.


