Industrial & Manufacturing Industrial Manufacturing & Robotics Supply Chain Network Design

Network Optimization

Complex deployments where integration, safety, and operational handoff determine production success.

LLamasoft (Coupa) Blue Yonder Kinaxis o9 Solutions
Inside this journey
  1. Pre-Discovery

    Align the room on outcomes, decision process, and constraints before deeper discovery.

    1. Stakeholder Alignment

      Identify decision owners, board reporting requirements, timeline pressures, and what success looks like for each stakeholder.

      Alignment Questions

      Getting Comfortable: The Part of the Network We’ll Explore

      • In one sentence, which part of your network should we focus on for this engagement (e.g., North America finished-goods distribution, European inbound from Asia, last-mile to key retail partners)?
      • Who on your team will be the day-to-day partner for data and decisions on this project? Options: VP Supply Chain Strategy, Network Design Manager, Operations Research Analyst, Head of Logistics/Distribution, IT/Data Owner, Other
      • Which systems hold the history and cost inputs we should ingest first? Options: ERP (shipments/orders), TMS (movement-level), WMS, Carrier EDI/Rating, Rate tables/contract PDF, Other
      • How mature is your internal modeling capability today—do you rely mostly on spreadsheets, have a commercial optimizer, or something in between? Options: Spreadsheets only, Hybrid (spreadsheets + some tools), Commercial network optimization platform, In-house optimization models, Unsure
      • What prompted this re-evaluation now—pick the best fit (you can select more than one)? Options: Tariff or tax change, Acquisition/merger overlap, Capacity constraint at a plant/DC, Customer service failure or complaint, Board/CFO directive, Sustainability/carbon target, Other
      • If there’s one immediate story you want the board or CFO not to ask you that you currently can't answer with confidence, what is it?

      Are We Pretending Everything Is Fine?

      • Where do you see the biggest gap between what your network model or reports say and what operations actually delivers?
      • How often do service-level misses, cost overruns, or inventory surprises trigger emergency changes rather than planned optimization? Options: Weekly, Monthly, Quarterly, Rarely, Never
      • When a shipment misses its service commitment, what typically happens next—who gets involved and how long before a workaround is in place?
      • Tell us about a recent example where the current network design failed to prevent a material issue (what happened, impact, and how it was resolved).
      • How does that recurring issue make you feel about the team’s ability to recommend a confident, board-ready plan? Options: Confident, Somewhat confident, Worried, Undecided
      • What would have to change in your current reports or story to make you feel genuinely comfortable defending a network recommendation?

      Where Contracts, Tariffs, and Reality Collide

      • If we redesigned your network ignoring contracts and tariffs, what realistic element do you think would immediately invalidate the plan?
      • Which of the following contractual or regulatory constraints are most likely to block a recommended change? Options: Long-term facility leases, Carrier minimums or lane commitments, Customer service-level agreements (SLAs), Import duties / tariffs, Regional labor agreements, Tax residency implications, Other
      • How frequently do carrier rate changes or accessorials make your model’s cost assumptions obsolete? Options: Monthly, Quarterly, Annually, Rarely, Never
      • Do you have penalty clauses or service credits in customer contracts that significantly constrain acceptable transit times? Options: Yes, material penalties exist, Yes, but penalties are infrequent, No, Unsure
      • Which tariff or trade policy changes in the last 18 months forced you to re-run network scenarios or rethink sourcing? Options: Import tariffs, Export controls, Regional trade agreement changes, Sanctions, No changes affected us, Other
      • Describe an instance where a tax or tariff outcome materially shifted your sourcing or routing decision—what was the insight and consequence?

      When Capacity Suddenly Becomes the Center of the Room

      • Which facilities (plants, DCs, ports) are currently the tightest against capacity limits?
      • How predictable is your capacity crunch—seasonal spikes, rolling shortages, or sudden failures? Options: Seasonal, Gradual growth over time, Sudden outages/events, Rolling/variable, Not sure
      • Tell us about a capacity workaround you relied on recently—overtime, temporary storage, expedited freight—and the downstream cost or service impact.
      • What internal constraints must any feasible plan respect (e.g., production run lengths, safety stock minima, shelf-life, LTL handling limitations)? Options: Production run constraints, Minimum order quantities, Product shelf-life/temperature, Hazmat handling, LTL/palletization rules, Other
      • How quickly can you increase capacity at a constrained site if a model recommends shifting more volume there (weeks/months/years)? Options: Weeks, 1-3 months, 3-6 months, 6-12 months, 12+ months, Cannot increase
      • If we recommended moving volume to relieve a bottleneck, what operational or financial hurdles would be hardest to overcome?

      What Would Convince the Board to Say Yes?

      • Imagine the board asks, 'Why should we change the network now?'—what single metric or story would most persuade them? Options: Quantified annual cost savings, Risk mitigation/story for continuity, Service improvement for key customers, Payback timeline, Carbon reduction impact, Other
      • How do your board and CFO weigh risk vs. cost—is short-term cash preserved even if long-term costs are higher, or are multi-year ROI and resilience prioritized? Options: Short-term cash priority, Multi-year ROI prioritized, Balance depends on context, Unsure
      • What level of modeling fidelity do they expect—high-level directional analysis or a board-ready model validated with actual shipment and contract data? Options: Directional analysis ok, Board-ready validated model required, Depends on the ask, Unsure
      • Who besides the supply chain team must be comfortable with the recommendation before it reaches the board (e.g., CFO, tax, legal, operations, commercial)? Options: CFO/Finance, Tax, Legal/Compliance, Operations/Plant Managers, Commercial/Sales, HR/Labor, Other
      • What is the firm deadline or event that would force a decision (e.g., next board meeting date, contract renewal, tariff implementation date)?
      • What concerns would make the board delay or reject a recommendation even if it showed cost savings?

      What If We Could Build a Baseline in Days, Not Months?

      • We often build a validated baseline from ERP/TMS snapshots—are you willing to run a pilot on a single region or product set to test speed and fidelity? Options: Yes—single region/product, Yes—but need internal approval, No—not at this time, Unsure
      • What shipment sampling window would you consider representative for a baseline—last 3 months, 6 months, 12 months, or specific peak windows? Options: Last 3 months, Last 6 months, Last 12 months, Peak season window only, Other
      • Who owns data extraction for ERP/TMS and who will need to approve access for a rapid model build?
      • Which data quality concerns worry you most when we ingest historical shipments (missing weights, incorrect SKUs, bad geo-coding, split tendering)? Options: Missing weights/dimensions, Incorrect SKUs/customer IDs, Missing cost fields, Bad geocodes/addresses, Duplicate records, Other
      • If we surfaced a model discrepancy driven by data, how much time and resource can your team commit to remediation during the engagement? Options: Dedicated full-time data lead, Part-time support, Ad-hoc as available, Minimal availability
      • What would success look like for a two-week baseline run versus a full engagement in terms of deliverables and confidence?

      Implementation Reality Check: What Would Break the Plan?

      • If the model recommends facility consolidation or relocation, which real-world constraints would most likely stop you from moving ahead? Options: Lease break penalties, Labor/union issues, Customer proximity requirements, IT/system integration burden, Regulatory approvals, Other
      • How much lead time do your major leases and labor agreements typically require for changes (weeks/months/years)? Options: Weeks, 1-3 months, 3-6 months, 6-12 months, 12+ months, Varies widely
      • Have you implemented network changes in the last 5 years? If so, what was the single biggest operational challenge during the transition?
      • What governance or change-control steps must be in place before operations can enact a recommended shift (e.g., pilot windows, customer notifications, carrier tendering)?
      • Which implementation risks would you want quantified up front so you can compare options side-by-side? Options: Lease exit costs, One-time transition freight, Operational downtime risk, Customer SLA breach risk, Labor retraining costs, Regulatory/compliance risk, Other
      • If we surfaced a plan with attractive savings but meaningful implementation hurdles, how would you prefer we present trade-offs to the board? Options: Phased roadmap with pilots, Contingency scenarios, Full-costed ‘do nothing’ comparison, Sensitivity ranges, Other

      Outcome Signals: What Will Make This Win Stick?

      • What measurable KPIs would you use to judge whether a recommended change succeeded after 6–12 months? Options: Total landed cost, On-time delivery rate, Customer fill rate, Inventory turns, Carbon emissions, Working capital improvement, Other
      • What is a realistic target for annualized savings or service improvement that would justify the effort for your leadership? Options: >10% cost reduction, 5–10% cost reduction, 1–5% cost reduction, Service improvement prioritized over cost, Not sure
      • How comfortable are you with small short-term service degradation if it unlocks larger long-term savings (e.g., 2–4 week transitional service dip)? Options: Comfortable with clear mitigation, Somewhat comfortable, Prefer zero degradation, Not comfortable
      • Who should own post-implementation validation and ongoing tracking if we deliver an executable plan? Options: Supply Chain Strategy, Operations/Distribution, Finance, Third-party implementation partner, Other
      • Which dashboards or reports would make you feel confident the change is on track (frequency and primary viewers)?

      Next Steps: What Would ‘Ready to Proceed’ Look Like?

      • If we agreed a pilot or diagnostic, what is your target timeline for the next decision milestone (e.g., internal kickoff, board-ready draft)? Options: 1–2 weeks, 2–4 weeks, 1–2 months, 2–3 months, Unsure
      • Who are the three people who must say yes for us to proceed to a pilot and who will be the single escalation if things stall?
      • What would make you decline a pilot or diagnostic even if the scope and cost were reasonable? Options: Data access blocked, Leadership not aligned, Competing priorities, No perceived urgency, Other
      • What level of commercial transparency do you need up front (fixed-fee pilot, success-fee structure, full engagement pricing) to feel comfortable committing? Options: Fixed-fee pilot, Success-based/contingent, Time & materials, Need to discuss internally, Other
      • Last question—what would make you say this was the best diagnostic you've ever run (what outcome or experience would we need to deliver)?
    2. Data & Systems Access

      Confirm ERP/TMS data sources, extraction owners, sampling windows, and any contractual or privacy constraints to enable rapid baseline modeling.

      Data & Access Checklist

      Quick Intro: How You Work with Data Today

      • What's the single most common source we should look at first to build a baseline (ERP, TMS, WMS, carrier EDI, spreadsheets, other)? Options: ERP (order/shipment records), TMS (shipment legs & events), WMS (inventory movements), Carrier EDI/CTPAT feeds, OMS/CRM exports, Ad-hoc spreadsheets, Other
      • Who usually prepares that data today—an internal analyst, IT, 3PL, or the carrier—and how do they prefer to hand it off? Options: Internal analytics team, IT/BI team, Operations/Network design team, 3PL partner, Carrier, External consultant, Other
      • What file formats and delivery methods are most realistic for your organization right now (CSV/SFTP, API, database read-only, EDI, manual upload)? Options: CSV via SFTP, API endpoints, Database read-only account (ODBC/SQL), EDI extracts, Manual spreadsheet upload, Secure file share (HTTPS), Other
      • Roughly how many rows or shipment records should we expect for the sample window you plan to share? Options: <10k, 10k–100k, 100k–1M, 1M–5M, >5M, Unsure / need help estimating
      • When data has been prepared in the past, what has felt easiest to coordinate? What has felt hardest?

      If Your Data Could Speak, What Would It Complain About?

      • Are you confident your shipment history actually tells the truth about where costs and service break down—or is that a risky assumption? Options: Confident, Somewhat confident, Doubtful, Not confident at all
      • Where do you see the biggest gaps in the historical dataset we’ll need for a reliable baseline (missing rates, incorrect lane distances, inconsistent SKU mapping, incomplete cost fields)? Options: Missing freight rates, Inaccurate carrier segmentation, Inconsistent customer/ship-to IDs, Incomplete product/SKU mapping, Missing facility cost/lease data, Insufficient lead-time/service window data, Other
      • Give a recent example when a data quality issue led to a misleading conclusion or delayed a decision—what happened and how long did it take to fix?
      • How often have you been burned by late-arriving data or last-minute corrections during a modeling engagement, and how does that typically impact timelines? Options: Rarely, Occasionally, Often, Almost always
      • If we found a critical data gap during baseline building, how would you prefer we surface it—an immediate escalation, a documented assumption with impact estimate, or a paused data-clean phase? Options: Immediate escalation to stakeholders, Documented assumption + impact estimate, Pause and request corrected extract, Proceed with best-effort imputation, Other

      Who Holds the Keys? Mapping Access and Accountability

      • Who are the specific people or teams with authorization to extract ERP/TMS data, approve secure connections, and sign off on sharing—list names, roles, and business email domains if possible.
      • Which of the following groups typically control access to the systems we need (select all that apply)? Options: Central IT / Data Governance, Supply Chain / Logistics Ops, Finance / Cost Accounting, 3PL/managed services, Legal / Compliance, Business unit IT, Other
      • Have we worked with these owners before on a similar extract—do they understand the fields we need or will this require re-education? Options: Worked together recently — they know the fields, Worked together long ago — some re-education needed, Never worked together — will need full briefing, Unsure
      • What authorization steps usually trip you up (change request, security questionnaire, VPN approval, SOC2 review, legal data transfer approval)? Options: Security questionnaire, VPN/network access, SOC2/attestation review, Legal/data transfer approval, Change control window, Other
      • If approval is likely to take longer than expected, who on your side can escalate to speed things up (role/title)?

      Legal, Contracts & Privacy: What's Really Restricted?

      • How comfortable are you that sharing shipment and customer-level data for modeling won't violate existing contracts or privacy obligations? Options: Very comfortable, Somewhat comfortable, Unsure, Not comfortable
      • Which contractual or regulatory constraints should we anticipate (customer confidentiality clauses, cross-border data transfer limits, carrier contract non-disclosure, GDPR/CCPA concerns)? Options: Customer confidentiality clauses, Carrier/3PL NDAs, Cross-border transfer restrictions, GDPR/CCPA/other privacy regs, Proprietary rate clauses, None of the above, Other
      • If redaction or anonymization is required, which fields must be removed or masked (customer name, exact address, invoice numbers, SKU descriptions)? Options: Customer name, Exact ship-to address, Invoice numbers, SKU descriptions, Unit-of-measure detail, None—full data allowed, Other
      • Would a hashed ID mapping approach (we provide a mapping key that stays internal to you) be acceptable to keep analyst-level fidelity while protecting identities? Options: Yes - acceptable, Maybe - need legal review, No - cannot use hashed mappings, Unsure
      • Do you have a preferred legal template (DPA, data processing addendum, DAA) we should use, or should we propose one? Options: You have a template, We should propose our standard DPA, Need to discuss with legal first, Unsure

      Timeline Truth-Telling: What's the Real Deadline and Pain If We Miss It?

      • If the CFO or board asked you to present a defensible network alternative, what is the calendar date you need model-ready results by?
      • Which of these best describes the reason for that date—board review, budget cycle, tariff effective date, M&A close, capacity crisis, regulatory filing, other? Options: Board meeting, Budget cycle/annual planning, Tariff/tax change effective date, M&A/portfolio integration, Plant/lease capacity constraint, Regulatory filing, Other
      • What happens if we miss that date—does the decision get delayed, does execution proceed with risk, or do you lose an opportunity (quantify impact if possible)? Options: Decision delayed (re-scope), Proceed with risky assumptions, Lose commercial opportunity, Operational disruption, Reputational/board confidence hit, Unsure
      • How much runway do we actually have to iterate after initial submissions (days/weeks), and how many scenario runs do you expect within that window? Options: <1 week, 1–2 weeks, 3–4 weeks, >4 weeks
      • Who on your team must approve a compressed timeline (title/role), and what evidence do they require to accept a faster baseline build?

      What Would a Rapid Baseline Look Like to You?

      • If we promised a validated baseline model in two weeks, what would worry you most about that promise—accuracy, completeness, stakeholder buy-in, or technical risk? Options: Accuracy of inputs, Completeness of data, Stakeholder acceptance, Technical integration risk, Contract/legal clearance, Other
      • Which sample window best represents a meaningful baseline for your business—last 3 months, 6 months, 12 months, or a rolling 12 months excluding outliers? Options: Last 3 months, Last 6 months, Last 12 months, Rolling 12 months (exclude outliers), Other
      • When building a baseline, which elements must be modeled absolutely correctly versus which can be treated as assumptions to be validated later (e.g., carrier rates vs. lease costs)? Options: Carrier rates must be correct, Facility fixed costs must be correct, Service windows/commitments must be correct, Inventory policy assumptions can be provisional, Other
      • What visualization or deliverable would make the baseline 'board-ready' in your view (cost bridge, service heatmap, lane-level P&L, uncertainty bands)? Options: Cost bridge summary, Service level heatmap, Lane-level P&L, Scenario comparison dashboard, Uncertainty/assumptions appendix, Other
      • If we had to accept one trade-off to accelerate delivery (e.g., model fewer SKUs, use representative customers, or use average lane costs), which trade-off would you accept and why?

      Next Steps & Quick Wins to Unlock Access

      • What small, immediate action could your team take today to unblock data access (approve an SFTP account, nominate a data owner, sign an NDA, or provision a read-only DB user)? Options: Approve SFTP credentials, Nominate a data owner/contact, Sign NDA/DPA, Provision read-only DB user, Provide a sample extract, Other
      • Would a short technical workshop (30–60 min) with your IT/data owner to map required fields and delivery methods be valuable to accelerate the process? Options: Yes — schedule it, Maybe — need to check with IT, No — not necessary
      • Which internal stakeholders should we bring into a kickoff call to prevent later surprises (titles only, e.g., Head of IT, Network Design Lead, Legal Counsel)?
      • What concerns would you want us to document up front in a 'data readiness note' so stakeholders can approve access faster (privacy mitigations, sample window, assumed imputations)?
      • Finally, how confident are you that with the right permissions we could deliver a defensible baseline within your deadline—and what would make you feel more confident right now? Options: Very confident, Somewhat confident, Skeptical, Not confident
  2. Customer Discovery

    Clarify current network pain points, service commitments, capacity constraints, and tax or tariff triggers driving the re-evaluation.

    Discovery Questions

    Quick Orientation: How this re-evaluation landed on your desk

    • What was the primary event or trigger that prompted you to re-evaluate the network now? Options: Tariff or tax change, Acquisition / merger, Plant capacity constraint, Board directive (cost/carbon/service), Customer churn or major account risk, Carrier contract change, Other
    • Who is sponsoring this initiative and what single metric will they use to judge whether it’s successful?
    • How soon does leadership expect to see defensible options (before the next board, quarter, or other milestone)? Options: Immediately / Emergency, Within 2 weeks, 1–3 months, 3–6 months, No firm deadline
    • Which internal stakeholders will need to sign off on a recommended network change? Options: VP Supply Chain Strategy, CFO / Finance, Network Design / Modeling, Operations / Plant Management, Commercial / Sales, Procurement, Legal / Tax, HR / Labor, Other
    • How confident are you in the accuracy of the data and assumptions that underlie your current network decisions? Options: Very confident, Somewhat confident, Neutral, Somewhat doubtful, Not confident at all

    Are We Just Living With It? — assumptions we never challenge

    • What assumptions are you currently accepting that, if wrong, would make our recommended network changes appear reckless?
    • Which parts of the network feel like legacy decisions held for convenience rather than performance? Options: Inherited DCs/warehouses, Regional cross-docks, Sourcing regions, Last-mile carriers, Dedicated lanes with a carrier, 3PL contractual footprints, Other
    • Tell us about a recent recommendation or change that hindsight proved was based on poor assumptions — what happened?
    • How often do exploratory model runs flip the recommendation because of a single missing or incorrect input? Options: Almost always, Often, Sometimes, Rarely, Never
    • When model outputs and operational intuition disagree, whose viewpoint usually prevails and why?

    Where Costs Bite and Risks Hide

    • If the CFO demanded 10% lower total landed cost by next quarter, what's the first lever you'd pull—and what would you risk by doing that?
    • Which cost categories are most volatile or least trusted in your current baseline? Options: Transportation rates, Inventory carrying cost, Facility rent / lease costs, Labor and overtime, Tariffs / duties, Handling and packaging, Third-party fees, Other
    • Do you have lane-level validated rates and accessorials available, and how complete are they? Options: Fully validated lane rates, Partially validated (major lanes), Only high-level averages, No rate visibility, Unsure
    • Have recent tariff or tax changes already shifted sourcing or routing decisions in ways that surprised you? Options: Yes — sourcing shifts, Yes — routing changes, No noticeable impact, Impact expected but not implemented, Unsure
    • Give a concrete example (lane or SKU) where a small cost delta changed the optimal facility or carrier decision.
    • How do you currently model duties and tariffs in analysis? Options: Line-item duties per SKU, Percentage uplift per shipment, Applied per-source region, Ignored in current models, Other

    What Service Would Look Like If It Mattered

    • If a single missed delivery could cost you a major account, are you confident the current network design would prevent it? Options: Confident, Somewhat confident, Unsure, Not confident
    • What are your committed service levels by customer tier (examples: key accounts, national retailers, e-commerce)? Options: Same-day / Next-day, 2-day, 3–5 day, Customer-specific SLAs, Non-contractual targets, Other
    • Which customers or SKUs are non-negotiable on service and what would failure cost (penalty, churn, brand impact)?
    • How do you track OTIF or SLA performance today and on what cadence? Options: Daily, Weekly, Monthly, Quarterly, Ad hoc / Not tracked
    • Would you accept a modest cost increase to guarantee a step-change in service for top-tier accounts? Options: Yes — for top-tier only, Yes — across most accounts, No — cost first, Depends on quantified trade-offs
    • Share an example where a model recommended a cost-saving change but operations rejected it for service concerns — what prevented adoption?

    Hidden Limits: Capacity, Labor, and Lease Realities

    • Could an ideal model be infeasible because of lease terms, labor availability, or equipment constraints you’re overlooking? Options: Yes — leases, Yes — labor, Yes — equipment/handling, Possibly multiple, Unlikely / no constraints, Unsure
    • List facilities with hard capacity limits, upcoming lease expirations, or known labor shortages (facility + constraint + date if known).
    • Which facilities have contractual clauses (break fees, exclusivity, minimum throughput) that would materially change financials if altered? Options: Long-term lease with break penalty, Minimum throughput obligations, 3PL exclusivity clauses, Contracted carrier capacity, Owned property (no lease), Unknown
    • How responsive is local labor supply at peak season (can you scale +20% throughput quickly)? Options: Very responsive, Somewhat responsive, Tight but possible, Not possible, Unsure
    • Do you have committed throughput or exclusivity agreements with carriers/3PLs that limit routing or consolidation options? Options: Yes — significant constraints, Yes — minor constraints, No, Unsure
    • When was the last time you ran a stress test that combined demand spikes and facility outages to validate feasibility? Options: Within 3 months, 3–12 months, Over 12 months, Never

    What Would a Board-Ready Recommendation Need to Prove?

    • If you handed the CFO a network recommendation tomorrow, what single skeptical question would you expect them to ask?
    • Which artifacts does leadership expect with a recommendation (choose all that must be included)? Options: Baseline model and run-of-data, Scenario list and sensitivity analysis, Implementation roadmap with owners, Financial P&L impact and cashflow, Risk mitigation and contingency plans, Third-party validation or reference cases
    • What confidence metric or risk tolerance would satisfy the board (e.g., guaranteed minimum savings, probabilistic range, scenario envelope)? Options: Guaranteed minimum, Point estimate with sensitivity bands, Probabilistic / Monte Carlo range, Qualitative confidence with validation steps, Unsure
    • How important are executive-friendly visuals (maps, heatmaps, C-suite slides) relative to technical appendices for acceptance? Options: Critical — visuals first, Important but needs technical backup, Technical appendix is primary, Equal importance, Unsure
    • Who must co-sponsor the recommendation for it to pass (name roles rather than individuals if possible)?
    • Post-deployment, which KPIs and time windows will you use to declare success (examples: cost reduction in 6 months, OTIF improvement in 90 days)?

    Commitments, Data Needs, and the Fastest First Step

    • If speed-to-insight matters more than perfection, which minimum data extracts would you prioritize to get a defensible baseline in two weeks?
    • Which of the following data sources are available and who owns access? Options: ERP shipment history, TMS shipment detail, WMS throughput, Carrier invoices, Rate cards / contracts, Inventory master / SKU attributes, Customer SLAs / contracts
    • Are there contractual or privacy constraints (customer anonymization, non-disclosure clauses) that will limit data sharing? Options: Yes — strict limitations, Yes — limited anonymized sharing, No constraints, Unsure
    • Which historical sample window best reflects typical demand for modeling: last 3 months, 6 months, 12 months, or a seasonally blended year? Options: Last 3 months, Last 6 months, Last 12 months, Seasonally blended 12 months, Other / custom
    • How quickly can your team deliver a sample extract and a daily point-of-contact for data validation? Options: Under 1 week, 1–2 weeks, 2–4 weeks, More than 4 weeks, Unsure
    • Which pilot scenario should we model first as a proof point to build confidence (pick one)? Options: Facility consolidation, Nearshoring / sourcing shift, Mode shift (rail/intermodal), Inventory repositioning, Carrier optimization / re-rate
    • Who will be our day-to-day contact and who is the executive sponsor we should align deliverables to (name + role preferred)?
  3. Solution Experience

    Using the customer’s baseline data, walk through diagnosed failure modes and outcome-focused scenarios (consolidation, nearshoring, mode shift) to show concrete impacts.

    Experience Workshops

    • Pre-Experience Alignment (Baseline & Objectives Sign-off)
    • Diagnosed Failure Modes Review (Baseline → Why it Breaks)
    • Scenario Impact Workshop — Consolidation & Nearshoring
    • Scenario Impact Workshop — Mode Shift & Hybrid Strategies
    • Executive Implications & Board-Ready Outcomes
    • Agree on the sensitivity exposures that must be reduced to make a recommendation board-ready.
    • Stakeholders to confirm which failure modes must be included in the scenario slate for the next workshop.
    • Recap Preconditions & Success Metrics
    • Demonstrate concrete delta-to-baseline for consolidation and nearshoring and tie each delta to a diagnosed failure mode.
    • Get stakeholder confirmation that model assumptions reflect contractual realities and operational constraints.
    • Agree which scenario(s) merit deeper sensitivity analysis and potential hybrid testing.
    • Customer to provide lease termination dates and estimated exit costs for any facilities implicated by consolidation scenarios.
    • Customer to confirm tariff/duty rate interpretation or supply customs counsel contact for verification.
    • Model team to run requested sensitivity variants (e.g., +/- 10% transport rates, different inventory policies) and deliver within agreed SLA.
    • Quick KPI Recap & Decision Criteria
    • Quantify mode-shift benefits and identify service trade-offs that require mitigation.
    • Establish which hybrid scenarios materially improve the future state and are operationally feasible.
    • Introductions & Meeting Objective
    • Customer to provide modal rate cards or recent tender results for high-volume lanes to refine rate inputs.
    • Model team to produce a robustness matrix showing which scenarios retain benefits under adverse rate/capacity swings.
    • Operations lead to confirm whether hybrid sequence changes (e.g., phased consolidation with mode trials) are operationally permissible.
    • One-slide Current State & Consequence
    • Get executive alignment on 1–2 recommended directions to advance to Mutual Commit.
    • Agree acceptance criteria and a short evidence checklist required for a defensible board recommendation.
    • Confirm owners and timelines for producing the board-ready deliverables and commercial proposal.
    • Engagement lead to produce a board-ready slide deck (executive summary + appendix) that ties recommendations to agreed KPIs.
    • Finance sponsor (customer) to validate financial assumptions used in the NPV and provide any alternate discount rates to test.
    • Schedule the Mutual Commit meeting and circulate a checklist of sign-offs required from legal, finance, and operations prior to that meeting.
    • Ensure the current state can be stated in one clear sentence and accepted by stakeholders.
    • Surface and quantify the primary business consequences driving urgency.
    • Agree a measurable future-state outcome that scenarios must prove.
    • Obtain formal sign-off that baseline data and constraints are sufficient to run scenario modeling.
    • Customer to sign-off baseline snapshot and KPI definitions in writing.
    • Customer to deliver any missing constraints (lease end dates, labor capacity bounds, tariff schedules) within 3 business days.
    • Modeling team to confirm baseline model run reproduces provided cost and service KPIs and share a validation checklist.
    • Agree which KPIs and data points require deeper validation or reconciliation post-meeting.
    • Baseline Model Snapshot
    • Have stakeholder confirmation that the presented failure modes are accurate and material.
    • Obtain a prioritized list of failure modes to target with scenarios (consolidation, nearshoring, mode shift, hybrids).
    • Customer owners to validate or correct specific baseline anomalies called out (e.g., disputed route costs) and provide supporting documents.
    • Model team to attach detailed cost breakdowns per failure mode and circulate within 48 hours for customer review.
    • Scenario 3 — Mode Shift Model Run
    • Scenario 1 — Consolidation Run: Model Walkthrough
    • Failure Mode 1 — Capacity & Fulfillment Pinch
    • One-Sentence Current State (Diagnosis)
    • Top Recommended Options (Executive Summary)
    • Hybrid Scenarios (Consolidation + Mode Shift / Nearshore + Mode Shift)
    • Quantify Consequence
    • Consolidation: Proof vs Problem
    • Failure Mode 2 — Tariff/Trade & Cost Shock
    • Financial Impact & Timing
    • Failure Mode 3 — Overlapping/Redundant DCs and Routing Inefficiency
    • Sensitivity & Risk Tests
    • Scenario 2 — Nearshoring Run: Model Walkthrough
    • Define One-Sentence Future State
    • Acceptance Criteria & Evidence Pack
    • Comparative Trade-offs & Side-by-side KPIs
    • Pre-work & Data Sign-off Checklist
    • Impact Aggregation & Prioritization
    • Forced Validation & Selection Criteria
    • Next Steps: Mutual Commit Preparation
    • Forced Validation
    • Validation & Assumption Check
  4. Solution Scope

    Define model boundaries, constraints to represent (rates, leases, capacity, service tiers), scenario list, deliverables, and validation criteria.

    Scope Configuration

    • Ingest ERP and TMS shipment histories
    • Clean and standardize product, customer, and site masters
    • Reconcile and load carrier rates and contract pricing
    • Build baseline transportation and network cost model
    • Generate distance and transit-time matrices
    • Configure MILP network model with capacity and service constraints
    • Run multi-scenario facility location optimization batch
    • Optimize production allocation and plant capacity assignments
    • Optimize inventory positioning and safety stock allocation
    • Run modal-shift and mode-selection optimization
    • Produce cost-vs-service trade-off curves and Pareto sets
    • Create interactive executive map visualizations and dashboards
    • Export facility-to-customer allocation tables and shipment plans

    Scope Questions

    Ingest ERP and TMS shipment histories

    • Which systems should we ingest from? Options: ERP, TMS, Both, Neither (we will provide extracts)
    • What historical window should be captured for baseline modeling? Options: 3 months, 6 months, 12 months, 24 months, Custom
    • What shipment-level extracts are available (select all that apply)? Options: Shipment headers, Line-level items, Bill-of-lading details, Carrier manifest / tracking, Inventory snapshots, Other
    • Who owns data extraction and can provide access/credentials?
    • Are there contractual or privacy constraints that require anonymization or field redaction? Options: No constraints, Yes – limited fields only, Yes – cannot share PII or customer IDs, Unknown

    Clean and standardize product, customer, and site masters

    • Which master data domains require cleaning and standardization? Options: Product (SKU), Customer, Site/Facility, Carrier, Other
    • Approximate counts for each domain (e.g., SKUs, customer records, sites)?
    • Do you have product hierarchies and attributes needed for modeling (weight, volume, pack-size, family)? Options: Complete, Partial, None
    • Should we perform deduplication and matching (customer/site consolidation) and flag uncertain matches for SME review? Options: Yes – full dedupe & SME review, Yes – automatic only, No
    • Do you expect manual reconciliation effort (e.g., mapping legacy site codes) and can SMEs allocate time? Options: Yes – SMEs available, Yes – SMEs limited, No

    Reconcile and load carrier rates and contract pricing

    • What formats are your carrier rates and contracts in? Options: Structured spreadsheets, TMS rate module, PDF/scanned contracts, Mixed/partial
    • Which rate components must be modeled? Options: Base linehaul, Fuel surcharge, Accessorials, Minimum charges, Lane-specific discounts/contracts
    • Do you need modeling of negotiated volume tiers, rebate passages, or contract exceptions? Options: Yes – tiers/rebates, Yes – exceptions only, No
    • Are there key carrier constraints (equipment types, weight/volume minimums) that must be enforced? Options: Yes, No, Unknown
    • Please provide a sample rate file or describe how rate lookups should be applied (lane-level, weight bands, class).

    Build baseline transportation and network cost model

    • Should baseline represent actual routed shipments, shortest theoretical routing, or both for comparison? Options: Actual routed shipments, Theoretical shortest/fastest, Both
    • Which cost elements must be included in the baseline? Options: Transportation (linehaul), Fuel and surcharges, Accessorials/handling, Inventory carrying, Facility fixed costs (leases)
    • Do you require per-SKU cost allocation or aggregated product-family costing? Options: Per-SKU, By product family, By weight/volume band
    • What service commitments must the baseline reflect (SLA definitions by customer or lane)?
    • What validation accuracy threshold do you expect for baseline (e.g., within X% of historical spend)? Options: Within 2% of spend, Within 5% of spend, Within 10% of spend, Custom

    Generate distance and transit-time matrices

    • Which distance basis should we generate? Options: Driving/road distance, Great-circle (Haversine), Rail/network distance, Carrier-provided distances
    • Should transit times reflect historical actuals, carriers' published transit times, or both? Options: Historical actuals, Published/expected, Both
    • What level of granularity is required for matrices (site-to-site, site-to-zip, site-to-customer)? Options: Site-to-site, Site-to-zip3/zip5, Site-to-customer, Custom
    • Are cross-border lanes or customs clearance delays required in transit-time modeling? Options: Yes, No
    • Do you want sample shipments validated against the generated matrices? Options: Yes, No

    Configure MILP network model with capacity and service constraints

    • Which constraint types must be enforced in the model? Options: Facility capacity (space/throughput), Vehicle/equipment capacity, Service time windows/SLA, Production capacity, Lease/contract limits
    • Should facility open/close decisions be modeled as binary (integer) variables or as continuous capacity adjustments? Options: Binary open/close, Continuous capacity scaling, Both
    • Which service metrics are hard constraints versus objectives (e.g., on-time %, max transit days)? Options: On-time %, Max transit days, Fill rate, Order cycle days
    • What solver runtime limits or optimality gap thresholds are acceptable for large scenario runs? Options: Short (<=1 hour), Moderate (<=4 hours), Overnight, Custom
    • Who will approve configured constraints and model assumptions from your team?

    Run multi-scenario facility location optimization batch

    • How many scenarios should the initial optimization batch include? Options: 1-3, 4-6, 7-10, 10+
    • Which scenario types should be prioritized? Options: Consolidation, Nearshoring, Mode shift, Close legacy sites, Add regional DCs, Other
    • Do you require sensitivity sweeps (e.g., +/- demand, fuel cost) or single-point scenarios? Options: Sensitivity sweeps, Single-point scenarios, Both
    • What outputs are mandatory per scenario (select up to three)? Options: Total cost delta, Transport cost breakdown, Inventory impact, Service level changes, Capital/Opex impact
    • What delivery cadence or deadline do you need for the scenario batch results? Options: 1 week, 2 weeks, 4 weeks, Custom

    Optimize production allocation and plant capacity assignments

    • Should production allocation optimization be included in scope? Options: Yes, No
    • Are plant capacities fixed or can they be expanded/contracted (CAPEX) in scenarios? Options: Fixed, Expandable with CAPEX, Contracted constraints, Unknown
    • Do we need to model production changeover costs, minimum run sizes, or lead-time impacts? Options: Yes – all, Yes – some (specify in comments), No
    • Is multi-stage routing or co-manufacturing (parts to multiple plants) required? Options: Yes, No
    • Who owns production/plant data and will validate plant-level parameters?

    Optimize inventory positioning and safety stock allocation

    • Which inventory objective should guide optimization? Options: Minimize total cost, Target service level (fill rate), Balance cost and service, Reduce working capital
    • Do you want safety stock optimized per SKU-location or at aggregated levels? Options: Per SKU-location, By product family, By location class
    • What target service levels should safety stock support (e.g., 95%, 98%)? Options: 95%, 98%, 99%, Custom
    • Should lead-time variability, supplier constraints, and demand seasonality be modeled in the safety stock calculation? Options: Yes, No, Partial
    • Do you require simulation of safety stock performance under demand shocks or supply disruptions? Options: Yes, No

    Run modal-shift and mode-selection optimization

    • Should modal optimization be applied globally or limited to specific lanes/regions? Options: Global (all lanes), Specific lanes only, Regional only
    • Which transport modes should be modeled? Options: Truck, Rail, Ocean, Air, Intermodal
    • Do you require mode-specific lead time, reliability, and carbon metrics to influence mode selection? Options: Yes – cost + lead time, Yes – include carbon, No – cost only
    • Are there contractual mode constraints or exclusivity clauses to enforce for certain lanes? Options: Yes, No, Unknown
    • Do you want mode selection outputs at lane-level granularity or regional averages? Options: Lane-level, Regional averages, Mode class only

    Produce cost-vs-service trade-off curves and Pareto sets

    • Do you require Pareto front visualizations and trade-off curves for executive presentations? Options: Yes, No
    • Which metrics should be plotted on trade-off axes? Options: Total cost, Delivery days / transit time, Carbon/CO2e, Inventory days, Service %
    • How many points per curve or granularity do you expect (e.g., 5, 10, 20)? Options: 5, 10, 20, Custom
    • Do you need scenario-level Pareto comparison tables and downloadable slide-ready exports? Options: Yes, No
    • Which audience(s) will review these trade-offs (select all that apply)? Options: Operations, Finance/CFO, Executive/Board, Supply Chain Leadership

    Create interactive executive map visualizations and dashboards

    • Which dashboard types are highest priority? Options: Cost summary, Network map, Service performance, Inventory heatmap, Scenario comparison
    • Do you require interactive filtering by SKU, region, scenario or user role? Options: Yes, No
    • Will dashboards be embedded in your BI stack or delivered as standalone interactive reports? Options: Embedded (PowerBI/Tableau), Standalone (web), Both
    • What export formats do you need for executive deliverables (e.g., PPTX, PNG, CSV, API)? Options: PPTX, PNG, CSV, API, Other
    • What refresh cadence is required for dashboards during the engagement? Options: One-off/static, On-demand refresh, Daily, Weekly
  5. Mutual Commit

    Agree commercial terms, engagement cadence, acceptance criteria, and board-ready deliverables to ensure a defensible recommendation.

    Agreement Modules

    • Statement of Work (SOW)
    • Master Services Agreement (MSA)
    • Pricing & Commercial Terms
    • Payment Schedule & Purchase Order
    • Acceptance Criteria & Signoff
    • Data Processing & IP License Agreement
    • Confidentiality & Data Security Addendum (DPA)
    • Implementation Roadmap & Governance Plan
    • Change Order & Scope Management
    • Board-Ready Deliverables & Executive Package
    • Resource Commitment & RACI Matrix
    • Risk & Contingency Annex
    • Termination, Extension & Exit Plan
  6. Deployment

    Operationalize rollout with readiness checks, enablement, and outcome validation.

    1. Pre-Deployment Readiness

      Confirm data handoffs, model inputs validated, owners for implementation tasks, and mitigation plans for lease or labor constraints.

      Readiness Questions

      Quick Check: Where Are We Right Now?

      • How would you best describe your current readiness for deployment in one short phrase? Options: Not started, Data validated, no owners assigned, Model validated, owners assigned, no implementation plan, Implementation plan in progress, Deployment scheduled
      • Which stakeholder groups have already reviewed and tacitly accepted the baseline recommendations? Options: Supply Chain Strategy / VP, Network Design / Manager, Operations / Plant Managers, Finance / CFO, Commercial / Sales, IT / Data Team, Legal/Compliance, None yet
      • When was the last time your team validated the model against historical shipments (month/year)?
      • What remaining assumptions or inputs do you feel are the least certain right now?
      • Are there known contractual or regulatory constraints we must resolve before any cutover? Options: Yes - leases/real estate, Yes - carrier contracts, Yes - union/labor agreements, Yes - tariffs/regulatory, No known constraints, Unsure

      If Launch Failed, Whose Head Would It Be?

      • Who would ultimately be held accountable if an early deployment caused service failures or material cost overruns? Options: VP Supply Chain Strategy, Network Design Manager, COO/Operations Head, CFO/Finance, Plant/Region Manager, Shared accountability
      • Please list the named decision owners who must sign final go/no-go (name and title).
      • Is there an executive sponsor willing to publicly defend the program to the board if short-term metrics wobble? Options: Yes - strong sponsor, Yes - conditional sponsor, No sponsor yet, Unsure
      • What is the formal escalation path for critical issues during rollout (who gets looped in, and when)? Options: Site-level escalation → Regional Ops → VP Ops → Exec Sponsor, Regional Ops → VP Supply Chain → CFO, Ad-hoc / depends on issue, No formal path
      • How confident are the named owners in the model's assumptions and inputs today? Options: Very confident, Somewhat confident, Skeptical but open, Not confident

      What Would Stop This from Going Live?

      • Which single constraint—leases, labor, systems, or carrier contracts—would make the recommended change impossible to implement? Options: Fixed lease terms / penalties, Local labor / union constraints, Carrier minimums / contract floors, IT/system integration limitations, Regulatory/tariff barriers, None of the above / unsure
      • Which facilities have lease clauses or termination penalties that materially restrict change, and what are the key dates?
      • Where do you face the most acute labor or skills constraints that could delay ramp-up (sites, roles, or regions)?
      • Are there carrier minimum volume commitments or guaranteed lanes that, if changed, would significantly alter cost assumptions? Options: Yes - major impact, Yes - minor impact, No commitments, Unsure
      • How long (realistically) to obtain any external approvals or permits required for the changes we recommend? Options: <2 weeks, 2–6 weeks, 6–12 weeks, >12 weeks, Not required / unsure

      Do Your Data and Systems Play Nice?

      • If we requested two weeks of raw ERP and TMS exports today, could your team deliver clean, complete files within 10 business days? Options: Yes - complete in <10 days, Yes - but >10 days, Partial data only, No significant effort required, Unsure
      • Who owns each extraction (ERP owner, TMS owner, BI/IT contact) and how do we get access (SFTP/API/manual)?
      • Which data elements are commonly missing or unreliable in your current exports (e.g., customer IDs, product hierarchies, cost columns)? Options: Customer identifiers, Product hierarchies/SKUs, Actual landed cost, Carrier/SCAC data, Service commitments/dates, Inventory levels, Other
      • What historical window is realistic for sampling and validation: 3 months, 6 months, 12 months, or rolling year? Options: 3 months, 6 months, 12 months, Rolling 12 months, Unsure
      • Are there contractual, privacy, or regulatory constraints on sharing shipment or customer data with our team and tools? Options: Yes - needs NDA/controls, Yes - anonymized only, No constraints, Unsure

      Who Will Do the Heavy Lifting?

      • Who will be the day-to-day owner(s) responsible for executing implementation tasks (names/titles and % of time available)?
      • Do you have a dedicated program manager or PMO assigned, and if so, what percent FTE is allocated? Options: Yes - >0.5 FTE, Yes - 0.25–0.5 FTE, Yes - <0.25 FTE, No PMO / not assigned
      • Which external partners must be involved (3PLs, carriers, integrators, landlords) to execute the plan? Options: 3PL(s), Primary carriers, IT integrator, Real estate broker/landlord, Labor provider/agency, None / Unsure
      • How many people from operations, IT, and finance can be dedicated to cutover activities (hours/week) for the next 8 weeks? Options: <20 hours/week, 20–40 hours/week, 40–80 hours/week, >80 hours/week, Not able to commit
      • What training or enablement will be needed for site teams to operate under the new configuration? Options: Operational SOPs, WMS/TMS training, Carrier coordination playbooks, Change management sessions, No training needed, Other

      What’s Your Plan B If Something Breaks?

      • Before we go live, what fail-safe would you insist on—full rollback capability, parallel run, pilot at one site, or another approach? Options: Full rollback plan, Parallel / shadow run, Pilot at single site, Phased regional roll-out, Other / not sure
      • What operational thresholds should trigger a rollback or pause (service level drops, cost variances, inventory outages)? Please be specific.
      • If a recommended closure or consolidation is delayed by a lease, what short-term mitigation options are acceptable (subleases, temporary cross-dock, phased transfers)? Options: Sublease, Temporary cross-dock, Phased transfer by SKU, Increase safety stock, Accept delay, Other
      • Who is empowered to make the call to pause or roll back during go-live hours (name/title)?
      • How quickly can you stand up an emergency response team to remediate critical issues (hours to assemble, expected SLA)? Options: Within 2 hours, Same day, 24–48 hours, >48 hours, No plan / unsure

      How Will We Know We’ve Succeeded?

      • If the CFO asked today for three measurable signals that prove success, which would you choose? (select up to 3) Options: Total delivered cost reduction, On-time in-full (OTIF) improvement, Customer lead-time reduction, Inventory turns increase, Transportation cost per unit, Carbon emissions decrease, Service complaint reduction
      • What are the pass/fail thresholds for each core acceptance metric (e.g., OTIF >= X%, cost delta <= Y%)?
      • Describe the acceptance testing plan you'd expect — duration, sample SKUs/customers, and who signs off.
      • Do you require board‑ready deliverables (executive slide pack, model appendix, risk register) as part of acceptance? Options: Yes - all of the above, Yes - executive pack only, Yes - model appendix only, No - not required, Unsure
      • What documentation and handoffs must be completed before internal teams take operational ownership? Options: SOPs / runbooks, Data dictionaries, Cutover checklist, Training records, All of the above, Other

      Ready to Commit to the First Step?

      • What is the earliest date leadership will authorize the first deployment milestone (data handoff, pilot kickoff, or cutover prep)? Options: This week, Within 2 weeks, Within 1 month, 1–3 months, No timeline / undecided
      • Which internal approvals are still required before that date (finance sign-off, legal, board, union, other)? Options: Finance / budget, Legal / contracts, Board approval, Union/works council, IT security, None / all approved
      • Is budget allocated for implementation activities and change management, or will we need a separate funding request? Options: Budget allocated, Partial budget - needs approval, No budget - funding required, Unsure
      • Who from your side should sit on a weekly deployment steering committee (names/titles and primary responsibilities)?
      • Which implementation approach do you prefer to start with: 30‑day pilot, phased roll‑out, or full cutover? Options: 30‑day pilot, Phased roll‑out, Full cutover, Prefer vendor recommendation
    2. Deployment Enablement

      Schedule implementation steps, assign owners, map transition risks, and coordinate change windows to minimize service disruption.

    3. Validation Checklist

      Execute acceptance tests against service levels, cost targets, and operational feasibility, documenting any deviations and required remediation.

      Validation Questions

      Getting Comfortable — Tell Us About Your Network Today

      • How often do you formally review or re-run a network model today? Options: Annually, Quarterly, Biannually, Only after a triggering event, Rarely / never
      • What recent event prompted you to engage in this review (pick all that apply)? Options: Tariff or trade change, Acquisition / M&A, Plant or DC capacity constraint, Board directive for savings/carbon, Carrier rate shock, Other
      • In two sentences, describe the current network topology and one operational habit you wish would change.
      • Who currently owns network strategy, modeling, and board reporting inside your organization? Options: VP/Head Supply Chain Strategy, Network Design Manager, Operations Research / Analytics, Third-party consultant, Cross-functional steering team, Other
      • How confident are you that your existing baseline (rates, volumes, service commitments) reflects reality? Options: Very confident, Somewhat confident, Unsure, Not confident at all
      • What is the single most important outcome you want this engagement to produce?

      What If Your Board Asked for Proof Tomorrow?

      • If the CFO asked you in next week's board meeting 'Why should we trust this recommendation?', what would you be most afraid they'd find wrong?
      • Which model assumptions do you expect adversaries (CFO, legal, ops) to challenge first? Options: Carrier rates and accessorials, Inventory assumptions, Lease and fixed cost estimates, Service level guarantees, Tax / duty treatment, Other
      • Can you share an example where a past network recommendation was pushed back or rejected—what broke down?
      • How much lead time do we realistically have to produce board-ready materials? Options: Less than 2 weeks, 2–4 weeks, 4–8 weeks, More than 8 weeks
      • Which stakeholders must sign off on a final recommendation (select all that will be involved)? Options: CEO/Board, CFO/Finance, Head of Supply Chain, Network/Operations, Commercial / Sales, Legal / Tax, HR / Labor, Other
      • How would it feel professionally if you presented a recommendation and it didn’t hold up to scrutiny?

      Where the Numbers Don’t Match the Reality

      • How confident are you that ERP and TMS history reliably map to customer orders and true landed costs? Options: Very reliable, Somewhat reliable, Patchy; needs clean-up, Unreliable / missing large portions
      • Which systems contain the master data we'll need (select all that apply)? Options: ERP (orders/invoicing), TMS (shipments), WMS (inventory), Carrier EDI / rate files, Custom spreadsheets, Other
      • Are there contractual, privacy, or regulatory constraints that limit sharing of rates, customer addresses, or SKU data? Options: No constraints, Non-disclosure agreements in place, Carrier contract restrictions, Customer confidentiality constraints, Regulatory / export controls, Unsure
      • What sample window would best represent your normal run-rate (pick one)? Options: Last 3 months, Last 6 months, Last 12 months, Seasonal period we prefer to define
      • Who will be the day-to-day owners for data extraction and validation? (names/roles and availability)
      • Tell us about the most common data quality issue you expect (eg. missing customer classifications, mis-routed shipments, or split ASN logic).
      • How quickly can we get a sanitized, anonymized sample dataset for a 2-week rapid baseline? Options: Within 48 hours, 3–7 business days, 1–2 weeks, Longer / needs planning

      What Keeps You Up at Night About Implementation?

      • If our model recommends closing or consolidating one or more sites, what is the single consequence that worries you most?
      • Which of the following are real, non-negotiable constraints we must honor? Options: Existing lease terms, Union / labor agreements, Customer-specific service windows, Production capacity limits, Regulatory footprints (e.g., cross-border rules), None / flexible
      • Have you ever had an 'optimal' recommendation fail during execution? What was the root cause?
      • How much temporary service disruption is acceptable during transition (select the tolerance range)? Options: None — zero disruption, Up to 1 week for localized outages, 1–4 weeks acceptable, Longer acceptable with compensation plans
      • What internal capabilities do you have to implement changes—project leads, PMO, change management, IT—select those available? Options: Dedicated PMO, Cross-functional steering committee, External integrator budgeted, Limited internal bandwidth, No formal capability yet
      • Emotionally, what would make an implementation feel successful to you and your team?

      Imagine a Board‑Ready Recommendation That Can't Be Dismantled

      • What pieces of evidence would make a recommendation 'bulletproof' when a skeptical CFO looks at it? Options: Audited cost model, Validated historical baseline, Sensitivity and scenario analysis, Third-party reference case, Clear implementation plan with owners, Tax / legal review
      • Which deliverables must be in final handover for you to consider the engagement complete? Options: Full model files and assumptions, Executive slide deck (board-ready), Implementation roadmap and owners, Detailed cost / ROI workbook, Risk & mitigation register, Validation test results
      • What acceptance criteria would you use to sign off on our recommendation (examples: ROI threshold, service level maintained, break-even timeline)?
      • What visualization style persuades your board—detailed financial tables, maps with heatmaps, scenario dashboards, or story-driven slides? Options: Executive slides + highlights, Interactive dashboard, Static financial appendices, Map-centric visuals with narrativized scenarios, All of the above
      • Who will be the presenter at board level and who prepares the financial rebuttal if needed?

      If We Showed You a Better Future — What Would That Feel Like?

      • What are the top three outcomes that would make you call this engagement a success? Options: Sustained cost savings, Improved service levels, Reduced carbon footprint, Faster order-to-delivery, Lower inventory carrying costs, Stronger board confidence
      • Do you have numeric targets we should hit (cost reduction %, service uplift %, emissions reduction %) — please list if available.
      • How will you know in 6–12 months that the recommendation delivered value—what signals or KPIs will you watch?
      • Which trade-off is hardest for your leadership team to accept (cost vs. service vs. carbon)? Options: Cost over service, Service over cost, Carbon prioritized, Context dependent / no single priority
      • If a recommended change required us to run a pilot, what minimum pilot scope would you accept to prove the idea? Options: Single route or lane, One SKU family, One region or DC, Phased multi-site pilot, Not interested in pilots
      • What would success feel like personally for you as the sponsor—career-wise, reputationally, or operationally?

      Making This Fast, Accurate, and Non-Disruptive

      • If speed mattered more than perfection, what is the minimum viable timeline you'd accept for a validated baseline model? Options: 48–72 hours (sample), 1 week, 2 weeks, 4 weeks
      • Which individuals or teams can commit to daily or every-other-day reviews during the rapid build phase?
      • What level of external support is realistic and budgeted: advisory only, co-managed modeling, or turn-key implementation? Options: Advisory / coaching, Co-managed modeling, Full turn-key execution, Undecided / need guidance
      • Which reporting cadence would keep your team engaged without derailing operations? Options: Daily standups during ingestion, Twice-weekly checkpoints, Weekly reviews, Biweekly steering committee
      • What would trigger you to pause or stop the engagement (examples: data concerns, cost overruns, leadership change)?
      • Finally, what one thing could we do in the first two weeks that would immediately increase your confidence in our approach?
  7. Success

    Review delivered outcomes against success signals, capture lessons learned, and maintain a shared channel for issues and enhancement requests.

    Success Reviews

    • Success Review — Executive Summary
    • Operational Validation & Acceptance Testing
    • Lessons Learned & Continuous Improvement Workshop
    • Support & Enhancement Governance — Ongoing Channel Setup

    Issues & Enhancements

    • One-sentence Current State
    • Confirm Test Scope & Data Sets
    • Validate that model outputs are accurate and operationally feasible against live datasets and acceptance tests.
    • Identify root causes for any deviations and agree on mitigations, ownership, and timelines for retest.
    • Produce an explicit defect/remediation list with dates for closure to move to post-acceptance support.
    • Deliver corrected model inputs or assumptions and re-run the specified acceptance tests within the agreed SLA.
    • Assign implementation owners for operational mitigations (carrier changes, scheduling shifts, inventory moves) and set deadlines.
    • Upload test artifacts, logs, and validation evidence to the shared project repository.
    • One-sentence Current State Recap
    • Capture a complete set of lessons learned and convert them into a prioritized backlog of improvements with owners.
    • Agree on a small set of monitoring KPIs and assign owners for ongoing validation of model and operational performance.
    • Define immediate training and documentation updates to prevent recurrence of identified issues.
    • Create the prioritized improvement backlog in the shared tool and assign owners and target dates for the top 5 items.
    • Publish lessons-learned artifacts and update the project playbook and runbooks.
    • Schedule targeted training sessions for model users and operations teams within the next 30 days.
    • Define Shared Channel & Access
    • Establish a single shared channel with clear access and taxonomy for issues and enhancement requests.
    • Agree triage rules, SLA targets, and a predictable governance cadence for reviewing and prioritizing requests.
    • Seed the enhancement roadmap with prioritized items and assign owners for initial grooming and delivery.
    • Provision the shared channel, invite stakeholders, and publish the triage playbook and SLA definitions.
    • Add initial enhancement and defect items to the backlog and assign triage owners for each.
    • Schedule the recurring governance meetings and circulate the reporting template for the first monthly report.
    • Confirm whether delivered outcomes meet the board-ready success signals and obtain formal executive acceptance or defined escalation.
    • Surface any high-impact gaps with quantified consequences and agree immediate remediation or mitigation actions.
    • Assign owner and timeline for executive reporting and stakeholder communications.
    • Produce a 1-page executive summary showing baseline vs delivered results for each success signal and circulate to execs.
    • If gaps exist, create an agreed remediation plan with owners, milestones, and impact estimates within 5 business days.
    • Publish formal sign-off or escalation memo and file in the project repository.
    • Recap of Success Signals & Acceptance Criteria
    • Issue Triage & Priority Matrix
    • Retrospective — What Worked / What Didn't
    • Run Acceptance Tests — Cost & Service
    • Root Cause Deep Dive on Top 2 Issues
    • Measured Outcomes vs Targets (Diagnosis & Proof)
    • Operational Feasibility Checks
    • Enhancement Request Lifecycle
    • Generate & Prioritize Improvement Opportunities
    • Governance Cadence & Reporting
    • Root Cause Analysis for Deviations
    • Consequence Assessment
    • Future State Confirmation (Is this board-ready?)
    • Define Monitoring Metrics & Ownership
    • Initial Backlog Grooming & Roadmap Alignment
    • Confirm Mitigations & Re-tests
    • Decision & Next Steps
    • Sign-off on Operational Acceptance or Defect List
    • Escalation Paths & Emergency Response
    • Training & Knowledge Transfer Plan
    • Communications & Stakeholder Reporting
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.