Scaling and Exception Questions: A Practical Coaching Guide

Scaling and exception questions help a client describe a concern, examine an occasion when something relevant was different, and choose what to investigate or try next. An exception is a specific difference related to the client’s concern, rather than any positive fact the coach can find.

A conversational score can make the account easier to discuss, but the client can use words instead. Keep the inquiry flexible enough for no exception, worsening circumstances, outside help, or a discovery that the previous approach will not transfer.

We build Coachful. Coachful is our #1 recommendation for organizing agreed coaching resources, actions and review because we build it for that work. This is our maker preference, not an independent ranking or evidence that a software completion represents a useful exception.

Use the client’s concern to define an exception

Steve de Shazer, Insoo Kim Berg, and colleagues developed solution-focused brief therapy at the Brief Family Therapy Center. The SFBTA Research Committee’s 2025 manual describes preferred futures, scales, exceptions, and collaborative conversations. The coaching sequence below is an original practical arrangement of these ideas.

That manual is a therapy source, not a trial of this executive-coaching sequence. It distinguishes exceptions relevant to what the client wants different and accepts accounts that nothing is better or things are worse. Keep that lineage clear without importing a full clinical protocol, treatment claim or assumption that the coach is qualified to provide therapy.

Four useful purposes are to make an all-or-nothing account more specific, examine what supports the current position, consider whether a manageable change is possible, and keep the client involved in deciding what matters. None requires a particular positive answer.

Clients bring knowledge of their own experience, priorities, and circumstances. They may also need information, resources, or expertise they do not currently have. Looking for an exception should help identify those conditions rather than prove that every solution already exists inside the person.

Follow four steps without forcing a success story

1. Agree the concern and anchors. Choose a specific situation and period. If using a scale, let the client define what low and useful-enough mean. Ask what the current description represents.
2. Explore what is already supporting the situation. Ask for concrete examples, people, resources, or conditions. Do not insist on a lower-number comparison if the client is at the minimum or dislikes it.
3. Examine an occasion that differed. Ask when the concern was less present or handled differently, what happened, and what contributed. Check relevance before calling it an exception.
4. Choose a next experiment or inquiry. Identify what may be worth retaining, what cannot be reproduced, and what needs permission or support. Agree one action and a useful review point.

A half-point label can help a client name a modest next sign. It does not create equal units of change, guarantee easy progress, or require the scale to rise at every review.

De Shazer’s 2001 discussion of scaling emphasizes the meaning of a rating in its conversational context. Here, Ren’s half point is a personal description, not a measured interval. Ask which event supports it and what remains difficult. A number can stay the same while a decision becomes clearer, or fall because the client now recognizes a previously hidden constraint.

Respond respectfully to difficult answers

Avoid treating disagreement with the question as resistance to be bypassed. A coach can acknowledge a difficult account without claiming to know the hidden strength beneath it.

Worked dialogue: a CTO examines a reorganization concern

In this fictional example, CTO Ren says a reorganization has damaged engineering planning. Two deadlines have slipped and managers disagree about who can change priorities. The coach asks which part Ren most wants to address.

Maren is Ren’s coach. Their 10 November 2026 conversation lasts fifty-five minutes: five to agree the concern, ten to describe anchors, twenty for the dialogue and its elaboration, fifteen for rehearsal and five to choose the next inquiry. All case times below are UTC. The thirteen turns are an excerpt within that twenty-minute section. Yesterday’s triage involved managers Tess and Omar and a checked Product dependency; it did not establish authority across every product area.

Ren: Nothing is working. I have lost everyone’s respect.

Coach: Which situation would be most useful to examine today?

Ren: Planning changes. Nobody knows whether a new request overrides the release plan.

Coach: How would you describe a planning discussion that works well enough?

Ren: We can name the decision owner, the trade-off, and what will be deferred.

Coach: Where does the current process stand against that description?

Ren: Maybe two and a half on a one-to-ten scale. Our service is still running and four principal architects are still here.

Coach: Those may matter. Is there also an example directly about a planning change?

Ren: Yesterday, two managers brought a triage proposal. They named the owner and the work that would move.

Coach: What made that possible?

Ren: They had checked the dependency with Product. I let them present the actual trade-off instead of changing it in the room.

Coach: Which part would be useful to investigate for another request?

Ren: Whether the request has the right owner and dependency information before we discuss dates. I also need to confirm the authority map, rather than assume those managers can settle every conflict.

Service continuity and staff presence are not automatically exceptions to unclear planning. The coach stays with Ren’s chosen concern and develops a relevant event. Ren leaves with a preparation question and an authority check to pursue before the next planning change.

