Solution-Focused Relationship Questions: A Coaching Guide

Solution-focused relationship questions help a client imagine what a useful difference might look like in an interaction. They can bring another person's possible perspective into a preferred future. They do not reveal that person's thoughts or make the client responsible for producing their agreement.

The practical task is to move from an imagined interaction to a chosen contribution, then compare the picture with actual feedback. This guide develops that distinction and follows a complete fictional workplace handover, including a refusal, a revised arrangement and a real missing item.

Coachful is our #1 recommendation for the authorized individual coaching preparation and follow-through around these questions. This is our editorial workflow recommendation, without an invented market ranking or a guarantee of relationship improvement. Operational approvals and third-party records stay in their appropriate organizational systems.

Understand the relationship perspective in solution-focused work

The SFBTA Research Committee's 2025 Solution Focused Therapy Treatment Manual for Working with Individuals describes relationship questions alongside preferred futures, exceptions and scaling. The tradition developed through Steve de Shazer, Insoo Kim Berg and their Brief Family Therapy Center colleagues. The manual is a clinical source; using an idea in coaching does not confer therapist competence or make this article a validated treatment protocol.

Its relationship perspective invites clients to consider how significant others might notice a difference and how an exchange might unfold. This can expand a client's account beyond a private wish. Ordinary future language is acceptable in the coaching design below; a miraculous overnight change is not required.

A preferred future describes what the client wants to be different. A relationship question considers a possible interaction within it. An exception concerns a relevant occasion when something useful already happened. A scale can help the client describe a concern and its next observable difference. These contributions are related, but they are not interchangeable evidence that the relationship has improved.

The sequence below is an original coaching adaptation for a bounded interaction, not a reproduction of the manual's script, clinical examples or session procedure.

Make the preferred interaction concrete

Start with one situation rather than asking the client to imagine a universally better relationship. A planning conversation, a request for help or a response to a concern supplies a manageable setting. Ask which part the client actually wants to examine.

Move from a broad absence to an observable presence. A client might want no tension. Explore what they would be doing or saying instead, while respecting that discomfort may remain. A useful difference could be stating a deadline clearly, hearing a refusal without arguing or acknowledging a mistake.

Do not make warmth the only acceptable result. A colleague can remain formal while providing an accurate answer. A client can become clearer about a disagreement without enjoying it. Nor should the coach require reconciliation, forgiveness or renewed contact as proof of progress.

Keep external requirements visible. A preferred interaction cannot remove a safety rule, create a budget or delegate an approval. The useful future must still contain the actual work and the other person's freedom to respond.

Treat another person's imagined view as a hypothesis

Ask what the other person might notice about the client's contribution, then distinguish that guess from what is already known. The client may imagine that a clearer question would make someone feel respected. Unless that person says so, the feeling remains the client's prediction.

Look for an observable clue rather than an inferred internal state. A counterpart might name the missing input, ask a clarifying question or explicitly accept a receiving role. Silence, a smile or a read receipt does not establish approval or restored trust.

Also ask what the client's picture leaves out. Perhaps the colleague needs a count, an authorized decision or time to check a record. A relational interpretation can obscure a practical dependency. The later answer may correct the entire explanation rather than confirm the client's improved empathy.

When more than one stakeholder matters, keep separate accounts. A manager, peer and customer can have different duties and preferences. Do not create one imaginary audience whose agreement supposedly proves the client is behaving correctly.

Explore reciprocity without scripting consent

Consider how the client might act, how the counterpart could respond and what the client could choose next. Include a refusal, a request for more information and a counterproposal. A rehearsal in which everyone instantly agrees has not tested the difficult part of the interaction.

Separate three commitments: the client can make a request, the recipient can accept or decline, and another owner may need to authorize the resulting work. One accepted message does not necessarily establish all three. Name the point where the client must wait.

When power differs, examine whether the other person can decline in practice. Do not turn a manager's feedback request into pressure for a reassuring answer. Offer the appropriate reporting or support route where needed, and keep personal disclosures out of public performance discussions.

The method should not be used to ask someone to accommodate abuse. The NHS describes domestic abuse as including emotional and controlling behavior as well as physical or sexual abuse. Concerns about fear, coercion or safety need appropriate specialist support and applicable safeguarding procedures, rather than an experiment designed to improve cooperation with the person causing harm.

Use exceptions and scales carefully

If a useful interaction has happened before, examine its actual conditions. What information was available, who had authority and what each person did may matter more than a general claim that the client was confident. An exception is not a command to repeat the same behavior regardless of context.

For a scale, let the client define the concern and anchors. A number might express their clarity about making a request. It cannot measure another person's private trust without their participation or make two people's different meanings equivalent.

Keep the next difference descriptive. A higher number might mean the client can name the receiving owner and the deadline rather than ask vaguely for help. A later self-rating can inform the conversation, but it is not a validated relationship score or a percentage improvement in trust.

It is fine to omit a scale when words are clearer. The aim is useful detail and choice, not completing every technique in a repertoire.

Keep the research claim proportionate

