Appreciative Inquiry:
A Practical Guide to Building Change Around Strengths, Possibility and What Works

Appreciative Inquiry, often shortened to AI, is a strengths-based approach to organisational development, change and problem-solving.

At its simplest, Appreciative Inquiry asks:

What is already working well, why does it work, what future do we want to create, and how can we build more of it?

That makes it useful for leadership, organisational change, team development, strategy, culture, service improvement, charity governance, public sector transformation, education, healthcare, community development, customer experience, staff engagement and board planning.

Appreciative Inquiry is often described as a positive and collaborative approach to change. Rather than beginning with failure, deficit or blame, it begins by identifying strengths, successful experiences and the conditions that allow people and organisations to perform at their best. AI Commons describes the 5-D cycle as a practical process for change at levels ranging from one-to-one coaching to team building and whole-system change.

Used properly, Appreciative Inquiry is not about ignoring problems. It is about changing the starting point of the conversation so that improvement is built on evidence of what already gives life, energy and value to the organisation.

What is Appreciative Inquiry?

Appreciative Inquiry is a method for creating change by exploring strengths, successes, values, hopes and possibilities.

A traditional problem-solving approach often starts with:

1. What is wrong?
2. Why did it go wrong?
3. Who is responsible?
4. How do we fix the problem?
5. How do we stop it happening again?

That can be useful, especially where there are serious risks, compliance failures, safeguarding concerns, safety issues or financial weaknesses.

Appreciative Inquiry starts differently.

It asks:

1. When have we been at our best?
2. What made that possible?
3. What strengths already exist?
4. What do people value most?
5. What future do we want?
6. What would it look like if we had more of what works?
7. What practical steps would move us towards that future?

This makes the conversation more constructive.

It helps people move from blame, frustration or helplessness towards possibility, ownership and action.

A useful way to think about Appreciative Inquiry is:

Instead of asking only what problem needs fixing, it asks what strength can be built upon.

History and development of Appreciative Inquiry

Appreciative Inquiry developed within the field of organisational development.

It is most closely associated with David Cooperrider and Suresh Srivastva at Case Western Reserve University. Their 1987 work, Appreciative Inquiry in Organizational Life, helped establish Appreciative Inquiry as a different way of thinking about organisational change, moving away from purely deficit-based diagnosis towards inquiry into what gives life to organisations when they are at their best.

The approach became influential because many organisational change efforts were built around problems, gaps and weaknesses. That can identify issues, but it can also create defensiveness and fatigue. People can become trapped in a story that the organisation is broken.

Appreciative Inquiry offered a different premise:

Organisations grow in the direction of the questions they ask.

If people are only asked about failure, they may become focused on failure.

If they are asked about success, energy, values and possibility, they may discover resources that can be used for change.

Over time, Appreciative Inquiry has been applied in:

1. Organisational development
2. Leadership development
3. Culture change
4. Strategic planning
5. Team building
6. Community development
7. Healthcare improvement
8. Education
9. Charity and voluntary sector work
10. Public sector transformation
11. Coaching
12. Conflict resolution
13. Innovation
14. Staff engagement
15. Whole-system change

The method is now commonly associated with the 4-D cycle and the expanded 5-D cycle. The familiar 4-D model includes Discover, Dream, Design and Destiny or Deliver. Later versions often add Define at the beginning, creating the 5-D model: Define, Discover, Dream, Design and Destiny.

Why Appreciative Inquiry matters

Appreciative Inquiry matters because the way a question is framed shapes the answer.

Many organisations spend a great deal of time asking negative questions:

1. Why are staff disengaged?
2. Why are customers unhappy?
3. Why are projects late?
4. Why are teams not performing?
5. Why is communication poor?
6. Why do changes fail?
7. Why is morale low?

Those questions may be legitimate, but they can also create defensive answers.

Appreciative Inquiry reframes the conversation:

1. When have staff felt most engaged?
2. What created excellent customer experiences?
3. When have projects worked well?
4. What helps this team perform at its best?
5. When has communication been clear and useful?
6. What change has succeeded before?
7. What gives people energy and commitment?

This does not deny problems.

It simply looks for evidence of capability.

That matters because organisations often already contain examples of the future they want to create.

A business that wants better customer service may already have pockets of excellent customer service.

A charity that wants stronger collaboration may already have examples of excellent partnership working.

A public body that wants more resident-focused services may already have teams that do this well.

