What is it?

An Appreciative Inquiry Summit brings an entire system into one room to discover what it does best, dream about what it could become, design the structures to get there, and commit to action. It follows the 4D cycle (Discover, Dream, Design, Destiny) across one to four days, with mixed stakeholder tables doing the thinking. Instead of diagnosing problems and building solutions around gaps, the Summit builds strategy from strengths. Participants interview each other about peak experiences, map the organisation's "positive core," co-create bold visions, and self-organise into action teams before they leave the room. It is loud, fast, and generative. When it works, people leave not just aligned but energised, because they built the plan themselves.

Also Known As

• AI Summit
• Large-Scale AI

When to Use It

• You need strategic alignment across an entire organisation or community and want the people who will deliver the strategy to shape it.
• A merger, restructuring, or major transition is underway and you want to build a shared identity from the start rather than imposing one.
• Multiple stakeholder groups (employees, customers, suppliers, community members) need to plan together and traditional top-down planning has left people disengaged.
• The organisation is stuck in a deficit-based cycle of problem analysis and wants to shift the conversation toward what is working and what is possible.
• You have a strategic question that requires creative thinking and broad ownership, not just executive sign-off.
• There is enough leadership support to act on what comes out of the room. The Summit only works if something happens afterwards.

When NOT to Use It

• Leadership has already decided the answer and wants the Summit to rubber-stamp it. People will spot the manipulation and trust will drop.
• The organisation is in immediate crisis that requires rapid top-down decisions. A Summit takes weeks to plan and days to run. There is no shortcut.
• You have fewer than 20 participants. Below that threshold, smaller AI processes or a facilitated planning day will do the job without the overhead.
• There is no budget or willingness to follow through. A Summit that generates excitement but leads to nothing is worse than never running one.
• Key decision-makers refuse to attend. Without people who can authorise action, the Summit produces wish lists rather than commitments.
• Deep interpersonal conflict needs to be resolved first. The Summit is not a conflict resolution process. Unresolved tension will derail the generative work.

The Appreciative Inquiry Summit was developed by David Cooperrider, Diana Whitney, and colleagues at Case Western Reserve University in the late 1990s and early 2000s. It grew from Cooperrider and Suresh Srivastva's original Appreciative Inquiry theory (1987), which challenged the assumption that organisations improve only by fixing what is broken. Inspired by the Search Conference method, Cooperrider adapted the 4D cycle into a large-group format and first used it at scale with GTE (now Verizon) and the United Religions Initiative. The definitive practitioner guide was published by James Ludema, Diana Whitney, Bernard Mohr, and Thomas Griffin in 2003 as The Appreciative Inquiry Summit: A Practitioner's Guide for Leading Large-Group Change.

What You Need

Group size: 20 to 1,000+. The sweet spot for a first Summit is 60 to 300. Below 20, use a smaller AI process. Above 300, you need a very experienced design team and a large venue.

Time required:

• Minimum one full day (compressed, covers all 4Ds at pace).
• Typical is two to three days.
• Extended versions run four days with deeper discovery and more design iterations.

Space:

• A single large room with round tables seating 6 to 8 people each (mixed stakeholder groups)
• Enough floor space for people to move between tables without squeezing
• Wall space for posting outputs (provocative propositions, design prototypes, action plans)
• A stage or raised area for plenary moments
• Breakout space is helpful but not essential since the work happens at the tables

Materials:

• Round tables with chairs (not classroom-style rows)
• Flip chart paper and markers for every table
• Large sticky notes (A5 or larger) and standard sticky notes
• Pre-printed participant workbooks with the interview guide, dream prompts, and design templates
• Microphones (roving and fixed) if the group is over 50
• A "positive core" wall: a large blank wall or set of boards for posting discovery themes
• Projector and screen for plenary instructions and shared visuals
• Dot stickers for voting and prioritisation
• Name badges that include the person's role and stakeholder group
• Timer visible to the whole room (projected countdown works well)
• A bell, chime, or music system to signal transitions
• Pre-assigned table maps showing where each person sits for each round