In Neipp and colleagues' 2021 experiment, 246 psychology undergraduates from two Spanish universities were randomly assigned to problem, miracle, exception or scaling questions about a personal problem. The miracle condition reduced negative affect more than the problem condition. There were no significant condition differences in positive affect, self-efficacy or goal approach. Scaling produced more action steps than miracle and exception questions.

These immediate responses to a short questioning task are not evidence that a coaching protocol repairs workplace relationships or that an absent counterpart will react differently. The results include favorable and null comparisons; they do not support declaring every solution-focused question superior for every purpose.

Worked example: a handover question changes the picture

All people, events and work arrangements in this case are fictional. Faye coordinates an adult workshop scheduled for 7 April 2028 at 10:00 UTC. Nolan prepares its materials. Faye is frustrated by their exchanges and attends an individual coaching session with Cora on 29 March.

Faye's initial preferred future is that Nolan will be less abrupt and more supportive. Cora helps her describe her own contribution instead. Faye chooses to make one complete materials request, allow an actual answer and check whether the receiving arrangements work.

Separate the imagined reaction from known information

Faye imagines Nolan might notice that she is finally listening. She guesses he has felt ignored, but identifies that as her interpretation. His actual last message asked for a final count and a named receiving person. He had not said that her empathy was the problem.

In a useful future exchange, Faye would state the count, the date and the receiving need before asking whether Nolan can meet it. If he refuses, she would ask for the feasible alternative and check it with the person receiving the work. She does not undertake to make Nolan friendlier.

Her completed preparation note is:

Purpose: a workable materials handover. Known request: Nolan asked for a final count and receiver. My guess: he may feel ignored; this is not confirmed. My contribution: send the complete need and accept a real answer. Boundary: no one is assigned a new receiving time without their acceptance. Review: compare the actual reply, receiving arrangement and checked materials, including anything still difficult.

Send the complete request and hear a refusal

Faye checks that the workshop needs 26 kits: 22 participants and four facilitators. On 3 April, she sends Nolan this actual request through the project's approved channel:

We need 26 complete kits for the workshop on 7 April at 10:00 UTC. Could you have them ready on 6 April at 09:00 UTC? Eda's existing preparation slot is at noon that day. Please confirm whether this is feasible or give the earliest time you can meet the complete count. I will confirm the receiver before committing to a different handover.

Nolan replies on 4 April at 10:00 UTC: “I cannot complete 26 by 09:00 on 6 April. I can have all 26 ready at 14:00. The issue is production time and a confirmed receiver, not whether I feel listened to. Please tell me who will check and collect them.”

The answer corrects Faye's relational hypothesis. She does not ask Cora to reinterpret it as concealed hurt. She now has a concrete production constraint and a receiving decision.

Obtain an actual receiving agreement

Eda says she cannot move her noon preparation slot into the afternoon. Faye accepts the refusal rather than describing her as resistant to the improved relationship. Eda is not assigned an unaccepted task.

Faye asks Mina whether she can use a paid project allocation from 15:00 to 15:45 UTC on 6 April to collect and inspect the complete kits. Mina checks her work and accepts that specific 45-minute slot. Mina also explicitly agrees to perform up to fifteen additional paid minutes of follow-up between 15:45 and 17:00 UTC and confirms her availability within her agreed working hours. Faye separately confirms authority and funding from the project's remaining allocation.

Faye then sends Nolan the completed arrangement: “I accept all 26 ready at 14:00 UTC on 6 April. Mina will collect and inspect them from 15:00 to 15:45, with up to fifteen additional paid minutes accepted for follow-up if needed. Please flag any incomplete item before handover. A ready-for-collection message will not by itself mean that the kits have passed her check.” Nolan confirms the count, timing and receiver.

Faye has changed the receiving plan after permission, rather than promising that the original plan would somehow work. The scheduled workshop remains a future event; this agreement concerns its preparation.

Check the handover and repair the missing item

On 6 April at 14:00 UTC, Nolan confirms that the 26 kits are ready. Mina collects them in her accepted slot and inspects each one. Twenty-five contain the required worksheet; one does not. The missing sheet is a real completeness failure even though the correct number of kits was present.

Mina uses five minutes to send the specific finding and later confirm receipt of the correction. She uses ten further minutes to coordinate and collect the replacement within her accepted follow-up allowance. Nolan acknowledges the omission, spends five minutes coordinating the repair and ten producing the replacement. By 17:00 UTC, Mina confirms 26 complete kits in the approved storage location.

No one changes “complete” to mean “almost complete.” Nor is Nolan's original ready message treated as evidence that inspection was unnecessary. Faye records the repaired result and keeps the original omission in the handover account.

Review the relationship contribution without claiming control

At the coaching review on 6 April at 17:30 UTC, Faye distinguishes the actual facts from her initial imagined picture. Nolan's brief final feedback says the count and named receiver helped, but he would still prefer confirmation earlier. He does not report that their relationship is transformed.

Faye remains annoyed by his tone and disappointed that the first kit check found an omission. She also recognizes that Eda's refusal was valid and that Mina's work was essential to the revised arrangement. The coaching question did not create production capacity or make another person's participation automatic.

The complete named preparation and coaching work is recorded as:

