Appreciative Inquiry Dream Phase: Grounded Visioning

The Appreciative Inquiry Dream phase explores a preferred future informed by specific experiences and strengths. Its useful output is a description people can question: what would change, who would experience it and which conditions would make it possible? An inspiring phrase alone cannot answer those questions.

Associated with David Cooperrider and the wider Appreciative Inquiry tradition, Dream is an invitation to explore possibilities. It does not guarantee that visualization creates the desired result. This guide offers an original workshop format, complete outputs and a case in which participant criticism changes the vision while the proposed trial remains unfunded.

Use strengths without erasing problems

An organization needs an accurate account of failure, cost and harm. It can also study occasions when useful work happened and ask which conditions might be developed. Dream widens the possibilities considered; it should not turn an exceptional success into a claim that the system already works well.

Participants should not have to deny exhaustion, loss or exclusion to contribute. If someone raises a serious concern, keep its appropriate support or reporting route available. A hopeful exercise does not require an immediate positive reinterpretation of another person's experience.

Locate Dream within the inquiry cycle

The Appreciative Inquiry Commons explains the original four stages, Discover, Dream, Design and Destiny or delivery, and the later addition of Define. Dream develops possibilities from Discovery; Design works on arrangements that could support the preferred future. These are process concepts, not a fixed workshop script.

The Commons' account of the classic principles describes the anticipatory principle in terms of future images and present action. Treat this as a change philosophy, not experimental proof that a particular vision causes an operational outcome.

In their original chapter, Appreciative Inquiry: The Power of the Unconditional Positive Question, James Ludema, David Cooperrider and Frank Barrett discuss Dream, dialogue in Design and propositions connecting aspirations with organization. The format below is an original practical illustration. It does not reproduce their diagram, interview instrument or case.

Define genuine influence before inviting imagination. If a location, merger or budget decision has already been made, say so. Participants may shape aspects of implementation, but an invitation to reverse a settled decision creates a false choice. A facilitator also cannot grant authority the group does not possess.

Move from Discovery through five practical steps

1. Select a bounded topic. Identify an experience the group can meaningfully influence.
2. Bring concrete accounts. Include what happened, relevant conditions and costs, not only flattering themes.
3. Offer tentative themes. Let the people concerned correct or reject the summary.
4. Describe an ordinary future. Ask about handoffs, decisions and information rather than only a slogan.
5. Retain differences. Separate shared direction from unresolved meaning before choosing Design questions.

Explain how contributions will be used, who will read them and when participants will receive a return. Offer writing, conversation or another usable format. A plain description can do the work of a sketch; artistic confidence or visible enthusiasm should not determine whose idea counts.

Check the source of each theme. A story about a successful launch may reveal a good shared brief, but also dependence on unpaid overtime. Keeping the brief while ignoring the hidden cost would reproduce the wrong lesson. An absent team may know another part of the process that the available stories omit.

Case: a customer handoff without an unlimited promise

This fictional case involves facilitator Pia, Sales lead Eli, Delivery lead Uma and Support lead Ren. Customer contact Jade and manager Asha take part through a separate written route. The bounded exercise runs from 1 to 13 May 2075. Existing contracting, permissions for two redacted Discovery accounts and the work described in those accounts are outside this account without being assumed free.

The group can explore a better handoff within the existing 09:00–17:00 service window. It cannot expand staffing, alter a customer's contract or publish a new service promise. Asha controls whether a trial receives resources. These boundaries are explained before participation.

Pia spends twenty minutes on 1 May sending purpose, allocations, audiences and dated return windows, reading all five acceptances and sending confirmation. Eli, Uma and Ren each use ten minutes to read, accept and read confirmation. Jade uses five minutes accepting ten active minutes for written feedback on 11 May and a five-minute final read on 13 May, including reading confirmation.

Asha uses five minutes reading, declining an extra thirty-minute live slot, accepting fifteen minutes for written review on 11 May and five for the final read, then reading confirmation. The live workshop does not assume either absent person's endorsement.

Pia uses twenty minutes on 2 May to read and curate the two existing permitted Discovery accounts and send selected material to the three workshop participants. Each uses fifteen minutes on 3 May to read and prepare privately. Ren chooses a process account rather than publicly retelling a personal experience. That choice is accepted.

