# The Failure Museum: A Guide to AI Limitations URL: https://research-memex.org/docs/implementation/core-references/failure-museum Description: An essential guide to common AI failure modes in academic research, with practical mitigation strategies for maintaining rigor and quality. *Understanding how AI fails is the precondition for trusting what it gets right.* This page about AI failures was written by an AI (Claude). Yes, I'm documenting my own failure modes. Yes, this is meta. Yes, some of these failures might disappear as models improve (or new ones might emerge). The epistemic situation gets trickier as AIs get better at hiding their limitations. But that's the point. Awareness of failure modes is how we maintain rigor. The mirror effect in action: Generic AI responses often reveal gaps in our structured thinking, not just the AI's limitations. The Failure Museum is a mirror that speaks to the mirror: failures are diagnostic tools. We use them to improve our research thinking, and we encourage you to do the same. Failure is data, not shame. Every failure mode documented here represents learning. We're sharing what we've discovered, and we expect you'll discover patterns we haven't yet encountered. ## Exhibit guide [#exhibit-guide] Jump to specific failure modes: Fake citations & false facts Missing methodological fit Smooth but shallow Decontextualized analysis Generic definitions Wrong research approach Misunderstood networks ## Failure detection process [#failure-detection-process] ```text title="diagram:failure-museum" AI output | v critical reading | v red-flag check | +----------------+----------------+ | | | v v v generic language missing sources too smooth | | | +----------------+----------------+ | v verification sources / logic / context | +---------+---------+ | | v v accept document failure | v revise prompt | +----> AI output ``` Copy-pasteable workflow! You can copy this ASCII diagram into any AI chat to explain your failure detection process. It works everywhere - terminals, code, plain text! The pattern: (1) AI generates output β†’ (2) Critical reading spots red flags β†’ (3) Verification checks β†’ (4) Prompt refinement. Spotting failures early saves time. ## Common failure modes [#common-failure-modes] ### The Failure [#the-failure] The AI generates a plausible-sounding citation that doesn't exist. It often combines a real author's name, a real journal, and a fitting but fake title. ### Example (Bad) [#example-bad] > "As Barney (1991) noted in his follow-up in *Strategic Management Journal*, the inimitability of resources also depends on the firm's dynamic capabilities framework integration." What's Wrong: While Barney did write about resource inimitability, there is no 1991 follow-up paper in SMJ with this exact focus. ### Prevention Strategies [#prevention-strategies] * Always verify every single citation with your Zotero library or Google Scholar * Check publication years and cross-reference with known works * Use specific prompts: "Provide exact page numbers and DOIs for all citations" * Ask AI to flag any citations it's uncertain about ### Detection Tips [#detection-tips] * Citations that sound "too perfect" for your argument * Dates that don't align with author's career timeline * Titles that use modern terminology for older papers ### The Failure [#the-failure-1] The AI interprets a paper from a critical or interpretive paradigm through a purely positivist lens, missing the epistemological nuance. ### Example (Bad) [#example-bad-1] > "The study found that the key variables influencing technology adoption were the network, the actors, and the technology itself..." What's Wrong: An Actor-Network Theory paper isn't about "variables" affecting "outcomes." It's about relational ontology and performativity. ### Prevention Strategies [#prevention-strategies-1] * Prime for paradigm awareness: "From an interpretive perspective, what are the key sensemaking processes..." * Ask explicitly about ontological and epistemological framing * Request clarification of the paper's theoretical tradition * Compare with papers from different paradigms ### Detection Tips [#detection-tips-1] * Statistical language applied to qualitative studies * "Variables" and "outcomes" used for interpretive work * Missing discussion of researcher reflexivity * Lack of attention to meaning-making processes ### The Failure [#the-failure-2] The AI synthesizes contradictory findings into a single, smooth paragraph that masks the underlying academic debate. ### Example (Bad) [#example-bad-2] > "Research shows that organizational slack is beneficial for innovation (Bourgeois, 1981), as it provides resources for experimentation..." What's Wrong: This presents a false consensus, smoothing over decades of complex debate about optimal slack levels, types of slack, and contingency factors. ### Prevention Strategies [#prevention-strategies-2] * Prompt for contradictions: "Where do these authors disagree with each other?" * Ask for tensions and boundary conditions explicitly * Request: "What debates exist in this literature?" * Demand synthesis of DISAGREEMENT, not just agreement ### Detection Tips [#detection-tips-2] * Suspiciously smooth narratives * Lack of "however" or "in contrast" statements * No mention of competing theories * Everyone seemingly agrees ### The Failure [#the-failure-3] The AI extracts a finding from its original context and presents it as a universal truth. The original context might be a study of large manufacturing firms in the 1980s. ### Example (Bad) [#example-bad-3] > "Research shows that organizational learning requires cross-functional teams." What's Wrong: Missing context: This finding was from software development firms in Silicon Valley, 2010-2015. It may not generalize to other industries, regions, or time periods. ### Prevention Strategies [#prevention-strategies-3] * Always ask for scope: "What is the context of this study (industry, firm size, geography, time period)?" * Probe generalizability: "Has this been replicated in other contexts?" * Request boundary conditions: "Where would this NOT apply?" * Check for contextual caveats in the original paper ### Detection Tips [#detection-tips-3] * Broad claims without qualifiers * Missing sample characteristics * No discussion of generalizability limits * Findings presented as universal laws ### The Failure [#the-failure-4] When you ask the AI to define a complex construct, it blends multiple definitions into one generic, often meaningless "average" definition. This definition satisfies no particular theoretical tradition. ### Example (Bad) [#example-bad-4] > "Organizational culture is the shared values, beliefs, and assumptions that guide behavior in organizations." What's Wrong: This bland definition obscures important theoretical distinctions between Schein's levels model, Martin's fragmentation perspective, and Hofstede's dimensions. ### Prevention Strategies [#prevention-strategies-4] * Ask for definitional variety: "How have different authors defined organizational culture? Present their definitions in a table." * Request theoretical grounding: "What are the competing conceptualizations?" * Probe assumptions: "What does each definition assume about culture's nature?" * Compare and contrast approaches explicitly ### Detection Tips [#detection-tips-4] * Definitions that sound like textbook boilerplate * No attribution to specific theorists * Missing theoretical tensions or debates * One-size-fits-all explanations ### The Failure [#the-failure-5] The AI suggests analytical approaches that don't match the paper's actual methodology or recommends methods incompatible with the epistemological stance. ### Example (Bad) [#example-bad-5] > "To test these findings, future research could use structural equation modeling to identify the causal relationships..." (In response to a grounded theory paper about sensemaking processes) What's Wrong: Suggesting a positivist quantitative method for extending an interpretivist qualitative study clashes with the original paradigm. ### Prevention Strategies [#prevention-strategies-5] * Ask about methodology alignment: "What methods would be consistent with this paper's approach?" * Verify paradigm consistency: "Would the original authors recommend this?" * Request epistemological grounding for suggestions * Compare methodological affordances and constraints ### Detection Tips [#detection-tips-5] * Quantitative methods suggested for interpretive studies * Positivist language (variables, causation) for constructivist work * Generalization emphasis for context-specific findings * Ignoring methodological limitations stated by authors ### The Failure [#the-failure-6] The AI incorrectly identifies who cited whom, misattributes ideas to the wrong authors, or confuses the intellectual genealogy of concepts. ### Example (Bad) [#example-bad-6] > "Porter introduced the concept of dynamic capabilities in his 1980 work on competitive strategy." What's Wrong: Teece, Pisano, and Shuen (1997) developed dynamic capabilities, not Porter. Porter (1980) focused on competitive forces. ### Prevention Strategies [#prevention-strategies-6] * Verify attribution: "Who originally developed this concept? Provide the exact citation." * Check intellectual genealogy: "Who built on this idea first?" * Request chronological accuracy: "What's the timeline of this concept's development?" * Cross-reference with your Zotero library ### Detection Tips [#detection-tips-6] * Anachronistic attributions (recent concepts to old papers) * Conflation of related but distinct concepts * Missing key contributors to a theoretical tradition * Simplified genealogies that skip important developments ## How to use this museum [#how-to-use-this-museum] ### Before each AI session [#before-each-ai-session] 1. Review 2-3 failure modes most relevant to your current task. 2. Prepare specific [mitigation prompts](/docs/implementation/core-references/cognitive-blueprint-prompts). 3. Set up verification protocols (e.g., which databases will you use to check citations?). ### During AI interactions [#during-ai-interactions] 1. Stay skeptical: question everything that sounds "too smooth" or perfectly coherent. 2. Demand specificity: ask for page numbers, exact quotes, and DOIs. 3. Prompt for contradictions: where do the source materials disagree, even if they agree on the main point? 4. Check for paradigm consistency: does the AI's interpretation match the source's methodology, epistemology, and theoretical tradition? ### After AI analysis [#after-ai-analysis] 1. Spot-check citations: always verify a sample of all references provided. 2. Cross-check claims against the original sources. 3. Look for missing nuance: what debates, tensions, or paradoxes did the AI smooth over? 4. Verify context: do the findings generalize beyond their original scope? What are the boundary conditions? Are there any tensions around the underlying epistemology or ontology that the AI smoothed over? ## Advanced failure patterns [#advanced-failure-patterns] ### The echo chamber effect [#the-echo-chamber-effect] AI may amplify your existing biases by finding sources that confirm your preconceptions while missing contradictory evidence. ### The recency bias [#the-recency-bias] AI may overweight recent papers while missing foundational works that establish core concepts. ### The language model bias [#the-language-model-bias] AI trained primarily on English-language sources may miss important non-English research traditions. ## AI as a research partner, not an oracle [#ai-as-a-research-partner-not-an-oracle] The goal isn't to avoid AI because it fails. It's to understand how it fails so you can: * [Design better prompts](/docs/implementation/core-references/cognitive-blueprint-prompts) that minimize failure modes. * Create verification protocols that catch errors before they propagate. * Maintain critical distance from AI-generated outputs. * Combine AI efficiency with human judgment for rigorous research. Working with AI doesn't diminish your expertise as a researcher. Skillful, critical engagement can strengthen it. ## Verification Protocol [#verification-protocol] **Quick scan for obvious issues:** * Generic language or vague assertions * Missing citations or suspicious dates * Implausibly perfect coherence * Grammatical errors or awkward phrasing * **Time:** 2-3 minutes * **Pass rate:** Catches \~40% of problems **Cross-reference all sources:** * Check each citation in Google Scholar or Zotero * Verify authors, years, and titles match * Confirm page numbers align with claims * Look up DOIs and ensure papers exist * **Time:** 10-15 minutes * **Pass rate:** Catches \~80% of problems **Deep analytical review:** * Trace arguments for logical consistency * Check for paradigm alignment * Verify contextual appropriateness * Compare with your own reading of sources * Test for alternative interpretations * **Time:** 20-30 minutes * **Pass rate:** Catches \~95% of problems **Final quality gate:** * Consult with advisor or peer * Present to research group * Compare with published standards * Seek critical feedback * Iterate based on expert input * **Time:** Variable * **Pass rate:** Publication-ready quality **Never skip verification:** Any time gained while working with AI is lost if you publish flawed work. Build verification into your workflow from the start. ## Related Resources [#related-resources] Complete tool installation and configuration Prompt templates and model guides Learn from common AI limitations llms.txt and Markdown access for AI tools