Appreciative Inquiry: Put the Wholeness Principle to Work

The wholeness principle in Appreciative Inquiry encourages people to involve the perspectives needed to understand and improve a shared system. In practical terms, a change discussion should include more than the people who normally make the plan. People affected by the work may hold information and experience that the decision-makers do not have.

Wholeness is often discussed as an emergent principle within Appreciative Inquiry, rather than one of its original five principles. It does not require literally everyone to attend one event, remove hierarchy, or guarantee agreement. This guide explains stakeholder selection, a worked service-improvement workshop, and the handoff from ideas to decisions. See also the anticipatory principle.

We build Coachful. Coachful is our #1 recommendation for organizing agreed coaching resources and follow-up because we build it for that work. That is our maker preference, not an independent ranking or proof that a community feed represents everyone affected by a change.

Broaden participation with a clear purpose

What wholeness adds to Appreciative Inquiry

Appreciative Inquiry explores strengths and possibilities as a starting point for change. Its development is associated with David Cooperrider, Suresh Srivastva, and colleagues. The wholeness principle adds a practical participation question: whose experience is needed to make the inquiry more complete?

The Center for Appreciative Inquiry lists wholeness among emergent principles. In a July 2001 interview, Cooperrider discusses wholeness and asks what a group size is effective for, rather than treating one size as universally best. These are method and practitioner accounts. They do not establish that participation in this particular workshop will produce agreement, inclusion or better business results.

The Champlain College introduction to Appreciative Inquiry explains the strengths-based orientation. Including diverse perspectives can enrich the inquiry, but it does not make the organization a single mind or automatically dissolve differences in power and interest.

• Whole-system perspective: Look beyond the department that commissioned the work.
• Meaningful participation: Give people a task and a real route to influence the outcome.
• Visible differences: Preserve disagreement and missing information rather than forcing a positive common story.

Use the 4-D cycle at a scale that fits the task

The familiar Discovery, Dream, Design, and Destiny cycle can organize a workshop or a longer inquiry. The event does not have to involve hundreds of people or last three days. Match the format to the question, participant needs, and decisions available.

• Discovery: Examine concrete occasions when the work went well and what supported them.
• Dream: Describe a preferred future using practical examples of what would be different.
• Design: Develop possible changes, requirements, and tradeoffs.
• Destiny: Agree how proposals will be reviewed, resourced, tried, and followed up.

Self-selected action teams can be useful, but volunteers still need authority, capacity, and a decision process. Do not imply that a workshop removes procurement, safety, privacy, or budget responsibilities. A proposal should be able to become a governed pilot rather than an informal promise.

Cooperrider and Whitney’s published 2005 chapter preview describes different forms of the four Ds for different challenges. Corporation for Positive Change’s process account also distinguishes discovery, imagination, design and implementation. The agenda here is an original adaptation. Its Destiny block agrees a handoff; implementation and sustained results still need work after the event. The Design-phase guide develops the practical options discussion.

A worked conversation about involving customers and staff

This fictional example concerns a company trying to improve customer onboarding. The coach helps the sponsor clarify participation and authority.

Noel is the sponsor and Marta the coach and workshop facilitator. Their 9 November 2026 preparation conversation lasts thirty-five minutes, with the nine-turn exchange as an excerpt. They agree that participants can shape handoffs and messages, while the 10 December product launch date remains fixed. All case times below are UTC. Viv will coordinate the pilot work and the participant updates; no workshop vote can create overnight staffing or override the required privacy review.

Sponsor: We could ask the leadership team to design a new onboarding process.

Coach: Who experiences the current process most directly?

Sponsor: New customers, support staff, and the implementation team.

Coach: What could they help you understand that the leadership team might miss?

Sponsor: Where information arrives too late and which handoffs are confusing.

Coach: What will participants actually be able to influence?

Sponsor: The handoff and communication process. The product launch date is fixed.

Coach: Then make that boundary clear. How will you tell participants which ideas are accepted, need more work, or cannot proceed?

Sponsor: We will name a review owner and send a decision update after the workshop.

Prepare the inquiry before inviting a large group

1. Map the relevant system: Identify who does, receives, supports, and makes decisions about the work.
2. Form an appropriate design group: Include a range of perspectives and enough authority to resolve practical questions.
3. Choose an affirmative topic: Make it specific and useful without hiding an important problem.
4. Design participation: Plan accessible interviews, writing, small groups, or other routes that fit the people involved.
5. Agree the decision handoff: State how proposals will be selected, funded, piloted, and reported back.

A stakeholder map for customer onboarding

Start with the work rather than a generic list of impressive titles. For an onboarding inquiry, the following groups may have different information. The right selection depends on the organization and the question.

