Skip to main content
Category: Methods
Type: Strengths-based change method
Origin: David L. Cooperrider and Suresh Srivastva, Case Western Reserve University, 1986–1987
Also known as: AI; 4-D cycle; Appreciative Inquiry Summit; strengths-based inquiry
Quick Answer — Appreciative Inquiry is a change method that studies what already gives life to a group at its best, then uses those stories to imagine and design more of it. David L. Cooperrider and Suresh Srivastva developed it at Case Western Reserve University from Cleveland Clinic fieldwork in the early 1980s; the public statement is their 1987 essay Appreciative Inquiry in Organizational Life. The practical lesson is that the first question is already an intervention: ask only about defects, and the room fills with defects; ask what worked, and you get a map of capacity you can actually build on.

​
What is Appreciative Inquiry?

Appreciative Inquiry is a strengths-based change method that searches for the best of what is, imagines what might be, and then designs social arrangements that could make that future ordinary.
Appreciative Inquiry is about the coevolutionary search for the best in people, their organizations, and the relevant world around them.
Picture a family meeting that opens with “Who is always late, and why is homework a mess?” Everyone has a file. Now open with “When did a week go well, and what made it possible?” You still have to cook dinner and pay bills. You just start from soil that already grows something, instead of from a list of weeds. That is the everyday cue. Unlike five whys or root-cause analysis, which hunt a defect until it names a cause, Appreciative Inquiry treats the system as a living story you can rewrite. The craft of the question is closer to Socratic method than to a repair ticket.

​
Appreciative Inquiry in 3 Depths

  • Beginner: Ask what already worked, not only what broke. Write down the conditions that made the good hour possible.
  • Practitioner: Name an affirmative topic, run Discovery–Dream–Design–Destiny, and end with people who own next moves, not a slide of recommendations.
  • Advanced: The method is generative, not cheerful. Peak stories that do not change how people think leave the culture intact. Bushe and Kassam found that only seven of twenty published cases showed transformation.

​
Origin

Appreciative Inquiry began as a research surprise, not as a workshop brand. In 1980, David L. Cooperrider, then a doctoral student at Case Western Reserve University working under Suresh Srivastva, joined a diagnostic study of the Cleveland Clinic. The brief was the usual one: what is wrong on the human side of a high-performing medical group. Interviews about defects drained energy. Interviews about what made the place excellent lit it up. The term first appeared as a footnote in a feedback report to the Clinic’s Board of Governors, as an “appreciative analysis” of life-giving factors rather than a problem list. Cooperrider’s 1986 dissertation, Appreciative Inquiry: Toward a Methodology for Understanding and Enhancing Organizational Innovation, set out the logic. The field paper is Cooperrider and Srivastva, “Appreciative Inquiry in Organizational Life,” in Research in Organizational Change and Development, Volume 1 (1987). It argued that action research had become too problem-centered, and that social science should aim at generative theory: ideas that open new options for action. The theoretical root is Kenneth Gergen’s social constructionism: words and questions help make the world they claim to describe. The practitioner form arrived later. Cooperrider and Diana Whitney named five working principles—constructionist, simultaneity, poetic, anticipatory, and positive—and popularized the 4-D cycle: Discovery, Dream, Design, Destiny. Their short manifesto A Positive Revolution in Change: Appreciative Inquiry (around 1999–2001) and the Appreciative Inquiry Handbook (with Jacqueline Stavros) made the cycle teachable. Large-group versions are often run as an Appreciative Inquiry Summit, documented by Ludema, Whitney, Mohr, and Griffin in 2003. Some practitioners add a fifth D, Define, for choosing the affirmative topic before Discovery begins.

​
Key Points

Appreciative Inquiry earns its keep when the work is to grow a capacity that already exists in fragments, not when the work is to isolate a fault that must be stopped.
1

Choose the topic as if the question were already the change

The simultaneity principle says inquiry is intervention. “Why is morale so low?” and “When did people here feel most proud to stay?” send the room in different directions before anyone answers. Write an affirmative topic: something you want more of, stated in language people can tell a story about. If leaders already know the answer, or need a safety finding, pick another method.
2

Discover the positive core in stories, not slogans

Discovery is a search for the best of what is. Pair people. Ask for a peak moment, who was there, and what conditions made it possible. Collect themes. That bundle—strengths, relationships, know-how, values—is the positive core. A poster of values is not Discovery. A room that can point to three real hours when the place was at its best is.
3

Dream, then write Design as a provocative proposition

Dream asks what might be if the best were the norm. Design turns that image into statements of the ideal organization: “We are a clinic where every handoff is a teaching moment,” not “we should improve communication.” These are sometimes called provocative propositions. They must be grounded in Discovery, or they become wishes.
4

Treat Destiny as improvisation, not a delivery plan

Destiny (sometimes renamed Delivery, a label Cooperrider dislikes) is how people start living the design. In the cases Bushe and Kassam judged transformational, this phase was improvisational: many small, self-organized moves rather than one project plan. A 4-D day that ends with a task force and no new image of who we are has copied the furniture of the method and missed the engine.

​
Applications

