Appreciative Inquiry Wholeness Principle in Practice

The appreciative inquiry wholeness principle asks whose knowledge, experience and participation belong in an inquiry about a system's future. For a coach, that means helping a client examine the boundaries of the conversation: who shaped its question, who can contribute, who will bear the work and who can authorize a change.

A room full of enthusiastic people can still miss an important perspective. A smaller inquiry can be useful when it states its limits, gives contributors usable routes and returns a real decision. Neither attendance nor a positive atmosphere proves that the organization has heard everyone or achieved systemic growth.

This guide explains the principle and six practical design choices, then follows a complete fictional inquiry about community-room booking information. The result is deliberately limited: an improved internal reference, several unanswered questions and no public rollout.

Understand the principle and its place in AI

AI Commons lists Constructionist, Simultaneity, Anticipatory, Poetic and Positive as the five classic Appreciative Inquiry principles. The Center for Appreciative Inquiry describes wholeness among later, emergent principles, emphasizing the potential of bringing stakeholders together. Keep that conceptual claim separate from a measured guarantee that a particular meeting will create collective capacity.

Amanda Trosten-Bloom, coauthor of The Power of Appreciative Inquiry, discusses both the whole system and the whole person in her first-person interview with Sarah Noll Wilson. Someone can contribute practical knowledge, imagination, values and feeling. That does not require intimate disclosure, bodily exercises or agreement with a facilitator's preferred story.

Wholeness changes what a coach notices. The sponsor's account becomes one situated view rather than a complete description. A staff member may know where a handover fails; a customer may interpret an instruction differently; a budget owner may identify a dependency. Bringing those accounts into relationship can reveal alternatives that one role would overlook.

It does not remove hierarchy or settle conflicting interests. A person may understand the work without owning the decision. Another may have formal authority while lacking direct experience of its effects. A useful inquiry makes both visible rather than giving participation an implied promise of control.

Choice 1: Define a boundary people can question

Start with a concrete purpose and a provisional system boundary. “Improve our organization” gives contributors little basis for deciding whether to join. “Explore how prospective room users understand the information before requesting a booking” identifies an experience, while leaving room to ask whether the boundary excludes something important.

Separate what the inquiry can influence from what is fixed for this round. If prices, eligibility or employment arrangements cannot change, state that before asking people to imagine possibilities. If a supposedly fixed condition turns out to be central, record a request for the proper owner to reconsider it. Do not quietly promise that the workshop can change it.

Use a boundary question such as, “Whose work becomes harder if we choose this option?” alongside questions about useful existing practice. Appreciative attention can identify conditions worth extending without concealing a harmful requirement or a disputed decision.

Choice 2: Seek perspectives without assigning identities

Map who experiences the activity, supplies essential work, manages constraints and decides what happens next. Then ask who selected those people and what they cannot represent. A single customer contributes their own experience; they do not become a proxy for every customer with a similar age, disability or background.

Choose contributors for relevant knowledge and willing participation rather than presumed personality or demographic traits. A junior employee can understand a long-standing process. A senior employee can propose an unfamiliar approach. Leave people able to correct the role you have assigned them.

Missing perspectives need a consequence. An absence might permit a limited internal draft but block public replacement of existing information. Document that distinction. A map that names missing voices while allowing every decision to proceed unchanged offers little practical protection.

Choice 3: Make contribution usable and optional

A live meeting is one route. An individual conversation, an accessible written account or a linked local discussion may serve the purpose better. Ask what a person can actually use, including preparation time and a way to pass on personal questions. Different routes need a common decision question, not identical performances.

The W3C guidance on accessible events recommends adaptable materials and attention to participants' access needs. Sending a PDF does not establish that its recipient can change text size or spacing as needed. Check the actual material and ask whether the chosen alternative works for that person.

Explain the audience, use and return arrangement before collecting an account. A contributor may accept a discussion of generic instructions while declining publication of their story. Participation in a work inquiry is not permission for a marketing quotation, a public recording or access to personal coaching records.

Choice 4: Put different accounts into the design

Collect more than a satisfaction score. Ask for an example of an instruction that helped, the condition that made it useful and a point that remains unclear. Invite corrections to your interpretation. You need enough detail to make a design choice, without collecting unnecessary personal information.

Synthesis should preserve material differences. “Everyone wants convenience” may erase a real conflict between an immediate online answer and a staffed response requiring a working day. Show the alternatives, the relevant constraints and which contribution changed the proposed wording or process.

A shared aspiration can guide inquiry while remaining provisional. The accompanying poetic principle guide examines the accounts that enter a shared story. Here, check whether the story still includes a refusal, uncertainty or minority preference that matters to the decision.

Choice 5: Match influence with authority and capacity

Give contributors an honest description of influence: advice, joint design, a defined decision or something else. Do not call an advisory meeting a vote when a manager will decide. Conversely, if a team has authority over a bounded choice, avoid taking that choice back merely because the sponsor prefers another answer.