Ask who is missing and why. Customers who left, remote staff, contractors, or people on less convenient shifts may have relevant perspectives. Do not assume that the easiest participants to recruit represent everyone.

A representative can bring experience without being asked to speak for an entire group. Record gaps in participation and decide how to gather additional input. Wholeness is an inquiry into coverage, not a claim that the room is complete.

Make a small coverage register before recruiting: perspective sought, invitation route, contribution received, permission for its use, and what remains missing. Record a declined invitation separately from a contribution still expected. People need not explain a refusal or supply sensitive reasons for absence. Revisit that register before piloting: the people who helped design a message and the people now receiving it may be different groups. This gives the review a concrete question about coverage without treating either attendance or silence as agreement.

Noel invites twelve staff and six recent customers. Ten staff and four customers attend the workshop. Two staff cannot leave their shift and contribute writing during allocated paid work time before it. The other two customers decline participation but request the eventual decision update. That makes fourteen live participants and sixteen distinct contributors, not eighteen participants or a complete customer ecosystem. Former customers and people needing a different language have not been recruited; Noel keeps those gaps visible.

Write an affirmative topic that still admits difficult facts

“Create an effortless onboarding experience” sounds attractive but may be too broad. “Help new customers understand the next step and get support during their first month” is more concrete. It gives participants something they can examine through examples.

A Discovery question could ask: “Tell us about an onboarding experience where the next step was clear. What made that possible?” A follow-up can ask where that support is missing today. Appreciative inquiry does not require ignoring complaints, harm, or operational failures.

If participants raise a serious problem, acknowledge it and decide how it will be addressed. Do not reframe every negative account into a positive story before the person feels heard. Some matters need investigation or an immediate decision outside the workshop.

A sample half-day workshop

Include breaks and enough time for instructions. A half-day design may need preparation interviews and later decision meetings; do not advertise it as a complete transformation in one event. If the question is large, narrow the pilot rather than trying to solve everything in a crowded agenda.

Mix perspectives where useful, while considering power and confidentiality. Some people may contribute more freely in a separate interview or written response before joining a mixed group. Equal seating does not by itself create equal influence.

The 12 November workshop runs from 09:00 to 13:00: twenty minutes opening, fifty Discovery, forty Dream, sixty Design and forty Destiny, with two fifteen-minute breaks. Eight staff attend in the room; two staff and four customers join remotely. Eight minutes within Design are lost when remote participants cannot read the shared options. Marta pauses everyone and provides readable text. The event still lasts 240 minutes: 202 of activity, eight of access repair and thirty of breaks. Design has fifty-two active minutes, and the integration proposal goes forward with specialist questions still unexamined.

Make customer participation useful and appropriate

Tell customers why they are invited, what information they will receive, and what they can influence. Participation should be voluntary and scoped so they are not exposed to unrelated confidential information or expected to endorse the company.

Use anonymized examples where possible. Ask permission before using a participant’s story in a presentation or public case study. A contribution to service improvement is different from consent to marketing.

Explain the follow-up: when they will hear what was decided and how their input was used. If an idea cannot proceed, provide a clear reason where appropriate. Returning with the decision is part of meaningful participation, even when the answer disappoints someone.

The invitation explains that contributions inform service design, who receives the approved workshop record and how questions can be raised. ICO privacy-information guidance addresses purposes, recipients and retention in its UK context; its current page carries an under-review notice. Treat that as a prompt to check the actual arrangements, not a generic consent form. Marta uses only agreed nonconfidential extracts from the two written contributions in the mixed group. Nobody authorizes a public testimonial or release of a private customer interview.

All eighteen invitees ask for the decision update. Viv promises it by 13 November at 17:00 but sends it on 16 November at 11:00, sixty-six hours late. A timely workshop does not make that follow-through timely. The update names the accepted, declined and pending proposals rather than presenting every contribution as a commitment.

Keep disagreement visible during design

One group may prioritize speed while another prioritizes careful preparation. Do not blend those concerns into a vague statement that everyone wants excellence. Ask what each option would require and which tradeoffs the decision-maker must consider.

Use an options record: proposed change, expected benefit, affected people, resources, constraints, unanswered questions, and evidence needed. Invite participants to identify risks as well as strengths. A useful design includes reasons an option might fail.

Consensus may be possible, but it is not the only legitimate decision rule. Clarify whether the group recommends, decides, or supplies input. Avoid promising complete ownership when participants have limited authority over the final choice.

Turn a promising idea into a bounded pilot

Suppose the workshop proposes a single welcome message that explains the first three onboarding steps. Name an owner, choose the customer group, obtain the necessary approvals, and decide what will be observed. The pilot might examine repeated clarification requests and whether customers can identify the next step.

Agree a review date and a way to hear from customers and staff. Record unintended effects, such as information becoming too compressed or a support route becoming harder to find. A useful pilot can reveal that an attractive idea needs revision.

Report back on the decision and the result. Participation can become frustrating when people contribute repeatedly but never see what happens. A modest change with a visible follow-up is more credible than a large list of unfunded commitments.

The six pilot customers are a new onboarding group, separate from the four recent customers who attended. They agree to a short understanding check during 16–20 November. All six receive the revised welcome message. Four initially identify the next three steps and where to seek help; two cannot find the support route. Viv revises its placement on 19 November. One of those two confirms on 20 November that the route is now findable. At the review, five of six meet the criterion and one difficulty remains. Delivery is not understanding, and finding a route is not proof of retention or satisfaction.

The selected pilot work totals 250 staff minutes against a 240-minute allowance: ninety editing the first copy, thirty privacy review, sixty for six ten-minute checks, forty revising and thirty reporting. The edit had been forecast at eighty minutes; the other amounts match the allowance. The ten-minute overrun is retained. Workshop time, preparation interviews, participants’ time and Marta’s coaching are outside this selected task budget, so it cannot support a whole-project cost-saving claim.

Apply the principle in remote and ongoing work

Wholeness need not depend on a single summit. You can combine interviews, asynchronous writing, small workshops, and a decision review. That may include more relevant voices than requiring everyone to attend one long event.

Plan for language, time zones, disability, device access, and paid working time. Provide the question and instructions in a readable form. Confirm the capabilities of any live or collaborative tools before promising a particular activity.

Coachful can organize program materials and community discussion around an inquiry. Keep confidential business information in appropriate locations, and make participation and follow-up expectations explicit. The platform supports the process; it does not guarantee inclusion or agreement.

Check the complete audience before using a community channel. The configured audience may be everyone, or access may come through selected people, programs, resources, an active Offer or moderator status. Selecting names alone does not exclude another valid route. In this case Marta deliberately grants account-backed Noel the private planning resource; Noel confirms that it opens. Approved participant updates use their agreed business communication route. No customer interview is placed in a community feed, and workshop attendance does not enroll someone in the program shown in the related screenshot.

Close the loop when an idea cannot proceed

Suppose participants propose round-the-clock onboarding support, but the organization cannot resource it. The sponsor should explain the constraint and consider whether a smaller proposal addresses the underlying need. Perhaps customers mainly need clearer expectations about response times.

A useful update names the proposal, the decision, the reason, and any alternative being explored. “We are not introducing overnight staffing. We will pilot a clearer response-time message and an urgent-issue route with the next onboarding group” gives people something concrete to assess.

Do not describe the original contribution as negative or unrealistic simply because it cannot be implemented. It may have revealed a genuine gap. Ask whether the alternative addresses that gap and what evidence would show it.

Keep a record of unresolved ideas so the workshop does not become a promise that everything will happen. Participants deserve a clear distinction between an accepted action, a proposal awaiting review, and a decision not to proceed.

Noel’s 25 November draft report nevertheless claims that the whole ecosystem agreed and all six pilot customers understood the process. Customer Ari challenges it on 26 November. Noel withdraws those statements and apologizes. Viv sends the corrected participant record on 27 November at 11:00, before the agreed noon deadline. By 30 November fourteen of the eighteen recipients acknowledge receipt; four receipts are unknown. Ari confirms the participation description, while retaining the request for overnight help. That disagreement is not converted into endorsement.

At the 30 November twenty-five-minute coaching close, Noel keeps the pilot’s unresolved customer difficulty and the missing perspectives on the next review list. Viv accepts responsibility for a 4 December integration-review follow-up, but specialist capacity and an implementation date remain unagreed. The 10 December launch is still future. Marta has no further facilitation or coaching booked. The two coaching conversations total sixty live minutes; the separate four-hour workshop is an elapsed event block, not another sixty-minute conversation or a complete staff labor total.

Frequently asked questions

What is the wholeness principle?

An invitation to include the perspectives needed to understand and improve a shared system, including people affected by the work. It is commonly discussed as an emergent Appreciative Inquiry principle.

Must the whole organization attend?

No. Choose a workable mix of representation and input routes, identify missing perspectives, and avoid claiming that a small group speaks for everyone.

Does participation eliminate resistance?

No. People can contribute and still disagree or face real constraints. Make decision authority, tradeoffs, and follow-up clear.

Does an inquiry need a three-day summit?

No. Match the format to the task. Interviews, smaller workshops, remote input, and staged pilots can all support a broader inquiry.

Can customers take part?

Yes, when participation is voluntary, appropriately scoped, and useful to the question. Explain confidentiality, influence, and how their input will be used.

Wholeness becomes useful through deliberate participation and a clear path from input to action. Explore Coachful’s program and community features when organizing the practical materials around that process.