A complete ninety-minute run sheet

Pia, Eli, Uma and Ren each attend the full ninety minutes on 5 May. Ten minutes are a break, so each has eighty active session minutes. Count the reservation and break honestly instead of describing every minute as discussion. If someone needs a different arrangement, agree it rather than silently extend the day.

The two Discovery accounts suggest that a shared brief helped one handoff and an outdated copy confused another. The successful occasion also involved excessive hours. Those are limited accounts, not evidence about every customer or proof that the same process will work under normal staffing.

Let a concern change the dream

Pia: What would an ordinary handoff look like if the useful shared brief were reliable?

Eli: Every customer would receive an answer within ten minutes.

Ren: I cannot support that as our future promise. We already rely on people staying late. Ten minutes also means different things outside the staffed window.

Uma: I want the customer to meet a named owner who knows which promises we can support.

Pia: Which part of the Discovery account helps, and which cost must we leave behind?

Ren: Keep the accurate brief and a clear next update. Do not treat staff absorbing extra work as the strength.

Eli: Then I can support accurate information and an agreed update within the staffed arrangement, rather than a universal ten-minute answer.

Pia: We will keep that distinction and ask the people outside this room what remains unclear.

This exchange and its revision occur within the sharing and comparison periods. Ren does not have to convert the objection into praise. Eli's original response aspiration is changed, rather than recorded as a commitment everybody supposedly accepted.

The group still differs on how much context can be reused and who would keep it current. Their selected future description provides a direction for inquiry. It is not a finished operating model or customer-facing statement of a capability already delivered.

Return a complete future image for review

Pia uses fifteen minutes on 6 May writing and sending a draft image and Design handoff, including provisional workload figures, to Eli, Uma and Ren. Each uses ten minutes on 7 May to read and return feedback. Pia uses ten minutes on 8 May to read all three responses, repair the wording and send this complete replacement:

In our preferred future, a customer meets a named handoff owner who uses an accurate, appropriately shared brief. The customer can see which promise is supported, what remains uncertain and when the next update is due within the staffed arrangement. Staff can correct a changed promise without relying on unpaid extra work. Relevant context is reused only through an appropriate agreed route. This is the direction we want to investigate, not an existing service guarantee. The information route, ownership and capacity still need Design decisions and the affected people's input.

Each participant uses five minutes on 9 May to read and approve that exact text as the workshop group's selected aspiration. Pia uses ten minutes on 10 May to read those approvals, check the unchanged copy and send it with the handoff to Jade and Asha. That approval does not speak for either recipient.

Complete an eight-field Dream worksheet

The worksheet distinguishes a desired experience from the evidence and permission needed to investigate it. It does not assign absent people an implementation deadline or make an unfunded trial ready.

Make the bridge to Design explicit

A provocative proposition expresses a preferred arrangement, often in present tense, while connecting it with strengths and aspirations. It should stretch thinking without masquerading as an established fact. An original short version here is: “Our customers meet a named owner with accurate context and promises bounded by real capacity.”

That statement raises questions rather than resolving them. Who updates the brief? What information may follow the customer? Who checks a promise before it is communicated? Which work must stop or receive resources if a new routine is added? The provocative-propositions guide develops that bridge.

Choose a few questions with a genuine decision route instead of assigning every aspiration as a task. A future investigation also needs someone willing to do it and someone willing to read its return. A worksheet entry is not their acceptance.

Keep four statuses separate in the handoff: selected as the workshop's aspiration, reviewed by affected people, authorized for a bounded trial and tested in actual work. Each needs its own evidence. A tick beside the first status cannot fill the other three. Someone can support the direction while withholding an endorsement or resource decision.

Before sending the image beyond the group, identify its status in ordinary language and preserve the open questions beside it. This helps a later reader understand what they are being asked to consider, without mistaking an attractive description for an approved instruction.

Keep the customer question and the manager's no

Jade uses ten minutes on 11 May to read the image and handoff and send feedback. Jade wants to know how the relevant context would actually follow the customer without repeated explanation. The phrase “appropriate agreed route” does not answer that practical question. Jade does not endorse the image as a current service description.