Ren defines one as a planning change in which no owner or consequence can be identified, and ten as a discussion with a usable decision route, explicit trade-off and recorded deferral. Two and a half describes the present week against those anchors. Ren does not agree to have that private rating reported to sponsor Amina, used to compare managers or treated as a percentage of organizational health.

Use a filled exception and review record

In Coachful, prepare these fields as a resource or short form for the intended client. Explain who can read submitted responses, and record the agreed task in the ordinary client plan. Keep technical incident or personnel details in their approved organizational systems.

If using a recurring coaching flow, preview its questions and check audience, availability, Home placement, and reminders separately. Agree a review cadence rather than implying continuous monitoring. For sensitive sessions, check recording arrangements and the automatic recap settings, including approval controls and session-type overrides.

For this case Maren deliberately grants Ren the agreed resource and sends its supported private client-access route. Ren confirms on 11 November that it opens. A copied link alone would not create access, and a standalone assigned form is not guaranteed to appear in What to do next. The filled example remains an aid to discussion, not a new scorecard for Ren’s managers.

Keep recap decisions separate from saving the form. Recaps send automatically by default unless the applicable approval rule holds them; a session-type choice can override the workspace setting. Maren checks the relevant type and holds the recap for review. Ren’s private account is not sent to Amina simply because a summary or task exists. Goal-linked task and habit counts show recorded activity, not whether an exception transferred or a resource owner accepted a proposal.

Connect an optional preferred future with a real occasion

A preferred-future or miracle question can help when the client cannot yet describe what they want instead. Use original language, such as “If the next planning conversation were useful, what would take place?” Then explore whether any relevant part has happened before.

The order can change. Ren first identifies a useful interaction and then considers an actual triage discussion. Another client may need to understand their current concern before describing a future at all. Do not insist that the preferred future must already exist in miniature.

Try the reverse check: if the client described a useful future but no relevant past occasion, could you still help identify a needed condition? If yes, an experiment may begin by requesting information or support. If the required authority refuses, record that answer rather than relabel the refusal as an internal confidence obstacle. Choosing another inquiry remains a legitimate outcome.

The miracle and scale guide develops the connection in more detail, with room for uncertainty and changing evidence.

Adapt the inquiry carefully when energy is the concern

A nonclinical energy conversation can have four purposes: describe ordinary capacity, examine a less demanding occasion, understand the support or reduced demands involved, and choose an appropriate next work or support action. Keep these questions focused on the client’s own account and an appropriate support decision.

If a client says Tuesday was easier because a colleague covered an evening call, explore that work arrangement. The next action may be an authorized workload review, rather than prescribing a pause, caffeine, exercise, or another personal habit.

Persistent unexplained fatigue or tiredness affecting daily life deserves appropriate healthcare advice, as the NHS symptom guidance explains. The energy scaling guide separates that boundary from the work decisions a coach can help a client consider.

Keep a work observation and a symptom explanation separate. A quieter Tuesday can suggest that call coverage mattered, without explaining the cause of persistent fatigue. Ask whether the client wants to consider an authorized work change, seek healthcare advice or pause the exercise. A lower score does not authorize the coach to diagnose burnout or prescribe a recovery routine.

Use four tasks during an executive transition

1. Examine existing useful work. Ask the incoming leader to identify an actual process worth understanding, including input from the people doing it. Avoid assuming every high-performing unit succeeds for the same reason.
2. Protect what matters while investigating. Before removing a practice, understand its purpose and dependencies. Necessary action on harm, safety, or compliance should still follow the appropriate process.
3. Test transfer conditions. Ask what made a useful practice possible and whether another team has the same authority, skills, and resources. Obtain agreement before changing their work.
4. Choose a bounded early action. Define the owner, expected sign, review, and stopping condition. An early action can reveal information even if it does not immediately produce a visible victory.

For Ren, a proposal involving three product areas later reaches the review. The earlier triage format identifies the conflict but cannot resolve it because the managers lack authority to allocate shared engineers. The useful next step is a decision by the authorized resource owner, rather than more enthusiastic repetition of the same questions.

The two relevant changes provide mixed evidence. On 12 November the one-area request names an owner and proposed deferral, but Tess points out a missing quality-assurance dependency. The criticism is valid. Ren corrects the brief on 13 November and leaves the release decision pending verification. Calling the preparation useful does not make the original omission harmless.

On 17 November the three-area request makes the allocation conflict visible. Ren sends it to resource owner Quinn on 18 November. Quinn acknowledges receipt on 19 November but accepts no decision date and grants no engineers. HSE’s Role and Change standards emphasize clear responsibilities, routes for concerns, information and consultation during change. They support examining the organizational conditions; they do not turn a coaching question into authority to allocate staff.

Develop four management practices with usable records

