--- # === IDENTITY === id: consulting/recipes/retail-adoption-psychology-assessment/2026 canonical_question: "How do you assess retail adoption psychology with influence mapping and fear inventory?" aliases: - "Retail AI adoption psychology assessment" - "Influence mapping and fear inventory for retail AI" - "TAM-based adoption readiness assessment for retail" entity_type: execution_recipe domain: consulting > recipes > Retail Adoption Psychology Assessment region: global jurisdiction: global temporal_scope: 2026-2027 # === VERIFICATION === last_verified: 2026-03-30 confidence: 0.85 version: 1.0 first_published: 2026-03-30 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "Initial release — adoption psychology assessment v1.0" next_review: 2026-09-26 change_sensitivity: high # === CONSTRAINTS === constraints: - "Anonymity required — fear inventory responses must be aggregated, never attributed to individuals" - "ONA/network analysis requires communication platform admin access (Slack, Teams, or email metadata)" - "Minimum sample: 30 employees per store/region to achieve statistical significance on fear inventory" - "Hero/star dependency scoring requires at least 4 weeks of communication metadata for reliable centrality measures" - "Survey fatigue risk — combine fear inventory with existing employee engagement cadence where possible" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs a full post-diagnostic implementation roadmap, not adoption assessment" use_instead: "consulting/recipes/retail-ai-implementation-roadmap/2026" - condition: "User needs general OIA theory, not retail-specific adoption psychology" use_instead: "consulting/oia/organizational-immune-system-theory/2026" - condition: "User needs technology capability assessment, not human adoption readiness" use_instead: "consulting/retail-ai/six-dimension-maturity-model/2026" # === AGENT HINTS === inputs_needed: - key: store_count question: "How many stores or regions are in scope?" type: choice options: ["1-5 stores", "5-20 stores", "20-100 stores", "100+ stores"] - key: communication_platform question: "What communication platforms do store employees use?" type: choice options: ["Slack", "Microsoft Teams", "Email only", "Mixed/proprietary"] - key: existing_ai_tools question: "Are any AI tools already deployed in stores?" type: choice options: ["none", "1-2 tools (pilot)", "3-5 tools (scaling)", "5+ tools (mature)"] - key: prior_change_history question: "How did the last major technology rollout go?" type: choice options: ["smooth adoption", "moderate resistance", "significant pushback", "failed/rolled back", "no prior rollout"] # === EXECUTION METADATA === execution: required_inputs: - name: "Store/region employee roster" source: "client/HR" format: "spreadsheet" - name: "Communication platform admin access" source: "client/IT" format: "API credentials or export" - name: "List of current and planned AI tools" source: "client/operations" format: "document" outputs: - name: "Influence Network Map" format: "PDF + interactive graph (HTML)" description: "Per-store/region informal influence network with centrality scores, bridge nodes, and formal-vs-informal gap analysis" - name: "Rational Fear Inventory Report" format: "PDF + structured JSON" description: "Anonymized fear distribution across five threat categories with severity scoring and store-level heatmap" - name: "TAM Readiness Scorecard" format: "PDF + JSON" description: "Technology Acceptance Model scoring per AI tool: perceived usefulness, perceived ease of use, behavioral intention" - name: "Adoption Pilot Design" format: "document" description: "Peer-driven pilot plan using identified informal leaders as adoption champions" tools_required: - name: "ONA Tool (Viva Insights or custom)" purpose: "Organizational network analysis from communication metadata" tier: "enterprise" cost: "$3K-$8K/engagement" alternatives: ["Custom Python NetworkX analysis", "Gephi", "Polinode"] - name: "Survey Platform" purpose: "Anonymous fear inventory and TAM questionnaire deployment" tier: "free" cost: "$0-$200" alternatives: ["Typeform", "Google Forms", "SurveyMonkey", "Qualtrics"] - name: "Interview Protocol Kit" purpose: "Semi-structured interviews for constraint boundary transparency audit" tier: "free" cost: "$0" alternatives: ["Custom protocol", "Dovetail for analysis"] credentials_needed: - service: "Communication Platform" type: "Admin API token or export access" where_to_get: "Platform admin console" free_tier_limits: "N/A — requires admin-level access" estimated_duration: "3-5 days" estimated_cost: "$8K-$15K (consulting)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/consulting/recipes/retail-adoption-psychology-assessment/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-30)" # === RELATED UNITS === related_kos: depends_on: - id: "consulting/oia/organizational-immune-system-theory/2026" label: "OIA theoretical framework underpinning adoption psychology" feeds_into: - id: "consulting/recipes/retail-ai-implementation-roadmap/2026" label: "Post-diagnostic implementation roadmap using adoption findings" related_to: - id: "consulting/recipes/oia-network-analysis-execution/2026" label: "Network analysis sub-recipe for influence mapping" - id: "consulting/recipes/oia-autoimmune-scan-execution/2026" label: "Autoimmune scan for detecting shadow workarounds" # === SOURCES === sources: - id: src1 title: "Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology" author: Davis, F.D. url: https://www.jstor.org/stable/249008 type: academic_paper published: 1989-09-01 reliability: authoritative - id: src2 title: "The Informal Organization" author: Cross, R. & Parker, A. url: https://hbr.org/2004/03/the-hidden-power-of-social-networks type: academic_paper published: 2004-03-01 reliability: authoritative - id: src3 title: "AI Anxiety: How Workers Fear and Embrace Artificial Intelligence" author: Pew Research Center url: https://www.pewresearch.org/social-trends/2023/07/26/which-u-s-workers-are-more-exposed-to-ai-on-their-jobs/ type: primary_research published: 2023-07-26 reliability: high - id: src4 title: "Change Management Best Practices for Retail Digital Transformation" author: McKinsey & Company url: https://www.mckinsey.com/industries/retail/our-insights/the-next-frontier-of-retail-digital-transformation type: industry_report published: 2024-01-15 reliability: high - id: src5 title: "Organizational Network Analysis: A Practical Guide" author: Merrill, J. et al. url: https://journals.sagepub.com/doi/10.1177/0890117120977174 type: academic_paper published: 2021-01-01 reliability: high --- # Retail Adoption Psychology Assessment ## Purpose This recipe assesses retail organization readiness for AI adoption by mapping informal influence networks and conducting a rational fear inventory. It produces an influence network map per store/region, a categorized fear distribution report, TAM readiness scores per AI tool, and a peer-driven adoption pilot design using identified informal leaders as champions. The methodology combines organizational network analysis with behavioral psychology to predict and prevent adoption failure before rollout begins. [src1, src2] ## Prerequisites - [ ] **Store/region employee roster** available from HR with role, tenure, and location data - [ ] **Communication platform admin access** confirmed — Slack, Teams, or email metadata export capability - [ ] **AI tool inventory** documented — list of current and planned AI tools with deployment timelines - [ ] **Executive sponsor** identified with authority over stores/regions in scope - [ ] **Minimum 30 employees per store/region** in scope for statistical significance on fear inventory ## Constraints - Anonymity is non-negotiable — fear inventory responses must be aggregated, never attributed to individuals. Violation destroys trust and invalidates all subsequent data. [src3] - ONA requires at least 4 weeks of communication metadata for reliable centrality measures. Less data = unreliable influence mapping. [src5] - Minimum sample size: 30 employees per store/region. Below this threshold, fear category distributions are not statistically meaningful. - Survey fatigue risk — combine fear inventory with existing employee engagement cadence where possible. [src4] - AI constraint boundary transparency audit requires access to the actual AI tools in use — demo environments are insufficient. ## Tool Selection Decision ``` Which path? ├── Client has Slack or Teams enterprise │ └── PATH A: Platform ONA — automated network extraction from metadata ├── Client has email only (no chat platform) │ └── PATH B: Email Metadata ONA — sender/receiver pairs from Exchange/Gmail ├── Client has no digital communication metadata │ └── PATH C: Survey-Based ONA — self-reported network mapping └── Client has mixed platforms across regions └── PATH D: Hybrid — combine available metadata with survey gap-fill ``` | Path | Tools | Cost | Speed | Network Quality | |------|-------|------|-------|----------------| | A: Platform ONA | Viva Insights or Slack export + NetworkX | $3K-$8K | 1-2 days | Excellent — automated, comprehensive | | B: Email Metadata | Exchange/Gmail metadata + NetworkX | $1K-$3K | 2-3 days | Good — limited to email interactions | | C: Survey-Based | Survey platform + manual network mapping | $0-$500 | 3-4 days | Adequate — self-report bias | | D: Hybrid | Mixed tools per region | $2K-$6K | 2-4 days | Good — uneven coverage | ## Execution Flow ### Step 1: Map Informal Influence Networks **Duration**: 1-2 days **Tool**: ONA tool (Viva Insights, Slack export + NetworkX, or survey-based) Extract communication metadata across stores/regions in scope. Build directed weighted graphs per location: nodes = employees, edges = communication frequency and direction. Calculate betweenness centrality (information brokers), degree centrality (social hubs), and eigenvector centrality (influence amplifiers). [src2, src5] Overlay formal org chart to identify formal-vs-informal gaps: - **Bridge nodes**: employees connecting otherwise disconnected groups - **Shadow leaders**: high informal influence, no formal authority - **Isolated clusters**: groups communicating only within themselves - **Bottleneck risks**: single points of failure in information flow **Verify**: Influence map validated — top 5 informal leaders identified per store/region. Formal-vs-informal gap report generated. **If failed**: If metadata coverage < 70% of employees, switch to survey-based ONA or extend data collection window. ### Step 2: Conduct Anonymous Rational Fear Inventory **Duration**: 1-2 days **Tool**: Survey platform + interview protocols Deploy anonymous survey categorizing employee fears about AI into five rational threat categories: [src1, src3] 1. **Identity threat** — "AI devalues my expertise/experience" (e.g., veteran merchandiser whose product knowledge becomes less valued) 2. **Autonomy threat** — "AI removes my decision-making authority" (e.g., store manager overridden by AI scheduling) 3. **Job security threat** — "AI will replace my role entirely" (e.g., cashier facing self-checkout expansion) 4. **Surveillance threat** — "AI monitors and judges my performance" (e.g., warehouse worker tracked by productivity AI) 5. **Hallucination/trust threat** — "AI gives wrong answers and I get blamed" (e.g., customer-facing associate using AI product recommender) Score each category 1-5 per respondent. Aggregate by store/region to produce heatmap. Supplement with 5-8 semi-structured interviews per store targeting employees with highest influence scores from Step 1. **Verify**: Survey response rate > 60% per store/region. All five fear categories scored. Heatmap generated. **If failed**: If response rate < 60%, extend survey window by 3 days, have executive sponsor send personal message, add interview-only option for non-respondents. ### Step 3: Score AI Tools on TAM Dimensions **Duration**: 0.5-1 day **Tool**: Structured assessment framework For each existing or planned AI tool, score on Technology Acceptance Model dimensions: [src1] - **Perceived Usefulness (PU)**: Does this tool make employees' jobs measurably easier or better? Score 1-5 based on fear inventory responses + interview data. - **Perceived Ease of Use (PEOU)**: Can employees learn this tool in < 30 minutes without support? Score 1-5 based on UI complexity assessment + training requirements. - **Behavioral Intention (BI)**: Would employees voluntarily use this tool if it were optional? Score 1-5 based on survey responses. Flag tools with PU < 3 or PEOU < 3 — these will face adoption resistance regardless of mandate strength. **Verify**: Every in-scope AI tool scored on all three TAM dimensions. Tools below threshold flagged. **If failed**: If tool access is unavailable for scoring, use demo + employee descriptions. Mark scores as "estimated" with lower confidence. ### Step 4: Audit AI Constraint Boundary Transparency **Duration**: 0.5-1 day **Tool**: Direct tool testing + employee interviews For each AI tool in scope, assess whether employees can see and test its limits: [src3, src4] - Can employees see what the AI can and cannot do? (documented limitations visible in UI) - Can employees test edge cases safely? (sandbox mode or low-stakes testing environment) - Are failure modes explained? (what happens when AI is wrong, who is responsible) - Is override capability clear? (can employees override AI decisions, and do they know how) Score each tool 1-5 on constraint transparency. Tools scoring < 3 create adoption anxiety because employees cannot form accurate mental models of AI capability boundaries. **Verify**: Constraint transparency score per tool documented. Recommendations for improving transparency drafted. **If failed**: If tool vendor restricts testing access, score based on documentation review + employee interviews about their experience. ### Step 5: Measure Hero/Star Dependency Concentration **Duration**: 0.5 day **Tool**: Network analysis output from Step 1 Using the influence network from Step 1, calculate hero dependency concentration: [src2, src5] - **Single-point-of-failure score**: What percentage of information flow passes through the top 3 individuals per store? - **Bus factor**: How many people would need to leave before a store/region loses critical operational knowledge? - **Knowledge concentration ratio**: Ratio of unique knowledge held by top 10% vs bottom 90% of employees. High hero dependency (top 3 handling > 40% of information flow) means AI adoption risks triggering organizational immune rejection — heroes perceive AI as threatening their irreplaceable status. **Verify**: Hero dependency scores calculated per store/region. High-concentration stores flagged. **If failed**: If network data is insufficient for reliable centrality, supplement with manager interviews about "who do people go to for answers." ### Step 6: Design Peer-Driven Adoption Pilot **Duration**: 0.5-1 day **Tool**: Pilot design document Using outputs from Steps 1-5, design a peer-driven adoption pilot: [src2, src4] 1. **Select adoption champions** from informal leaders identified in Step 1 (high eigenvector centrality + low fear scores from Step 2) 2. **Match champions to fear clusters** — assign champions to stores/regions where their influence network overlaps with high-fear groups 3. **Design champion training** — address top 2 fear categories per store using evidence from fear inventory 4. **Set pilot scope** — select 2-3 stores with moderate (not extreme) fear scores for initial rollout 5. **Define success metrics**: adoption rate at 30/60/90 days, fear score reduction on re-survey, champion NPS 6. **Build escalation path**: what happens when adoption champion encounters resistance they cannot resolve **Verify**: Pilot design document approved by executive sponsor. Champions identified and willing to participate. **If failed**: If no informal leaders have low fear scores (all influencers are fearful), redesign: address champion fears first in a pre-pilot workshop before asking them to champion. ## Output Schema ```json { "output_type": "adoption_psychology_assessment", "format": "PDF + JSON", "sections": [ {"name": "influence_network_map", "type": "object", "description": "Per-store/region graph with centrality scores and formal-informal gaps", "required": true}, {"name": "fear_inventory_report", "type": "object", "description": "Anonymized fear distribution across 5 categories with store-level heatmap", "required": true}, {"name": "tam_scorecard", "type": "array", "description": "TAM scores (PU, PEOU, BI) per AI tool", "required": true}, {"name": "constraint_transparency_audit", "type": "array", "description": "Transparency scores per AI tool with improvement recommendations", "required": true}, {"name": "hero_dependency_analysis", "type": "object", "description": "Concentration scores and bus factor per store/region", "required": true}, {"name": "adoption_pilot_design", "type": "object", "description": "Champion selection, pilot scope, success metrics, escalation path", "required": true} ], "expected_sections": "6", "sort_order": "execution sequence" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Survey response rate (per store) | > 60% | > 75% | > 90% | | Network data coverage (% of employees) | > 70% | > 85% | > 95% | | Fear categories with actionable data | 3 of 5 | 4 of 5 | 5 of 5 | | TAM tools scored | All existing tools | + planned tools | + competitor tools | | Champion identification rate | 1 per store | 2-3 per store | 3+ per store with backup | **If below minimum**: Extend data collection period by 3-5 days, add interview-based gap-fill for low-response stores, escalate through executive sponsor. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Survey response rate < 60% | Survey fatigue or distrust of anonymity | Executive sponsor endorsement, extend deadline, switch to interview-based collection | | Network analysis shows disconnected stores | No cross-store communication channels | Document as finding — isolated stores need different adoption strategy | | All informal leaders show high fear scores | Organization-wide anxiety about AI | Pre-pilot champion workshop to address fears before asking them to champion | | TAM scores uniformly low across all tools | Tools genuinely difficult to use or not useful | Flag as implementation problem, not adoption problem — escalate to product/vendor | | Hero dependency > 60% in a store | Extreme knowledge concentration | Recommend knowledge distribution program before AI rollout in that store | ## Cost Breakdown | Component | Focused (1-5 stores) | Standard (5-20 stores) | Enterprise (20+ stores) | |-----------|---------------------|----------------------|------------------------| | Network analysis setup | $2K-$3K | $3K-$5K | $5K-$8K | | Fear inventory deployment | $1K-$2K | $2K-$3K | $3K-$5K | | TAM scoring + transparency audit | $1K-$2K | $2K-$3K | $3K-$5K | | Hero dependency analysis | $0.5K-$1K | $1K-$2K | $2K-$3K | | Pilot design | $1K-$2K | $2K-$3K | $3K-$5K | | **Total engagement** | **$5.5K-$10K** | **$10K-$16K** | **$16K-$26K** | ## Anti-Patterns ### Wrong: Skipping the influence network and going straight to fear surveys Deploying fear inventory without understanding who influences whom. Result: you identify fears but have no mechanism to address them — no champions, no influence leverage, no adoption pathway. [src2] ### Correct: Map influence first, then survey Influence mapping must precede fear inventory because the network data determines champion selection, survey distribution strategy, and pilot store selection. ### Wrong: Attributing fear inventory responses to individuals Breaking anonymity to "help" fearful employees. Result: trust collapse — employees stop reporting honest fears, all subsequent data is contaminated, and organizational immune system activates against the assessment itself. [src3] ### Correct: Aggregate to store/region level only Present fear data only at store or region level. Use interview data (voluntary, with consent) for individual-level insights. ### Wrong: Ignoring hero dependency in adoption planning Rolling out AI in stores with extreme hero concentration without addressing dependency first. Result: heroes perceive AI as existential threat, actively sabotage adoption through their disproportionate influence. [src2, src5] ### Correct: Sequence hero dependency reduction before AI rollout In stores with hero dependency > 40%, run knowledge distribution program (documentation, cross-training) for 4-8 weeks before introducing AI tools. ## When This Matters Use when an agent needs to assess human readiness for AI adoption in a retail organization before implementation begins. This is Dimension 3 of a retail AI maturity assessment — it produces the adoption psychology inputs needed for the implementation roadmap recipe. Requires communication platform admin access and minimum 30 employees per store/region in scope. ## Related Units - [OIA Theory — Organizational Immune System](/consulting/oia/organizational-immune-system-theory/2026) - [Retail AI Implementation Roadmap](/consulting/recipes/retail-ai-implementation-roadmap/2026) - [OIA Network Analysis Execution](/consulting/recipes/oia-network-analysis-execution/2026) - [OIA Autoimmune Scan Execution](/consulting/recipes/oia-autoimmune-scan-execution/2026)