OSKAR Coaching Model: 5 Stages, Questions and an Example

How do you use the OSKAR coaching model without making the client feel they are being marched toward a better score? Start with a difference they actually want, find usable know-how, and agree a small experiment whose value you can review honestly. The number is a prompt, not the point.

OSKAR stands for Outcome, Scaling, Know-how, Affirm and Action, and Review. It gives a coach a solution-focused structure for connecting a preferred future with existing resources and a practical next step. Its most useful feature is not optimism. It is the discipline of asking what could help before prescribing what the client should do.

This guide explains the five stages through one continuous, hypothetical workplace example. The prompts and working record are original educational adaptations, not a client transcript, a validated assessment or a promise of results.

What is the OSKAR coaching model?

Mark McKergow and Paul Z. Jackson developed OSKAR around 2000. Their first-party explanation at sfwork describes its use with independent coaches and managers, including its emphasis on know-how sharing, specific affirmation, small actions and noticing useful change.

Read the letters as connected jobs:

• Outcome: describe the difference the client wants coaching to help make.
• Scaling: explore where the client sees themselves relative to that difference.
• Know-how: identify skills, experience, helpful conditions and available support.
• Affirm and Action: recognize concrete resources and invite a manageable next step.
• Review: examine what changed and what should happen next.

These are not five compulsory boxes for every appointment. The developers explicitly allow OSKAR to be taught as tools rather than a fixed process. You can return to the outcome when it changes, or spend a whole conversation examining know-how if that is the useful work.

When should a coach use OSKAR?

Consider it when the client wants a practical difference, can explore what that difference would look like, and is willing to examine existing resources. It can fit leadership, career, business or life coaching; the specialty matters less than whether the conversation suits the person and the situation.

It is particularly useful as a way to connect separate pieces of a conversation. A client may have a goal, a memory of something that went better and an action idea, but no link between them. OSKAR invites you to make that connection explicit rather than ending with a task selected because time is running out.

Do not choose it simply because a client talks about problems. They may need you to understand a genuine constraint, a loss or a harmful situation before imagining a preferred future. Ask whether exploring a next step would help; do not label reluctance as resistance to solutions.

For the example below, imagine Jordan, a team lead whose cross-team handovers repeatedly generate last-minute questions. Jordan wants fewer interruptions but has no authority over the other team's workload. The coaching task is to find a useful experiment within that reality, not persuade Jordan to feel better about an unworkable process.

1. Outcome: describe a visible difference

Agree what Jordan wants from today's conversation and how it relates to the wider situation. “Better communication” is a theme. “The receiving team knows what is ready, what is missing and who can answer a question” is a description you can work with.

Useful questions include:

• “What would make this conversation useful today?”
• “If the handover worked better, what would you and the other team notice?”
• “Which part of that difference could you influence?”
• “What would be good enough, rather than perfect?”

In the hypothetical conversation, Jordan identifies a modest outcome: finish the next handover with a named receiving owner and an agreed route for questions. The coach checks that this is Jordan's chosen focus, not just a target imposed by a manager.

Keep the distinction between an outcome and an action. Sending a checklist is an action. A receiving colleague knowing what they are taking responsibility for is part of the desired difference. If you confuse them, a sent checklist can look like success even when nobody uses it.

Before moving on: can the client describe what they hope will be different, in language that means something to them? You do not need a polished goal statement. You need enough shared understanding to ask a relevant next question.

2. Scaling: explore the position, not just the number

Invite Jordan to locate the current situation on a scale with agreed anchors. For example, ten could mean the handover is sufficiently dependable for the work involved, and zero could mean Jordan's least workable experience of it. Check that the anchors make sense rather than supplying a universal definition.

Then ask:

• “Where would you place the situation today?”
• “What tells you that position fits?”
• “What is helping it be here rather than a little lower?”
• “What would you notice if it were a little more workable?”

Jordan chooses four. That does not mean the handover is 40 percent successful. It means Jordan has selected a position that needs explaining. They describe one receiving colleague who already confirms ownership and another handover where questions arrived before the deadline rather than afterward.