A professional firm that wants better client relationships may already have advisers who are trusted, proactive and commercially useful.

Appreciative Inquiry helps find those examples, understand them and scale the conditions that made them possible.

The 5-D cycle of Appreciative Inquiry

The 5-D cycle is one of the most common Appreciative Inquiry frameworks.

It includes:

1. Define
2. Discover
3. Dream
4. Design
5. Destiny

The Center for Appreciative Inquiry describes the 5-D process as Define, Discover, Dream, Design and Destiny, used to facilitate Appreciative Inquiry sessions and create shared vision and action.

1. Define

Define sets the focus of the inquiry.

It asks:

What do we want to explore, improve or create?

This is important because Appreciative Inquiry needs a clear topic.

The topic should be framed positively.

For example:

Weak topic:

Why is communication poor?

Stronger AI topic:

How can we create clearer, more useful and more trusted communication across the organisation?

Weak topic:

Why are staff disengaged?

Stronger AI topic:

What helps people feel motivated, valued and able to do their best work?

The Define stage should identify:

1. The subject of inquiry
2. The people involved
3. The purpose of the work
4. The desired direction
5. The boundaries of the inquiry
6. The practical output required
7. How the findings will be used

A good Define stage prevents the process becoming vague or sentimental.

2. Discover

Discover explores the best of what already exists.

It asks:

When has this worked well, and what made it work?

This stage often uses interviews, workshops, storytelling and group discussion.

Typical Discover questions include:

1. Tell me about a time when this team worked at its best.
2. When have we delivered excellent service?
3. What made that success possible?
4. What strengths were being used?
5. What conditions helped people perform well?
6. What relationships mattered?
7. What values were visible?
8. What systems or behaviours helped?
9. What can we learn from that experience?
10. What should we do more of?

The Discover stage is evidence-based.

It does not ask people to pretend everything is fine. It asks them to find real examples of success and understand the factors behind them.

3. Dream

Dream imagines the preferred future.

It asks:

What could this look like if we built on our strengths?

This stage encourages people to think beyond current constraints.

Possible Dream questions include:

1. What would the organisation look like at its best?
2. What would customers, service users or beneficiaries experience?
3. What would staff notice?
4. What would leaders do differently?
5. What would be easier, clearer or better?
6. What would we be proud of?
7. What would stakeholders say about us?
8. What strengths would be visible every day?
9. What would success look like in one year?
10. What would success look like in five years?

The Dream stage is not fantasy.

It should be ambitious but grounded in what was discovered.

The point is to create a shared picture of what the organisation wants to build.

4. Design

Design turns the desired future into practical choices, structures, behaviours and commitments.

It asks:

What needs to be designed, changed or strengthened to make the dream possible?

This may include:

1. Processes
2. Roles
3. Systems
4. Services
5. Behaviours
6. Governance
7. Communication
8. Training
9. Culture
10. Customer journeys
11. Decision-making
12. Performance measures
13. Meetings
14. Policies
15. Partnerships

Possible Design questions include:

1. What must be in place for this future to happen?
2. What processes would support it?
3. What behaviours should become normal?
4. What should leaders do more consistently?
5. What should teams do differently?
6. What systems or structures need changing?
7. What should we stop doing?
8. What should we start doing?
9. What should we protect?
10. What practical commitments can we make?

The Design stage turns positive thinking into operating reality.

5. Destiny

Destiny, sometimes called Deliver, focuses on action, learning and sustained change.

It asks:

What will we do, who will do it, and how will we keep momentum?

This stage may include:

1. Action plans
2. Owners
3. Milestones
4. Experiments
5. Pilot projects
6. Communication
7. Review points
8. Success measures
9. Accountability
10. Learning loops

Possible Destiny questions include:

1. What is the first action?
2. Who will lead it?
3. Who needs to be involved?
4. What can be piloted quickly?
5. What will show progress?
6. What support is needed?
7. What could block momentum?
8. How will we review progress?
9. How will we keep people engaged?
10. What will we celebrate and learn from?

This stage is where Appreciative Inquiry becomes practical change.

Without action, it remains an interesting conversation.

Appreciative Inquiry compared with traditional problem-solving

Traditional problem-solving is often based on finding and fixing deficits.

It can be effective when there is a clear fault, failure or gap.

For example:

1. A process is broken.
2. A control has failed.
3. A safety issue exists.
4. A deadline has been missed.
5. A customer complaint must be resolved.
6. A statutory duty has not been met.
7. A system error needs correction.

