What it means
Most change programmes begin with a problem, whereas appreciative inquiry begins with a peak, asking when the organisation was at its best and what made that possible. The method was developed in the 1980s by David Cooperrider and colleagues at Case Western Reserve University, growing from the observation that organisations move toward what they study.
The premise is simple and radical: attention is a resource, and dwelling on deficits breeds more deficit talk, while studying strengths grows more of them. The classic framework runs in four stages: Discovery finds the best of what is, Dream imagines what could be, Design builds what should be, and Destiny sustains what will be.
Discovery is storytelling at scale, with people interviewing each other about moments of excellence so that the collected stories reveal the organisation's positive core. The Dream phase turns themes into images of the future, and because those images are built from real memories, they feel attainable rather than imported.
Design converts dreams into structures, as teams draft provocative propositions, statements of how the organisation will work when its strengths are routine. Destiny embeds the changes without heavy programme machinery, because the energy comes from the participants, who designed what they are now implementing.
The approach suits some settings better than others, with morale-building, culture change, mergers and strategy renewal responding well to it. Critics note its blind spots, since glossing over genuine failures can leave serious problems unaddressed and some situations need hard diagnosis, not celebration.
Skilled practitioners combine both lenses, because appreciation mobilises energy and honest problem-solving protects the flank. For a manager, the entry cost is low, since one well-run session asking when the team last did its best work changes the room's mood and reveals reusable strengths.
Summits scale the method, with hundreds of people working through the 4-D cycle in one room and aligning a whole organisation in days. Questions carry the change: ask what went wrong and the room defends, while asking when it went brilliantly makes the room build.
Measurement still matters afterward, so track whether the designed changes stick, because enthusiasm without follow-through quietly reverts. The approach spread far beyond business, as schools, hospitals, churches and cities all use it for the same reason: people support what they help discover.
Start small if sceptical, because one meeting reframed around what works teaches more than any description of the method. Behind the jargon sits a plain habit, which is to find the best and make more of it, and teams that practise it keep a library of their own best days and draw on it whenever the next change begins.
In practice
Real-world examples.
Example
A merger integration team interviews staff from both companies about each firm's proudest moments, building the combined culture from two sets of proven strengths. The shared stories give both sides a reason to feel ownership of the new organisation.
Example
A retailer replaces its complaint-review meeting with a best-service story session, then trains new staff on the behaviours the stories kept repeating. Managers notice that the sessions are shorter and that staff volunteer more ideas.
Example
A city council uses appreciative inquiry with residents, starting from neighbourhoods' best days to design a regeneration plan people already believe in. The plan is easier to defend in public meetings because residents helped to write it.
Formula
Calculation
There is no formula. The working mechanics are the 4-D cycle: Discovery (interview for peak experiences and success factors), Dream (envision possibilities from those strengths), Design (craft provocative propositions and structures), Destiny (implement and sustain through participant ownership).
A simple count can still show whether Discovery reached enough people. Worked example: a department of 1,200 staff collects 300 peak-experience stories, so participation = 300 / 1,200 x 100 = 25%. If coding the stories shows that 180 of them mention rapid informal teamwork, that theme appears in 180 / 300 x 100 = 60% of the stories and becomes a strong candidate for the positive core.Case study
Seen in the real world.
A made-up hospital group, Northgate Health, faces bleak engagement scores. This case study is fictional and illustrative. Instead of another deficit audit, it runs appreciative inquiry across wards, collects 300 stories of exceptional patient care, finds rapid informal teamwork as the common thread, and redesigns shift handovers to protect exactly that. The leadership team does not drop its safety audits, which continue alongside the programme, because appreciation is not a substitute for fixing real risks.
It does, however, change the tone of ward meetings, which now begin with a story of care done well before turning to problems. After a year, the group checks whether the new handover routine is still in use on every ward and asks staff to tell fresh stories of what it makes possible. The follow-up shows which wards kept the change and which have slipped back.
Watch out
Common mistakes.
- Using it to avoid hard truths; appreciation is not denial. Run it alongside honest diagnosis when real failures threaten the organisation.
- Treating it as a feel-good workshop; without the Design and Destiny stages, nothing changes. Commit to building structures from the discovered strengths.
- Scripting the stories; the method's power comes from genuine participant voices. Let people tell their own peak moments rather than feeding them examples.
Questions
People also ask.
What is appreciative inquiry?
A change management approach that improves organisations by discovering and amplifying what works best, using structured storytelling and design rather than problem-focused diagnosis.
What are the stages of appreciative inquiry?
The classic 4-D cycle: Discovery of peak experiences, Dream of possibilities, Design of structures and propositions, and Destiny, where participants implement and sustain the changes.
When should appreciative inquiry not be used alone?
When genuine failures pose serious risk, such as safety, fraud or compliance breakdowns. Those need direct diagnosis, with appreciative methods supporting the wider change.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%