Count the receiving work. Reading an invitation, preparing an example, reviewing a revision and answering a closing message all take time. Protected work time, coverage or an agreed fee may be necessary. An invitation that asks for unpaid work is not made voluntary simply by calling it collaborative.

The US Environmental Protection Agency's AI participation guidance identifies broad representative access as a challenge and staff time as a significant cost. That is planning guidance, not evidence that this inquiry satisfies a statutory consultation duty. Use the organization's actual employment, governance and professional processes where they apply.

Choice 6: Return a decision and retain the limits

Before people contribute, tell them what they will receive back and when. The return should identify the decision, changes made, unresolved differences and any future work requiring permission. An internal thematic report does not fulfill a promise of individual feedback unless that was the agreed arrangement.

Give contributors a bounded opportunity to correct how their input was represented. The decision owner must still decide. A correction window is not an obligation to keep reviewing indefinitely, and silence is not approval unless an appropriate arrangement actually establishes that meaning.

The enactment principle guide asks whether the current interaction reflects the future being described. Apply that question to the return itself: does a process promising participation acknowledge a refusal and explain a limit, or only celebrate the convenient answers?

What the research can and cannot establish

Bushe's 2010 comparative case study followed eight sites in one Canadian school district. Four were classified as showing transformational change, two incremental change and two little or none. Positive affect and summit-success ratings showed no meaningful relationship with change outcomes; generativity, process quality and contextual relationships appeared relevant.

The author had helped design and support the intervention and conducted participant observation. Earlier stages were partly reconstructed retrospectively because research data collection began at the summits. This was neither a randomized comparison nor an isolated test of wholeness. The eight-site pattern cannot supply a universal success rate or establish that inviting more roles causes improvement.

Use that distinction when choosing evidence for a client. Attendance and enjoyment describe an event. A corrected instruction describes an artifact. Subsequent service use, workload and organizational change require their own observations. None can be inferred simply from naming an AI principle.

Complete the inquiry brief before inviting people

In this original fictional case, Dalia manages information for a UK community venue. Sam coaches her on designing a bounded inquiry. Noor works at the front desk, Ivo hosts activities and Eva is a prospective room user. All dates below are in June 2032, with times in Europe/London. No real participant information is used.

On Monday 7 June, Dalia spends fifteen minutes preparing the purpose. Sam reads it and prepares for twenty minutes; they then meet for forty minutes. Dalia initially wants to describe the result as the community's preferred booking process. Sam asks which community members have agreed to participate and what Dalia can actually change. They replace that claim with the following brief.

This is a small inquiry applying the principle, not a complete AI summit or a claim to have assembled the whole community. Dalia's existing authority and the allocated time are case facts, not permissions supplied by a coaching method.

Repair the first invitation and hear the difference

On 8 June, Dalia uses fifteen minutes to compose and send the invitations and an initial PDF. Noor and Ivo each spend five minutes reading and accepting the allocated work, including the discussion on 10 June from 10:00 to 10:30, later draft review and closing return. Their other five preparation minutes will cover reading the brief before that discussion.

Eva uses ten minutes to read and reply. She accepts the £45 arrangement and the forty-five-minute limit, but declines live attendance. She writes: “I can comment in writing. I cannot comfortably resize this PDF. Please send adaptable text. I can use twenty minutes on 10 June, ten on 22 June and five to read your decision on 23 June. This reply uses the other ten.”

On 9 June, Dalia spends ten minutes reading the three replies and twenty preparing and sending the corrected HTML brief and draft outline. This is actual access repair, not a claim that every possible access need is now met. Eva reads the HTML and writes her comments within her accepted twenty minutes on 10 June.

Eva's actual contribution: “The room-size description helps me picture whether my group fits. ‘Request received’ is unclear: I would not know whether I could announce the event. Please distinguish receiving a request from confirming a booking. I do not want my reading difficulty described in the shared account.”

During the staff discussion, the three participants use five minutes on scope, ten on useful experiences, ten on alternatives and five recording decisions. Noor explains that a confirmation reference has helped callers distinguish a completed booking from an inquiry. Ivo wants an immediate weekend answer, while Dalia explains that no additional staffing is available. They retain that disagreement rather than inventing cover.

Produce the artifact and check what changed

Dalia spends twenty-five minutes on 11 June synthesizing the contributions and sending a first complete draft to Noor and Ivo. On 14 June they each use ten minutes to read and comment. Noor finds that Dalia has accidentally written “your booking is confirmed when we receive your request.” Ivo asks for a phone route and wants the weekend limitation visible before someone sends a request.

Across 10 and 14 June, Dalia uses fifteen minutes to read Eva's substantive input and the two staff reviews. On 15 June she uses twenty minutes to correct the draft, record how the comments affected it and send version two to all three contributors. She does not distribute their individual replies.