Appreciative Inquiry is different.

It is more useful when the organisation needs energy, engagement, culture change, collaboration, learning or shared ownership.

Traditional problem-solving asks:

What is wrong and how do we fix it?

Appreciative Inquiry asks:

What is working and how do we build on it?

Both can be useful.

The mistake is thinking only one approach is valid.

A serious safeguarding issue should not be handled only through positive inquiry.

A culture change programme should not be handled only through fault-finding.

The right approach depends on the situation.

When to use Appreciative Inquiry

Appreciative Inquiry is useful where engagement, culture, collaboration and shared ownership matter.

Good uses include:

1. Team development
2. Staff engagement
3. Leadership development
4. Culture change
5. Organisational values
6. Strategy workshops
7. Customer experience improvement
8. Service redesign
9. Charity development
10. Public sector transformation
11. Community engagement
12. Board away days
13. Partnership working
14. Volunteer engagement
15. Innovation workshops
16. Coaching
17. Conflict recovery
18. Change programmes
19. Mergers and integration
20. Learning from success

It is especially useful where:

1. Morale is low.
2. Change fatigue is high.
3. People feel blamed.
4. The organisation needs a more constructive conversation.
5. There are examples of good practice to build upon.
6. The issue is complex and relational.
7. Stakeholder ownership matters.
8. The desired change requires behaviour and culture change.

It is less useful where there is an urgent compliance failure, immediate safety risk, fraud concern or unresolved serious incident requiring formal investigation.

In those cases, Appreciative Inquiry may still help later with learning and culture, but it should not replace proper investigation, accountability or risk control.

Appreciative Inquiry in different industries

SMEs and owner-managed businesses

For SMEs, Appreciative Inquiry can help business owners and teams identify what already works and use it to improve the wider business.

Typical uses include:

1. Improving customer service
2. Building a stronger team culture
3. Reducing owner dependency
4. Improving internal communication
5. Developing managers
6. Strengthening sales behaviours
7. Improving staff retention
8. Identifying what makes the business special
9. Supporting growth
10. Creating a clearer service proposition

An SME might ask:

1. When have customers been most delighted?
2. What did we do differently in those cases?
3. When has the team solved a problem well?
4. What strengths make this business valuable?
5. What do staff enjoy doing well?
6. What would the business look like if we had more of that?
7. What can we design into our normal processes?

For owner-managed businesses, AI can be particularly useful because many strengths are informal. The business may work well because of personal relationships, judgement, responsiveness and trust. Appreciative Inquiry helps identify those strengths so they can be protected, developed and shared.

Manufacturing

Manufacturing businesses can use Appreciative Inquiry for quality improvement, safety culture, teamwork, production reliability and continuous improvement.

Typical uses include:

1. Learning from high-performing shifts
2. Improving safety culture
3. Reducing rework by studying successful production runs
4. Improving maintenance behaviours
5. Strengthening supervisor communication
6. Improving cross-functional working
7. Supporting lean improvement
8. Improving supplier collaboration
9. Increasing staff engagement
10. Building pride in workmanship

A manufacturer might ask:

1. When has this production line performed at its best?
2. What made that shift successful?
3. What behaviours helped prevent defects?
4. When have safety conversations worked well?
5. What does excellent handover look like?
6. What can we learn from the teams with the best quality results?
7. How can we design more of those conditions into normal work?

For manufacturing, Appreciative Inquiry should complement data-driven quality, safety and operational control. It should not replace root cause analysis where defects or incidents require technical investigation.

Retail and ecommerce

Retail and ecommerce businesses can use Appreciative Inquiry to improve customer experience, retention, service culture and team performance.

Typical uses include:

1. Understanding excellent customer reviews
2. Improving customer service
3. Strengthening brand experience
4. Learning from successful promotions
5. Improving fulfilment teamwork
6. Reducing returns through positive examples
7. Improving staff engagement
8. Strengthening store culture
9. Improving online customer journeys
10. Building repeat purchase behaviour

A retailer might ask:

1. Which customer experiences have created excellent reviews?
2. What did we do that made the customer feel valued?
3. When has fulfilment worked especially smoothly?
4. What makes customers come back?
5. Which products create the strongest loyalty?
6. What would our ideal customer experience feel like?
7. What can we build into training and process?

For ecommerce, AI can help connect data with human insight. Analytics may show what happened. Appreciative Inquiry can help understand why customers or teams responded positively.

