Participatory & qualitative approachesStrengths-basedOrganizational developmentStakeholder participationTransformationPositive

Appreciative Inquiry

Appreciative Inquiry
Also known as: AI (Appreciative Inquiry)、AI evaluation、Appreciative inquiry approach

A dialogue approach exploring successful experiences and their enabling conditions, connecting them to desired futures and concrete actions. It investigates strengths for improvement. [1]

Difficulty
Intermediate
Cost
Medium
Duration
Illustrative estimate, adjusted to scale and staffing: 1–3 days for an AI summit to several weeks across multiple sessions
Content updated: 2026-10-07Source checked: 2026-09-13 (includes AI cross-checking)No documented human reviewIncludes fictional examples

How it works at a glance

Appreciative Inquiry focuses on experiences that created value in organizations or activities and uses them to envision the future. The 4D process involves discovery, dreaming, design, and action and learning. [1]

Participants describe positive events and their contexts in detail, then consider how enabling conditions can inform future practice. This site's examples start from positive experiences while separately checking remaining disadvantages and participation barriers. [1]

  1. Define: design the theme and AI questions
  2. Discovery: explore strengths and successful experiences
  3. Dream: envision the desired future
  4. Design: plan transformation
  5. Destiny/Deliver: move into practice
Sequence of implementation steps. See “Implementation steps” for details of each stage.

When to use it and when it is unsuitable

When to use it

  • When stakeholders are exhausted by problem-finding and strengths-based dialogue can encourage evaluation participation
  • When systematically collecting and sharing what worked in an end-of-program retrospective
  • When community development or organizational change requires participants to co-create future directions
  • When pursuing staff learning and organizational capacity development alongside evaluation

When it is unsuitable

  • Severe power imbalances or conflict can make strengths-based processes superficial and conceal underlying problems.
  • When accountability requires thorough causal analysis of negative results or failures. Problem-focused methods are appropriate.

Participants, roles, and deliverables

Participants and roles

All program stakeholders, including staff, beneficiaries and partners. Large AI summits involve 50 to several hundred people; small ones involve 10–30. Consider 1–2 experienced facilitators.

Main deliverables

  • Success stories and best practices
  • Dream vision records: diagrams, stories and declarations
  • Action commitments

Implementation steps

  1. Define: design the theme and AI questions
    Set a positive inquiry theme, such as the most effective support moment or when community trust deepened most. Design specific, open questions eliciting past successes.
  2. Discovery: explore strengths and successful experiences
    Through paired interviews or group dialogue, participants share experiences they are proud of, successes and strengths. Focus on peak moments, exploring what happened and what made them possible.
  3. Dream: envision the desired future
    Build on discovered strengths to envision a future where the best conditions always exist. Creative formats such as drawing, drama and stories expand imagination.
  4. Design: plan transformation
    Design structures, processes, relationships and actions needed to realize the dream. Express these as strong propositions, “X is...” or “X should be...”
  5. Destiny/Deliver: move into practice
    Participants develop specific commitments and action plans. Clarify who does what by when, and design follow-up arrangements.

Strengths and limitations

Strengths

  • Increases stakeholder motivation and reduces resistance to evaluation.
  • Elicits tacit organizational or community knowledge, patterns of success, and makes it shared knowledge.
  • Creates synergy by advancing evaluation, organizational development and capacity together.
  • Sharing strengths is accessible even in culturally diverse groups.

Limitations

  • Less suited to problem-focused evaluation because critical analysis and root-cause exploration are weaker.
  • Overemphasis on strengths or success may impede learning from failure.
  • Requires careful design amid complex power structures or conflicting interests.

Common pitfalls

  • A fixed positive-only atmosphere prevents discussion of problems and failures. Facilitators should appropriately include dialogue on improvements.
  • Stopping at Discovery without Design or Destiny produces only a feel-good workshop.
  • Discussing strengths without changing organizational decisions or resource allocation makes the process hollow.

Conditions of use and evidence

  • Connect discovered strengths to future visions, joint design, action and adjustment. [1]
Fictional example; not actual results

Design collaboration from successful consultation handovers

A fictional illustrative example where desk staff explore shared conditions enabling successful handovers.

Question numberInterview questionResponse notes: keywords and quotations
1When recently did a service user feel safe moving to the next desk?With the person's agreement, could telephone the next staff member in advance.
2What conditions made that possible?Knew the contact person and times when they could respond.

Common errors in judgment

Common mistake

Seeking only positive stories and stopping people who discuss burdens

How to revise

Explore enabling conditions while recording remaining disadvantages.

ReasonStrengths inquiry must not conceal problems.

Common mistake

Ending after discussing dreams

How to revise

Specify trial actions, responsibilities and reflection.

ReasonThe process includes action and learning.

References and checked sections

  1. Appreciative inquiry
    BetterEvaluation
    Section consulted
    DISCOVER; DREAM; DESIGN; DESTINY
    How it relates to the text
    Connect discovered strengths to future visions, joint design, action and adjustment.
    Source checked: (includes AI cross-checking)

Editorial and checking information

Content updated: Source checked: (includes AI cross-checking)No documented human reviewIncludes fictional examplesEditorial policy and scope of checkingCite this pageReport a correction

How to cite this page

EvalCompass Editorial Team. “Appreciative Inquiry”. EvalCompass, updated 2026-10-07. https://evalcompass.jun-nakatani.com/en/methods/appreciative-inquiry/
Add the date you accessed the page. Text created by this site is available under CC BY 4.0. Quotations, external materials, and bundled fonts have their own terms of use. When reusing content, credit the source, link to the license, and indicate any changes.

Suggest a correction or improvement to this page

Change history
  • — Updated explanations to correspond with sources, and added method-specific fictional worksheet examples, judgment examples and revision history.
  • — Made minimal corrections to assertions, fixed conditions or inconsistencies between worksheets and examples based on content check FW-07. Preserved field counts, order, labels and section structure. Did not change verification status of unchecked material.