Discovery field guide / Department
How to find AI opportunities in Operations & Supply Chain
Where should discovery start?
Follow a delayed order, production exception, or shift handover through the actual operating process. Look for repeated interpretation of status, missing context, and coordination across planning, the floor, and dispatch. Interview the people managing disruptions, not only the planner viewing the dashboard. Separate language and evidence work from physical capacity constraints, unsafe procedures, and inaccurate inventory that AI cannot simply reason away.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one site, product flow, and recurring disruption. Walk the route with the operator and planner using a normal shift and an exception shift. Capture timestamps, source records, manual workarounds, and the point where someone had to make a judgment.
Operations covers production, fulfillment, and daily supply-chain execution. Procurement & Supply Chain covers sourcing and supplier-commercial decisions; supplier delays enter this guide when they change the operating plan.
Where to look in the work
Shift handovers and dispatch exceptions
Inspect paper notes, status messages, and spreadsheets used to explain why work is not proceeding. Identify missing facts and duplicated interpretation. A shared structured handover may be enough when everyone already knows the rule but lacks a consistent place to record the state.
Planning-to-execution gaps
Trace a schedule revision through inventory, labor, equipment availability, and transport commitments. Record the constraint that forced the revision and who approved it. Distinguish stale master data or physical shortages from uncertainty that might be reduced through better evidence or forecasting.
Who to interview and what each person knows
Operator, shift lead, and planner
Observe the person doing the work and ask the shift lead how exceptions are contained. Compare their account with the planner's assumptions. Include a night or peak shift where possible; the easy daytime path can conceal unavailable specialists and manual recovery steps.
Quality, safety, and systems owners
Interview the quality or safety owner and the administrator of the execution or inventory system. Ask who can authorize a deviation and stop work. A local productivity gain is not an acceptable trade if it bypasses inspection, creates a hazard, or hides a downstream shortage.
What to ask: follow the evidence
Why could the next step not start?
Ask which fact, material, person, or approval was missing at the moment of delay. How did staff find out? What workaround did they use and who inherited the consequences? Separate waiting for capacity from time spent diagnosing the problem so the candidate targets a controllable cause.
What happens when the recommendation is wrong?
Ask how an incorrect schedule, stock assumption, or handover note would be detected. Can work safely pause or revert? Which constraints are non-negotiable? Capture units, timestamps, asset identifiers, and authority boundaries; plausible language is not enough to direct physical work.
Signals of opportunity, and reasons to look elsewhere
Recurring evidence reconstruction
Repeatedly assembling a disruption history from notes and systems can indicate a bounded summary or triage opportunity. The source state must be trustworthy and current. If the system says material exists but the floor cannot find it, inventory accuracy is a prerequisite, not a model feature.
Stable constraints with visible exceptions
A repeatable decision with measurable outcomes and a named approver can support investigation. Rare safety-critical interventions and unexplained operator expertise need deeper process discovery. Check whether ordinary workflow automation, scheduling logic, or process redesign better fits the identified problem.
How to evaluate what you find
Replay disruptions under real constraints
Use historical shifts with only the information available at the time. Include shortages, equipment downtime, and conflicting status updates. Evaluate feasible recommendations, incorrect assumptions, and supervisor review effort. Do not accept a locally faster plan that increases downstream queues or misses service commitments.
Separate advisory work from control
Check data freshness, integration reliability, site connectivity, and the fallback when a system is unavailable. Involve safety and quality owners before any live trial. Evidence for a handover assistant does not establish suitability for machine control or autonomous scheduling with physical consequences.
How to compare, prioritize, and invest
Start at a visible bottleneck
Prefer one bounded handoff or exception path with an accountable supervisor and observable results. Sequence master-data repairs and basic status capture first if needed. Avoid a broad optimization program until the team can explain which constraint it expects to change and who owns that change.
Compare the whole flow
Rank candidates on end-to-end lead time, quality, reliability, and usable capacity rather than local task speed. Include training across shifts and ongoing review. Set stop conditions for unsafe suggestions or hidden downstream rework, and have operational leaders decide whether the evidence supports another site.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Map an operating exception in IntakeOS
Bring a site-level process, a sanitized disruption, and the physical and approval constraints. Use IntakeOS to structure discovery before committing to a tool that changes schedules, priorities, or instructions on the floor.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo