Appreciative Inquiry Dream Phase and Provocative Propositions

The Appreciative Inquiry Dream phase explores a desired future grounded in what people have already experienced at their best. Provocative propositions give that future a form people can discuss, challenge and eventually design around. The practical skill is to create a compelling possibility without presenting an aspiration as an achievement.

This guide connects the Appreciative Inquiry Dream phase and provocative propositions through a complete fictional community-learning workshop. You will see the stories, rejected drafts, participant objections, revised proposition, failed information prototype and actual design decision. The result is a usable direction with limits, rather than an attractive sentence nobody knows how to enact.

Understand what the Dream phase contributes

In an Appreciative Inquiry cycle, Discovery investigates concrete experiences and the conditions that helped them happen. Dream expands those findings into images of what might become possible. Design develops arrangements that could support that future. Delivery or Destiny concerns continuing action and learning; different accounts use different names and cycle adaptations.

A Dream conversation should therefore do more than list improvements to an existing process. Imagine the experience you want to make possible. Who participates? What can they do? What do they notice? What would become ordinary that is currently exceptional? Then return to the Discovery stories to explain why that possibility matters and what might support it.

For orientation, read the Appreciative Inquiry 4D coaching guide. This article focuses on the narrower bridge from an imagined future to a proposition and an initial design brief. You do not need to finish an entire organizational transformation to create that bridge responsibly.

A participant who identifies an exclusion or a missing resource has contributed useful information. Asking them to replace every concern with praise can conceal the conditions the group needs to change. An appreciative focus is a choice about inquiry, not permission to dismiss harm, avoid accountability or rename a mandatory requirement as negative thinking.

Distinguish a provocative proposition from a slogan or target

David Cooperrider's facilitation resource on provocative propositions connects the best of current experience with a stretching picture of possibility. Its purpose is to challenge established assumptions and help shape an organization people want to create. It is practitioner guidance, not evidence that a particular sentence produces better organizational outcomes.

The Open University's teaching on provocative propositions brings past examples together with imagined futures. It places this work in its designing session. Treat propositions as a bridge between Dream and Design rather than insisting that every model assigns them exclusively to Dream.

Present-tense wording can help participants picture an enacted future. Put an explicit label on it: “Proposed future practice, not a description of current performance.” Without that distinction, the same sentence could become an unsupported public claim. A proposition also does not authorize a budget, change a policy or commit someone who has not accepted the work.

Prepare a focus and a genuinely mixed group

All people, activities, dates and results in the following case are fictional. A community learning centre wants newcomers to decide whether an introductory craft class suits them without needing insider knowledge. Director Iris commissions facilitator Ravi for one 90-minute workshop on 12 November 2026 and one 30-minute closing review on 19 November. Ravi's engagement ends after that review.

The six workshop participants are Iris, front-desk coordinator Mona, programme lead Ned, finance coordinator Ben, occasional visitor Lea and volunteer Dara. Ravi facilitates as a seventh person. Lea and Dara participate voluntarily; they can pass on a question and do not have to disclose financial, health or personal circumstances to explain an unclear listing.

The agreed focus is “a clear and welcoming decision before joining an introductory class.” It does not assume every visitor should enroll. Deciding that a class does not fit can be a useful outcome. Nor does it let the workshop redesign fees, teaching qualifications or the centre's whole booking system.

Iris can approve a limited information prototype. Ben controls the agreed cost information, Ned verifies programme details, and Mona can accept a specific staffed contact route. A proposition cannot transfer those responsibilities to Ravi. The group agrees that any later publication needs Iris's approval after the relevant owners check the actual information.

Before collecting stories, Ravi explains the record: a shared, non-identifying workshop summary for these six participants and him, held in the centre's existing workspace. Personal coaching reflections, if any, stay outside it. Nobody is promised a permanent confidential record against colleagues who have agreed access to this shared document.

Recover the conditions in Discovery stories

