Research paper
Adaptive Diagnostic Methodology: Question-Led Context Extraction for Organizational Problem-Solving
Preprint, submitted to arXiv (cs.AI / cs.HC). Not yet peer reviewed.
Abstract
Practitioners in consulting, technology implementation, and organizational problem-solving routinely arrive at engagements with pre-formed solutions. This pattern of prescribing before diagnosing produces recommendations shaped by assumption rather than reality, a condition we term epistemic overreach. This paper introduces Adaptive Diagnostic Methodology (ADM™), a formal question-led framework for extracting organizational context prior to any prescription. ADM operates on the premise that question quality is the upstream variable of solution quality: the accuracy of any recommendation is bounded by the accuracy of the context feeding it. The methodology defines a six-phase cycle (Inquiry, Extraction, Synthesis, Validation, Prescription, Adaptation), a six-category Question Taxonomy that guides practitioners from surface symptoms to quantified root conditions, and a graduated completeness standard that defines when a diagnostic record is sufficient to support prescription. ADM's Synthesis and Validation phases produce structured context outputs designed to feed directly into AI implementation pipelines, bridging organizational reality and AI-assisted execution. Because ADM is defined by a structural condition rather than an industry, its applications span organizational diagnostics, technology scoping, messaging, employee onboarding, and sales conversations, wherever a workflow prescribes to a person or organization from assumed rather than extracted context. Limitations, including respondent fatigue and the current absence of controlled outcome evidence, and the conditions under which ADM is inappropriate, are addressed.
1. Introduction
There is a pattern in professional services that rarely gets named but almost everyone has experienced. A consultant, vendor, or internal specialist arrives with a solution already in hand. The initial meetings are nominally about understanding the client's situation, but the questions asked are shaped by the answer that is coming. By the time a recommendation appears, it bears a suspicious resemblance to the practitioner's existing product, framework, or specialty. The diagnosis was never really a diagnosis. It was a sales process.
This is not cynicism. It is a structural problem. Practitioners build expertise by solving categories of problems, and that expertise creates a cognitive prior: the situations they encounter look like the situations they have seen before. [Kahneman, 2011] describes the human tendency to substitute fast, pattern-matched judgments for slower, effortful analysis: System 1 thinking masquerading as deliberate reasoning. In professional services, this manifests as a predisposition to map new problems onto familiar solution templates. The result is recommendations that are technically competent but contextually misaligned.
The downstream costs are predictable. Implementations fail to account for constraints that were never surfaced. Solutions address symptoms rather than root causes. Organizations invest in change that does not hold because the change was designed around assumed needs rather than actual ones. The practitioner moves to the next engagement; the client is left managing the consequences.
This paper proposes Adaptive Diagnostic Methodology (ADM™) as a formal alternative. ADM inverts the typical consulting sequence: questions precede answers, context is extracted rather than assumed, and the prescription is held in suspension until the diagnostic work is complete. The core thesis is direct: every good answer is found at the end of a great question. Solution quality cannot exceed question quality, because questions are how context enters the process.
ADM does not operate in isolation. Organizations are increasingly deploying AI systems to assist with decision-making, content generation, project management, and analysis. These systems are only as useful as the context they receive. ADM addresses this directly: the structured outputs produced by the Synthesis and Validation phases are designed to feed AI systems with validated organizational context, bridging the diagnostic process and AI-assisted execution.
The paper proceeds as follows. Section 2 situates ADM within related work across consulting theory, organizational inquiry, and context engineering. Section 3 defines ADM's design principles, Question Taxonomy, and the six-phase cycle. Section 4 works through five application domains and the conditions under which ADM does not hold. Section 5 discusses scope conditions, limitations, and implications for AI-augmented organizations. Section 6 identifies future directions, and Section 7 concludes.
2. Background and Related Work
2.1 Diagnostic vs. Prescriptive Paradigms
The tension between diagnostic and prescriptive approaches runs through the history of management consulting. The dominant commercial model (what might be called the expert model) positions the practitioner as a specialist who arrives with superior knowledge and delivers recommendations based on pattern recognition from prior engagements. This model has real value when problems are well-specified and the solution domain is bounded. It performs poorly when the problem itself is unclear, contested, or embedded in organizational dynamics that are not visible to an outside observer.
Edgar Schein identified this limitation in his foundational work on process consultation [Schein, 1969]. Schein argued that the expert model assumes the client can accurately diagnose their own problem and communicate it clearly. In practice, neither assumption reliably holds. Problems presented by clients are often symptoms of deeper systemic conditions; clients frequently do not know what they do not know. Schein proposed that the consultant's primary function is not to deliver answers but to help the client develop their own diagnostic capacity: a relational, iterative process rather than a transactional one.
Lean manufacturing traditions offer a parallel diagnostic discipline. The Toyota Production System's A3 methodology and the broader PDCA (Plan-Do-Check-Act) cycle attributed to Deming [Deming, 1986] both require thorough problem definition before any corrective action is designed. The A3 format explicitly allocates a fixed portion of the analysis to "current condition" before the practitioner reaches "countermeasures." The sequence is not incidental; it is the methodology. Womack and Jones [1996] document how organizations that skip diagnostic rigor in lean implementations routinely optimize the wrong processes and achieve efficiency in areas that were never the constraint.
The medical profession offers perhaps the most formalized version of this principle. Evidence-based medicine's PICO framework (Population, Intervention, Comparison, Outcome) structures clinical questions before any evidence search begins [Richardson et al., 1995]. PICO was developed specifically because physicians operating on pattern recognition alone selected treatments without adequate problem framing. The framework does not generate answers; it generates precise questions, and those questions determine which evidence is relevant. A clinician who skips PICO-style framing is performing the medical equivalent of epistemic overreach: generating a treatment plan from assumed diagnosis rather than from structured inquiry. The underlying standard is stated bluntly in a maxim with no single citable origin but wide currency in both medicine and consultative selling, which this paper adopts for knowledge work: prescription without diagnosis is malpractice. Khalsa and Illig formalize the same principle for client engagements as "diagnose before you prescribe" [Khalsa & Illig, 2008]. No patient expects a physician to write a prescription before the examination, and no profession that takes its outcomes seriously should expect otherwise of itself.
What these traditions share is a structural commitment: diagnosis precedes prescription, and diagnosis requires a method. ADM formalizes this commitment for knowledge-work contexts (consulting, technology implementation, and organizational problem-solving) where the A3, PDCA, and PICO frameworks were not designed to apply directly.
2.2 The Socratic Method and Organizational Inquiry
The philosophical foundation for question-led knowledge extraction is ancient, but its organizational applications are more recent. The Socratic method, systematic questioning to expose assumptions, test beliefs, and arrive at more reliable conclusions, translates directly to diagnostic practice. The practitioner who asks "why does this problem exist?" and then follows the answer with "what produced that condition?" is performing a variant of Socratic inquiry adapted for organizational contexts.
Cooperrider and Srivastva's Appreciative Inquiry (AI) [1987] represents one influential organizational adaptation. AI reframes the diagnostic question from "what is broken?" to "what is working, and what conditions produced it?" The methodological insight, that the questions an organization asks determine the future it constructs, anticipates ADM's central claim. How practitioners frame their inquiries shapes what becomes visible and what remains hidden.
Peter Senge's work on organizational learning provides additional grounding [Senge, 1990]. His concept of mental models (the tacit assumptions and generalizations that shape how members of an organization see the world) describes precisely the mechanism through which epistemic overreach operates. Practitioners arrive with mental models formed by prior experience. Without an explicit diagnostic process, those models filter out disconfirming information. Senge's prescription, surfacing and testing mental models through structured dialogue, is a direct precursor to ADM's Inquiry and Extraction phases.
Where these traditions differ from ADM is in scope and specificity. Appreciative Inquiry was designed for organizational transformation; its question categories are broad and forward-looking. Senge's framework is primarily descriptive. ADM is designed for the narrower, more common situation of a practitioner engaging with an organization or individual to identify a problem and design a solution. It requires actionable question categories, a defined phase sequence, and explicit integration with modern AI implementation pipelines.
2.3 Context Engineering and AI Integration
The emergence of large language models as organizational tools has introduced a new dimension to the diagnostic problem. AI systems do not have access to organizational reality. They receive what they are given. If the context provided to an AI assistant is shaped by assumption rather than by accurate diagnosis, the AI's output inherits that distortion. Inaccurate inputs produce confidently articulated outputs that are misaligned with the organization's actual situation.
The framing of context engineering, the practice of deliberately constructing the information environment in which an AI system operates, was proposed by Tobi Lütke and popularized by Andrej Karpathy in mid-2025 [Lütke, 2025; Karpathy, 2025]. Karpathy describes it as the art and science of filling the context window with just the right information for the next step. The quality of AI output is not solely a function of model capability; it is a function of context quality. This observation reframes the organizational AI implementation problem: the upstream question is not "what model should we use?" but "what context are we feeding it, and is that context accurate?"
Van Clief and McDermott's Interpretable Context Methodology (ICM) [2026] addresses the structural side of this question. ICM defines a folder-based architecture for organizing organizational context in a form that AI agents can navigate and interpret. It treats the context container itself as a design artifact: not just storage, but a structured representation of organizational knowledge that shapes agent behavior. ICM provides a rigorous answer to how context should be organized.
What ICM does not address, by design, is how context should be extracted in the first place. ICM assumes that accurate context exists and defines how to structure and transmit it. ADM addresses the prior question: how does a practitioner extract accurate context from an organization where that context is often implicit, contested, or obscured by assumption? Extraction precedes structure; without accurate inputs, no context architecture can produce reliable AI output.
Kahneman's framework [2011] provides the cognitive grounding for why explicit extraction protocols are necessary. System 1 thinking (fast, associative, pattern-matched) dominates under conditions of time pressure and expertise. Experienced practitioners are especially susceptible to this because their expertise makes fast pattern-matching feel reliable. ADM is a System 2 intervention: it slows the diagnostic process down, requires explicit question formulation, and forces engagement with the specific context of the current situation before any pattern-matching is applied.
This grounding requires an immediate qualification, because fast pattern-matching is not always unreliable, and a methodology that ignored this would overclaim. Kahneman and Klein [2009], reconciling two research traditions that had reached opposite conclusions, agree that intuitive expertise is trustworthy only in high-validity environments: settings that provide regular, reasonably rapid, and unambiguous feedback, such as firefighting, chess, or anesthesiology. Where feedback is delayed, sparse, or confounded by uncontrolled factors, the same intuition that serves an expert well elsewhere has no reliable basis on which to have formed. Most settings ADM addresses are low-validity in exactly this sense: outcomes arrive weeks or months later and are shaped by many variables, so a diagnosis is rarely followed by a clean signal that it was right or wrong. ADM therefore does not claim that structured inquiry outperforms expert intuition in general. It claims the narrower position that in low-validity environments, where intuition lacks the feedback conditions that would make it dependable, deliberate extraction of context is the safer default. In high-validity environments the diagnostic latency ADM introduces may not be worth its cost, a boundary Section 5.2 returns to.
2.4 Problem Framing and the Ceiling on Solutions
ADM's central thesis, that solution quality is bounded by question quality, has a foundation in the literature on problem framing and problem construction. Schön [1983] distinguishes problem setting from problem solving and argues that professionals rarely encounter well-formed problems; they face indeterminate situations and must first name what they will treat as the problem and frame the context in which they attend to it. Rittel and Webber [1973], introducing the idea of wicked problems, put the point more sharply: for such problems there is no definitive formulation, and understanding the problem is bound up with the idea one has for solving it, so the formulation of the problem is, in effect, the problem. If framing determines the solution space, then the questions that produce the framing set an upper bound on the quality of any solution that follows.
Empirical work on problem construction supports the same direction. In studies of creative performance, the degree to which a person actively explores and constructs the problem before committing to a solution predicts the rated quality and originality of the result [Getzels & Csikszentmihalyi, 1976; Mumford, Reiter-Palmon & Redmond, 1994; Reiter-Palmon & Robinson, 2009]. Separately, self-generated elaboration, prompting someone to answer why a claim holds rather than handing them the explanation, deepens processing of the material, with the important boundary that the benefit rises with the responder's prior knowledge and can reverse when a low-knowledge responder generates a wrong explanation [Pressley et al., 1987; Dunlosky et al., 2013]. That boundary is itself an argument for ADM's structure rather than against it: the practitioner supplies domain knowledge while the questions extract the situational context the practitioner lacks, which is the combination the elaboration literature finds most productive.
The defensible form of the thesis follows from this evidence. Question quality is a necessary constraint on solution quality, not a sufficient cause of a good solution. The evidence that this holds in general, rather than only in creative-task laboratories, is not settled, and reviews of behavioral interventions at scale find effects considerably smaller than laboratory work implies [DellaVigna & Linos, 2022]. ADM's claim is bounded accordingly: better questions raise the ceiling on the answer; they do not guarantee the answer reaches it.
2.5 Adjacent Question-Led Methods
Several established methods already couple structured questioning to professional work, and ADM's novelty claim must be stated against them rather than around them. SPIN Selling [Rackham, 1988], derived empirically from analysis of roughly 35,000 sales calls, sequences Situation, Problem, Implication, and Need-payoff questions and is the closest existing taxonomy to ADM's. The difference is terminal, not superficial: SPIN's questions are engineered to advance a buyer toward the seller's solution, culminating in questions that lead the buyer to voice the payoff of a predetermined product, whereas ADM extracts the situation regardless of what solution, if any, follows, and has no analogue to the Need-payoff move. Jobs-to-be-Done [Christensen et al., 2016] and behavior-first interviewing [Fitzpatrick, 2013] scope customer discovery for a product decision; contextual inquiry [Beyer & Holtzblatt, 1998] extracts user context to inform a design; and the Question Formulation Technique [Rothstein & Santana, 2011] proves, in an education setting, that question generation itself can be turned into a repeatable procedure. Each is either locked to a domain (a sale, a product, an interface, a classroom) or describes extraction without prescribing it as a gated precondition to action.
ADM's contribution is therefore not the diagnose-before-prescribe ethos, which these methods and the consulting canon already embody, but the specific combination of three properties none of them holds together: a portable question taxonomy that is not tied to a single outcome, phase gates that make extraction a precondition to prescription rather than a norm a skilled practitioner may skip, and outputs structured for direct consumption by AI systems. The last property is absent from every prior method above, because all of them predate the use of large language models as the downstream executor of the diagnosis.
3. Adaptive Diagnostic Methodology
3.1 Design Principles
ADM rests on six foundational principles. These are not aspirational values; they are operational constraints that distinguish ADM-compliant practice from conventional consulting behavior.
Principle 1: Diagnose before prescribing. No recommendation is formed before the diagnostic cycle is complete. This is the anti-pattern to the expert model. Practitioners who feel a solution forming during the early inquiry phases should note it privately and return to questioning. The solution may be correct; what changes is when it is introduced.
Principle 2: Questions precede solutions. This is a sequencing rule, not just a philosophical position. In practice, it means that the first deliverable of any ADM engagement is a question set, not a proposal. The question set is reviewed, refined, and executed before the practitioner synthesizes any recommendations.
Principle 3: Context is not assumed; it is extracted. The practitioner's prior experience is a hypothesis-generation tool, not a substitute for organizational inquiry. What worked elsewhere is a starting point for questions, not a template for answers.
Principle 4: Adaptability is built into the cycle, not appended. Priorities shift. New information changes the problem definition. ADM includes a dedicated Adaptation phase at the end of each cycle, which feeds back into the next Inquiry phase. This is not a correction mechanism for when things go wrong; it is a standard component of every cycle.
Principle 5: Reality over perception. Organizations present themselves as they believe themselves to be, which is not always how they are. ADM question categories are designed to surface disconfirming evidence: constraints that have not been articulated, priorities that conflict with stated ones, patterns that persist despite intervention. The methodology treats epistemic overreach as an adversarial condition to be actively countered.
Principle 6: Practitioner neutrality in the diagnostic phase. During Inquiry and Extraction, the practitioner does not share opinions, signal preferred solutions, or affirm client assumptions. The goal is to hear what is actually true, not to confirm what the client believes is expected. Neutrality is lifted during Synthesis and Prescription.
3.2 Question Taxonomy
ADM organizes diagnostic questions into six categories. Each category serves a distinct epistemic function. Practitioners use all six categories across an engagement, with the relative weight of each shifting by phase.
| Question Type | Purpose | Example |
|---|---|---|
| Context Questions | Establish the current state without normative framing | "Walk me through what a typical week looks like for this team." |
| Root Questions | Identify the generative conditions behind observed problems | "How long has this been happening, and what changed around that time?" |
| Constraint Questions | Map the boundaries of the solution space before designing within it | "What has already been tried, and why didn't it hold?" |
| Magnitude Questions | Quantify the size, frequency, and cost of the problem, including the cost of leaving it unaddressed | "How often does this happen in a month, and what does each occurrence cost in hours or dollars?" |
| Priority Questions | Surface what actually matters rather than what is nominally important | "If you could only fix one thing in the next 90 days, what would it be?" |
| Validation Questions | Establish criteria for knowing whether the right problem was solved | "What would success look like in a way that would be hard to argue with?" |
Context Questions are the entry point for most engagements. They are deliberately open and descriptive, designed to allow the client to tell their story without the practitioner imposing a frame. Root Questions follow once the surface narrative is established; they push below symptoms toward causes. Constraint Questions are critical and often overlooked; many implementations fail not because the solution was wrong but because the constraint map was incomplete. Priority Questions expose the gap between stated priorities and actual ones, which is frequently where the most important diagnostic information lives. Validation Questions close the diagnostic loop by defining success criteria before the prescription is written, which prevents the common failure mode of delivering a solution that was never tested against a clear standard.
Magnitude Questions convert the narrative into measurement. A diagnosis without numbers is an opinion: the practitioner who knows that invoicing is painful but not how many invoices, how many hours, or how many errors per month cannot rank that problem against any other. Magnitude Questions attach time, frequency, volume, cost, and failure rate to the problems the other categories surface, and they extend to stakes: what the condition costs now and what it will cost if it is never addressed. Two disciplines govern the category. First, best-effort estimates are acceptable and expected; a prospect rarely has exact figures at hand, and stalling the diagnostic session to chase precision defeats its purpose. Estimates are recorded as estimates and flagged for verification. Second, the inability to estimate is itself diagnostic data. An organization that cannot approximate its own cycle time, error rate, or cost per incident has just revealed a measurement gap, and that gap frequently sits closer to the root condition than the symptom that opened the conversation.
3.3 The ADM Cycle
ADM operates as a six-phase cycle. Each phase has defined inputs, a process, and an output that feeds the next phase. The cycle is designed to be iterable; the Adaptation phase does not close the process but resets it with updated context.
| Phase | Input | Process | Output |
|---|---|---|---|
| 1. Inquiry | Engagement scope, practitioner hypotheses | Develop question set across all six taxonomy categories; sequence for the diagnostic session | Structured question set, ordered by category and dependency |
| 2. Extraction | Question set, access to organizational stakeholders | Execute diagnostic sessions; document responses verbatim before interpretation; run the gap-detection loop against completeness criteria | Raw context record: unfiltered, unedited organizational input, with explicit gap register |
| 3. Synthesis | Raw context record | Identify patterns, contradictions, and gaps; map stated problems to Root and Constraint findings; rank problem candidates by extracted Magnitude data | Diagnostic summary with problem candidates ranked by measured impact, with confidence levels |
| 4. Validation | Diagnostic summary | Return findings to stakeholders for accuracy confirmation; surface any corrections or additions | Validated problem statement, agreed upon by practitioner and client |
| 5. Prescription | Validated problem statement, constraint map | Design solution within confirmed constraints; sequence implementation against stated priorities | Recommendation document with implementation sequence and success criteria |
| 6. Adaptation | Implementation results, new organizational inputs | Compare outcomes to Validation criteria; identify what changed; reset Inquiry scope for next cycle | Updated context record, refined question set for next cycle |
Several aspects of this cycle warrant elaboration.
The Extraction phase uses verbatim documentation as a discipline. Practitioners who paraphrase in real time introduce their own interpretation before the raw record is complete. ADM requires that the first pass of documentation captures what was said, not what the practitioner understood it to mean. Interpretation happens in Synthesis, not before.
The Validation phase is the most frequently skipped in practice and the most important. Returning to stakeholders with a summary of what the practitioner heard, before writing any recommendations, catches misinterpretations early. It also shifts the locus of problem ownership: when the client confirms the problem statement, they are more likely to engage authentically with the solution.
The distinction between Prescription and Adaptation is intentional. Many consulting frameworks treat adaptation as error recovery: something that happens when a recommendation does not work. In ADM, Adaptation is a standard phase that follows every implementation cycle regardless of outcome. Success changes the organization's situation; changing situations produce new contexts; new contexts require new inquiry.
3.4 Diagnostic Completeness: A Phased Definition of Done
A diagnostic methodology that cannot say when the diagnosis is finished is a checklist, not a method. Without a completion standard, practitioners face two symmetric failure modes: stopping too early, which reintroduces the assumption-filling the methodology exists to prevent, and never stopping, which converts diagnostic rigor into diagnostic paralysis. ADM resolves this with a phased definition of done: three completeness levels, each a defined end point that produces a usable artifact and gates entry to a later phase of the cycle.
Level 1: Narrative completeness. Every taxonomy category holds at least a first-pass response, captured in the client's own words. No category is empty, and the client's account of the situation could be read back to them without objection. Level 1 is the minimum standard for closing an initial diagnostic session, and its artifact, a structured problem narrative, is sufficient to decide whether the engagement should proceed at all.
Level 2: Measured completeness. The leading problem candidates carry Magnitude data: time, frequency, volume, cost, and failure rate, with estimates flagged as estimates. Prior attempts are documented with an account of why each did not hold. Priorities are forced-ranked rather than listed. Level 2 is the standard for closing Extraction and gates entry to Synthesis, because ranking problem candidates requires numbers to rank them by. Its artifact is a quantified diagnostic record.
Level 3: Validated completeness. The client has confirmed or corrected the diagnostic summary. Success criteria are stated in falsifiable terms. Every remaining unknown is recorded as an explicit gap rather than silently absorbed into the synthesis. Level 3 is the standard for closing Validation and is the sole gate to Prescription: no recommendation is written against a record below Level 3.
Within each level, a taxonomy category is satisfied when four criteria hold: the responses describe specific instances rather than generalities; whatever can be quantified has been, at least by estimate; at least one follow-up question has probed for disconfirming evidence rather than confirmation; and anything still unknown is written into the gap register as a gap. These criteria drive the gap-detection loop that operates throughout Extraction: after each response, the practitioner compares the record against the criteria for the active category, and each unsatisfied criterion generates the next question. A category closes when its criteria are met or when the client genuinely cannot answer, and inability to answer is documented as diagnostic data in its own right, since what an organization cannot say about itself is often more informative than what it can.
The gap-detection loop is what distinguishes an adaptive diagnostic from a scripted intake form. A form asks a fixed set of questions and accepts whatever comes back. The loop asks whatever the completeness criteria demand next, which means the depth of inquiry scales with the ambiguity of the situation rather than with the length of a script. It also gives the phased levels their climbing structure: each level is an end point the practitioner can stand on, ship an artifact from, and ascend from, rather than a single undifferentiated mass of discovery that is finished only when time runs out.
3.5 ADM Outputs and AI-Ready Context
The outputs of the ADM cycle are not incidental byproducts of the diagnostic process. Each phase produces a specific type of structured content that corresponds to a distinct class of context that AI systems require to operate accurately. Organizations deploying AI for knowledge work need all six of these context types present and verified before any AI output is trustworthy.
| ADM Phase Output | Context Type Produced |
|---|---|
| Context Question responses | Current-state and organizational identity |
| Root Question responses | Historical patterns and causal context |
| Constraint Question responses | Operational constraints and prior attempts |
| Magnitude Question responses | Quantified baselines, impact data, and cost of inaction |
| Priority Question responses | Objectives and decision-weight context |
| Validated problem statement | Success definition and evaluation criteria |
This structure means that an organization executing ADM correctly does not need a separate exercise to create AI context. The diagnostic process, completed with discipline, produces validated, categorized organizational context as a direct output. That material is ready for use in any machine-readable context architecture without additional translation.
The implication is significant. AI systems fed context produced by ADM are operating on organizational input that has been checked with stakeholders rather than assumed. AI systems fed context assembled without a diagnostic process are operating on whatever the organization believes to be true about itself, which may or may not match its actual situation. To the extent output quality depends on the accuracy of the input, it depends on what the AI system received, not on the model alone.
4. Applications
The applications below are illustrative rather than exhaustive. ADM is defined by a structural condition, not by an industry: it applies wherever a workflow begins from assumptions about a person or organization whose actual context could instead be extracted by asking. Consulting is where the pattern is most visible, and where the method has been applied most and shown its clearest results to date, but the same mechanism governs technology scoping, messaging, onboarding, and sales conversations alike, each of which routinely prescribes something (a system, a message, a first-week experience, a pitch) from an assumed model of the person on the other side. Substitute the diagnostic subject and the six phases hold: a client, a new hire, a prospect, and a target customer are each a context to be extracted before anything is prescribed to them. The cases below are chosen because they make the mechanism legible, not because they bound it.
4.1 Organizational Diagnostic
Consider a professional services firm engaging a business consultant to address declining client retention. The prescriptive approach would have the consultant audit the firm's onboarding process, compare it to industry benchmarks, and recommend improvements. This is not necessarily wrong, but it assumes the problem is onboarding, an assumption that may not survive a rigorous diagnostic.
An ADM engagement begins differently. Context Questions establish the full picture: which clients are leaving, at what point in the relationship, and what the exit communications say. Root Questions probe deeper: when did the retention decline begin, what else changed at that time, what do long-retained clients say about their experience versus the ones who left? Constraint Questions map the organizational limits: what has already been tried, what is the capacity for change across different teams, what are the resource constraints on any solution?
In a real scenario, this process might reveal that the retention problem correlates more strongly with a change in account management staffing than with onboarding practices. The diagnostic would have redirected the engagement entirely. Without ADM, the consultant might have delivered a technically sound onboarding improvement that had no effect on the actual problem.
4.2 Technology Implementation
Software implementations depend heavily on the quality of their requirements work: field research finds that requirements engineering practices are a clear contributor to project success [Hofmann & Lehner, 2001], and defects traced to the requirements phase are among the most expensive to correct, with post-delivery fixes costing up to one hundred times more than fixes made during requirements and design [Boehm & Basili, 2001]. A system built to solve a problem that was not the actual constraint is the most expensive requirements defect of all. ADM applied at the scoping stage of a technology project reframes the initial engagement from requirements gathering (which assumes the problem is known) to context extraction (which does not).
The Question Taxonomy is particularly valuable here. Constraint Questions surface technical, organizational, and political constraints that are rarely volunteered but are frequently decisive. A company may request an AI-assisted customer communication tool, but a Constraint Question session might reveal that the real bottleneck is response time on complex inquiries, which requires a different architecture than a general communication assistant. Priority Questions distinguish between the features that matter to the person approving the budget and the features that matter to the people doing the work, which are often different sets.
The output of ADM's Extraction and Synthesis phases in a technology context produces a validated scope document: not a requirements list, but a structured account of the actual problem, the constraint map, and the success criteria. This document is a structured context package that feeds directly into the AI development environment.
4.3 Marketing and Messaging Strategy
Marketing practitioners face a version of the assumption problem that is structurally identical to consulting: practitioners write copy and design campaigns based on what they believe the audience wants to hear, which is often based on what similar audiences wanted in other contexts. The specific customer's actual decision-making process, actual objections, and actual language are frequently never directly investigated.
ADM applied to messaging strategy treats the target customer as an organizational context to be extracted. Context Questions establish how customers currently talk about the problem the product solves. The goal is to capture their actual language, not the terminology the company prefers. Root Questions probe the conditions under which customers experience the problem acutely, which determines timing and placement. Priority Questions identify which customer concerns are genuinely decision-determinative versus which are raised but not actually blocking.
The resulting diagnostic output is a customer-context document that precedes any creative work, and its value is structural rather than promissory. A message is recognized by a customer when it uses the language the customer already uses for the problem, and extracted context captures that language directly instead of substituting the terminology the company prefers. Messaging built on assumed context may still land, but it does so without knowing which words the customer was waiting to hear.
A second structural property is worth naming, because it is where diagnosis and commercial value meet. A completed diagnostic record surfaces more distinct, addressable problems than a narrow intake does, and it does so by construction: questioning across all six taxonomy categories, at increasing depth, exposes conditions that a single presenting complaint would never reveal. Each surfaced condition is a candidate that some solution could address. This is not a claim that the methodology sells more work; it is a claim about what a fuller record contains. A practitioner who extracts the whole picture is holding more true statements about the client's situation, and some of those statements describe problems the client did not open with. Whether any of them becomes follow-on work is a separate question the methodology does not settle.
A third property carries the diagnostic record into the message itself, where a question stops being a tool for hearing an answer and becomes a tool for holding attention. A prospect who reads a question that names their exact situation, "Still stitching your scheduling tool to your payment system by hand at month end?", is prompted to answer it internally, which draws them into the problem before any solution is offered. Two mechanisms in the persuasion literature account for this. A question makes a specific gap between what the reader knows and what they want resolved salient, and an open gap motivates its own closure [Loewenstein, 1994]. And a question posed about the reader's own circumstances induces self-referencing, which deepens engagement with whatever follows [Burnkrant & Unnava, 1995]. This device is downstream of ADM, not part of it: the hook only lands when it is built from language the diagnostic actually surfaced, because a question the reader recognizes as their own opens a real gap, whereas a generic question opens none.
The effect is real but conditional, and the paper claims no more than the mechanism. The same research shows the device reversing when it is overused or when its persuasive intent becomes obvious, at which point attention shifts from the problem to the persuader and the question backfires [Petty, Cacioppo & Heesacker, 1981; Ahluwalia & Burnkrant, 2004]. The related question-behavior effect, in which merely asking someone about an intention shifts their later behavior, is on average small and, notably, turns negative in face-to-face settings even as it holds in anonymous one-to-many channels [Spangenberg et al., 2016]. That contrast marks the boundary: the question-as-hook belongs in broadcast copy, not in the live diagnostic interview, where the same phrasing can read as manipulation. ADM's role here is upstream, supplying the extracted, validated language that determines whether a hook addresses a gap the reader actually holds, which is the condition under which the mechanism works at all.
4.4 Employee Onboarding
Onboarding is a diagnostic problem that is rarely treated as one. The organization prescribes a first-week experience, a training sequence, and a set of introductions built on an assumed model of what the new hire needs, while the new hire reconstructs the role, the norms, and the informal system by observation and scattered questions. The socialization literature has long described entry as a two-way information problem: newcomers actively seek technical, referent, normative, performance-feedback, and social information [Morrison, 1993], using tactics from overt questions to quiet monitoring [Miller & Jablin, 1991], and organizations that attend to compliance, clarification, culture, and connection onboard more successfully [Bauer, 2010]. What this literature describes but does not proceduralize is the extraction itself. ADM applied to onboarding treats the incoming hire as a context to be extracted before the plan is written: Context and Root Questions surface what the person already knows and how they work, Constraint Questions surface what would block them, and Priority Questions establish what a successful first ninety days would contain from their vantage rather than the manager's. The output is a per-hire context record that the same downstream systems consuming any ADM output can act on.
4.5 Sales Scripting
A sales script is a prescription issued before the diagnosis, which is the pattern ADM inverts. Scripts written from an assumed model of the prospect ask questions engineered to steer toward a known offer, the move SPIN [Rackham, 1988] formalizes and the one Section 2.5 distinguishes ADM from. ADM does not replace the sales conversation with an interrogation; it reorders it so that the Question Taxonomy runs before the pitch is shaped. The result is not a fixed script but an adaptive one whose branches are governed by what each answer leaves unresolved, and whose eventual recommendation rests on the prospect's stated constraints and priorities rather than the seller's default sequence. This is the gap-detection discipline of Section 3.4 applied to a commercial conversation, and it is subject to the same limit discussed below: a prospect can be over-questioned, and the method's value depends on stopping when the picture is complete rather than continuing because the script has more lines.
4.6 Threats to Validity
ADM's diagnostic quality depends on conditions that are not always present. Five limitations warrant explicit acknowledgment.
First, ADM requires organizational willingness to be questioned. Some engagements involve clients who have already decided on a solution and are seeking validation rather than diagnosis. ADM cannot extract accurate context from a client who is not willing to engage openly with diagnostic questions. Practitioners should assess this willingness at the outset and should not attempt to apply ADM in contexts where it will be resisted at a structural level.
Second, question quality depends on practitioner skill. The Question Taxonomy provides categories and examples, but formulating questions that genuinely surface root conditions, rather than leading the client toward the practitioner's preferred diagnosis, requires experience and self-awareness. Poorly executed Inquiry phases can produce context that is systematically biased in the practitioner's direction, which undermines the methodology's core purpose.
Third, ADM outcomes are not reliably replicable across organizations. Two organizations with similar surface problems may have entirely different root conditions, and ADM's value is precisely that it does not assume otherwise. This means ADM cannot produce the kind of generalizable playbooks that some organizations prefer. Each engagement produces context-specific findings.
Fourth, the claim that ADM improves outcomes is at this stage a mechanism argument, not an empirically demonstrated result. No controlled study establishes that structured diagnostic protocols produce better decisions than expert judgment in knowledge-work settings, and the nearest adjacent evidence is mixed: controlled trials of cognitive-forcing and debiasing strategies in clinical reasoning have shown little or no reduction in diagnostic error [Sherbino et al., 2014; Norman et al., 2017]. The distinction ADM draws is that those interventions ask practitioners to reason more carefully with information they already hold, whereas ADM changes what information is available by extracting context the practitioner does not yet possess. Whether that difference produces measurably better outcomes is an open empirical question. The argument of this paper is that the mechanism is sound and the question is worth testing, not that the result is settled.
Fifth, questioning has a natural limit, and past it the method degrades the very context it exists to gather. Survey and interview research is consistent on this point: as the volume of questions grows, people shift from giving considered answers to giving merely adequate ones, agreeing rather than reflecting, skipping, or flattening their responses, a drift the survey literature calls satisficing [Krosnick, 1991; Herzog & Bachman, 1981; Galesic & Bosnjak, 2009]. A diagnostic that mistakes a long question list for thoroughness produces a record that looks complete and reads as fatigued. ADM's defense against this is structural rather than a matter of counting questions or scoring an instrument. The gap-detection loop of Section 3.4 asks only what the completeness criteria still require and stops probing a category the moment it is satisfied or the respondent genuinely cannot answer, so depth is spent where the record is thin and withheld where it is already sound. Two human disciplines keep the load down further: best-effort estimates are accepted in place of exact figures, which removes the most tiring demand of all, and inquiry is permitted to lead with a hypothesis rather than start from a blank slate, so a well-briefed practitioner confirms and corrects rather than making the respondent assemble the picture from nothing. This last point also separates the delivery method from the sales conversation that precedes it: the industry research on buyer fatigue that warns against open-ended fishing [Dixon & Adamson, 2011] is a caution about how to win an engagement, not about how to conduct structured extraction once one is underway. None of this makes fatigue impossible. The bound holds only to the extent that the loop's stopping criteria are well specified and honestly applied, which is a demand on the practitioner and the tooling, not a property the method can claim on its own.
5. Discussion
5.1 Where ADM Works
ADM is most effective in knowledge-work contexts where the problem is ambiguous, contested, or embedded in organizational dynamics that are not visible from outside. This includes management and strategy consulting, technology implementation scoping, organizational design, product development discovery, and any context where the practitioner's initial hypothesis about the problem may be incorrect.
The methodology also performs well in contexts where past interventions have failed or produced partial results. When an organization has already tried several solutions to a persistent problem, ADM's Root and Constraint Question categories are particularly effective at surfacing why previous approaches did not hold. That information is rarely volunteered but is often the most important input for designing an effective intervention.
Complex AI implementations represent an increasingly important application domain. As organizations deploy AI systems for a growing range of functions, the quality of the context those systems operate on becomes a strategic variable. ADM provides a disciplined method for ensuring that AI systems receive accurate context rather than organizational mythology.
5.2 Where ADM Does Not Work
ADM introduces diagnostic latency: the prescription is delayed until the diagnostic cycle is complete. In time-critical operations such as emergency response or acute crisis management, where the cost of delay exceeds the cost of an imperfect but fast solution, this latency is unacceptable. ADM is not a framework for real-time decision-making.
Commodity tasks with fully specified requirements also do not benefit from ADM. When the problem is genuinely known, the constraints are documented, and the solution space is well-understood, a diagnostic phase adds process without adding value. ADM is a tool for navigating ambiguity; it is unnecessary in the absence of ambiguity.
Finally, ADM is not appropriate for engagements where the client relationship cannot support the level of inquiry the methodology requires. Short-term transactional engagements, RFP-driven procurement contexts, and relationships where the client is primarily evaluating whether to hire the practitioner, rather than investing in a diagnostic process, are not suitable conditions for ADM execution.
5.3 Epistemic Overreach
We use the term epistemic overreach to describe the practice of generating solutions, recommendations, or diagnoses from perceived or assumed context rather than from extracted fact. It is not a passive condition but an active one: the practitioner reaches past what is known toward what feels known, and produces output as if the two were equivalent.
Epistemic overreach compounds over time. Each recommendation built on assumed context rather than extracted fact produces a new layer of assumption that subsequent recommendations treat as established. Long-tenured leadership teams, stable market positions, and successful historical performance all accelerate this: success reduces the pressure to interrogate assumptions, and uninterrogated assumptions become the substrate for the next round of overreach.
ADM is designed to counter epistemic overreach directly. The Validation phase, in particular, surfaces it explicitly: returning a diagnostic summary to stakeholders and asking them to confirm or correct it often produces the most valuable context of the entire engagement. Corrections to the practitioner's synthesis reveal where the client's self-presentation in the Extraction phase did not match their actual recognition of the problem. This discrepancy is diagnostic data.
5.4 Diagnosis as Strategic Position
For a firm that adopts it, ADM is not only a quality discipline. It is a strategic position in the sense Porter gives that term. Porter distinguishes operational effectiveness, performing similar activities better than rivals, from strategy, performing different activities or similar activities in different ways, and argues that operational effectiveness alone is not a durable advantage because best practices diffuse [Porter, 1996]. If ADM were merely a better discovery process, competitors would copy it. The claim here is narrower and stronger: ADM constitutes a different activity set, and the trade-offs it demands are precisely what protect it from imitation.
The scope conditions documented in Sections 4.6 and 5.2 are, read strategically, those trade-offs. A firm practicing ADM does not present a proposal in the first meeting. It accepts diagnostic latency. It declines engagements where the client wants validation rather than diagnosis. Each of these is a genuine cost, and Porter's central insight is that genuine costs are what make a position defensible: a competitor whose commercial model is built on solution-led selling cannot adopt diagnosis-led engagement without dismantling its own sales motion [Porter, 1996]. This is also why publishing the methodology does not erode the position. The barrier to imitation is not secrecy; it is the trade-off. Rumelt makes the complementary point from the strategy side: the kernel of any good strategy begins with diagnosis, and most bad strategy fails precisely by skipping it [Rumelt, 2011]. A methodology that operationalizes diagnosis is therefore not adjacent to strategy work; it is the entry condition for it.
The activities also fit together in the reinforcing way Porter's activity-system analysis describes [Porter, 1985; Porter, 1996]. Question-led engagement produces validated context; validated context feeds AI-assisted execution; execution results are compared against Validation criteria in the Adaptation phase; Adaptation resets Inquiry with a higher baseline. Copying any single activity yields little, because the value sits in the interlock.
Run across repeated cycles, that interlock behaves like the flywheel Collins describes: no single turn is decisive, but each turn compounds the momentum of the last [Collins, 2001]. The phased completeness levels of Section 3.4 are the flywheel's ratchet points. Context validated at Level 3 in one cycle becomes the starting baseline of the next cycle's Inquiry, so subsequent extraction concentrates on what changed rather than re-deriving what is known. The practical consequence is an accumulating, validated, machine-readable model of the client's actual business, an asset that deepens with every cycle and does not transfer to a competitor arriving later, who starts at zero.
The commercial model follows from the medical framing established in Section 2.1. A patient pays for the office visit that determines why the symptoms exist, before and separately from paying for any treatment. Positioned this way, the diagnostic is not unbilled pre-sales effort; it is the first engagement, with a standalone deliverable, the validated diagnostic record, whose value survives even if no implementation follows. Firms that give diagnosis away signal that it is worthless; firms that price it signal that it is the product.
5.5 Implications for AI-Augmented Organizations
AI systems that participate in organizational decision-making, communication, and analysis are context-dependent at a level that is more explicit and more consequential than human practitioners. A human consultant can draw on embodied experience and non-verbal organizational observation to partially compensate for incomplete or inaccurate briefing. An AI system has no such compensation mechanism. It operates on what it receives.
This means that as organizations increase their reliance on AI-assisted work, the accuracy and completeness of the context those systems receive becomes a major determinant of organizational AI performance, alongside the capability of the models themselves. A less capable model with accurate, well-structured context can outperform a more capable model operating on assumed or bloated context.
ADM creates the institutional discipline for context hygiene: the practice of regularly extracting, validating, and structuring organizational context so that AI systems operate on reality rather than perception. This is not a one-time configuration exercise. Organizational context changes continuously: priorities shift, constraints evolve, new information changes the problem landscape. The Adaptation phase of ADM, feeding back into new Inquiry cycles, is what keeps the context current.
6. Future Directions
6.1 ADM-Trained AI Assistants
Current large language models are optimized to respond to queries. Their default behavior is to answer, not to ask. This creates a structural bias toward the prescriptive pattern that ADM is designed to counter: the model receives a problem statement and immediately generates a solution, regardless of whether the context feeding that problem statement is accurate or complete.
A natural extension of ADM is the development of AI assistants explicitly trained to apply the methodology: systems that, when presented with an organizational problem, first generate and ask a structured question set before synthesizing any response. The Question Taxonomy in Section 3.2 provides a natural training scaffold. Fine-tuning on ADM question sequences, combined with evaluation criteria that reward diagnostic depth over response speed, could produce AI assistants that function as genuine diagnostic partners rather than answer generators.
This capability would be especially valuable for AI systems deployed in consulting, product discovery, and implementation-scoping contexts, where the cost of a fast but contextually misaligned answer is high.
6.2 Question Quality Metrics
ADM's current formulation identifies question categories and provides examples, but does not offer a formal scoring rubric for evaluating question quality. This is a limitation for organizations attempting to train practitioners and for AI systems being evaluated on their diagnostic capability.
A question quality metric for ADM would need to evaluate several dimensions: specificity (does the question target a defined information gap?), neutrality (does the question avoid leading the respondent toward a particular answer?), dependency (is the question positioned correctly relative to the information it requires from prior questions?), and yield (does the question reliably produce decision-relevant context?). Developing this rubric through structured practitioner evaluation and empirical testing across diverse organizational engagements represents a meaningful research program.
6.3 Context Hygiene as Organizational Practice
The deepest implication of applying ADM within a structured context architecture is that the combination can function as an organizational operating layer for AI deployment: not just a methodology for individual engagements, but a continuous institutional practice.
In this conception, ADM provides the quarterly or semi-annual diagnostic cycle that refreshes organizational context: what is the current state, what has changed, what are the new constraints, what are the current priorities? That extracted context is then organized within a machine-readable context architecture and made available to AI systems across the full range of organizational work.
This is meaningfully different from current AI deployment practice, which typically treats context as a configuration step rather than a continuous discipline. Organizations that treat context as a living, regularly extracted, formally structured resource will have a systematic advantage over organizations that treat AI context as a setup parameter that rarely changes. Formalizing this as an institutional operating standard, rather than a per-project practice, is the long-term direction this approach points toward.
7. Conclusion
The pattern this paper describes is not new, but naming it precisely allows it to be addressed directly. Practitioners arrive with solutions. Solutions shape the questions they ask. The questions they ask shape the context they receive. The context they receive confirms the solutions they already had. This cycle produces work that is technically competent and contextually misaligned, and it produces it consistently because the cycle is structural, not individual.
ADM interrupts the cycle at its start. By requiring that questions precede solutions, that context be extracted rather than assumed, and that reality be validated before any prescription is written, it creates a process in which the solution is genuinely downstream of the diagnosis. This is not a harder process than the alternative; it is a more honest one.
ADM's reach extends into the AI-augmented organization, where the stakes of context accuracy are higher because an AI system has no embodied experience to fall back on when its briefing is wrong. The structured outputs produced by the ADM cycle are designed to feed AI systems with validated organizational context. It is a practical model for any organization that wants AI assistance grounded in extracted context rather than assumption.
The central claim of this paper is simple enough to state directly: the quality of any solution is bounded by the quality of the questions that produced the diagnosis it is based on. This paper provides a formal methodology for taking that claim seriously.
References
Ahluwalia, R., & Burnkrant, R. E. (2004). Answering questions about questions: A persuasion knowledge perspective for understanding the effects of rhetorical questions. Journal of Consumer Research, 31(1), 26–42.
Bauer, T. N. (2010). Onboarding New Employees: Maximizing Success. SHRM Foundation.
Beyer, H., & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. Morgan Kaufmann.
Boehm, B., & Basili, V. R. (2001). Software defect reduction top 10 list. IEEE Computer, 34(1), 135–137.
Burnkrant, R. E., & Unnava, H. R. (1995). Effects of self-referencing on persuasion. Journal of Consumer Research, 22(1), 17–26.
Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). Know your customers' "jobs to be done." Harvard Business Review, 94(9), 54–62.
Collins, J. (2001). Good to Great: Why Some Companies Make the Leap... and Others Don't. HarperBusiness.
Cooperrider, D. L., & Srivastva, S. (1987). Appreciative inquiry in organizational life. Research in Organizational Change and Development, 1, 129–169.
DellaVigna, S., & Linos, E. (2022). RCTs to scale: Comprehensive evidence from two nudge units. Econometrica, 90(1), 81–116.
Deming, W. E. (1986). Out of the Crisis. MIT Press.
Dixon, M., & Adamson, B. (2011). The Challenger Sale: Taking Control of the Customer Conversation. Portfolio/Penguin.
Dunlosky, J., Rawson, K. A., Marsh, E. J., Nathan, M. J., & Willingham, D. T. (2013). Improving students' learning with effective learning techniques: Promising directions from cognitive and educational psychology. Psychological Science in the Public Interest, 14(1), 4–58.
Fitzpatrick, R. (2013). The Mom Test: How to Talk to Customers and Learn if Your Business Is a Good Idea When Everyone Is Lying to You. CreateSpace.
Galesic, M., & Bosnjak, M. (2009). Effects of questionnaire length on participation and indicators of response quality in a web survey. Public Opinion Quarterly, 73(2), 349–360.
Getzels, J. W., & Csikszentmihalyi, M. (1976). The Creative Vision: A Longitudinal Study of Problem Finding in Art. Wiley.
Herzog, A. R., & Bachman, J. G. (1981). Effects of questionnaire length on response quality. Public Opinion Quarterly, 45(4), 549–559.
Hofmann, H. F., & Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE Software, 18(4), 58–66.
Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
Kahneman, D., & Klein, G. (2009). Conditions for intuitive expertise: A failure to disagree. American Psychologist, 64(6), 515–526.
Karpathy, A. [@karpathy]. (2025, June 25). "+1 for 'context engineering' over 'prompt engineering'" [Post]. X. https://x.com/karpathy/status/1937902205765607626
Khalsa, M., & Illig, R. (2008). Let's Get Real or Let's Not Play: Transforming the Buyer/Seller Relationship. Portfolio/Penguin.
Krosnick, J. A. (1991). Response strategies for coping with the cognitive demands of attitude measures in surveys. Applied Cognitive Psychology, 5(3), 213–236.
Loewenstein, G. (1994). The psychology of curiosity: A review and reinterpretation. Psychological Bulletin, 116(1), 75–98.
Lütke, T. [@tobi]. (2025, June 19). "I really like the term 'context engineering' over prompt engineering" [Post]. X. https://x.com/tobi/status/1935533422589399127
Miller, V. D., & Jablin, F. M. (1991). Information seeking during organizational entry: Influences, tactics, and a model of the process. Academy of Management Review, 16(1), 92–120.
Morrison, E. W. (1993). Newcomer information seeking: Exploring types, modes, sources, and outcomes. Academy of Management Journal, 36(3), 557–589.
Mumford, M. D., Reiter-Palmon, R., & Redmond, M. R. (1994). Problem construction and cognition: Applying problem representations in ill-defined domains. In M. A. Runco (Ed.), Problem Finding, Problem Solving, and Creativity (pp. 3–39). Ablex.
Norman, G. R., Monteiro, S. D., Sherbino, J., Ilgen, J. S., Schmidt, H. G., & Mamede, S. (2017). The causes of errors in clinical reasoning: Cognitive biases, knowledge deficits, and dual process thinking. Academic Medicine, 92(1), 23–30.
Petty, R. E., Cacioppo, J. T., & Heesacker, M. (1981). Use of rhetorical questions in persuasion: A cognitive response analysis. Journal of Personality and Social Psychology, 40(3), 432–440.
Porter, M. E. (1985). Competitive Advantage: Creating and Sustaining Superior Performance. Free Press.
Porter, M. E. (1996). What is strategy? Harvard Business Review, 74(6), 61–78.
Pressley, M., McDaniel, M. A., Turnure, J. E., Wood, E., & Ahmad, M. (1987). Generation and precision of elaboration: Effects on intentional and incidental learning. Journal of Experimental Psychology: Learning, Memory, and Cognition, 13(2), 291–300.
Rackham, N. (1988). SPIN Selling. McGraw-Hill.
Reiter-Palmon, R., & Robinson, E. J. (2009). Problem identification and construction: What do we know, what is the future? Psychology of Aesthetics, Creativity, and the Arts, 3(1), 43–47.
Richardson, W. S., Wilson, M. C., Nishikawa, J., & Hayward, R. S. A. (1995). The well-built clinical question: a key to evidence-based decisions. ACP Journal Club, 123(3), A12–A13.
Rothstein, D., & Santana, L. (2011). Make Just One Change: Teach Students to Ask Their Own Questions. Harvard Education Press.
Rumelt, R. P. (2011). Good Strategy Bad Strategy: The Difference and Why It Matters. Crown Business.
Schein, E. H. (1969). Process Consultation: Its Role in Organizational Development. Addison-Wesley.
Senge, P. M. (1990). The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday.
Sherbino, J., Kulasegaram, K., Howey, E., & Norman, G. (2014). Ineffectiveness of cognitive forcing strategies to reduce biases in diagnostic reasoning: A controlled trial. CJEM, 16(1), 34–40.
Spangenberg, E. R., Kareklas, I., Devezer, B., & Sprott, D. E. (2016). A meta-analytic synthesis of the question-behavior effect. Journal of Consumer Psychology, 26(3), 441–458.
Van Clief, J., & McDermott, D. (2026). Interpretable Context Methodology: Folder structure as agent architecture. arXiv:2603.16021.
Womack, J. P., & Jones, D. T. (1996). Lean Thinking: Banish Waste and Create Wealth in Your Corporation. Simon & Schuster.
ADM™ is a methodology developed by Dovito Business Solutions.
Submitted to arXiv, cs.AI / cs.HC David Coleman, Dovito Business Solutions, Fort Collins, Colorado Contact: david@dovito.com