West Africa is a growth market for many companies – and at the same time a stress test for traditional supply chain logic. The question is rarely whether disruptions will occur, but where they will occur (port, border, route, carrier, supplier) and how quickly the organization can switch gears.

Resilience here does not mean “more planning” or “more inventory.” Resilience means: options + triggers + decision-making rights so that the supply chain continues to function under stress.

HSC is not a standard consulting firm, but a project stabilizer with leadership and lean DNA: We first stabilize execution (roles, cadence, decisions) – and then improve it sustainably.

Why West Africa makes supply chains particularly vulnerable

Many risks are not “exotic,” but arise at interfaces:

• Ports: Capacity bottlenecks, weather and operational risks, handling variability
• Borders & regulatory processes: Documentation, inspections, throughput times, rule interpretations
• Corridors & routes: Infrastructure condition, detours, security and incident situations
• Information situation: ETA uncertainty, lack of exception transparency, late escalation

All in all, this not only causes delays, but above all variance – and variance is the enemy of predictability.

Symptom vs. cause: What is often confused in practice

Typical symptoms

• Unreliable delivery times / “ETA jumps”
• Ad hoc inventory build-up
• Constant escalation calls
• Blame assigned to freight forwarder, port, or border

Common causes

• No prioritized critical flows (everything is considered critical → nothing can be controlled)
• No clear triggers (when to switch?)
• Unclear decision rights (who decides within what time frame?)
• Alternatives exist “on paper” but not in operation (no dual-node capability)

30–60 days Playbook: Minimum Viable Resilience (MVR)

Instead of a large-scale program, an operational start that takes effect quickly is helpful.

Step 1 (Weeks 1–2): Create a critical flow map

• Define the top 20 goods flows/parts/SKUs (by sales, service criticality, security relevance, reputation risk)
• Per flow: Record port(s), border(s), route(s), carrier(s), DC/hub(s)
• Mark bottlenecks & variance points

Output: 1 page per critical flow (understandable for Ops, Procurement, Finance).

Step 2 (Weeks 2–4): Define triggers & decision rights

Define 5–7 triggers that trigger a decision (examples):

• Port/border dwell time above threshold
• Repeated ETA slips or missing scan events
• Capacity drop at carrier/equipment
• Documentation exception (e.g., missing/incorrect paperwork)
• Weather/event warning

Then: Who decides what by when (including deputization & approval limits).

Step 3 (Weeks 4–8): Pilot dual nodes (not just dual sourcing)

Run through 2–3 critical flows once in real life and test them operationally:

• alternative port OR alternative border crossing OR alternative route
• Process steps, documentation, cost logic, carrier handling
• “Switch” checklist: What needs to happen in 24/48 hours?

Goal: Switching becomes a process – not a heroic feat.

Step 4 (parallel): Introduce visibility light

No “control tower large-scale solution” necessary. Start with a lean exception board:

• ETA / Status / Delay Reason / Next Action / Owner / Deadline

KPIs: These 4 metrics drive resilience (without buzzwords)

1. Lead time variance (not just average; e.g., p90 logic internally)
2. OTIF (On-Time-In-Full) for critical flows
3. TTR (Time-to-Recover) per node/corridor (how quickly can you resume delivery?)
4. Port/Border Dwell Time at bottlenecks

When these KPIs are visible, resilience becomes controllable – and discussions become shorter.

Risks & trade-offs (honestly)

• Redundancy costs: Dual nodes/alternatives can appear more expensive in the short term.
• Transparency requires governance: Data sharing without rules creates conflicts.
• Too much inventory ties up cash and increases obsolescence – it can only simulate “security.”
• Complexity increases if alternatives are not clearly standardized.

Resilience is therefore not a “maximization goal,” but a balance of costs, service, and switchability.

Conclusion: Resilience is decision-making ability – along the real nodes

Anyone who wants to deliver reliably in West Africa should not view resilience as a policy, but as an operating model: prioritized flows, clear triggers, clear responsibilities, and tested alternatives.

In other words, resilience is not the opposite of efficiency. Resilience is efficiency that still works under stress.

FAQ (for SEO & reader questions)

What are the biggest supply chain risks in West Africa?

They often arise at ports, borders, and corridors – less so with the supplier alone. The variance at interfaces is crucial.

What has the fastest effect?

Prioritize critical flows, define triggers and decision rights, and pilot dual nodes for a few flows.

Which KPIs are most important?

Lead time variance, OTIF (critical flows), time-to-recover (TTR), and dwell time at port/border.