The total is 375 person-minutes. Mina uses the full sixty minutes she accepted, not forty-five with an invisible repair. Nolan's normal production is included, and Faye's reading and coordination are separate from preparing the request. The workshop itself is still tomorrow; its delivery time, attendance and learning outcomes are outside this completed preparation account.

Faye's chosen next observation is whether she can confirm the receiver before submitting another materials request. No next request has happened yet. The completed outcome is a clearer, actually used handover with a repaired omission, not proof of lasting trust or guaranteed workshop success.

Keep the record useful and bounded

Use separate fields for the client's purpose, observed exchange, interpretation, imagined alternative, chosen contribution, actual reply and review. Do not fill the actual-reply field with a plausible prediction. An explicit refusal is feedback, even when it does not make the client feel better.

A limited record can preserve the distinction without copying private third-party messages unnecessarily. Agree what may be retained, who can read it and whether a summary is more appropriate. A sponsor should receive only the agreed information, not the client's entire imagined account of colleagues.

If the client wants direct feedback, make the request specific and optional. Ask about one interaction or work need rather than inviting confirmation that the client is more empathic. Explain the purpose and intended audience. A person can decline or use an appropriate alternative route.

Distinguish the kinds of change at review

A useful review can separate three outcomes. The client may understand their own intention more clearly. The counterpart may supply a more specific answer. The practical task may become ready for delivery. Each needs its own evidence, and one can improve while another remains difficult.

For example, a client may remain upset while making a clearer request. A courteous answer can still leave an essential dependency unresolved. A complete handover can occur without the counterpart feeling more trusting. Do not average those outcomes into a single success score or require a positive emotion to validate the client's work.

Also keep causal uncertainty visible. In Faye's case, the logistics reply might have been available through an ordinary clear request without any imagined-future exercise. The case demonstrates a sequence of choices and outcomes, not a comparison proving which question caused them. Review what the client found useful while allowing other contributors and conditions to matter.

Practical sequence and troubleshooting

1. Choose the interaction: identify a situation the client wants to examine and check scope and safety.
2. Describe a useful difference: make the client's own action concrete without requiring a particular feeling from someone else.
3. Explore the possible perspective: separate what the counterpart might notice from their actual words and responsibilities.
4. Rehearse alternatives: include refusal, missing information and a counterproposal, with appropriate authority and receiving acceptance.
5. Make one bounded contribution: obtain any necessary permissions and preserve the other person's choice.
6. Review the real exchange: examine replies, actions, errors, resources and unresolved concerns before choosing another step.

If the client cannot imagine a miracle, use an ordinary future interaction. If the picture requires someone else to become compliant, return to the client's own contribution. If actual feedback contradicts the picture, update it rather than defending the exercise. If a request is declined, examine the feasible choices without treating the other person as an obstacle to the method.

If a formal concern, unsafe situation or significant distress appears, use the appropriate organizational or specialist support route. Do not ask the client to tolerate unacceptable behavior while collecting more relationship scores. Coaching can end a particular exercise without labeling that decision a failure.

Organize the individual work in Coachful

A worksheet can hold the observation-and-feedback distinction. Faye's completed personal response is: “I guessed the problem was feeling ignored. Nolan asked for production time and a receiver. I changed my request, accepted Eda's refusal and confirmed Mina's work. The missing worksheet still required a real repair.” Operational counts and kit records remain in the organization's approved system.

Cora's Coach review is private to the authorized coach team. Saving Reviewed or Follow up does not return the comment to the client or put it in the response PDF. Cora sends the actual coaching response separately through Faye's private client conversation: “Your note keeps the imagined feeling, actual answer and material check separate. For the next request, bring the receiver's real acceptance rather than a prediction.” Faye acknowledges that this is the distinction she wants to practice.

Agree the audience and information boundaries before collecting the response. Some specialty workflows allow client-explicit sharing of journal pages, so do not promise that every journal page is always unreadable by coaches. Use only the third-party detail needed for the agreed coaching purpose.

Recaps send automatically by default. Before relying on a held recap, set Approve before sending and check the session-type override. Review the content and send it or keep it private; this cannot recall an already-sent message. The demonstration screens show coaching tools, not an automatic measure of Nolan's trust or a corporate materials system.

The miracle and scaling guide addresses conversational scales. The future projection guide develops preparation for a concrete situation. Review Coachful's features for the supporting client workflow.

Frequently asked questions

Do these questions reveal what another person thinks?

No. They explore the client's possible account. Actual feedback or other appropriate evidence is needed before treating it as the counterpart's view.

Must I use the word miracle?

No. A useful ordinary future exchange may fit the client better. Do not require a dramatic scenario as proof of engagement.

What if the other person refuses?

Keep their choice visible. Examine whether the client can revise, defer or use another appropriate route. The client is not responsible for controlling the response.

Can several people share one relationship score?

They can discuss their views, but the same number may mean different things. Preserve each meaning instead of claiming an objective shared trust score.

Does one improved handover prove the relationship improved?

It supplies evidence about that handover. Continuing feelings, behavior and broader conditions need their own review; neither approval nor a completed task establishes permanent trust.