The scale belongs to the client. Do not correct the rating because the evidence sounds more positive to you, compare it with another client's number or quietly turn it into an employee performance measure. Ask about the examples behind it.

If a number does not help, use a description or another client-preferred way of locating the situation. If the client chooses zero, do not insist on the “why not lower?” question. Ask what makes the situation so difficult and what support would matter. Our guide to scaling questions explores that individual technique in more detail.

3. Know-how: find what can actually be used again

The next task is not to generate a long strengths list. It is to discover usable ingredients related to this outcome. Skills, another person's cooperation, clear authority and a quieter environment are different kinds of resource. All may matter.

Ask about a specific occasion:

• “When has some part of this handover worked better?”
• “What did you do, and what did someone else contribute?”
• “What do you already know about making ownership explicit?”
• “Whose experience could help, with their agreement?”

Jordan remembers a handover where the teams briefly spoke before sending the document. The receiving colleague had a chance to challenge an assumption and name the owner. Jordan already knows how to write a clear summary; what was different was the opportunity to check understanding.

Do not jump from that occasion to “schedule a call every time.” The colleague may not have capacity, and some handovers may be routine enough not to need one. Explore which ingredient can be repeated and what it would cost.

Can the coach share their own know-how?

Yes, OSKAR's first-party description explicitly permits know-how from other people and even the coach. That is not a license to smuggle advice into every question. Make the role change visible and optional.

For example: “Would it be useful to hear a handover format I have seen, or would you rather develop yours first?” If Jordan welcomes it, offer a brief example and ask what fits, what does not and what they would change. Do not present your method as the answer the client was supposed to discover.

This is a distinctive coaching decision inside OSKAR: when to elicit, when to invite outside knowledge and when to acknowledge that a required resource is unavailable. A resource-led conversation remains realistic only if “we do not have that” is an acceptable answer.

4. Affirm and Action: connect evidence to a small experiment

The A carries two jobs. Affirmation recognizes something concrete that has emerged. Action invites the client to decide how to use that information. Skipping the first can produce a task disconnected from capability; overdoing it can feel like a motivational speech.

In Jordan's example, an affirmation might be: “You made space for the other team to question the brief, and you noticed that it changed the handover. That seems useful. How do you see it?” This is specific and open to correction.

“You are an amazing communicator” is broader than the evidence. It may sound warm, but it does not identify anything Jordan can choose to repeat.

Then explore action:

• “Which part would you like to try again?”
• “What is the smallest fair test in the next handover?”
• “What needs the other person's agreement?”
• “What would make the test worth reviewing?”

Jordan chooses to ask one receiving owner whether a short pre-handover conversation would help. If they agree, Jordan will bring a draft summary and explicitly check ownership and the route for questions. If they decline, Jordan will ask which asynchronous confirmation would be workable instead.

Notice that the experiment begins with a request, not a demand. Jordan cannot promise another team's participation. The coach can help make the test clear without turning cooperation into something the client must somehow manufacture.

Close the stage by checking willingness and capacity. “Would you actually like to do this?” can be more revealing than “How committed are you?” A smaller experiment, more preparation or no action yet may be the honest answer.

5. Review: ask what changed, including what did not

Agree the review before ending the conversation. What will Jordan notice? When will you discuss it? Is any between-session contact useful? Review should not arrive as a surprise accountability interrogation.

At the next appointment, OSKAR traditionally invites attention to what is better. Ask that as an opening, not a requirement to report success. If nothing improved, accept the answer and investigate the experience.

Possible prompts are:

• “What, if anything, has been more workable?”
• “What happened when you tried the experiment?”
• “What did you contribute, and what changed around you?”
• “What should we keep, adapt or stop?”

Suppose the receiving colleague agreed to the conversation, ownership became clearer, but questions still arrived late because another decision was delayed. The useful learning is mixed. You can acknowledge clearer ownership without claiming the whole handover is fixed.

Revisit the outcome and scale only if they remain useful. Jordan might keep the same number while describing a better understanding of the obstacle. A static score does not erase learning. Equally, a higher score does not establish that coaching caused the change.

A copyable OSKAR session record

