Lead a Resilience Strategy Discussion With Operating Evidence

A request for a resilience strategy often arrives after a difficult operating week. A supplier shipment arrives late, a plant changes production order, customer service moves promised dates, and finance sees extra stock or freight expense. Each leader describes a different issue. A useful discussion begins by choosing one decision worth preparing, rather than launching a broad program around every concern.

Ask for a short record of recent events. Find out where work slowed, which material or service mattered, whose commitments changed, and who chose a temporary response. Use records already held by teams. Production schedules, supplier reviews, inventory reports, freight exception logs, and customer service notes each show part of an event. Place those details on one timeline. Mark first signal, operating effect, response, and leadership involvement. This sequence separates a warning problem from a response problem.

Do not begin with a promise to prevent every future disruption. A consulting partner needs a narrower question. Ask each leader to finish this sentence: “At the end of this review, I need enough evidence to decide whether to ____.” One leader might need a source review for a component. Another might need a product family inventory choice. A plant leader might need a routing review. Different choices need different evidence, owners, and decision dates. Write down disagreement instead of folding several choices into one large resilience statement.

Choose measures connected to each choice. For a source review, procurement brings current agreements, supplier contacts, delivery history, and records of known alternatives. Operations brings material use, production order, past workarounds, and site constraints. Finance brings internal records for cash tied up in stock and emergency spending. Commercial leaders bring product priorities and service commitments. Put a source, owner, record date, and known limit beside every measure. A number without context produces argument. A number with a source gives leaders a way to test an assumption.

Names often create confusion between functions. Procurement might use a supplier code while plant staff use a material label. Customer service might refer to a product family using a sales label. Align those references before a leadership meeting. An analyst does not need to rebuild every record. The analyst needs a small register showing how each name connects. This avoids a meeting spent asking whether two reports describe one exposure or two separate exposures.

Bring differing views together before a senior review. Procurement sees supplier terms and contact history. Plant leaders see material availability at a specific work center. Finance asks why a buffer belongs with one product family instead of another. Give each person a shared timeline and two decision questions. Ask, “Which assumption would change your recommendation?” A plant leader might say an alternate source solves little if internal review work extends past available stock. Procurement might point to an agreement detail affecting lead time. Both statements belong in the working record.

Use a fictional working session to see how this works. Chief executive Marisol says, “We need a plan so this never happens again.” Consulting partner Theo replies, “Which recent event caused the largest operating effect, and which choice do you want ready this quarter?” Marisol selects a production interruption tied to a specialized component. Procurement brings an agreement. Operations brings a production log from the same week. Theo asks leaders to choose between a source review, an inventory position review, and an alternate routing review. The group selects source review because no current record identifies an alternative.

Theo assigns a small evidence pack rather than promising an outcome from incomplete records. Procurement owns agreements and contact history. Operations owns material use and production sequence. Finance owns the current internal view of stock carrying cost. The consulting team owns the timeline, interview questions, and decision paper. Each owner describes record coverage and missing information. A delivery history might show late shipments without reasons. Marking this limit prevents a later meeting from treating a guess as a fact.

Set a decision rhythm before analysis grows. A first forty five minute review focuses on evidence quality. Participants ask whether records cover the right period, whether names align, and whether gaps matter. A second review compares response paths using agreed criteria. Leaders might use continuity of production, effect on customer service, cash use, time required from internal teams, and timing for a decision. Avoid scores made for presentation polish. Ask whose work changes under each path, when change begins, and who owns approval.

Prepare a decision paper around choices rather than a long risk description. Give every path a short statement of operating effect, supporting evidence, open questions, internal effort, decision owner, and target date. A source review path might need procurement interviews and review of existing agreements. An inventory path might need finance and plant planning input. Put uncertainty in an open question area. Do not hide uncertainty inside a recommendation. During review, ask whether a missing fact blocks a decision. If yes, assign one person to obtain a record and set a return time.

Trace every conclusion before leaders meet. When a conclusion comes from an interview, name the speaker, date, and question. When a report uses an average, ask whether an unusual stoppage sits outside view. A quarterly average might hide a short halt with serious effect. This check serves a practical purpose. Leaders should question choices, rather than spend half a meeting locating a document or resolving a product name.

Urgent requests often seek certainty. Respond with limits and a next question. If an executive asks, “Will a second source remove our risk?” Theo might answer, “The review will show which exposures another source addresses, what records support each view, and which exposures sit outside scope.” Such language keeps discussion useful without turning incomplete evidence into a promise. Customer leaders decide supplier commitments, capital choices, and operating policy. The consulting partner structures analysis and tests assumptions.

For a fictional practice situation, use a component called R17. On Monday, an operations manager reports eight hours of lost production after a late shipment. On Tuesday, procurement finds one supplier agreement and no recorded alternate source. On Wednesday, Marisol asks Theo for a recommendation before Friday. Theo writes “R17 source review” in the working record. He asks procurement for an agreement copy by 2 p.m. and asks operations for material use across affected products by 4 p.m. On Thursday morning, he opens both records with Marisol, circles one missing supplier contact, and assigns procurement to confirm contact ownership before their Friday decision review.