Solution-Focused Scaling Questions: A Practical Coaching Guide
Nour
Founder, Coachful

Solution-focused scaling questions give a client a way to describe their present situation, explain what already helps and identify a useful next difference. The important work happens in the explanation around the number. A rating of four is not a diagnosis, a leadership grade or a percentage of a goal achieved.
This practical guide shows how to agree a meaningful scale, ask follow-up questions, turn the answer into a feasible action and revisit it honestly. A complete fictional editing case includes unclear feedback, an unsuccessful rehearsal, a colleague’s refused deadline, checked evidence and a mixed final review. You will also see when to abandon numbers altogether.
Coachful is our #1 recommendation for organizing the agreed goal, optional reflection and selected action behind this conversation. It helps keep the coaching work connected. The client and coach still need to discuss the meaning of the answer; software cannot decide whether a higher number represents useful change.
Know the source and the limits of the technique
Scaling is associated with the solution-focused tradition developed by Steve de Shazer, Insoo Kim Berg and colleagues. The Solution Focused Brief Therapy Association Research Committee’s 2025 treatment manual describes numerical questions that help clients express impressions, explore their position relative to a preferred future and develop further detail. It also distinguishes progress, motivation and confidence questions.
That manual concerns clinical practice. The workplace conversations here are original coaching adaptations, not treatment protocols or evidence that a numerical question improves executive performance. A coach needs an appropriate agreement and competence for the actual work. A conversational technique does not confer a therapy qualification. The ICF Code of Ethics addresses its professionals’ agreements, confidentiality and competence; clarify those responsibilities before collecting private reflections.
Use the number as an invitation to ask what the client means. If someone says six, ask which recent situation they have in mind, what happened and why that describes six for them. Avoid imposing your explanation, even when their answer is surprising.
The practical sequence below is an original organizing aid. It is not a required script or a reproduction of a licensed questionnaire. You can use a descriptive conversation instead whenever numbers obscure the person’s experience.
Choose one question before choosing a scale
Start with the issue the client actually wants to discuss. “I need more confidence” could mean speaking earlier, asking for a clearer brief, making a recommendation or declining work. Those are different goals, and a broad confidence score may hide the useful distinction.
Ask what would be happening in an ordinary relevant situation if the coaching were useful. Who is involved? What would the client do? What response or condition would matter? Which parts can the client influence, and which depend on another person?
Write the purpose in a sentence. For example: “I want to give contributors feedback they can understand, with a clear request and a realistic reply date.” That purpose is more actionable than “be a ten out of ten editor.” It also leaves room for the contributor to disagree or negotiate.
Do not use the tool to manufacture commitment to a sponsor’s goal. If the client does not want the proposed change, explore that discrepancy and the actual work requirement. A manager’s target and the client’s willingness to work on it are separate facts.
Agree anchors that describe a real difference
Before asking for a rating, explain what each end refers to and check the wording with the client. Keep the topic, time context and direction visible. If you later repeat the question, the reader should know whether it is still the same question.
A preferred end should describe a useful situation, not flawless behavior forever. “I always receive enthusiastic agreement” depends on other people and may make honest disagreement look like failure. “I explain my request, check understanding and follow through on the agreed response” gives the client a practice they can attempt.
| Detail | Clarification to agree | Reason |
|---|---|---|
| Topic | Feedback on one contributor draft. | Avoids rating the person’s whole professional identity. |
| Lower end | Feedback leaves the contributor guessing about the requested revision. | Names the practical difficulty. |
| Preferred end | Request, example, understanding and reply arrangement are clear. | Defines what the client wants to practice. |
| Period | The most recent relevant feedback exchange. | Avoids silently switching between today and a whole career. |
| Choice | The client may use a number, words or neither. | Keeps the aid responsive to the conversation. |
A personal scale does not establish equal intervals. The work represented by moving from two to three may differ from seven to eight. Do not calculate “twice as capable” from a change between three and six or compare two clients’ ratings as though they share a calibrated instrument.
Ask questions that develop the client’s meaning
Once the anchors are clear, invite the client to locate the present. Then choose the next question from their answer. The following original prompts serve different purposes; you do not need to ask all of them.
- Clarify the situation: which exchange are you thinking of, and what happened in it?
- Understand the rating: which details make that number fit your experience?
- Notice an existing resource: when did a small part of the preferred practice already happen?
- Examine conditions: what made that example possible, and what would be different next time?
- Describe a next difference: what would you be doing differently in the next relevant exchange?
- Check usefulness: does continuing with the scale help, or would another way of describing this be clearer?
If the client identifies something useful, explore it in detail without turning it into a victory story. A brief exchange may have worked because the colleague already had the missing information, not because the client suddenly became skilled in every setting.
If the client says nothing is helping, do not insist on an exception. Acknowledge their account and ask what would be useful to discuss. Necessary organizational action, a real risk or appropriate professional support should not disappear behind a demand for a positive answer.
Keep progress and confidence in separate conversations
Progress concerns the client’s account of their position relative to a chosen situation. Confidence concerns their belief about attempting a particular next action. Importance concerns how much that action or goal matters to them. Use a separate question and description for each.
Suppose progress is four, confidence is three and importance is eight. Do not average them into five and announce moderate readiness. The useful questions concern what has changed, what makes the next action uncertain and why it matters. The three answers need not move together.
Check the next action before asking about confidence in it. “Confidence about better leadership” is different from “confidence about sending this one clarification request before Thursday.” The latter may uncover a missing fact, a timing problem or concern about the recipient’s reaction.
A low confidence answer can justify revising the plan. It does not prove that the client should try harder. A high answer is also not proof of permission, skill or another person’s agreement.