For more on collecting concrete accounts, use the Discovery guide to high-point stories. Ravi begins with three short accounts gathered for this exercise. He asks for a particular occasion, what happened, who helped and what made the experience possible. He does not ask participants to invent a success or agree that their experience was positive.

• Dara's map: A newcomer found a craft room using a plain entrance map. The useful condition was a recognisable route with the room named, rather than a volunteer personally escorting every person.
• Mona's answer: A visitor asked whether materials were included. Mona checked with Ned, gave a definite answer and the visitor could decide. The condition was a reachable person with access to correct information, not friendliness alone.
• Lea's missing price: Lea previously left a class inquiry because its listing did not state the full fee. Ravi records this as a barrier to preserve in the inquiry. He does not relabel her departure as a successful customer journey.

The group identifies an emerging theme: people can make their own decisions when essential information is understandable and remaining questions have a real route. The map and direct answer support that possibility. Lea's account shows where it is absent. Three accounts do not represent every visitor, establish a prevalence rate or prove why people enroll.

Ask what you would lose by copying only the visible action. “Make a map” misses the need for recognisable labels. “Reply to questions” misses ownership and accuracy. The future should preserve useful conditions while leaving room for a different implementation.

Build an ordinary scene from the desired future

In the Dream portion, Ravi asks each person to picture an ordinary evening three months ahead. A newcomer sees a class listing, checks what matters and chooses whether to join. What can that person understand without asking a regular attendee? What happens if the information does not answer their question?

Lea describes comparing the total cost with her available budget before providing her details. Dara imagines a newcomer locating the room without searching for a volunteer. Mona pictures receiving a question through a route she actually monitors. Ned wants the description to explain the introductory level without releasing paid lesson materials.

They combine those scenes into a short imagined account: “I can see what the class involves, when and where it happens, and what I will pay. If I am unsure, I know whom to ask and when an administrative answer is normally available. I can choose yes or no without explaining private circumstances.” This is their original future image, not a testimonial from an actual visitor.

Ravi asks what would make the scene less credible. Ben says the centre cannot promise a personally tailored answer at any hour. Mona says an unowned shared inbox would reproduce the existing confusion. They keep the desired experience and record those constraints for the draft. Dream remains expansive, but the group does not make someone else's unaccepted availability the foundation of its vision.

Rewrite the proposition through real objections

The first draft is: “Everyone learns with us easily every time.” Iris likes its energy. Lea asks whether choosing not to attend counts as a failure. Ben asks what “everyone” promises when some classes have limited places. The group rejects this version because it obscures choice and makes an absolute claim the stories cannot support.

The second draft is: “Every newcomer sees all course material before booking.” Ned objects that it includes licensed lesson content and says nothing about total cost. Ravi asks whether “all material” was necessary in the imagined scene. Lea says she needs enough practical information to decide, rather than access to the entire lesson. The group removes that phrase.

Third draft, proposed future practice: “We make the essentials clear before a person decides to join, and provide a named route for unanswered practical questions.”

Now each word creates a useful design question. “Essentials” requires agreement about the minimum information. “Before” requires finding it before the booking decision. “Named route” requires an accepted owner and an actual way to reach them. “Practical questions” separates joining administration from an unlimited promise of personal teaching or coaching.

Mona initially declines responsibility for a new inbox. She already monitors the centre's existing front-desk email on staffed weekdays. The group accepts that route instead. Mona agrees to own joining questions there, normally answering by the end of the next staffed working day, Monday to Friday. Questions requiring programme facts go to Ned; Mona remains responsible for acknowledging the visitor and explaining any later answer date.

Iris, Ned, Ben, Lea and Dara each accept the revised direction. Lea specifically retains a concern about people who do not use email. The record says six participants accepted a proposition for this inquiry, with a remaining access question. It does not say the whole community was consulted or every disagreement resolved.

Use four drafting checks without turning them into a score