Use Appreciative Inquiry when you need energy and a shared picture of capacity. Do not use it as a substitute for a defect hunt when harm, fraud, or a broken part is the issue.

Strategy and culture that have to be lived

Before the slide deck hardens, interview across ranks for peak collaboration, then run a 4-D summit on the topic you actually want more of. GTE’s late-1990s work is the classic large-company case. Pair later with World Café if the room is too large for paired interviews alone.

Schools, clinics, and shift teams

Teachers, nurses, and night-shift staff often know when the work sings and never put it on the agenda. A Discovery round on confident learners or clean handoffs beats another deficit survey. If you then need a disciplined pass through risks, use six thinking hats so yellow-hat hope does not crowd out black-hat caution.

Career reviews and early-career growth

Replace “list three weaknesses” with a peak-experience interview: when did you do work you are proud of, and what made it possible? That is closer to a growth mindset than to a repair list. Still name one skill to practice. Strengths-based does not mean skip the hard part; it means start from a working example.

Family and community choices that stall

A household, a building committee, or a volunteer board can copy the skeleton: one affirmative question, paired stories, a shared dream sentence, one design statement, and who will try it this month. It will not replace a budget vote. It will stop the loudest complaint from being mistaken for the group’s whole story.

​
Case Study

The cleanest numbered window onto Appreciative Inquiry as a company practice is GTE (later part of Verizon) in the mid-1990s. The U.S. telephone business was opening to competition. Diana Whitney, David Cooperrider, and internal partners including Maureen Garrison and Jean Moore helped host a “positive revolution” question: how to engage the potential of a workforce on the order of 64,000 people. The process trained thousands, used frontline interviewers, and asked people to hunt stories of the organization at its best rather than a catalog of grievances. Practitioner reports, gathered by Cheney and Jarrett (1998) and retold in Bushe and Kassam’s 2005 Journal of Applied Behavioral Science review, give the measurable claims. From 1996 to 1997, employee support for GTE’s business direction was said to have jumped 50 percent, and the share who felt information was shared openly to have risen nearly 140 percent. One collections team was credited with 3million∗∗recoveredin1996,∗∗3 million** recovered in 1996, **7–8 million a year from a streamlined payment process, and $4 million from automating insufficient-funds handling. More than 10,000 innovations were attributed to the effort. In 1997 GTE received an American Society for Training and Development award for organizational change. The lesson is the method’s real bet: a question that treats tens of thousands of people as a source of life-giving practice can surface thousands of local moves that a deficit survey would never request. Boundary note: these figures are internal and practitioner-reported, not an independent randomized test. Bushe and Kassam examined twenty published Appreciative Inquiry cases before 2003 and judged only seven (35 percent) transformational. GTE later disappeared into the Verizon merger. A culture inquiry can change talk and local process. It does not repeal industry structure.

​
Boundaries and Failure Modes

Appreciative Inquiry fails when the problem is a defect that must be stopped. Infection control, a crashed system, fraud, and a safety near-miss need root-cause analysis, not a dream of the ideal ward. Using a 4-D cycle to postpone a hard finding is not strengths-based practice. It is avoidance. It also fails when “positive” is used to shut people up. Critics have warned that a forced smile can become repression with better lighting. If people cannot name harm, the inquiry is not appreciative. It is managed mood. Bushe’s point is sharper still: peak stories that do not generate new ideas leave the culture as it was. Cheer is not the outcome. New action that was not available yesterday is. The common misuse is to run Discovery as a one-day icebreaker and skip Design and Destiny. Colored cards and a vision sentence are cheap. Provocative propositions that people then improvise on are the work. If you need a ranked decision this afternoon, do not ask Appreciative Inquiry to be a vote.

​
Common Misconceptions

The method looks like optimism, so it is easy to copy the smile and miss the inquiry.
The method does not claim that defects are imaginary. It claims that a group becomes what it persistently studies. Start with life-giving practice when you want more capacity. Start with five whys when you need to stop a fault. Skipping a safety finding in the name of positivity is not this method.
Discovery, Dream, Design, and Destiny are a rhythm, not a Gantt chart. In the transformational cases, Destiny was improvisation by many people, not a task force delivering a plan. If you treat the cycle as four deliverables for a sponsor, you have borrowed the labels and kept ordinary change management.
Stories of the best hour are fuel, not the fire. Bushe argues that the core is generativity: new images that make new action possible. A room that only swaps proud anecdotes has had a pleasant day. It has not done Appreciative Inquiry until thinking, and then behavior, actually move.
These pages sit next to the same problem: how a group decides what to study, and whether it starts from a defect or from a living capacity.

Five Whys

A defect hunt that keeps asking why; the opposite opening move from an affirmative topic.

Root Cause Analysis

Isolate a fault that must be stopped; use this when harm, not capacity, is the issue.

World Café

Small-table dialogue that can carry Discovery stories through a large room.

Socratic Method

Question craft that keeps an inquiry open instead of collapsing it into a complaint list.

Growth Mindset

A belief that ability can grow; Appreciative Inquiry looks for working examples of that growth.

Design Thinking

Prototype a better offering after you know what “better” should feel like in use.

​
One-Line Takeaway

Ask what already gives life, then design more of it. The first question is already the first change.