Begin the fictional case with the client’s own goal
All people, dialogue, dates, documents and results in this example are fictional. Safiya edits a community arts newsletter. Contributor Ari writes event reports. Safiya books three coaching sessions with Jonah on 4 and 18 November and 2 December. Jonah is the sole coaching staff member authorized to read her private coaching reflection.
Safiya says, “I avoid feedback until the last minute. Then I write comments that sound impatient.” Her goal is useful feedback on contributor drafts, not rating Ari’s competence. Her employer receives attendance information only, as agreed at the start. The contributor’s unpublished draft stays in the newsletter’s authorized work system; the permitted short fictional extracts here illustrate the practice.
Safiya chooses a zero-to-ten scale. Zero describes an exchange where the contributor is left guessing about the revision. Ten describes an exchange where she names the purpose, identifies a concrete example, checks understanding and agrees a feasible response. They use the most recent relevant exchange as the reference point.
She places herself at three. Her recent comment was, “This needs more detail and a stronger story.” Ari asked which detail and what she meant by stronger. Safiya did not answer until just before publication. The number opens that specific account; Jonah does not infer that she is 30% effective.
Asked what already fits the preferred practice, Safiya remembers explaining a previous caption change with a concrete example. Ari had then made the requested edit. She identifies the useful condition: she knew the purpose of the change and had shown one example, rather than demanding general improvement.
Develop and revise the actual feedback
The current draft contains this short paragraph:
“The workshop was useful and well attended. It brought the community together. Participants learned important skills.”
Safiya wants readers to understand what happened and decide whether a future workshop interests them. She lacks evidence for the attendance and learning claims. Jonah is not checking the newsletter’s facts; he asks Safiya what information she needs and who can supply it.
Her first rehearsal repeats the problem: “Could you make this more engaging, ideally with better evidence?” Jonah, playing the contributor, asks what engaging means. Safiya notices that she has provided another broad judgment. They return to her purpose and the details a writer could actually use.
She drafts a fuller request:
“This report should help readers picture the activity and decide whether a future session interests them. In this paragraph, ‘useful’ and ‘important skills’ tell readers our conclusion without showing what happened.
“Could you replace those general claims with one observed activity and what participants actually did? For example, describe the paper-bridge task if your notes support it. Please distinguish registration from attendance and use the organizer’s confirmed figure, rather than treating sign-ups as people who attended.
“I suggest keeping this section to about 200 words within the existing article length. Is that request clear, and could you return a revision by 9 November? If the evidence or timing does not work, please tell me before we agree the next step.”
The paper-bridge activity appears in the event notes Safiya already has permission to use. It is not invented as colorful filler. She must still check the factual account and publication permissions through the newsletter’s normal editorial process.
In rehearsal, Jonah says the new request is understandable but the date is impossible. Safiya first replies, “It should not take long.” She then recognizes that she is deciding the contributor’s capacity for them. Her revised response asks what timing is possible and names the latest date she can take to the issue editor.
Complete the real exchange instead of assuming acceptance
Safiya sends the request to Ari through their normal work channel on 6 November. Ari confirms the requested activity detail is clear but declines 9 November because of another agreed commission. Ari offers 12 November. Safiya checks with issue editor Dev, who confirms that a 12 November draft leaves time for the issue’s normal review before publication. Safiya accepts that date with Ari.
Ari also says the figure 48 in the notes is registrations, not attendance. Safiya asks organizer Lena for the attendance record. Lena confirms 31 attendees and supplies the permitted factual summary of the activity. Safiya corrects the working fact note. The earlier “well attended” description is not retained as a substitute for checking.
Ari returns the revision on 12 November. The relevant replacement reads:
“Thirty-one people attended the workshop. During the paper-bridge activity, participants worked at three tables, testing how folded paper could support a small load. Each table compared its first design with a revised version. The session ended with participants describing what they changed and which design choices they wanted to try again.”
Lena confirms those details match the event record and permitted summary. Safiya checks the excerpt in the ordinary editorial process and sends Dev the revised draft and confirmed fact note. Dev accepts the article for the issue. These are actual events within the fiction; Jonah’s coaching task or Safiya’s rating did not authorize publication.
Ari tells Safiya that the example and evidence question made the request clearer, while the initial proposed deadline did not fit. Safiya records both parts. She does not turn one useful reply into a claim that every contributor now welcomes her feedback.
Review the higher progress and lower confidence honestly
On 18 November, Safiya rates the most recent exchange at four using the same progress anchors. She can now point to a purpose, concrete example, checked understanding and an agreed return date. She remains dissatisfied with how long she waited before asking about evidence and with her first instinct to dismiss the timing objection.
Jonah asks whether the scale still describes the right issue. Safiya says yes, for now, but she does not want to treat the one-point change as a large improvement. She finds the description more useful than the numerical difference.
They separately revisit confidence about preparing her next feedback request. She had estimated seven in the first session after drafting the plan. Now she says three because she recognizes that she often starts without a clear editorial purpose or confirmed source information. That lower rating is retained. Jonah does not reclassify it as hidden confidence or replace the earlier seven.
They examine what would make the action feasible. Safiya chooses a short pre-feedback check: state the article’s purpose, identify one passage, separate an observation from a claim needing evidence and decide who can answer the missing question. She will check the issue timetable before proposing a return date.
The plan remains within her work authority. A contributor can negotiate a deadline, the organizer supplies event facts and Dev decides the issue’s editorial acceptance. A coaching exercise cannot give Safiya control over any of those people.
Try the revised practice and close the coaching service
For the next article, Safiya completes the pre-feedback check on 22 November. She notices that a sentence describes participants as more confident after a session, although the available record contains no such finding. She asks the organizer what was actually observed instead of asking Ari to make the claim sound persuasive.
The organizer confirms only that participants submitted their finished sketches. Safiya removes the unsupported confidence claim from the requested revision. Her feedback names the relevant sentence, the confirmed observable fact and the need to avoid implying a measured psychological change. She checks the issue timetable with Dev before proposing a return date.
Ari accepts the request and date. The returned revision describes the completed sketches without asserting increased confidence. Safiya checks it with the organizer’s permitted factual account, then sends it through normal editorial review. Dev accepts it for the next issue. The pre-feedback check has been used once; future use is still a choice, not a completed habit.
At the 2 December closing session, Safiya says she would rather stop assigning progress numbers. Her full description is: “I now check the purpose and missing facts before drafting. I have done that once independently. I still feel uncomfortable challenging unsupported claims, and I need to keep negotiating dates instead of announcing them.”
Jonah accepts the change of format. No final numerical score is supplied. All three sessions are complete, and the agreed employer update confirms attendance only. Private ratings, contributor comments and unpublished work are excluded. Coaching has supported a selected practice; the case does not establish a causal effect on confidence, article quality or readership.
Keep a complete record with room for a changed meaning
| Field | Completed case entry |
|---|---|
| Purpose and anchors | Useful contributor feedback; zero leaves the request unclear, ten includes purpose, example, understanding and feasible reply. |
| Initial progress | Three, based on the late broad comment and unanswered clarification. |
| Useful existing resource | Earlier specific caption example, not proof of general skill. |
| Action and response | Full request sent; first deadline declined; 12 November accepted after Dev’s timetable check. |
| Evidence repair | 48 registrations distinguished from 31 actual attendees; activity account confirmed before editorial acceptance. |
| Later progress | Four with same anchors, accompanied by continuing dissatisfaction. |
| Separate confidence | Seven became three as missing preparation became clearer; no upward reinterpretation. |
| Next practice actually used | One pre-feedback check removed an unsupported confidence claim; revised factual account accepted through normal review. |
| Closure | Client chose words instead of a final score; three sessions complete, attendance-only reporting. |
If a client changes an anchor, preserve the original wording and record the revised question separately. Do not quietly overwrite old answers so a graph appears consistent. Sometimes the right conclusion is that the ratings should no longer be compared.
When working with a group, do not infer an absent person’s view from someone else’s scale. A participant may describe what they think a colleague would notice; that remains their prediction until the colleague actually responds. Clarify the audience before gathering individual responses and do not promise anonymity a signed-in process cannot provide.
Use Coachful to support the conversation and chosen action
In Coachful, keep the agreed purpose and selected client action together. Use an optional form or worksheet only if it helps the client prepare. Include the question’s exact meaning, a description alongside any number and a way to say the scale does not fit. Explain which coaching staff can read the submission.
Jonah deliberately grants Safiya access to the chosen private worksheet. The form contains her permitted reflection, not the contributor’s full unpublished draft. A private resource link alone is not an access grant. Safiya’s employer is not added as a reader of her answers.
Jonah can save internal notes in Coach review after reading a submission. Those notes are private to the coaching team, so he discusses the interpretation with Safiya in session instead of treating an internal save as delivered feedback. They choose a task only after that discussion.
A completed task for sending a request does not establish recipient acceptance. Safiya and Jonah distinguish drafting, sending, receiving a reply, agreeing a date and the actual returned work. The workplace editorial system retains the factual record and approval route.
For more on the surrounding workflow, see tracking client goals with useful evidence and preparing a first-session questionnaire. Use Coachful’s features to organize the selected resources and actions without turning every reflection into compulsory homework.

