Skip to content

Elicitation technique

A method for drawing specified knowledge or preferences from people's responses or observed behavior in an inquiry.

Version
v1 · 2026-09-28 · History
Domain-specific #
9209
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomains
Knowledge Acquisition, Requirements Engineering → Computer Science & Software Engineering
Aliases
Elicitation method, Knowledge elicitation technique

Core Idea

An elicitation technique is a method for making relevant human knowledge, preferences, requirements, or behavior available to an inquiry. The analyst specifies a question and human source, chooses questions, an assigned task, or an observation protocol, and records what the person says, chooses, or does. The method may be an interview, questionnaire, focus group, naturally occurring field observation, task analysis, scenario, or structured expert probe. Direct verbal report and assigned performance are possible routes, not universal conditions: planned observation can reveal practice without interrupting it.

Hoffman and colleagues distinguish interviews, usual-task analysis, and constructed tasks in expert-knowledge work, and their Critical Decision Method study shows repeated probes around actual incidents yielding decision requirements and timelines. Elicitation is not equivalent to an entire research program or to the resulting fact claim. A captured answer can be shaped by recall, question wording, role, setting, and sampling. Document analysis is an adjacent supporting activity: reading existing text without a human encounter is indirect acquisition, while discussing that text with its author can be part of elicitation.

Scope of Application

The method must expose a human contribution to a defined inquiry, even when it is not verbal.

  • Expert knowledge. Draw out decision cues and task structure for analysis.
  • Requirements inquiry. Ask stakeholders or observe work to identify needs and constraints.
  • Preference research. Use declared prompts to surface judgments or choices.
  • Field observation. Examine task behavior when explicit accounts omit tacit steps.

Clarity

Identify the inquiry target, human source, declared prompt, task or observation protocol, and captured response or behavior. A document review alone is the near miss: existing writing can inform an investigation without eliciting a new contribution. Interviews, naturally occurring field observation, and structured incident probes can all qualify, but their results still have framing, recall, and sampling limits. A UI command by itself operates software rather than gathering inquiry evidence.

Manages Complexity

The method turns otherwise tacit or dispersed human knowledge into examinable evidence. Its apparent simplicity hides choices about participant selection, prompt or observation framing, recording, interpretation, and validation. A richly detailed incident interview may reveal cues that a checklist misses, yet can also suffer retrospective reconstruction; naturalistic observation may show action but not the participant's reasons.

Abstract Reasoning

  1. Define the information, knowledge, or preference being sought.
  2. Identify participants and the context in which they hold or express it.
  3. Select an interview prompt, assigned scenario/task, or planned naturalistic observation protocol suited to the target.
  4. Capture the resulting statements or behavior without silently replacing evidence with interpretation.
  5. Assess framing, recall, sampling, and cross-checks before making claims from the record.

Knowledge Transfer

The target–human source–elicitation setup–captured contribution pattern travels from cognitive task analysis to requirements gathering or field research only after participants, evidence type, and validity checks are redefined. Critical Decision Method probes appropriate to an incident cannot be copied unchanged into naturalistic observation or a short preference survey. A UI gesture and a static document may share interaction or information but do not become elicitation until they contribute to a designed human-source inquiry.

Neighborhood in Abstraction Space

Elicitation technique sits in a crowded region of the domain-specific corpus (32nd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Communication, Learning & Information Practices (15 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08