Professional services

Professional services firms can use Appreciative Inquiry for client relationships, advisory development, quality, culture and team learning.

Typical uses include:

1. Learning from excellent client feedback
2. Developing advisory services
3. Improving client onboarding
4. Strengthening internal review culture
5. Supporting staff development
6. Improving cross-team communication
7. Building a coaching culture
8. Reducing deadline pressure through positive practice
9. Clarifying firm values
10. Improving client retention

For accountants, solicitors, consultants, architects and advisers, AI might ask:

1. When have we delivered real value to a client?
2. What made that engagement work well?
3. When did a client trust our advice?
4. What behaviours created that trust?
5. Which client meetings felt most useful?
6. What strengths do our best client relationships rely on?
7. How can we design more of that into normal service delivery?

Professional services firms often focus heavily on errors, deadlines and compliance. That is necessary, but AI can add balance by studying excellent practice and scaling it.

Charities and voluntary organisations

Charities can use Appreciative Inquiry to strengthen mission, volunteering, impact, staff engagement, partnerships and trustee development.

Typical uses include:

1. Volunteer engagement
2. Staff wellbeing
3. Service improvement
4. Beneficiary voice
5. Impact storytelling
6. Partnership development
7. Trustee away days
8. Funding strategy
9. Community engagement
10. Culture and values work

A charity might ask:

1. When have we made the biggest difference to a family, person or community?
2. What made that possible?
3. What do beneficiaries value most about our work?
4. When have volunteers felt most connected?
5. When have partnerships worked well?
6. What strengths should we protect as we grow?
7. What would our charity look like at its best?

For charities, Appreciative Inquiry is particularly powerful because it can reconnect people with purpose. However, it should still sit alongside safeguarding, risk management, financial control and proper governance.

Public sector and local government

Public bodies can use Appreciative Inquiry in service redesign, community engagement, workforce development and cultural change.

Typical uses include:

1. Resident engagement
2. Service improvement
3. Staff morale
4. Cross-department working
5. Transformation programmes
6. Partnership working
7. Community development
8. Leadership development
9. Equality and inclusion conversations
10. Preventative service design

A public body might ask:

1. When have residents experienced the service at its best?
2. What made that possible?
3. When have teams worked across boundaries well?
4. What conditions supported that collaboration?
5. When has public engagement been constructive?
6. What would a more responsive service look like?
7. What can we design into future delivery?

For public services, AI can help create more constructive conversations with staff and communities, especially where traditional consultation becomes defensive or adversarial.

Property and construction

Property and construction organisations can use Appreciative Inquiry for stakeholder engagement, project learning, safety culture, tenant relationships and regeneration planning.

Typical uses include:

1. Learning from successful projects
2. Improving contractor relationships
3. Strengthening safety culture
4. Improving tenant communication
5. Supporting regeneration engagement
6. Identifying what makes a place work
7. Improving project handovers
8. Reducing conflict
9. Creating shared vision
10. Building community support

A property or construction team might ask:

1. When has a project run especially well?
2. What made the contractor relationship work?
3. When have tenants felt properly informed?
4. What creates trust with local stakeholders?
5. When has site safety culture been strong?
6. What would a successful regeneration outcome feel like?
7. What should be built into the next phase?

For property and construction, AI should complement technical due diligence, risk registers, planning analysis, cost control and health and safety processes.

Technology and software

Technology teams can use Appreciative Inquiry for product development, user experience, agile teamwork, customer success and culture.

Typical uses include:

1. Understanding excellent user outcomes
2. Improving product adoption
3. Learning from successful releases
4. Strengthening agile retrospectives
5. Improving developer collaboration
6. Reducing support friction
7. Building customer success culture
8. Improving onboarding
9. Supporting innovation
10. Scaling good practice

A software team might ask:

1. When have users adopted a feature quickly?
2. What made that feature valuable?
3. When has a release gone smoothly?
4. What did the team do differently?
5. When did support resolve an issue brilliantly?
6. What does excellent collaboration look like here?
7. How can we design more of that into product and process?

For technology businesses, AI can help balance the tendency to focus only on bugs, defects and technical debt. Those matter, but so does learning from what users love and teams do well.

Healthcare and social care

Healthcare and social care organisations can use Appreciative Inquiry for quality improvement, staff morale, patient experience, safeguarding culture and service redesign.

Typical uses include:

1. Learning from excellent care
2. Improving staff engagement
3. Strengthening team communication
4. Improving patient or service user experience
5. Supporting quality improvement
6. Building safer handover practices
7. Improving family communication
8. Strengthening supervision
9. Reducing burnout
10. Supporting compassionate leadership

A care provider might ask:

1. When have we delivered care that made us proud?
2. What made that care possible?
3. When have handovers worked well?
4. What helps staff feel supported?
5. When have families felt reassured?
6. What conditions support safe and dignified care?
7. How can we build more of those conditions into everyday practice?

In healthcare and care, Appreciative Inquiry should never replace incident reporting, safeguarding procedures or clinical governance. It can, however, help organisations learn from excellence as well as from failure.

Education and training

Education providers can use Appreciative Inquiry for learner engagement, teaching quality, staff development, employer partnerships and curriculum improvement.

Typical uses include:

1. Learning from successful teaching
2. Improving learner engagement
3. Strengthening employer partnerships
4. Supporting staff development
5. Improving learner progression
6. Building inclusive culture
7. Improving feedback
8. Strengthening safeguarding culture
9. Developing curriculum
10. Improving attendance and retention

An education provider might ask:

1. When have learners been most engaged?
2. What made that learning experience successful?
3. When have learners overcome barriers well?
4. What support made the difference?
5. When have employer partnerships worked best?
6. What does excellent teaching look like here?
7. How can we design more of that into delivery?

For education, Appreciative Inquiry can support improvement by focusing on what helps learners thrive, not only what causes underperformance.

How to carry out Appreciative Inquiry properly

1. Define the topic positively

Start by choosing the focus.

The topic should be important, relevant and framed positively.

For example:

Instead of:

Why is morale low?

Use:

How can we create a workplace where people feel valued, trusted and able to do their best work?

Instead of:

Why are customers complaining?

Use:

What creates excellent customer experiences, and how can we make them more consistent?

A positive topic does not ignore the problem. It reframes the inquiry around the desired direction.

2. Involve the right people

Appreciative Inquiry works best when it includes the people affected by the change.

This may include:

1. Staff
2. Managers
3. Directors
4. Trustees
5. Volunteers
6. Customers
7. Service users
8. Beneficiaries
9. Suppliers
10. Partners
11. Community representatives
12. Professional advisers
13. Board members
14. Frontline teams
15. Support teams

The right mix depends on the topic.

If the issue affects frontline delivery, frontline voices must be included.

If the issue affects customers or beneficiaries, their experience should be understood.

3. Ask good questions

Questions are central to Appreciative Inquiry.

Good AI questions are:

1. Open
2. Positive
3. Specific
4. Experience-based
5. Forward-looking
6. Curious
7. Non-blaming
8. Practical
9. Values-led
10. Action-oriented

Examples include:

1. Tell me about a time when this worked really well.
2. What made that possible?
3. What strengths were present?
4. What did people do that helped?
5. What conditions supported success?
6. What did you value most?
7. What could we learn from that?
8. What would it look like if this happened more often?
9. What would be different?
10. What small step could we take now?

Poor AI questions are vague, leading or superficial.

For example:

Everything is great, isn’t it?

That is not inquiry. That is avoidance.

4. Collect real stories

Appreciative Inquiry relies on real examples.

Stories help identify what works in practice.

For example:

1. A customer interaction that went exceptionally well
2. A project that delivered under pressure
3. A team that solved a difficult problem
4. A volunteer who felt deeply connected to the mission
5. A service user who received life-changing support
6. A staff member who felt trusted and empowered
7. A partnership that created real value
8. A process that worked smoothly
9. A manager who supported a team effectively
10. A change that people embraced

Stories reveal conditions, behaviours and values that spreadsheets may miss.

5. Identify themes

After collecting stories, look for patterns.

Common themes might include:

1. Trust
2. Clear communication
3. Good leadership
4. Shared purpose
5. Quick decision-making
6. Strong relationships
7. Customer understanding
8. Practical support
9. Empowerment
10. Good systems
11. Recognition
12. Clear roles
13. Learning culture
14. Teamwork
15. Flexibility

The aim is to understand what enables success.

6. Create a shared future

Use the themes to imagine the desired future.

Ask:

1. What would it look like if these strengths were present every day?
2. What would staff experience?
3. What would customers or service users experience?
4. What would be easier?
5. What would be more effective?
6. What would be more consistent?
7. What would people be proud of?
8. What would stakeholders notice?
9. What would success feel like?
10. What outcomes would improve?