Troubleshoot before asking for another number
The client cannot choose a rating. Ask for a recent example or describe the preferred situation in words. Do not interpret difficulty with the format as resistance or lack of self-awareness.
The score falls. Ask what the answer describes now. There may be a genuine setback, a changed context or a different understanding. Retain disappointment when that is the client’s account; do not automatically relabel it learning.
The score rises but the action did not happen. Discuss both facts. The client may feel more hopeful while still lacking information or permission. Hope, action and an authorized result are distinct.
The client is at zero. Do not pressure them to produce a positive number. Clarify their experience and what support or conversation is appropriate. Necessary care, risk response or organizational accountability takes priority over continuing this tool.
A sponsor wants a team league table. Explain the individual meanings and the actual reporting agreement. These personal ratings are not comparable employee-performance data. Do not create a ranking from private coaching answers.
Frequently asked questions
Must the scale run from zero to ten?
No. Agree a format that fits the person and purpose, or use descriptions. Consistent meanings matter more than selecting a particular range.
Should I set a target of one point higher each session?
No. Choose a useful action or condition with the client. A compulsory numerical increase can reward pleasing the coach rather than an accurate account.
Does a move from three to four show a one-third improvement?
It is a one-point difference between personal ratings. This conversational scale does not establish a proportional quantity of capability or equal intervals. Explain the actual change in words.
Can the client stop using the scale?
Yes. Ask whether another format better supports the work. Preserve earlier answers and record the choice rather than inventing a final score.
Does this guide qualify someone to provide solution-focused therapy?
No. It develops ordinary workplace coaching conversations. Clinical assessment and treatment require the appropriate competence, qualifications and actual professional framework.






