✓ Use it when
- Morale is low and a problem-focus has stopped producing energy.
- Strategy or culture work where you want broad, hopeful participation.
- You want to amplify existing strengths rather than only close gaps.
Appreciative Inquiry
A change approach that studies an organisation or community at its best and designs the future from those strengths rather than from problems.
Best for Leading change by studying what works at its best, then designing more of it.
In short: Appreciative Inquiry is a change approach that deliberately studies an organisation or community at its best — when it is most alive and effective — and uses that as the foundation for designing the future, rather than starting from problems to be fixed.
Source & attribution
Developed by David Cooperrider and Suresh Srivastva at Case Western Reserve University in the 1980s.
Primary source: David Cooperrider / Appreciative Inquiry field
Source confidence: Medium
Attributed to David Cooperrider and Suresh Srivastva. Plain-English summary. Often confused with positive deviance — appreciative inquiry studies best moments; positive deviance studies measurably better outcomes under the same constraints.
What it is for
It is for energising change, strategy and culture work where a relentless problem focus has drained motivation. It reframes inquiry around peak experiences, strengths and possibility.
Key ideas
- Discovery
- Find and appreciate the best of what is — when has this worked brilliantly?
- Dream
- Imagine what could be if those best moments were the norm.
- Design
- Co-design the structures and practices that would make the dream real.
- Destiny / Deliver
- Sustain change by embedding it in everyday action and learning.
When to use it — and when not to
✕ Be cautious / avoid when
- When real harms, risks or failures need to be named directly and acted on.
- When "positivity" would silence legitimate criticism or whistle-blowing.
- For technical problems with a clear right answer.
A practical example
Illustrative example (hypothetical): A youth centre is struggling with poor behaviour. Instead of a meeting about "how to fix the bad behaviour", staff use AI to ask: "Think of a time when the atmosphere here was incredibly positive and respectful. What was happening? How can we design more of that?"
Questions to ask in a meeting or workshop
- When have we been at our absolute best?
- What conditions made that peak experience possible?
- How can we design our everyday systems to recreate those conditions?
- Are we focusing so much on problems that we are draining energy?
Decision-return loop
Take this lens back to the decision.
A framework is a useful lens, not the decision. Use it to sharpen one real choice, then return to the route that matches the responsibility you hold.
Name the decision before using the lens
Before citing this framework, write the decision in ordinary language. For example: “Are we funding the right conditions?”, “Is this participation meaningful?”, “What handoff breaks after this activity?”, or “What would make this opportunity easier to reach?”
If the decision cannot be named yet, return to the decision questions before using framework language.
Use one useful distinction
Do not try to carry the whole framework into the room. Take one useful distinction from this page and test whether it changes the next question, criterion, design choice or handoff.
A useful distinction should make the decision clearer, not more impressive-sounding.
Return to the route that matches your responsibility
I am funding or commissioning
Check whether the money changes opportunity conditions, not just activity.
I am designing a programme or youth route
Check access, trust, participation, progression and adult responsibility.
I am working across a place or partnership
Check who holds coordination, handoffs and local accountability.
I am in a school, college or employer role
Check preparation, expectations, quality and what happens after the encounter.
I am learning the language first
Use the beginner route before trying to apply the framework.
Boundary before action: This framework page is public learning material. It does not validate a local plan, accredit a programme, provide implementation support, replace safeguarding, procurement, legal or evaluation judgement, or prove that a decision will work. In a live decision room, the decision-holder remains responsible for local evidence, affected people, constraints, risks and follow-through.
Need a route overview? Use Learning pathways. Need the public boundary? Read Current boundary.
Common mistakes
- Using it to avoid hard truths or suppress dissent.
- Stopping after the inspiring conversation, with no design or delivery.
- Treating it as forced positivity rather than genuine inquiry.
Compare it with another framework
- Positive Deviance vs ABCD — Both build on strengths — one learns from uncommon success, the other maps community assets.
Related frameworks
Positive Deviance Approach
A strengths-based approach that looks for people or groups already achieving unusually good outcomes despite facing similar constraints to others.
Asset-Based Community Development
A community development approach that starts with local assets, relationships, capacities and associations rather than deficits alone.
Design Thinking
A human-centred problem-solving approach that uses empathy, definition, ideation, prototyping and testing.
Next step: Need to check the source basis? Start reading to choose by your goal, or browse the full library.