This future should be inspiring, but not vague.

It should be clear enough to design action around.

7. Design practical changes

Turn the future into practical design choices.

This may include:

1. Changing meeting structures
2. Improving onboarding
3. Redesigning customer communication
4. Strengthening supervision
5. Creating new service standards
6. Updating processes
7. Improving training
8. Changing decision rights
9. Creating recognition routines
10. Improving reporting
11. Redesigning roles
12. Strengthening partnerships
13. Improving feedback loops
14. Changing performance measures
15. Creating new pilot projects

This stage should connect the desired future to daily work.

8. Agree commitments

Appreciative Inquiry should lead to commitments.

These may be:

1. Individual commitments
2. Team commitments
3. Leadership commitments
4. Board commitments
5. Service commitments
6. Customer commitments
7. Partnership commitments
8. Process commitments
9. Training commitments
10. Governance commitments

Commitments should be specific enough to review.

For example:

Weak commitment:

We will communicate better.

Stronger commitment:

Team leaders will hold a 15-minute weekly update meeting every Monday morning to clarify priorities, risks and support needed.

9. Build momentum through action

Start with practical actions that create visible progress.

Examples include:

1. Pilot a new approach.
2. Share success stories.
3. Change one meeting format.
4. Improve one customer touchpoint.
5. Create one new feedback loop.
6. Recognise examples of desired behaviour.
7. Train managers in appreciative conversations.
8. Redesign one process.
9. Build one partnership.
10. Review progress after 30 days.

Momentum matters.

Appreciative Inquiry works best when people see that the conversation leads to action.

10. Review and learn

Review progress regularly.

Ask:

1. What has changed?
2. What is working?
3. What have we learned?
4. What should we do more of?
5. What is still difficult?
6. What support is needed?
7. What should be adapted?
8. What new strengths have emerged?
9. What stories show progress?
10. What should happen next?

The review should itself be appreciative, but honest.

Common Appreciative Inquiry techniques

Appreciative interviews

These are structured conversations focused on positive experience, strengths and possibility.

They often ask people to tell stories about when things worked well.

Storytelling workshops

Participants share examples of success and identify themes.

This is useful for culture, service improvement and team development.

Positive topic choice

The issue is framed around the desired future rather than the problem.

For example:

Creating excellent customer experiences rather than reducing complaints.

Strength mapping

The organisation identifies existing strengths, capabilities, relationships, values and success factors.

Dream workshops

Participants imagine what the organisation, team or service could look like at its best.

Design sessions

Participants translate the desired future into practical changes.

Appreciative retrospectives

Teams review what worked well, what made it possible, and how to build on it.

This is useful in project management, agile teams and continuous improvement.

Positive deviance inquiry

This looks for people or teams who are already achieving better results in the same conditions, then studies what they do differently.

Common mistakes in Appreciative Inquiry

Mistake 1: Treating it as positive thinking

Appreciative Inquiry is not simply being cheerful.

It is a structured inquiry into evidence of success and the conditions that make success possible.

Mistake 2: Ignoring real problems

AI should not be used to avoid difficult issues.

If there are serious risks, failures or harms, they must still be addressed.

Mistake 3: Asking vague questions

Questions such as “What is good?” are too broad.

Ask for specific stories and examples.

Mistake 4: Choosing the wrong topic

A poorly framed topic weakens the whole process.

The topic should be positive, important and actionable.

Mistake 5: Excluding key people

If the process only involves senior leaders, it may miss frontline reality.

AI works best when the right voices are included.

Mistake 6: Creating an unrealistic dream

The Dream stage should be ambitious, but it should still be connected to real strengths and organisational purpose.

Mistake 7: Failing to turn insight into action

A good workshop is not enough.

There must be practical design, ownership and follow-up.

Mistake 8: Using AI where investigation is needed

Appreciative Inquiry should not replace formal investigation, safeguarding action, health and safety review, fraud investigation or regulatory compliance.

Mistake 9: No leadership commitment

If leaders do not act differently after the process, people may become cynical.

Mistake 10: Not sustaining the change

AI is not a one-off event.

The learning should be built into systems, behaviours, meetings, governance and culture.

Limitations and weaknesses of Appreciative Inquiry

Appreciative Inquiry is useful, but it has limits.

It can feel uncomfortable in crisis