Use this compact record with the client rather than completing a private scorecard about them. Keep enough detail to support review, but avoid unnecessary personal information or speculative judgments.

1. Outcome: The difference the client wants to notice, and today's agreed focus.
2. Scale: The client's anchors, current position and examples behind it, if useful.
3. Know-how: A relevant occasion, the client's contribution, other support and important constraints.
4. Affirmation: A specific resource you noticed and the client's response.
5. Action: The chosen experiment, any prerequisites and what would count as useful learning.
6. Review: When you will revisit it, what the client wants to observe and any agreed follow-up.

For Jordan, the working record could be one short paragraph: “Seek clearer ownership at the next handover. Current position four, with one useful example of checking understanding before sending. Ask the receiving owner whether a brief conversation is workable; agree an alternative if not. Review ownership clarity, question timing and the cost of the extra step next session.”

A shared document can be sufficient. If you use a coaching platform, the value is making the agreed next step accessible, not converting the client's story into more data fields.

Coachful's client progress view is relevant here as a way to orient a progress-and-next-steps conversation. The screen is not a built-in OSKAR worksheet or evidence that an intervention worked. Keep the client's descriptions beside any number wherever you record them.

Similarly, a flow or check-in can support follow-up only when it reflects the agreement. Do not add daily scoring because the software can ask for it. Decide the purpose, wording and frequency with the client first, and check whether the follow-up is actually useful.

OSKAR vs GROW vs OSCAR: what changes for the coach?

GROW organizes a conversation around Goal, Reality, Options and Will. OSKAR makes scaling, existing know-how, affirmation and review explicit. Neither label removes the need to listen, contract well or adapt to the client.

OSCAR is a different acronym, commonly expanded as Outcome, Situation, Choices, Actions and Review. Do not silently swap its C for OSKAR's K. In OSKAR, the practical emphasis is on discovering and using know-how, not simply listing choices.

Choose by the work the conversation needs, not by a claim that one model is universally better. If you need a wider comparison, use our coaching models guide. If you need individual prompts without a named sequence, use the solution-focused question library.

Limits and mistakes worth catching

Using solutions to avoid hearing the problem. Acknowledge the situation before inviting another direction. A client describing discrimination or unsafe conditions does not need a more positive score. Work within your role, training and relevant professional responsibilities.

Turning affirmation into pressure. “You have managed before” must not become “so you should manage again.” A resource that is exhausted, unaffordable or dependent on someone else's unpaid effort may not be available now.

Hiding the manager role. If you also manage the person, be explicit about what is optional, what is a work requirement and what information will be recorded or shared. Do not invite apparently private coaching disclosure and then use it as undisclosed appraisal evidence.

Treating the model as clinical training. OSKAR is not a qualification to diagnose or treat a condition. Pause the exercise and discuss appropriate support when the situation requires expertise beyond your scope.

Frequently asked questions

Does every OSKAR session need all five stages?

No. The developers describe it as a flexible set of tools as well as a model. Understand the whole structure, but use the parts that fit the agreed purpose. Review may open a later appointment rather than occupy the final minutes of the first.

How long should an OSKAR conversation last?

There is no universal duration to impose on the client. A focused check-in may use a few tools; a complex conversation may need more exploration. Agree the available time and leave room to close without forcing an action.

What if a client dislikes the scale?

Ask what would help them describe the situation instead. An ordinary-language account can still support outcome, know-how, action and review. The client should not need to become comfortable with numbers to receive useful coaching.

Make the review possible before you close

For your next suitable conversation, keep one connection in mind: the chosen experiment should come from relevant know-how and lead to something worth reviewing. That is more useful than remembering five letters while losing the client's meaning.

If your next decision is how to keep that agreement usable between appointments, explore the client progress and follow-up views before changing your process. Try the interactive demo and assess whether Coachful fits the way you and your clients want to review next steps.

Source and scope: The model's attribution, stages, know-how sharing and flexible use are grounded in sfwork's first-party OSKAR description. The example, questions, record and safeguards here are editorial applications for coaches, not reproduced training materials, a clinical protocol or tested outcome claims.