Discovery field guide / Industry
How to find AI opportunities in Retail
Where should discovery start?
Follow a product or customer issue across store, ecommerce, inventory, and service teams. Look for repeated interpretation of product information, return policies, and fulfillment exceptions. Interview store staff as well as central teams so discovery reflects the operating floor. Separate information work from inaccurate stock, broken promotions, and physical availability; a confident answer does not make an item available or a refund authorized.
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 product category and one journey, such as a return initiated online and completed in store. Compare ordinary and exception cases across channels. Capture the item, policy date, inventory state, and staff authority at each handoff.
Where to look across departments
Store and customer-service exceptions
Inspect disputed promotions, return-policy questions, and stock inquiries that trigger calls to supervisors or other stores. Record where staff search for approved guidance and where they need an authorized action. A clearer policy or connected stock record may address the problem without generated advice.
Merchandising and product-information work
Trace supplier content into approved product descriptions, channel listings, and store instructions. Look for repeated fact checking, missing attributes, and inconsistent specifications. Keep interpretation of vendor material separate from claims approval and distinguish content preparation from merchandising or pricing decisions.
Who to interview and what each person knows
Store associate and channel counterpart
Ask an associate and supervisor to walk through an exception during an ordinary shift. Interview the ecommerce or service team that handled the same case. Include staff using shared devices or low-bandwidth connections; a headquarters demonstration may miss the conditions in which help is needed.
Inventory, merchandising, and policy owners
Bring the inventory-system owner, product-content editor, loss-prevention lead where relevant, and owner of customer policies. Ask who can approve refunds, substitutions, or claims. Identify who corrects inconsistent facts across channels rather than assuming a single catalog is authoritative for everything.
What to ask: follow the evidence
Why could staff not complete the promise?
Ask which policy, product fact, or system state was missing when the customer asked. Did the website and store show different information? Who had authority to resolve it? Capture the cost of a mistaken commitment, including a customer trip or an unavailable replacement.
What changes during peak trading?
Ask how promotions, seasonal staff, returns volume, and changing assortment alter the task. Which examples would fail outside a quiet week? Record how guidance is updated and how staff recognize outdated material before advising a customer.
Signals of opportunity, and reasons to look elsewhere
Repeated questions with maintained sources
Frequent product or policy searches may support assistance when the applicable version and channel are clear. Conflicting promotions and delayed inventory updates are warning signs. Measure whether staff can verify the answer quickly enough to help during a real interaction.
Consistent attribute or handoff gaps
Repeatedly missing product attributes or return reasons can reveal a structured capture opportunity. Check whether simple validation or supplier requirements would solve it. More generated descriptions are not useful if they contain unsupported claims or create additional editorial review.
Industry-specific risks and constraints
Customer promises and profiling
Wrong product, price, availability, or policy statements can harm customers and create obligations. Review applicable consumer and privacy requirements with responsible owners. Do not repurpose service or loyalty data for personalization without assessing permitted use, consent where relevant, and fairness.
Seasonality and operational access
A trial in one store or quiet period may not represent peak conditions, temporary staff, or a different channel. Check shared-device access and sensitive customer or employee information. Retain a practical human fallback when systems are slow or the information cannot be verified.
How to evaluate what you find
Test cross-channel contradictions
Use approved examples with changed promotions, similar product variants, missing attributes, and inventory discrepancies. Check factual support, policy selection, escalation, and staff correction effort. Include actual store conditions rather than testing only a desktop content workflow.
Separate activity from retail outcomes
Compare correct resolution, avoided rework, editorial effort, and customer complaints. Revenue or basket-size effects require a defensible commercial experiment that accounts for promotion and season. Do not label a larger content output or faster response as demonstrated incremental sales.
How to compare, prioritize, and invest
Choose a category and channel boundary
Start with an inspectable internal task in one category or a clear policy area. Fix catalog ownership and stock synchronization first when those drive failure. Avoid expanding immediately to customer-facing promises across every store and channel.
Fund reliability under real conditions
Compare candidates by usable staff capacity, accurate information, fewer repeated contacts, and maintained customer access. Include content updates and seasonal training. Set stop conditions for false claims or wrong policy guidance and require a retail operations owner to approve expansion.
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:
Qualify a retail handoff in IntakeOS
Bring a sanitized cross-channel journey and its policy, product-data, and authority gaps. Use IntakeOS discovery to compare the improvement with a catalog, integration, or process repair before selecting a tool.
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