If people are dealing with serious harm, loss, failure or conflict, a positive framing may feel inappropriate unless handled carefully.

It can be misused to avoid accountability

Leaders may use AI language to avoid discussing failure.

That is not good practice.

It depends on skilled facilitation

Poor facilitation can make the process feel superficial.

A good facilitator helps people stay positive without becoming unrealistic.

It may underplay structural problems

Some issues are not solved by better conversations alone.

There may be real problems with funding, staffing, systems, governance, power, workload or inequality.

It can exclude dissenting voices

If the process becomes too positive, people may feel unable to raise concerns.

A strong AI process makes room for challenge, but frames it constructively.

It can become vague

Without clear design and action, AI can produce inspiring words but little change.

It does not replace risk management

Risk registers, issue logs, internal audit, safeguarding processes and compliance controls are still needed.

It may not suit every culture immediately

In some organisations, people may be sceptical of positive inquiry if they have experienced poor leadership, broken promises or change fatigue.

Trust may need rebuilding first.

Appreciative Inquiry compared with other strategic and management tools

Appreciative Inquiry and SWOT

SWOT identifies strengths, weaknesses, opportunities and threats.

Appreciative Inquiry focuses especially on strengths, success stories and preferred futures.

Use SWOT for broad diagnosis. Use Appreciative Inquiry to build energy and action around what works.

Appreciative Inquiry and SOAR

SOAR stands for Strengths, Opportunities, Aspirations and Results.

It is closely aligned with Appreciative Inquiry because both focus on strengths and desired outcomes.

Use SOAR as a strategic framework. Use Appreciative Inquiry as the conversational and change process behind it.

Appreciative Inquiry and problem-solving

Problem-solving identifies causes of failure and fixes them.

Appreciative Inquiry identifies causes of success and builds on them.

Both are useful. The right choice depends on context.

Appreciative Inquiry and root cause analysis

Root cause analysis looks backwards from a problem to understand why it happened.

Appreciative Inquiry looks at successful examples to understand what made them possible.

Use root cause analysis for failures. Use AI for learning from success and designing positive change.

Appreciative Inquiry and roadmapping

Roadmapping turns strategy into phased action.

Appreciative Inquiry can identify the desired future and strengths that the roadmap should build upon.

Appreciative Inquiry and backforecasting

Backforecasting starts with a desired future and works backwards.

Appreciative Inquiry can help define that future by involving people in Discover and Dream conversations.

Appreciative Inquiry and stakeholder analysis

Stakeholder analysis identifies who matters and how they may be affected.

Appreciative Inquiry can engage those stakeholders constructively in shaping the desired future.

Appreciative Inquiry and change management

Change management focuses on helping people move from current state to future state.

Appreciative Inquiry can strengthen change management by creating ownership, energy and shared meaning.

Appreciative Inquiry and Balanced Scorecard

The Balanced Scorecard tracks strategic performance.

Appreciative Inquiry can help identify the behaviours, strengths and cultural conditions needed to improve performance.

Appreciative Inquiry and OKRs

OKRs define objectives and key results.

Appreciative Inquiry can help create engagement around the objectives and identify strengths that support delivery.

Alternatives and complementary frameworks

SOAR analysis

Use SOAR to structure strengths-based strategy around strengths, opportunities, aspirations and results.

Best used where the organisation wants a positive alternative to SWOT.

SWOT analysis

Use SWOT for a balanced view of internal and external factors.

Best used where strengths and weaknesses both need consideration.

Root cause analysis

Use root cause analysis when there is a failure, defect, complaint, incident or issue that needs investigation.

Theory of change

Use theory of change to map how activities create outcomes and impact.

Best used in charities, public services and social impact work.

Design thinking

Use design thinking to understand users, prototype solutions and improve services or products.

It can work well with Appreciative Inquiry where customer or service user experience matters.

Change management frameworks

Use change management frameworks to plan communication, sponsorship, resistance management, training and adoption.

Roadmapping

Use roadmapping to turn the preferred future into phases, milestones and actions.

Stakeholder engagement

Use stakeholder engagement to make sure the right people are involved and heard.

Internal audit

Use internal audit where independent assurance is needed over controls, governance or risk management.

Risk register

Use a risk register to manage risks identified during AI discussions.

A practical Appreciative Inquiry template

A useful Appreciative Inquiry template should include:

1. Inquiry topic
2. Purpose
3. Scope
4. Participants
5. Stakeholders
6. Define question
7. Discover questions
8. Success stories collected
9. Strengths identified
10. Themes identified
11. Dream statement
12. Design principles
13. Practical changes required
14. Actions
15. Owners
16. Deadlines
17. Measures of success
18. Risks and barriers
19. Review date
20. Learning and next steps

Example:

Inquiry topic: Creating excellent client communication

Purpose: Improve client experience and reduce confusion during project delivery.

Discover question: Tell me about a time when a client felt fully informed, reassured and confident in our work. What made that happen?

Themes identified: Clear ownership, proactive updates, plain English, early warning of issues, fast responses, honest advice.

Dream statement: Clients feel informed, respected and confident because communication is clear, timely and useful.

Design principles:

1. Every client has a named contact.
2. Updates are sent before clients need to chase.
3. Technical points are explained in plain English.
4. Delays are communicated early.
5. Client questions are acknowledged within one working day.

Actions:

1. Create client update template.
2. Agree communication standards.
3. Train staff on plain English updates.
4. Review feedback after three months.

Owner: Operations Manager.

Review date: Quarterly.

Questions to ask during Appreciative Inquiry

Define questions

1. What topic do we want to explore?
2. Why does it matter?
3. How can we frame it positively?
4. Who should be involved?
5. What outcome do we want?
6. What is in scope?
7. What is out of scope?
8. How will findings be used?
9. What decision or action should follow?
10. How will we know the inquiry has been useful?

Discover questions

1. When have we been at our best?
2. What made that possible?
3. What strengths were present?
4. What behaviours helped?
5. What relationships mattered?
6. What values were visible?
7. What did customers, service users or stakeholders value?
8. What conditions supported success?
9. What can we learn from that example?
10. What should we do more of?

Dream questions

1. What would this look like at its best?
2. What would people experience?
3. What would customers or service users notice?
4. What would staff feel proud of?
5. What would be different from today?
6. What strengths would be used more often?
7. What would success look like in one year?
8. What would success look like in five years?
9. What would stakeholders say?
10. What future is worth working towards?

Design questions

1. What needs to be designed differently?
2. What processes should change?
3. What behaviours should become normal?
4. What systems would support the future?
5. What roles need clarity?
6. What meetings or routines should change?
7. What training is needed?
8. What communication should improve?
9. What should we stop doing?
10. What should we start doing?

Destiny questions

1. What action will we take first?
2. Who owns it?
3. What deadline applies?
4. What resources are needed?
5. What can be piloted?
6. What will show progress?
7. What might block momentum?
8. How will we review progress?
9. How will we keep people involved?
10. What will we learn and adapt?

Governance questions

1. Who is sponsoring the process?
2. Who will approve actions?
3. How will progress be reported?
4. How will risks be managed?
5. How will dissenting views be heard?
6. How will the process avoid becoming superficial?
7. How will outcomes link to strategy?
8. How will actions link to owners and deadlines?
9. How will learning be captured?
10. How will change be sustained?

The best way to think about Appreciative Inquiry

Appreciative Inquiry is not positive thinking.

It is disciplined inquiry into what works.

A good Appreciative Inquiry process should be:

1. Strengths-based
2. Evidence-based
3. Inclusive
4. Practical
5. Future-focused
6. Honest
7. Well-facilitated
8. Linked to action
9. Connected to strategy
10. Reviewed regularly

A weak Appreciative Inquiry process says:

“Let’s only talk about the positives.”

A strong Appreciative Inquiry process asks:

“When have we been at our best, what made that possible, and how can we build more of it?”

The key question is not simply:

What is going well?

The better question is:

What can our best experiences teach us about the future we want to create and the actions we need to take now?

Conclusion: Appreciative Inquiry turns strengths into practical change

Appreciative Inquiry remains useful because organisations do not improve only by analysing failure.

They also improve by understanding success.

Every organisation has examples of good work, strong relationships, committed people, effective processes, trusted services and moments when things came together well. Those examples are not accidents. They contain clues.

Used badly, Appreciative Inquiry becomes superficial positivity.

Used properly, it becomes a practical organisational development tool. It helps people identify strengths, learn from success, imagine a better future, design practical changes and commit to action.

The real value is not in avoiding problems.

The real value is in creating a more constructive route to improvement.

A strong Appreciative Inquiry process helps an organisation move from saying, “What is wrong with us?” to asking, “When are we at our best, what makes that possible, and how do we build from there?”