The Process

Setup

1. Form a steering committee 6 to 12 weeks before the Summit. Include representatives from every stakeholder group. Their job is to define the Summit's affirmative topic (the strategic question framed in positive terms) and the participant list.
2. Craft the affirmative topic. This is the single most important design decision. Instead of "How do we fix our customer service problems?" the topic becomes "What does world-class customer experience look like when we are at our best?" The topic shapes every interview question and design task.
3. Build the interview guide. Write 6 to 10 appreciative questions tied to the affirmative topic. These are the questions pairs will use during Discovery. Test them with the steering committee and revise until they generate rich stories, not one-word answers.
4. Create the participant workbook. Include the interview guide, space for notes, dream prompts, design templates, and the day's agenda. Print one per person.
5. Design the table assignments. Each table should be a maximum-mix of roles, departments, levels, and stakeholder groups. Plan different table assignments for different phases so people work with new combinations throughout the Summit.
6. Brief table facilitators. Recruit one volunteer per table (from inside the organisation if possible). Give them a half-day orientation covering the 4D cycle, their role in keeping conversations positive and on track, and timing cues.
7. Prepare the room the evening before. Set tables, lay out workbooks, test AV, and post the agenda and affirmative topic on the walls.

Step 1: Opening and Framing

Time: 30 to 45 minutes

Purpose: Set the tone, explain why everyone is here, and establish the ground rules for how the Summit works.

1. A senior leader opens by explaining why this Summit matters and what the organisation is ready to do with whatever comes out of the room. This is not a motivational speech. It is a commitment. "We are here because the decisions we make over the next two days will shape our direction. I am here to listen and to act on what this room creates."
2. The lead facilitator introduces the 4D cycle in plain language. "We are going to do four things: discover what we do brilliantly, dream about what we could become, design the structures to make that real, and commit to action before we leave."
3. Explain the ground rules: everyone has equal voice regardless of title, conversations build on strengths, and the work happens at the tables, not in plenary lectures.
4. Run a brief "connection starter" at each table. A simple round of introductions using a question like "What is one thing you are proud of about this organisation?" This gets people talking before the formal interviews begin.

Watch for: Cynicism in the room, especially from people who have been through failed change programmes. Acknowledge it. "Some of you have been to events like this before and nothing happened. That is a fair concern. Here is what is different this time..." Then hand to the leader to reinforce the commitment.

Step 2: Discover

Time: 90 minutes to half a day (depending on Summit length)

Purpose: Surface the organisation's positive core through paired interviews and collective theme-finding.