The following four checks are an editorial aid developed for this guide. They are not an official four-factor Appreciative Inquiry instrument or a validated measure. Use them to produce a better draft, not to rank the optimism of participants.

1. Grounding: Which particular story supports the desired quality, and what condition enabled it? In this case, the map and checked answer support understandable information and a reliable route. They do not support universal ease.
2. Clarity: What would an affected person notice? Ask someone to explain the sentence in everyday terms. If “empowered access” means five different things, describe the intended experience before refining the language.
3. Stretch: What changes from today's exception? The centre already answers some questions well. The stretch is making useful information available before people must ask, with ownership for the remainder.
4. Responsibility: Who would carry the work, what can they actually approve and which unresolved concern remains? Mona's accepted weekday route is credible; a promise of immediate help from unnamed staff is not.

Check each draft against an unfavorable example. A visitor with a fee question should not have to book first to discover the price. A person who cannot email still needs consideration. The proposition can guide those questions without pretending the first prototype has solved every access need.

Turn the proposition into an initial design brief

The Open University's design-elements teaching develops concrete elements from the imagined future. That supports the transition in method; it does not validate this centre's particular listing. Here, Ravi asks the group to identify the smallest artifact that could reveal whether their words are useful.

Iris authorizes a private information prototype for one fictional Introduction to Bookbinding class on 15 December, 18:00–19:30. It has six places and a total fee of £12 per participant, including the listed materials. Ned confirms the class level, duration and materials; Ben confirms the full price. Dara checks the actual room route with the coordinator, including its ground-floor location and step-free main entrance. This is a checked description of that route, not a certification of universal accessibility.

The workshop's 90 minutes comprise 15 for stories, 20 for future scenes, 20 for drafting, 20 for challenge and revision, 10 for the initial design brief and five for closing. This is a timebox for these prepared materials, not a promise that any group can complete Discovery and Dream from scratch in 90 minutes.

Test the artifact and preserve the failed first reading

On 16 November, Mona gives the private prototype to two volunteer readers who were not in the workshop. She asks each to find the total price, start and finish time, room route and way to ask a practical question. They can say information is missing. Neither must enter a booking or share why they might attend.

The first sheet says “£12 including materials” and “Contact us for questions.” Reader Finn asks whether £12 covers a person or the whole group. Reader Jo can identify the time and room, but cannot find an actual email address or expected answer window. Mona records those failures. A clear proposition has not automatically produced clear information.

On 17 November, Ben confirms the per-person wording and Mona supplies her accepted contact details. The revised prototype includes this original administrative block. The address uses a reserved example domain because this is a fictional illustration, not a contact for a real centre.

Introduction to Bookbinding: 15 December, 18:00–19:30, ground-floor Craft Room, via the step-free main entrance shown on the accompanying map. Introductory level; six places. Total price: £12 per participant, including the listed paper, thread and cover materials. No prior bookbinding experience required.

Practical questions: Email Mona at frontdesk@example.org. She normally answers by the end of the next staffed working day, Monday to Friday. If she needs Ned to confirm a class detail, she will acknowledge your question and give you an expected answer date.

Finn rereads the revised sheet and correctly identifies £12 for each person, including materials. Jo identifies the email, Mona and the weekday answer window without prompting. Both find the start and finish time and the room route. Mona records the actual answers, not a fabricated satisfaction score or booking conversion.

This small retest supports a narrow conclusion: these two readers found the specified information in this version. They already saw the earlier sheet, so familiarity may help. The exercise does not establish how all newcomers will understand it, whether the class will fill or whether people unable to email can get an answer.

Complete a decision and name what remains unknown

On 18 November, Iris reviews the two versions, the reader answers and the unresolved non-email question. She approves the revised information structure for the December class, conditional on Ned and Ben rechecking facts before publication. She does not approve a claim that every centre activity already follows the proposition.

Mona accepts the specific December joining-question duty through the established route. Dara accepts a separate task to investigate a staffed telephone alternative by 24 November; no telephone availability is advertised before that check. Iris records both acceptances in the centre's workspace. The proposition has now influenced a real fictional decision and a bounded next inquiry.

