The Poetic Principle in Appreciative Inquiry: A Guide

The poetic principle in Appreciative Inquiry treats organizational life as open to continuing interpretation and learning. The stories people choose to examine influence what they notice, discuss and attempt next. For a coach or facilitator, the practical question is: Which part of this organization’s experience are we studying, and what possibilities or omissions does that choice create?

This does not mean facts are optional or that a positive story can erase a loss, unsafe condition or unfair decision. A useful application brings specific experiences into view and connects them with evidence and action. This guide explains the principle, how to conduct a careful inquiry and how to keep organizational storytelling from becoming selective corporate publicity.

To connect the stories a group studies with the future it wants to build, see our guide to the anticipatory principle.

Coachful is our #1 recommendation for organizing the learning material and agreed coaching follow-through around this work. We build Coachful, so this is the maker’s recommendation. The organization’s maintenance, staffing and incident records should remain in their appropriate operational systems. A shared document may be sufficient for a first inquiry; buying a platform does not make a story more accurate.

A fixed corporate story vs an organization open to inquiry

Teams often develop a shorthand account of themselves: “We never cooperate,” “Headquarters never listens” or “This plant resists every change.” Such accounts may contain real experience, but they can also become so complete that exceptions disappear from view.

The poetic principle invites a choice about what to study. A team can examine an occasion when cooperation worked, alongside the occasions when it failed, to learn more about the conditions involved. The aim is a richer account, not a compulsory replacement of criticism with praise.

The word “poetic” does not require writing poetry. It points to an organization being available for multiple readings and fresh questions. Plain, precise language is usually the most useful way to put that idea to work.

Choose what the organization studies

Appreciative Inquiry is associated with David Cooperrider and Suresh Srivastva and the development of the approach at Case Western Reserve University. Its poetic principle emphasizes choice in the subjects of inquiry and the continuing stories through which organizational life is understood.

The Case Western Reserve overview explains the approach’s interest in discovering and learning from what gives life to organizations. For a fuller account of the principles, see Cooperrider and Diana Whitney’s writing on Appreciative Inquiry.

The coaching application is not that stories determine all reality. A safety incident still occurred, an employee still lost a job and a financial loss still needs an accurate account. Stories can shape interpretation and attention without canceling those facts.

This distinction protects credibility. People are unlikely to trust a process that invites their “best experience” while refusing to hear what currently harms them. Explain the purpose of the inquiry, how difficult evidence will be handled and which decisions participants can influence.

Cooperrider and Whitney’s 2001 article Exploring Appreciative Inquiry, printed page 75, presents the poetic principle through the metaphor of an organization as an open book. Their discussion includes the choice to study difficult experience as well as joy or effectiveness. This is a theoretical account of inquiry, not a validated scoring instrument or a guarantee of performance.

The historical association with Srivastva is also specific: Cooperrider’s 2017 author retrospective identifies their joint 1987 article. That history and the current university overview serve different purposes. Neither turns the worksheet below into a prescribed original protocol. The plant exercises and the following trial are teaching adaptations.

Finding a positive core without selecting only flattering stories

Choose a topic that matters and leaves room for genuine learning. Instead of “How are we already excellent at collaboration?” ask about a particular time collaboration made useful work possible. The second question does not require the participant to agree that the organization is generally excellent.

Ask for a specific event. What was happening? What did people do? What made the outcome possible? What was difficult? A concrete story reveals conditions that can be examined, while a list of positive adjectives often produces little guidance.

Invite people beyond the usual success narrators. A project sponsor may remember a triumph that depended on unrecognized work by frontline staff. A new employee may notice a barrier others treat as normal. Include relevant perspectives and provide a way to contribute without public exposure when needed.

Ask what the story leaves out. Was the success repeatable, or did it rely on unsustainable overtime? Who benefited and who paid a cost? A useful positive core should not depend on ignoring those questions. The inquiry becomes stronger when a celebrated event can withstand a fuller examination.

1. Choose one meaningful topic rather than the whole culture at once.
2. Invite specific experiences, including limitations and mixed results.
3. Ask what people did and what conditions supported it.
4. Look for missing voices and unacknowledged costs.
5. Distinguish a promising hypothesis from a proven explanation.

Keep three things distinguishable when listening: the event, the participant’s interpretation and the proposed explanation. “We moved the shutdown date” describes an action; “they finally respected us” gives its meaning to a participant; “earlier involvement improved coordination” is a hypothesis. Do not silently promote the third into a finding. A second interview might reveal that parts arrived early or a customer changed its order, which could alter the explanation. Our wholeness principle guide develops the related choice of whose experience to include.

Illustrative dialogue: understanding an acquired plant

This invented example concerns an operations team after an acquisition. The facilitator does not claim that changing the story alone will improve performance.

Executive: The plant sees every new process as a threat. We need a more positive story.

Facilitator: What would you like to understand that the phrase “every process” may be hiding?

Executive: There was one recent change that went well. Maintenance and production planned it together.

Facilitator: Who could describe what made that possible, including what was difficult?

Supervisor: We were asked before the plan was final. We could change the shutdown timing. But two technicians worked excessive hours to make it happen.

Facilitator: So early influence may be worth repeating, while the overtime is not. What would a next trial need to preserve and change?

Executive: Bring the supervisors in before scheduling is fixed, and resource the maintenance work properly rather than relying on the same two people.

The revised account is more useful because it identifies a condition, a cost and a possible action. It does not require the supervisor to withdraw criticism or the executive to pretend there is no resistance.

Ask participants whether the summary represents their experience. A facilitator can unintentionally turn a nuanced contribution into an upbeat slogan. Let people correct the account before it becomes a slide, announcement or leadership narrative.

Continue the invented plant case with executive Mara, supervisor Leon, maintenance lead Safa and production planner Oren. At a ninety-minute inquiry on 11 March 2027, six people including the facilitator hear the account above. Leon refuses a proposed internal campaign quotation: permission to study the shutdown is not permission to endorse the acquisition. Mara accepts that refusal and asks instead for an unattributed operating recommendation.

The facilitator initially summarizes the story as staff pride overcoming resistance. Safa corrects this: the two technicians had covered a staffing gap, and pride does not explain or justify that arrangement. The facilitator withdraws the summary in the room. The revised record names early influence as a possibility to test and adequate staffing as a condition to establish, while retaining the excessive-hours concern for the responsible managers to address.

Translating stories into operating practices

Extract a hypothesis from the experience: “Earlier involvement allowed local knowledge to improve the plan.” Then decide how to test that proposition in another suitable situation. Do not assume the entire story can be copied into a different team with different constraints.

Specify a practice. For the plant, it might be a planning review before shutdown dates are fixed, with named decision authority and a clear response to suggestions. “Listen more” is too vague to know whether anything changed.

Choose evidence from several angles. The team might examine schedule changes, avoidable rework, workload and participants’ understanding of their influence. A positive quote can be useful feedback, but it should not substitute for operational data or the accounts of people who had a different experience.

Review what did not transfer. Perhaps early involvement helped, but the group lacked authority to alter a critical constraint. That is useful information about the process. The poetic principle should leave the organization open to another reading, not require every trial to confirm the preferred story.

The next experiment is deliberately smaller than an acquisition narrative. Oren proposes three maintenance changes for 15, 18 and 22 March. Before any work starts, Mara authorizes a planning review while dates can still change and requires a staffing decision from the operational owner. The facilitator helps describe the experiment but does not approve engineering methods, staffing sufficiency or a safe system of work.

The first change has an agreed ninety-minute window and takes eighty-five minutes. On the second, an unavailable part leaves the job unfinished at the ninety-minute boundary. The operational owner refuses an improvised extension and stops the work for rescheduling. The third change is canceled before it starts because the required operator is unavailable. Earlier conversation has exposed constraints; it has not supplied the missing part or operator.

At review, one of three scheduled changes finished within its window. One of two started changes did so; the one completed change was within its window. Those fractions answer different questions. Reporting only the completed job as a 100% success would conceal both the unfinished job and the cancellation. The team keeps all three scheduled cases visible and records each state, rather than selecting a denominator that flatters the experiment.

Two twenty-minute reviews each involve four people, including the facilitator. Together with the six-person ninety-minute inquiry, that is 700 selected participant-minutes: 540 plus 160. The facilitator’s 130 live minutes are already inside that total. Interviews, preparation, the maintenance work and follow-up administration are additional effort. These meeting counts are not evidence of cost savings or reduced technician workload.

Facilitation checklist: keeping poetic inquiry credible

Explain what the inquiry is for and what it cannot change. If a restructuring decision has already been made, do not invite people to co-author whether it happens. They may still be able to influence implementation, support or the preservation of valuable practices, but that boundary should be honest.

Make participation voluntary where personal disclosure is involved. A person should not have to produce a hopeful story to be regarded as constructive. Written contributions, small-group discussions or other appropriate routes can widen participation, though no method guarantees equal voice.

Keep records faithful to the source. Attribute a story only with permission and avoid using it later for marketing or internal reputation management without checking. An employee who shares a learning experience has not automatically consented to being the face of a change campaign.

Close with the action the inquiry will inform. Tell participants who will decide, how their contributions will be used and when they will hear back. Asking for stories and then disappearing can reduce trust, however positive the workshop felt.

1. State the inquiry topic and the decisions it can influence.
2. Seek detailed experiences rather than mandatory positivity.
3. Include relevant voices and investigate missing perspectives.
4. Retain difficult facts and test the explanation against evidence.
5. Turn a useful insight into a practice, owner and review date.

