Problem-Solving Coaching: When It Works, and When You Become the Crutch (2026)

Problem-solving coaching is a short, structured mode where you help a client name one specific problem, generate their own options, and commit to a single action before the session ends. It works when the client owns the options. It stops working the second you start supplying them.

That distinction is the whole post. Most coaches think they are doing problem-solving coaching. A lot of them are doing consulting with a friendlier tone.

What problem-solving coaching actually is

Problem-solving coaching sits at the tactical end of the coaching range. The client arrives with something concrete and stuck: a manager who will not give a straight answer, a job search that has gone quiet, a launch date that keeps slipping. You do not spend the hour on identity or values. You spend it turning a vague complaint into a defined problem, then into options the client generated, then into one commitment with a date on it.

The ICF core competencies are useful here for a reason people skip past: they never tell you to solve the problem. They point the other way, toward client autonomy and the client’s own discovery. Problem-solving coaching is a format, not permission to hand over answers.

Compared to the GROW model, which structures a whole conversation around a goal, problem-solving coaching is narrower and faster. GROW asks what the client wants. Problem-solving coaching asks what is in the way, right now, this week.

Test the problem before you solve it

Here is the mistake I made in my first few years of practice, and the one I watch new coaches make constantly: taking the presented problem at face value.

Clients present the problem they think is acceptable to bring. “I need help structuring my resume” is code for “I do not believe I am qualified for the roles I actually want.” If you run a clean problem-solving session on the resume, you will do good work on the wrong problem, and the client will be back in three weeks with a cousin of the same complaint.

Three questions I use before committing to this mode:

• “If this were solved tomorrow morning, what would be different by Friday?” A thin answer means the problem is a proxy for something else.
• “How long has this been on your list?” Something stuck for six months is rarely an options problem. It is an avoidance problem, and options will not move it.
• “What have you already tried?” If the answer is nothing, you are not in problem-solving territory yet. You are in a conversation about why they have not started.

If those come back clean, run the session. If they do not, you are looking at developmental coaching territory, which is a different job on a different clock.

How I run a problem-solving coaching session

Five moves, roughly 45 minutes:

• Define it in one sentence. Make the client say it out loud, in a single sentence, with a subject and a verb. If they cannot, the problem is not defined yet and everything after this is theater.
• Scale it. “Where is this on a 1 to 10 right now, and what would a 6 look like?” Scaling questions come out of the solution-focused tradition and they do two things at once: they give you a baseline, and a 6 is a far more achievable target than a 10.
• Make them generate options. Ask for five, not three. The first three are the ones they walked in with. Four and five are the ones worth having. Sit through the silence. This is the part that separates problem-solving coaching from advice.
• Have them pick. Not you. Even a mediocre choice the client owns beats a good choice you handed over, because the point is building the muscle, not closing the ticket.
• Put a date on it. “By when” is not a formality. A commitment without a date is a preference.

I write all five into my session notes before the client is off the call, because the fifth one is what I open the next session with. If you cannot remember what someone committed to, they learn fast that commitments here do not count.

Where problem-solving coaching goes wrong

Two failure modes, and I have been on the wrong side of both.

You become the crutch. The client brings a problem, you help them solve it, they leave happy, and you both feel useful. Repeat that for six months and you have built a dependency, not a capability. Harvard Business Review made a version of this argument about managers back in 2019: command-and-control leadership stopped being viable once nobody could be expected to have all the answers. The same logic applies to your client roster. The tell is that the problems keep arriving at the same size. Real progress looks like clients bringing you bigger problems over time, because they have stopped needing you for the small ones.

You solve every week and never look up. This mode is tactical by design, and tactical work has a gravity to it. A client can spend an entire engagement clearing this week’s obstacle and finish where they started, just less cluttered. I put a checkpoint every fourth session that is explicitly not tactical: what has changed since we started, and is that the change you paid for?

Problem-solving coaching vs the other modes

A quick way to keep them straight:

• Problem-solving coaching. The obstacle is specific, recent, and the client has real agency over it. Weeks, not months.
• Performance coaching. The client is already competent and wants to be better at a defined thing. The performance coaching models breakdown covers picking one.
• Developmental coaching. The same problem keeps returning in new costumes. That is a pattern, and patterns do not respond to options.

Most engagements use all three. The skill is not picking the right one once, it is noticing when the session in front of you needs a different one than the last.

Keeping the commitment alive between sessions

The commitment made at minute 44 is the entire product of a problem-solving session, and it dies in the six days that follow. I ran 33+ clients on Notion, Cal, and a spreadsheet before I built Sage, and this is the exact thing that broke. I could hold what someone committed to in my head when I had eight clients. At thirty, I could not, and neither could they.

Whatever you use, the requirement is the same. The commitment, the date, and the client’s own words have to survive the week and be in front of you when the next session opens. Everything else here is technique. That part is operations, and it is where most of the value leaks out.

FAQ

Is problem-solving coaching the same as solution-focused coaching? No, but they overlap. Solution-focused coaching is a broader approach centered on defining a desired future state and building a pathway toward it rather than dissecting the problem. Problem-solving coaching borrows its tools, like scaling questions, inside a tighter and more tactical format.

How long should a problem-solving coaching session be? 45 to 60 minutes. Past an hour you are usually not solving harder, you are circling. If one problem needs more than one session, it is probably more than one problem.

Can you do problem-solving coaching without giving advice? Yes, and that is the job. The structure carries it: define, scale, generate, choose, commit. You supply the structure. The client supplies the content.

When should I stop using problem-solving coaching with a client? When the same problem shows up a third time in a different outfit. That is a signal the tactical layer is not where the work is, and continuing to solve at that layer is comfortable for both of you and useless.

What to do next

See how Sage fits your practice: the Sage pricing page lays out what you get at each tier.

If you want the artifact that makes this stick, read Coaching Session Notes Template: The Six Fields I Fill In After Every Session.

Ready to try it on real clients? Start a 14-day free trial of Sage – no credit card required.