At the held 19 November review, Ravi returns the completed record: three Discovery accounts, imagined scene, three drafts, the accepted proposition, first-reading defects, repaired sheet, actual retest and Iris's decision. The six participants receive that summary and acknowledge the record. Lea's access concern remains visible rather than disappearing from the celebratory version.

Ravi's purchased 120 live minutes are complete: 90 workshop minutes plus the 30-minute closing review. The December class, public listing, 24 November investigation and any bookings remain future events at closure. The centre owns those actions. A subsequent facilitation engagement would need a separate agreement; the proposition creates no automatic continuing service.

Organize preparation and follow-up in Coachful

Coachful is our #1 recommendation for organizing the coaching preparation, original worksheets and agreed follow-up around this process. It can keep the learning materials and individual actions connected. It does not decide whether a group's vision is representative, authorize the centre's public claims or implement the information changes for them.

• Build an original preparation worksheet. Ask for one concrete experience, the useful condition, an imagined future scene, proposed wording, a challenge and the next design question. Allow an unanswered prompt where appropriate. The demo editor below illustrates form and worksheet construction; its wellness content is unrelated to this case.
• Grant the intended access deliberately. Check who can see the resource before sending it. A copied private link does not grant access. Keep identifiable personal accounts out of a shared lesson or group summary unless the person agreed to that specific use.
• Separate reusable education from live decisions. A course can teach the phases through modules and lessons. The centre's approved public information and staff responsibilities still belong in its own operating record.
• Assign actions only to the right person. An agreed client task can record a next step. A coach's own preparation task remains separate. A tick confirms the recorded action, not community consent, an improved experience or successful delivery of the future class.

Use Coachful's resources and client follow-up features for the coaching work you have actually agreed. A single workshop does not need a full ongoing Program just to hold a worksheet. If you are delivering a wider coached cohort, choose its delivery structure separately rather than treating a provocative proposition as a product configuration.

Troubleshoot the conversation before polishing the sentence

If people offer only abstractions, return to a specific occasion and ask what someone could see or do. If the same senior voice supplies every image, give others a quiet opportunity to contribute or pass before collecting ideas. Record whose perspective is absent instead of claiming representative agreement.

If a participant raises harm or a mandatory obligation, attend to it through the appropriate process. Do not require a positive reframe as the price of being heard. If the proposition depends on unpaid overtime, identify the actual resource decision and let its owner decline or negotiate it.

If the statement becomes a task list, recover the desired experience before choosing tasks. If it becomes a marketing claim, restore its aspiration label and verify current public facts separately. If everyone approves the words but nobody accepts a next step, the practical output is an unresolved design question. Say that clearly rather than announcing a completed change.

Frequently asked questions

Must a provocative proposition use present tense?

Present tense can make an imagined future vivid. Clear meaning and an explicit future-practice label matter more than a rigid grammar rule. Do not let drafting style turn a hoped-for condition into an unverified statement of current performance.

How ambitious should the Dream be?

It should stretch the current pattern while remaining connected to experiences participants can describe. Explore a larger possibility before narrowing implementation. Distinguish an expansive image from commitments that need actual authority, resources and consent.

Can one person use this in coaching?

Yes, as a reflective application. They can connect a concrete experience to a desired practice and an original proposition. They cannot commit colleagues through their private worksheet. Any shared change still needs the affected people and decision owners.

How many propositions should a workshop produce?

Use the number the group can examine meaningfully. This case develops one because it has a narrow focus. Several domains may need separate propositions, but a long collection of polished sentences is not evidence of depth or readiness to act.

Does this approach guarantee engagement or results?

No. The cited resources explain a method and teaching practice. This fictional case illustrates its application and limits. Evaluate the actual process, inclusion, decisions and later outcomes separately; readable wording and an accepted brief do not establish improved attendance or lasting organizational change.