1. Pair people at their tables (one interviewer, one storyteller). Give them 15 to 20 minutes each way to work through the interview guide. "Your job is to listen for the story behind the story. When they say 'it was a great project,' ask them what made it great. What did they do? Who else was involved? What conditions allowed it to happen?"
2. After both interviews, each pair shares the best story they heard with their table (not their own story, their partner's). The table captures the key themes on a flip chart.
3. Tables post their top 3 to 5 themes on the positive core wall. The lead facilitator walks the room, clusters similar themes, and names the emerging patterns.
4. Run a brief plenary to highlight the strongest themes. "Look at what is already alive in this system. These are not aspirations. These are things we have already done."

Watch for: Pairs drifting into problem talk. Table facilitators should gently redirect: "That sounds like a real challenge. Can you tell me about a time when something similar went well?" Also watch for dominant voices at the table. Ensure the sharing round gives equal airtime.

Step 3: Dream

Time: 60 to 90 minutes

Purpose: Use the positive core themes to create shared images of the future.

1. Reshuffle tables to new mixed groups. Introduce the dream task: "It is three years from now. Everything we heard in Discovery has been amplified. What does this organisation look, feel, and operate like?"
2. Give tables 30 to 40 minutes to build their dream. They can write a newspaper headline from the future, create a skit, draw a mural, or build a visual collage. The format does not matter. What matters is that the dream is vivid, bold, and grounded in the strengths they just discovered.
3. Each table presents their dream to the room (3 to 5 minutes per table). Encourage applause and energy. This is meant to be inspiring.
4. After all presentations, the facilitator draws out the common threads. "What do you notice across all of these dreams? What keeps showing up?"

Watch for: Dreams that are too safe. If a table presents "We will continue to do what we are doing, just a bit better," push them. "What would it look like if you were the best in the world at this?" Also watch for dreams that ignore the positive core entirely and jump to wish lists unconnected to the organisation's actual strengths.

Step 4: Design

Time: 2 to 4 hours (the most intensive phase)

Purpose: Translate the shared dream into concrete design elements the organisation can build.

1. Introduce the concept of "provocative propositions" (also called design statements or possibility statements). These are present-tense descriptions of the organisation as if the dream has already been achieved. "We are an organisation where every customer interaction begins with the question 'What does success look like for you?'"
2. Form design teams around the key themes. Participants self-select into the theme that matters most to them. Each team writes 2 to 3 provocative propositions and then identifies the structures, processes, roles, and relationships needed to make them real.
3. Give design teams 60 to 90 minutes to work. Provide a simple design template: What is the provocative proposition? What structures support it? What needs to change? What can we start immediately? Who needs to be involved?
4. Each design team presents to the room and invites feedback. Other tables add suggestions on sticky notes.
5. Run a dot-voting round on the design proposals to surface the highest-energy priorities.

Watch for: Design teams getting stuck in abstraction. If a group writes "We will create a culture of innovation" without specifying a single concrete action, ask them: "If I walked into this organisation next Monday, what would I see that tells me this is happening?" Also watch for power dynamics. Senior leaders in design teams can inadvertently shut down bold ideas. Remind the room that hierarchy is parked at the door.

Step 5: Destiny (Deploy)

Time: 60 to 90 minutes

Purpose: Turn design proposals into committed action with named owners and timelines.

1. Reform action teams around the top-priority design proposals. People volunteer for the actions they care most about. These teams will continue after the Summit.
2. Each action team completes a simple action plan: What will we do in the next 30 days? Who is the team lead? Who else needs to be involved? What resources do we need? When will we report back?
3. Action teams present their 30-day commitments to the room. The senior leader responds to each one, publicly committing support or resources where possible.
4. Individual reflection: every participant writes down one personal commitment on a card. "What is one thing I will do differently starting tomorrow as a result of what I have experienced here?"

Watch for: Vague commitments. "We will look into improving communication" is not an action plan. Push for specificity: Who will do what by when? Also watch for overcommitment. It is better to have 5 strong action teams than 15 under-resourced ones.

Closing

Time: 20 to 30 minutes

1. Run a closing round. Each table shares one word or phrase that captures their experience. Capture these on a shared wall.
2. The senior leader closes with a summary of what was heard and a personal commitment to follow through. This is not a generic thank-you. It is a specific statement: "I heard that you need X, Y, and Z. Here is what I commit to doing about it."
3. Announce the follow-up schedule: when action teams will meet, how progress will be communicated, and when the next check-in will happen.
4. Thank the table facilitators and the steering committee publicly.

Facilitator Guidance

What Makes This Work

The AI Summit works because it puts the people who will deliver change in charge of designing it. When hundreds of people build a plan together from their own stories of success, two things happen that top-down planning can never achieve: the plan is realistic (because it is built on proven strengths, not theoretical ideals) and the plan has built-in ownership (because the people who made it are the same people who will carry it out). The positive framing is not naive optimism. It is a deliberate choice to start from a position of capability rather than deficit, which generates more creative and ambitious solutions. The mixed-stakeholder tables break silos in real time. A customer sitting with an engineer and a finance person produces ideas that none of them would generate alone.

Common Pitfalls

• Running a Summit without follow-through: This is the number one killer. A Summit that generates excitement and then leads to silence destroys trust. Before you run a Summit, secure a clear commitment from leadership on how results will be actioned and communicated. If you cannot get that commitment, do not run the Summit.
• Skipping the steering committee: Without proper stakeholder involvement in the design phase, the affirmative topic will miss the mark and the participant list will have gaps. The steering committee is not optional.
• Weak affirmative topic: If the topic is too vague ("How can we be better?") or too narrow ("How do we fix the onboarding process?"), the Summit will either drift or feel like overkill. Invest time in crafting and testing the topic.
• Letting plenary sessions dominate: The power of the Summit is in the table conversations. If facilitators or leaders talk for too long in plenary, energy drops and people disengage. Keep plenary moments short and directive.
• Ignoring the sceptics: Some participants will arrive unconvinced. Do not dismiss them. Acknowledge that the positive framing can feel unusual, and let the process win them over through experience rather than argument.
• Homogeneous tables: If tables are not properly mixed, you get echo chambers instead of cross-pollination. Assign table seating deliberately and change the mix between phases.

Adaptations

• Virtual/hybrid delivery: AI Summits can be run online using breakout rooms as "tables," shared documents as flip charts, and digital whiteboards for the positive core wall. Cut time by 30 to 40 percent (attention spans are shorter online) and run the Summit across multiple half-day sessions rather than consecutive full days. Assign a chat moderator for each breakout room to play the table facilitator role.
• Smaller groups (20 to 50): A "mini-Summit" covers all 4Ds in a single day. Use 4 to 6 tables of 6 to 8 people. The process is identical but compresses each phase. You may not need table facilitators at this scale.
• Shorter timeframes (half-day): Focus on Discovery and Dream only, then use the outputs to feed a separate design process. This works when you need buy-in and energy but can do the detailed design work with a smaller team afterwards.
• Multi-day deep dive (3 to 4 days): Spread Discovery across a full day with multiple interview rounds, allow overnight reflection between Dream and Design, and dedicate a full half-day to Destiny with detailed project planning. This format produces the most robust outcomes.
• Community or cross-organisational Summits: Invite representatives from every stakeholder group including those outside the organisation. The setup is the same, but the affirmative topic needs to reflect the shared interest rather than a single organisation's agenda.

Real-World Applications

Healthcare system strategic planning: A regional health authority brought 200 staff, patients, community health workers, and board members together for a 3-day Summit to redesign primary care delivery. The Discovery phase surfaced dozens of stories of exceptional patient outcomes that had never been shared across the system. The Summit produced 8 action teams that implemented changes to referral pathways, community outreach, and patient intake processes within 90 days.

Post-merger integration: Two mid-sized technology companies used a 2-day Summit with 150 employees from both organisations to build a shared identity and operating model. Instead of the usual "us vs them" dynamic, the Discovery interviews surfaced strengths from both cultures. The Dream phase produced a unified vision that neither executive team had imagined on their own. Integration milestones were met three months ahead of schedule.

City neighbourhood revitalisation: A local council ran a 1-day community Summit with 80 residents, business owners, and council staff to develop a neighbourhood improvement plan. Residents who had never attended a council meeting contributed ideas that shaped the final plan. Three community-led initiatives launched within six weeks.

Manufacturing company culture shift: A global manufacturer ran a series of 2-day Summits across four sites (300 people per Summit) to shift from a compliance-driven culture to one focused on innovation and continuous improvement. The positive core mapping revealed pockets of innovation that had been invisible to senior management. Action teams from the Summits produced measurable improvements in quality metrics and employee engagement scores within six months.

University school of nursing: A nursing school used a 2-day Summit with 135 faculty, staff, students, and community partners to rewrite its strategic plan. Seven strategic teams formed during the Destiny phase and began implementing changes to curriculum, community partnerships, and research priorities immediately after the event.