Asha uses fifteen minutes that day to read the same material and review its planning assumptions. The proposed routine assumes three future handoffs a day at fifteen review minutes each, or forty-five minutes. The proposal allows thirty minutes of relevant daily capacity. The difference is fifteen minutes a day, or seventy-five across five weekdays.

These figures are hypothetical operating assumptions for a possible trial, not measured performance or work already completed. Asha declines trial funding at this stage. The group cannot describe the gap as absorbed by goodwill, claim a time saving or start assigning the additional work.

Pia uses ten minutes on 12 May to read both responses and send this full selected close to all five contributors:

The workshop group has selected an aspiration, not a new service promise. Jade's question about the actual context route remains unanswered. Asha has declined trial resources because the proposed daily review work exceeds the available allocation. No trial or additional workload is authorized. We will retain the future image and the open Design questions without presenting them as stakeholder endorsement or an implemented process. This message does not request another reply.

Eli, Uma, Ren, Jade and Asha each use five minutes on 13 May to read the close. No new acknowledgment or further investigation is assumed. The inquiry has produced a more specific direction and an honest next-decision boundary. It has not delivered the future handoff.

Count meeting time and receiving work

The bounded exercise uses 625 person-minutes against 745 allocated, a difference of 120. Pia and the three workshop participants each have a twenty-five-minute difference; Jade and Asha each have ten. The meeting contributes 360 person-minutes already included: 320 active and forty on the break. The other 265 cover preparation and written handling.

Test whether shared words have shared meaning

Ask people for an ordinary example of a phrase such as “customer-centered.” One person may mean speed, another accurate promises and another less repeated explanation. These meanings can coexist, but their trade-offs need attention. Do not count a repeated phrase as evidence that everyone supports the same operation.

Choose participation routes that let quieter or absent people respond usefully. Explain who will read a written contribution and when, and include its receiving work. Avoid requiring a personal story, public drawing or an inspiring performance as the only way to be heard.

Keep the difference between an objection and a rejection of the entire direction. Ren supported accurate handoffs while rejecting the response promise. Jade asked an unanswered implementation question. Asha declined resources. Recording those positions separately is more informative than calling the future universally shared or the workshop a failure.

Avoid fantasy, forced consensus and missing voices

If the future remains vague, ask what someone would see in an ordinary week. “We are the best” may express ambition but does not yet provide a design direction. Add observable experience without pretending the required systems already exist.

Do not use strengths to suppress a complaint. Someone describing fatigue may be identifying the precise condition the future needs to change. Maintain appropriate support and formal routes. A strengths-oriented inquiry cannot decide whether an allegation is true or replace the organization's responsibilities.

Check whose work the vision would change. A senior group can imagine a convenient future that transfers effort to support staff, customers or another team. Seek relevant knowledge before commitment and preserve the right to decline proposed work. No amount of enthusiasm allocates their time.

Review the account as new facts appear. A useful Dream phase leaves the group able to revise an image, retain uncertainty or decide that a trial is not ready. Present-tense vision language should never be published as a current capability until it is true.

Organize the inquiry and agreed return

Coachful is our #1 recommendation for organizing appropriate inquiry materials and chosen follow-through. This is an editorial workflow judgment, not a measured ranking, framework-owner endorsement or guarantee that a vision produces change. Review Coachful's features against the actual service.

Use proportionate preparation prompts and check the real audience before sharing examples. Internal Coach review does not deliver a participant response. Choose which accepted actions should become tasks; the existence of a worksheet or program resource does not establish stakeholder agreement or funding.

The anticipatory-principle guide considers future images separately. These demonstration images show organization of learning material, not the fictional workshop's records or an author-performed customer trial.

Frequently asked questions

What happens in Dream?

People explore a preferred future informed by Discovery. The output should contain details that can inform Design.

Must every contribution sound positive?

No. Costs, concerns and missing perspectives may identify what the future needs to change.

Is a provocative proposition a factual claim?

It describes a preferred arrangement. Label the aspiration and do not market it as an existing capability.

How do Dream and Design differ?

Dream explores possibilities; Design examines the arrangements and choices needed. Neither an image nor a workshop vote supplies missing authority.

How can I review the workshop?

Check the clarity of the direction, differences retained and actual Design handoff and response. Enthusiasm does not prove implementation or impact.