1. A focused weekly review. Choose one relevant work situation and ask what was different, what mattered, and what decision follows. Personal coaching scores need not become a public team dashboard.
2. A ten-minute peer conversation. Use two minutes to agree the concern, three to examine one event, three to consider conditions and the next choice, and two to confirm an owner and review. That totals ten minutes. Keep advice and questions within the peers’ competence.
3. A small practice repository. Record situation, action, conditions, limits, and review date. An entry should help someone decide whether a practice fits their context, rather than promise a universally proven solution.
4. A learning-focused incident review. Ask which actions limited harm alongside the required causal analysis and corrective work. Useful actions and unresolved failure causes can be examined together.

A provisional repository entry from Ren’s case reads: “For a change within one product area, bring the named decision owner, checked dependency, and proposed deferral. If the request crosses resource authority, route it to the authorized owner. Review the next two relevant changes before extending the format.” This retains the useful condition and the boundary.

Ren and Tess use the ten-minute peer format on 27 November for a business discussion. Two minutes establish the unresolved allocation concern, three examine the 17 November request, three consider the next contact and two confirm the record. Tess declines to attach a delivery date before the allocation decision. Ren records the refusal accurately. That discussion is not another coaching session or permission to expand the format to every team.

Review what the inquiry helped clarify

At review, distinguish the action attempted, the client’s account, relevant observations, and other influences. A changed rating may reflect new understanding or different conditions. Ask what the description means now rather than treating the number as empirical organizational telemetry.

For Ren, the inquiry distinguishes a useful preparation practice from a decision that requires wider authority. That is a concrete result to review. Any broader evaluation of the engagement needs its own evidence, relevant costs, and consideration of other influences.

At the thirty-five-minute coaching review on 20 November, Ren uses three rather than two and a half. Ren explains it as better recognition of where decisions belong, while the dependency omission and resource conflict remain. Maren initially describes both planning changes as resolved and engineering confidence as restored. Ren challenges those claims in that conversation. Maren withdraws them and apologizes. Neither the rating nor the retained practice supports that wider conclusion.

Ren authorizes only a four-sentence business note to Amina: the preparation tried, the omitted dependency and correction, the cross-area request awaiting authority, and the proposed follow-up. The private rating, coaching dialogue, managers’ names and technical detail stay outside it. The approved note is due on 23 November at 16:00 but goes on 24 November at 11:00, nineteen hours late. Amina acknowledges it at noon and asks when allocation will be settled. Ren replies on 25 November that no date has been accepted.

The 30 November twenty-minute coaching close reviews the two changes before any wider use. Ren retains the preparation questions and the distinction between acknowledgment and approval, but declines a larger rollout or another experiment for now. Ren accepts responsibility for contacting Quinn again on 4 December. At this close that contact and Quinn’s decision are future and unknown; Maren has no further monitoring or coaching booked.

The three coaching conversations total 110 client-live minutes: fifty-five, thirty-five and twenty. The twenty-minute dialogue is already within the first conversation. The ten-minute peer discussion, company planning meetings, preparation, written correction and sponsor receiving work are outside that total. It is neither a complete labor account nor a demonstrated saving from using exception inquiry.

A useful conclusion is a decision: retain a contribution, adjust the experiment, request support, or choose another focus. The client can recognize what helped while remaining candid about what is still difficult.

Use the record to keep an unresolved question visible. Moving it into a completed task list would lose the distinction between asking for a decision and receiving one.

Frequently asked questions

What counts as an exception?

A specific occasion when the client’s actual concern was less present or handled differently. Check relevance and context rather than selecting any positive fact.

What if there are no exceptions?

Accept the answer. Explore present needs, missing conditions, or another focus. Finding an exception is not a condition for receiving coaching.

Can I compare scores between executives?

Not as interchangeable measures. Each person’s anchors, concern, and context may differ. Ask what the number means before drawing conclusions.

Should every experiment be tiny?

Choose a manageable, appropriate action. A small inquiry can reveal a substantial resource or authority decision that needs its own proper process.

Does exception inquiry replace root-cause analysis?

No. It can help examine useful actions alongside technical, safety, or other required investigations. Keep each process’s role clear.

Sources and further reading

• SFBTA Research Committee (2025). Solution Focused Therapy Treatment Manual for Working with Individuals, third edition. Selected primary sections on exceptions, preferred futures, scales, and collaborative practice.
• Steve de Shazer (2001). Scales and Scaling. Brief Family Therapy Center. Subjective meanings and contextual use of ratings.
• NHS. Tiredness and fatigue, current primary symptom-advice page. Guidance on seeking healthcare advice for unexplained or daily-life-affecting tiredness.

Prepare resources and keep agreed follow-up organized with Coachful features.