Elicitation

When NOT to use this skill

• Clinical diagnosis or treatment — this skill is research/design-oriented, not therapeutic. Use a licensed professional.
• Structured data capture — if you only need facts (age, job title, preferences), use standard survey design. This skill is for depth, not breadth.
• Persona creation from scratch — use the persona-definition skill for building individual user personas from research data, then use this skill to design the research conversations that feed it.
• Stakeholder mapping — use the persona-mapping skill for Power-Interest matrices and RACI charts across an organization.

How to use this skill

On every query, first read the core principle below, then load ONLY the references relevant to the specific query. Do not pre-load all references — progressive disclosure prevents context bloat.

Core principle (always apply)

Depth through patience, not probing. People want to tell their stories — they rarely get the chance. Your role is to create conversational space where disclosure feels natural, not extracted. Three non-negotiables:

1. Reflections outperform questions. Target a 2:1 reflection-to-question ratio. Questions gather; reflections invite elaboration. See references/motivational-interviewing.md.
2. Earn depth incrementally. Never ask deeply personal questions before trust is established. Start with easier territory and let the person's energy guide where to go deeper.
3. Follow their lead, not your agenda. Their emphasis is data. Steering toward topics you consider important signals you are not actually listening.

Domain routing

Reasoning sequence (apply to every response)

1. Understand the use context. Research interview? Life history? Conversational AI? Script critique? The use context determines which frameworks apply.
2. Check trust stage. Is this a first-contact or an established relationship? Early-stage conversations need graduated disclosure; late-stage can go deeper earlier.
3. Load the matching reference(s). Do not dump all techniques into the response — pick the ones that fit the specific situation.
4. Design for reflections, not questions. Every proposed question should come with one or two matching reflection moves for when the answer arrives.
5. Flag anti-patterns explicitly when reviewing existing content. Name which anti-pattern is present and show the concrete fix, not just "avoid this".
6. Respect the ethical boundary. Elicitation creates intimacy; that intimacy can be abused. Flag consent, withdrawal rights, and psychological safety whenever designing a real-world application.

Three research traditions (one-paragraph summary)

Ethical guardrails (always apply)

Elicitation is powerful because it creates the conditions for people to reveal what they normally keep private. That power carries responsibility. When designing real-world applications:

• Consent must be specific, not general. "I agree to a user interview" is not consent to discuss childhood trauma. Re-consent as depth increases.
• Withdrawal must be friction-free. People should be able to stop, skip, or retract without having to justify themselves.
• This is not therapy. If someone discloses something that needs professional support, name that clearly and redirect — do not improvise.
• Stored disclosures are sensitive. Any system that persists elicited data must treat it with the care you would want for your own most private memories.
• Cross-cultural validity is limited. The frameworks here are primarily derived from WEIRD (Western, Educated, Industrialized, Rich, Democratic) research. Adapt carefully to other contexts.

Elicitation Skill — built on research by Singer, McAdams, Miller & Rollnick, Schwartz, Young, Haight, Birren, and Pennebaker. Curated and restructured by Viktor Bezdek from the original tasteray/skills content. Licensed under MIT.