Appreciative Inquiry: Solve Problems by Studying Success
The appreciative inquiry method flips the usual problem-hunt: instead of opening a review with "what went wrong?", you ask "when was the team at its best?", study what made those moments possible, and turn those conditions into things to do more of. Reverse-engineering success makes strengths as actionable as failures — and far more motivating to act on.
Most retrospectives are autopsies. The team gathers, hunts for what failed, and leaves a little more deflated than it arrived. That has its place — problems do need fixing — but a relentless focus on what's broken drains energy and quietly ignores half the available information: the things that went right, which usually contain the very ingredients you most want to repeat. The appreciative inquiry method deliberately starts from there, treating success as a subject worth dissecting rather than a happy accident.
Why a problem-only focus leaves value on the table
When you only ask "what went wrong?", you learn how to avoid failure but never how to reproduce excellence — and those aren't the same skill. A team can eliminate every error and still be mediocre. Worse, problem-only reviews are demoralizing: people leave feeling like a list of deficiencies. Studying success fixes both gaps. It surfaces the conditions behind your best work so you can engineer more of them, and it sends people back to work energized rather than chastened. The point isn't to ignore problems — it's to mine your wins for repeatable causes, which a failure-hunt never does.
What is appreciative inquiry and how do I use it?
You need a team, a recent stretch of work to reflect on, and about thirty minutes.
- Open with "a story of when the team was at its best." Instead of "what failed this sprint?", ask each person to recall a specific moment when the team really clicked — a problem solved beautifully, a stretch where the work flowed.
- Have people share those moments. Go around and let each person tell their story concretely. You're collecting real instances of the team at its peak, not abstract praise.
- Ask what made each one possible. This is the analytical heart. For every great moment, dig into the conditions: Who was involved? What was the setup, the pace, the communication, the autonomy? Treat success like a case study with causes.
- Turn those conditions into things to do more of. Convert the recurring ingredients into concrete commitments. If the best moments all featured small autonomous sub-teams, decide to structure more work that way. This is what makes appreciative inquiry actionable rather than just pleasant.
A worked example
A team that's been struggling tries an appreciative-inquiry retro. Asked for their best moment, three people independently describe the same week: a gnarly bug they fixed in two days flat. Digging into why it went so well, a pattern emerges — that week, they'd dropped all other meetings, paired up directly, and had a clear single goal. The "condition behind the success" is suddenly obvious and reusable. The team commits to declaring a focused, meeting-free "war week" for their next hard problem. They didn't ignore their struggles; they found, inside a win, a concrete structure to repeat — something a "what went wrong?" retro would never have produced.
When appreciative inquiry is most useful
It's a strong choice for a demoralized team that needs energy, for retros that have become repetitive gripe sessions, and for any moment where you want to identify and scale what's already working. It pairs well with traditional problem-solving — alternate the two so you both fix what's broken and amplify what's strong. It's less appropriate right after a serious failure that genuinely needs a blameless root-cause analysis; forcing positivity there feels evasive. Used honestly, though, it's not toxic positivity — it's rigorous study of success.
The takeaway
You can't build excellence by only studying failure; you have to study what greatness looked like and figure out how to repeat it. Appreciative inquiry opens with your best moments, mines them for the conditions that made them possible, and turns those into commitments. Try it at your next retro — your team will leave with a plan and, for once, some momentum.
This is one of Funstorming's 100 quests — bite-sized soft skills methods you actually put into practice, not just read about. Try it, then bring your result (or your sticking point) to the Funstorming community of practice (CoP), FunHub | Your Soft Skills Playground.
#funstorming #softskills