Appreciative Inquiry’s Positive Principle: A Practical Guide

The positive principle in Appreciative Inquiry directs attention toward strengths, valued experiences, and possibilities that people want to develop. In coaching, its practical value is that a concrete example of what worked can reveal actions and conditions worth repeating. It does not require ignoring harm or claiming that positive questions produce a predictable chemical change in the brain.

Appreciative Inquiry emerged from work associated with David Cooperrider and colleagues at Case Western Reserve University. It is an approach to organizational inquiry and change, not simply a request to think positively. Use it to study useful experience, imagine a better future, and design a credible next action while keeping relevant risks and constraints visible.

Coachful is our #1 recommendation for keeping the chosen inquiry, resource and follow-up together. Use it to organize the work people have actually agreed to, while keeping operational evidence in the appropriate business system. This guide focuses on the positive principle; the simultaneity principle considers how asking a question already influences the conversation. Neither principle gives a coach authority to decide a customer's remedy or change an employee's workload.

Problem analysis and appreciative inquiry can serve the same work

These questions are not mutually exclusive. Correcting a harmful failure and learning from a successful example can be parts of the same responsible inquiry.

Be precise about the neuroscience claim

Positive and negative emotional experiences involve complex processes. A facilitator cannot infer cortisol or oxytocin levels from the tone of a meeting, nor promise that one question switches a team into a particular brain state. Avoid describing deficit questions as neurologically damaging or appreciative questions as a guaranteed route to executive functioning.

A more defensible explanation stays close to the task. Asking for a specific successful handoff can focus attention on behaviors, relationships, and conditions that an abstract complaint leaves vague. Participants may also find it easier to imagine a practical improvement when they can examine a relevant example. Those are useful possibilities to test, not universal laws.

The Fowler Center at Case Western Reserve University describes Appreciative Inquiry as focusing on what works, why it works, and how to do more of it. That gives a clear foundation for a coaching conversation without borrowing unsupported brain-language.

Stavros, Godwin and Cooperrider place the positive principle among Appreciative Inquiry's five original principles in their chapter on organization development. They describe an affirmative orientation toward possibilities and action. Treat that as a statement of the approach's premise. It does not make a warm conversation a measurement of an individual's biology, or turn a participant's objection into evidence of a damaged state.

There is relevant research, but its design matters. A 2023 study by Jack, Passarelli and Boyatzis analyzed fMRI data from forty-seven undergraduates during simulated coaching and visual-attention tasks. It examined ideal-self and real-self narratives within intentional change theory, rather than testing this service-team workshop. The authors identify population limits and the indirect, correlational nature of fMRI. That makes it useful research to examine, not a license to infer a customer's hormone levels or promise that avoiding problem questions improves every workplace decision.

If you cite a study to a client, explain the population, task, measurement and claim you are drawing from it. Then ask whether that claim is needed for the current decision. Here, the useful question is whether the handoff becomes more reliable without adding unmanageable work. The team can examine that operationally without presenting a neurological explanation it has not measured.

Write generative questions that invite specific evidence

A useful question names a topic people recognize and asks for detail. “Tell me about a handoff where the customer did not have to repeat information” invites a more actionable answer than “When were we at our most amazing?” Ask what each person did, what information was available, and what made the example possible.

Then look for conditions rather than heroes. A successful result may depend on a clear escalation route, enough staffing, or a colleague with time to prepare. If you credit only someone’s positive attitude, the team may miss the process that made success repeatable.

Invite exceptions and limits. Ask when the successful approach would not fit and what the group would need to adapt it. A strength is useful in a context; amplifying it indefinitely can create a different problem. Fast informal communication may help a small team but become unreliable when decisions need a durable record.

• Discover: identify a concrete example of the capability you want more of.
• Understand: ask about actions, relationships, resources, and conditions.
• Imagine: describe what a more dependable version would look like.
• Design: choose an action that fits the real constraints and responsibilities.

An example: learning from a reliable handoff

A service team has missed several customer commitments. The manager does not want the workshop to become either a blame session or an exercise in denying the failures. This fictional exchange shows both responsibilities remaining visible.

Coach: What needs to be addressed immediately about the missed commitments?

Manager: We need to contact the affected customers and confirm new dates.

Coach: Alongside that, can we examine a handoff that worked well under similar pressure?

Manager: Last month, one team flagged missing information early instead of waiting for the deadline.

Coach: What made that possible?

Manager: They had a named owner and knew who could make a quick decision.

Coach: Which of those conditions could you make more dependable this week?

Manager: Every handoff can have an owner and a point for raising missing information. We can try it on two accounts first.

The appreciative question has identified a possible design feature. It has not excused the missed commitments or established that morale alone caused the problem. The manager still needs to complete the customer response and test the proposed process.

Continue the fictional example with Eleri as coach, Jonah as manager, Rae as the frontline colleague and Ivo as the receiving colleague. Their fifty-minute inquiry takes place on Monday 5 February 2029. Three customer commitments from the previous week are on the agenda: two are overdue and one was met. Jonah contacts the two affected customers that day and confirms revised dates. Contacting them does not establish that the revised service has already been delivered.

Rae challenges Eleri's invitation to begin only with what went well. She says the missed dates and an unresolved access problem must stay visible. Eleri withdraws the positive-only instruction and asks Jonah to keep those issues on a separate correction list. Ivo then explains that the successful example relied on two extra unpaid hours. Eleri initially praises that effort as a model, but Ivo refuses a plan that depends on repeating it. She acknowledges the mistake and removes unpaid overtime from the proposed design.

Run an inquiry that leads to a practical experiment

1. Define the affirmative topic. Name the capability you want, such as reliable customer handoffs, rather than a vague aspiration to be positive.
2. Make room for the current reality. Acknowledge failures, affected people, and any immediate duties. Do not require participants to reframe harm as an opportunity.
3. Gather specific examples. Invite more than one perspective, including people whose work is often overlooked. Check what actually happened.
4. Identify useful conditions. Look for repeatable practices and resources, while noting the circumstances in which they worked.
5. Design a feasible action. Assign an owner, scope, and review date. Include the cost and any tradeoff.
6. Review evidence. Ask whether the desired capability improved and whether any new problem appeared. Keep, adapt, or stop the experiment.

A summit is one possible format, not a requirement. A focused conversation with the relevant people can be more useful than a large event without authority or resources to act. The guide to Appreciative Inquiry’s wholeness principle considers whose perspectives belong in that inquiry.

The team chooses two small account trials, on 7 and 9 February, with a named receiving owner and one return time for each. Jonah authorizes twenty staff-minutes per handoff within paid time. Rae and Ivo agree what information the receiving colleague needs; neither agrees to copy customer histories into the coaching resource. A sanitized practice example is sufficient for learning. Customer remedies and access permissions stay with the people responsible for those systems.

Before assigning the resource, check the actual participant route and what the participant can read. A coach seeing a course in preview does not establish a colleague's access; enrollment, grants or other applicable access rules and lesson release can differ. Let someone use a brief paper prompt instead. Completing a lesson or ticking an action shows a recorded interaction, not that the customer received the answer or the handoff worked.

A worksheet that connects strengths to operating conditions

Notice that the design includes information and authority, not just a more enthusiastic attitude. If the successful example relied on overtime, ask whether the process can work sustainably. A heroic exception is not automatically a model for everyone.

For individual coaching, the same structure can explore a good delegation, a useful boundary, or a productive planning day. Keep the example relevant to the current goal. The client should be able to choose what to repeat without being told that every difficult feeling represents a deficit mindset.

Handle skepticism and difficult information openly

Some participants will worry that a strengths-based workshop is a way to silence complaints. Explain how problems and immediate responsibilities will be handled. Ask what would make the inquiry credible to them. A candid answer may reveal a practical barrier the facilitator needs to address.

If people cannot recall an excellent example, ask about a time the situation was slightly less difficult or about a capability they have observed elsewhere. Do not demand a success story that does not exist. You can also stop and use a different method when the task is an urgent investigation or correction.

Budget decisions still require costs, priorities, and tradeoffs. Appreciative inquiry can identify an existing strength to build on, but it does not establish that a proposal is affordable or that everyone should support it. Record the evidence and make the decision through the appropriate authority.

In Coachful, a reflection worksheet or team resource can preserve the example, design choice, and review date. Keep the record short enough to use. A collection of inspirational stories has limited operational value if nobody can find the decision or tell who owns the next step.

Turn a good example into a feasible budget choice

Suppose a customer-support team identifies an excellent handoff that relied on two people overlapping for an hour. The appreciative conversation has revealed a useful condition, but the organization cannot afford that overlap for every shift. The next task is design under constraints, not an instruction to amplify the strength regardless of cost.

Ask which part of the overlap mattered. Perhaps it allowed a short explanation of unresolved cases, or gave the receiving colleague a chance to ask one question. The team could compare a brief structured handoff, a shared case summary, and a small targeted overlap at the busiest time. Each option needs a cost and an owner.

Then define what the experiment should show. For example, the team might review whether cases contain the required information and whether customers need to repeat their issue. Include the staff effort required. A process that improves one metric by creating unsustainable unpaid work is not a dependable improvement.

The appreciative starting point has expanded the design options without deciding the budget. The authorized person still needs to compare alternatives and make the tradeoff explicit. If no option is currently feasible, record that constraint rather than asking people to maintain a positive attitude toward an impossible plan.

Use a clearly bounded model when comparing the options. Suppose one daily handoff requires two colleagues, each costing £30 per hour, over twenty working days. A full hour of overlap for both costs £1,200 in this model. Ten minutes each costs £200, a modeled £1,000 difference. These are selected staff-time valuations, not cash already saved, a complete operating budget or proof that the shorter option works. Setup, systems and other work would need separate consideration.

The trial is smaller than that monthly model. On 7 February the two colleagues use eighteen staff-minutes in total; the customer does not repeat the issue and the return commitment is met. On 9 February they use twenty-five staff-minutes. The record is complete, but a downstream team cannot read it, the customer repeats their history and the promised return is forty-five minutes late. The second trial exceeds its twenty-minute allowance by five. Across both trials, forty-three staff-minutes were used against forty authorized. One satisfactory handoff out of two is a description of this small test, not a general success rate.

Include experiences that challenge the preferred story

When a group hears one successful example, it may assume the same method will work everywhere. Invite another person to describe a situation where the conditions differed. A remote team, a new employee, or a customer with an accessibility need may reveal a limitation that the original story did not include.

Ask what should be preserved and what must adapt. This keeps the inquiry generative without making agreement a condition of participation. A person who identifies a risk may be contributing to a stronger design rather than resisting positivity.

At the review, include evidence that the experiment did not work as hoped. Perhaps the handoff became more complete but took too long, or customers still repeated information because a different team lacked access. Use that result to refine the process. Appreciative inquiry is more credible when people can name a disappointing result and still participate in choosing the next step.

Eleri and Jonah meet alone for the thirty-minute manager review on 12 February. Jonah refuses an immediate wider rollout. He asks for the access problem to be owned before another account is added. Before that review, Rae reports that the more complete record helped her prepare, while Ivo reports that the extra time still needs a real staffing decision. Those responses can coexist. Eleri corrects her draft claim that appreciative questions had solved the handoff problem. The revised conclusion is that named ownership helped once and the second trial exposed unresolved access and capacity constraints.

The HSE's Management Standards guidance on demands treats achievable work within agreed hours as a work-design issue. In this example, that supports examining the paid-time allowance rather than asking Ivo to become more positive about unpaid work. It does not provide a clinical assessment or determine an employer's legal position.

Prepare a balanced closing summary

Close the inquiry with four points: the capability the group wants, the example that informed it, the design choice, and the evidence needed at review. Include any immediate corrective action in its own line. This helps participants see that appreciating a strength has not displaced responsibility for a current failure.

For the handoff example, the summary might say: “We want customers to receive a clear answer without repeating their issue. Named ownership helped in the example we examined. We will try a brief structured handoff on two accounts and review completeness, customer repetition, and staff effort.”

Ask participants to correct the summary before it becomes the plan. If someone thinks the example was atypical or the workload has been understated, capture that concern and decide how to check it. The resulting experiment is stronger because it includes the question rather than concealing it.

Eleri promises the corrected decision note for 13 February at 12:00 but sends it at 12:25. Jonah opens it at 12:40 and points out that it still calls the access problem resolved. Eleri withdraws that version and sends a corrected note at 13:05, which Jonah reads at 13:20. The accurate copy is sixty-five minutes after the original promise; the first, inaccurate copy was twenty-five minutes late. Eleri apologizes and records both failures. A readable corrected note does not erase the missed commitment.

Rae declines permission to include her named complaint in a sponsor presentation. The team authorizes only the aggregate two-trial results and the outstanding access decision. The fifty-minute team inquiry and thirty-minute manager review total eighty facilitator live minutes. With four people in the first and two in the second, those meetings involve 260 participant-minutes, excluding preparation and all trial work. They are different measures, not interchangeable costs.

The scheduled 16 February access check remains future and unknown when the example closes. Jonah declines another positivity workshop while the operational decision is pending. Eleri accepts that limit and leaves a brief record of what was learned, what failed and who owns the next decision. Explore Coachful's coaching workspace for organizing the agreed practice, without treating the workspace as evidence that the operational problem has been fixed.

Frequently asked questions

Does the positive principle mean ignoring a crisis?

No. Address immediate harm, legal duties, safety, and operational failures through the appropriate process. Appreciative questions may support learning alongside that work, but should not replace necessary investigation or correction.

Do deficit questions damage the brain?

Do not make that claim. The effect of a question depends on context and many other factors. A coach cannot infer a person’s neurochemistry from a conversation or promise a specific biological effect from a positive question.

How is this different from positive thinking?

It asks people to examine real examples and the conditions behind them, then design action. Encouragement without evidence or a practical decision is not the same process.

Can it help with budgeting?

It can reveal strengths and useful possibilities, but financial decisions still require costs, constraints, alternatives, and clear authority. A compelling story should not bypass a responsible appraisal.

How quickly should results appear?

A conversation may produce a useful idea quickly, while implementation and reliable improvement take time. Agree an appropriate experiment and review date rather than promising a rapid cultural transformation.

The positive principle is most useful when it sharpens inquiry into something worth building. Ask for evidence, understand the conditions, and give the next action a realistic owner and review point.