Completed internal reference, version two: “Before requesting a community room, check the current room-size, price and eligibility information. Sending a request does not confirm a booking. The venue will confirm an approved booking separately and give you its reference. If you need the existing information in another format or want to ask a question, contact the front desk at rooms@oakmere.example or 01632 960204. The desk is staffed Monday to Friday, 09:00–16:00. Messages sent outside those hours are read during the next staffed day; an immediate weekend answer is not available. Do not announce an event as booked until the venue has confirmed it.”

The contact details are reserved fictional examples of the venue's existing staffed routes. The reference introduces no new response deadline, booking entitlement or online permission. Dalia remains its maintenance owner. The confirmation distinction comes from Eva and Noor; the visible weekend limit and phone route respond to Ivo without granting his preferred immediate service.

On 22 June, each contributor uses ten minutes to read version two and return a final comment by 13:00. Noor confirms that the request/confirmation distinction now matches the existing process. Eva confirms she can resize and read the text, accepts the unattributed summary and does not approve a quotation or public account of her access needs. Ivo says the phone route is useful but that he still wants weekend cover.

Close the inquiry with the actual decision

Dalia uses fifteen minutes that afternoon: five reading those final replies and ten recording and sending her decision. Her message says: “I approve version two as an internal desk reference only. I retained the existing staffing and booking rules, corrected the confirmation wording and added the phone route. Weekend cover remains unavailable. Evening-only visitors and the catering contractor have not contributed. We will not replace public information or call this a whole-community design on this evidence.”

On 23 June, Noor, Ivo and Eva each use their agreed five minutes to read that outcome. No further reply is requested or claimed. Eva's forty-five minutes are complete and the venue pays her agreed £45. The administrative work of arranging or checking that payment has not been measured or assigned to a timed person-row in this illustration. The payment is a financial fact, not a complete account of project cost or financial return.

Dalia sends Sam a selected generic account in ten minutes on 24 June. Sam reads it for fifteen minutes before their twenty-minute review on 25 June. Dalia initially calls the inquiry a successful whole-system change. They correct the account: three contributors affected a limited reference; one service preference remains unmet; missing experience and any effect on actual bookings remain untested.

Sam spends ten minutes returning a private coaching comment: “Keep the specific changes and the access repair in your account. Do not replace the missing perspectives with a claim that the community agreed. A later public-information decision will need its own authority, participation and work allocation.” Dalia uses five minutes to read and reply that the account is accurate and that she is not commissioning another round now. Sam spends five minutes reading that existing reply and completing notes, without another acknowledgment.

Account for measured participation work

The listed activities use 525 of the 600 person-minutes reserved across these five people. The nominal difference is 75: Sam 15, Dalia 30, Noor 15 and Ivo 15. Eva has no unused allocation. Because payment administration is unmeasured, these figures do not establish total project effort or available overall headroom. The staff discussion lasts thirty elapsed minutes but consumes ninety person-minutes. Reading, handling messages and sending the stated outputs are included rather than counted as uninterrupted design time.

This measured boundary excludes ordinary room bookings, the earlier creation of existing policies and any future public trial. Payment administration is a separate unmeasured project activity, not ordinary booking work or a future trial. Its owner and duration would need to be established before calling this a complete project account. The case ends with the stated internal decision and coaching return, not with an assumed rollout, improved booking rate or repaired relationship.

Use Coachful for the agreed coaching record

Coachful is our #1 recommendation for organizing the client's coaching worksheet, selected reflection and returned feedback in this workflow. This is an editorial recommendation about the workflow, not a measured ranking or a guarantee of organizational change. The venue's invitations, participant payment and approval records stay in its own authorized systems.

Dalia can submit the agreed generic account through her assigned worksheet. Sam can open it under Clients, select Dalia, then Reflections > Forms & worksheets. Internal Coach review remains private to the authorized coach team; saving it does not deliver Sam's comment to Dalia. He returns the actual comment through her private client conversation, opened from the message icon on her profile.

Keep unshared journal pages distinct from that selected submission. Clients can explicitly share individual journal pages through supported specialty flows and later revoke that sharing. Neither a worksheet nor a group inquiry requires sharing an entire journal. Before a summarized session, check the intended recap audience and approval settings: approval holds new unsent recaps, session-type overrides apply, and already-sent material is not recalled.

The demo images illustrate the coaching tools, not Dalia's venue record or actual contributor accounts. Use Coachful features to support the agreed coaching work while keeping organizational authority, access and participation decisions explicit.

Frequently asked questions

Is wholeness one of the classic five principles?

No. The classic five and later emergent principles have distinct histories. Describe wholeness as a later principle without claiming that it adds a scientifically established mechanism.

Must everyone attend the same summit?

No. Relevant contribution routes can differ. State who participated, whose experience is missing and which decisions that absence blocks. A small group should not claim universal representation.

Does wholeness require agreement or personal disclosure?

No. Preserve substantive disagreement and actual decision rights. Someone can decline a personal question, recording or live format while offering relevant practical knowledge through an agreed alternative.

What shows that participation mattered?

Trace a contribution to a changed artifact, a reasoned refusal or another real decision, then return that account. Wider service or organizational effects require later evidence; attendance alone does not establish them.