The International Association of Facilitators’ ethics statement treats group autonomy, participant boundaries, appropriate methods and consent for reporting as professional responsibilities. It also distinguishes process expertise from the group’s content knowledge. Apply that distinction here: the facilitator can improve how concerns are heard while the authorized operational people decide how maintenance will proceed. The statement is professional guidance, not a promise of confidentiality in every legal situation.

HSE’s Management Standards on demands identify workload, work patterns and achievable demands relative to agreed hours, with systems to respond to concerns. That supports asking about the technicians’ actual conditions. It does not authorize a coach to certify a staffing plan or prescribe a universal maximum shift. Use the appropriate workplace safety, employment and reporting processes for those decisions.

Worksheet: study one success without mythologizing it

Use this reflection to move from a compelling story to a decision. It can be completed by a client or a group, with privacy and attribution agreed in advance.

Add one disconfirming question: What evidence would make us revise this account? Perhaps another team had early involvement but still experienced major problems. Understanding that contrast may reveal a missing condition.

Keep the story open as new information appears. The aim is an organization that can learn from its experience, not one polished narrative everyone is expected to repeat.

For this trial, add the staffing authorization and unresolved constraint beside the six worksheet fields. On 23 March, Mara accepts the earlier-review practice but declines to call the trial an operational success. Safa asks for the unfinished job’s new date to remain blank until the part and crew are confirmed. That is a real limit on the executive’s announcement, not an incomplete coaching commitment to be chased.

The facilitator also misses an agreed listening commitment: Oren’s written account was to be discussed before the summary was settled, but the first draft omits it. Oren objects that the cancellation was foreseeable from the roster. The facilitator acknowledges the omission and reopens the account with him; the corrected summary keeps the roster issue rather than calling it an unexpected attitude barrier. Mara and Safa confirm that they have read that correction. Leon receives the unattributed learning record and again declines campaign use.

When a positive story is met with skepticism

Suppose employees respond to a success story by saying, “That is not how it felt to us.” Do not treat the response as resistance to appreciation. Ask which part is inaccurate, whose experience is missing and what evidence the account overlooked.

The inquiry may reveal that a celebrated customer launch depended on canceled leave or unreimbursed work. That does not erase the achievement, but it changes what should be repeated. Preserve the effective coordination while addressing the unsustainable conditions.

If leaders want the story for a public message, distinguish that communication decision from the learning process. Participants may be willing to discuss the experience privately without wanting to endorse a campaign. Check attribution and avoid converting a nuanced contribution into a quotation that implies broader approval.

A revised account can say both what worked and what needs to change. It will often be more credible because people can recognize their experience in it. The poetic principle is useful when it opens inquiry, including inquiry into an attractive story, rather than making the organization defend its preferred interpretation.

Keep the learning material separate from those operational records. In Coachful, a course can organize modules and lessons, and the Programs area provides a route into an enrolled program. A visible lesson completion count is a learning record, not proof that a staffing decision was carried out or that someone endorsed an acquisition. Check the intended assignment and actual access before asking participants to use a resource.

If someone keeps a personal journal reflection, inspect the applicable page-sharing controls and their deliberate sharing choice; do not promise that every journal page is unconditionally private. For session recaps, check the effective workspace and session-type approval and delivery settings. Approval is not universally required by default, and a type override can change the rule. A group recommendation should contain only the information approved for that audience.

The facilitation ends after the 23 March review with the corrected learning record and agreed operating recommendation. Mara owns a proposed 26 March staffing decision; Oren owns a 29 March check of the missing part and revised date. Those outcomes remain unknown. No additional coaching, completed repair, quotation permission or confirmed schedule follows automatically from closing the inquiry.

Frequently asked questions

What is the poetic principle in Appreciative Inquiry?

It emphasizes that organizational life is open to continuing study and interpretation, and that choices about what to investigate influence what people notice and learn. In practice, choose a meaningful topic and explore specific experiences rather than treating one fixed story as complete.

Does it mean ignoring mistakes and losses?

No. Keep difficult facts, accountability and appropriate investigation intact. Learning from what worked can add information, but it should not replace hearing harm, examining failure or addressing unsafe conditions.

Are stories more powerful than quantitative data?

They serve different purposes. Stories can reveal meaning, context and overlooked contributions; data can show patterns and challenge impressions. Use both where relevant. A compelling story is not proof of a causal explanation or a substitute for accurate reporting.

How can a newly hired executive use the principle?

Ask people about specific experiences worth learning from, including the limits and costs. Seek more than the official success stories, explain what decisions remain open and check your interpretation with participants before turning it into a change message.

How does it relate to the other Appreciative Inquiry principles?

The original principles also concern the role of language, the effects of inquiry, images of the future and positive inquiry. They offer a philosophy for change work. They should not be treated as scientific guarantees that a positive question will produce a particular organizational result.

A good organizational story gives people more to examine and a clearer action to try. Coachful’s coaching workspace can keep the chosen inquiry, participant reflections and practical follow-up connected to the next review.