Understanding Your Goals

Client names a goal clearly and confidently. They can describe it, justify it, and outline steps toward it. What they cannot do is generate any real energy when talking about it. The conversation feels correct but flat. When asked why the goal matters, they give an answer that is reasonable and technically accurate — and still flat. The goal has been named at the surface level only. What lies underneath it has not been examined, and that missing layer is where the actual motivation lives.

Frame the four-question cascade as going from the goal to what the goal is really in service of. 'You've named the goal. What we're going to do now is ask the same question four times: what will this give you? Each answer goes into the next box. By the fourth box, we usually arrive at something closer to what this goal actually means.' The resistance here is that clients who have already committed to a goal can experience the cascade as a challenge to that commitment. Name it: 'This is not a test of whether the goal is right. It is a map of why it matters. Knowing that makes the goal easier to pursue, not harder.'

Watch for the first box answer being restated in slightly different language in box two — the client is not descending, they are circling. Push: 'If you had that — if you had [box one answer] — what would that give you?' The boxes should become increasingly abstract, moving from outcomes to values. If the answers stay concrete across all four boxes, the client has not yet reached the motivational layer. Also watch for box four being a restatement of the original goal rather than what the goal ultimately connects to.

After all four boxes and the final 'why is this important' field are complete, read the chain back to the client from bottom to top: '[Box four answer] — and that matters because [final field answer].' Then: 'Looking at the final field — does the original goal you wrote at the top actually lead there? Or is there a different goal that would get you there more directly?' That question sometimes reveals that the stated goal is instrumental to something that could be pursued more directly. It is productive either way.

Client has been working toward a goal for months or years. Early in the pursuit, the motivation was clear. Now the goal is a fixture — it is on the list, it is discussed in coaching, it is referenced in performance conversations. But when asked directly why it matters, the client cannot produce the answer quickly. The original meaning has been obscured by the accumulated effort of pursuing it. The four-question cascade is useful here not because the goal is wrong but because the connection between the daily work and the underlying value has gone opaque.

Frame this as reconnecting rather than reexamining. 'You've been working on this for a while. I want to do something quick before we go further: run it through four questions to make sure the connection between the goal and what's driving it is still clear. It takes about five minutes and it's either confirming something you already know or surfacing something worth knowing.' The resistance here is minimal — clients who have been at a goal for a long time are often relieved to examine why rather than just report on how. The more common failure is superficiality: the client answers quickly without actually descending.

Watch for the cascade being completed too quickly — answers written in thirty seconds that do not reflect genuine reflection. Speed is often a defense against arriving at an answer the client does not want to find. Also watch for a mismatch between the energy at the top of the cascade (naming the goal) and the energy at the bottom (naming the underlying value). If the client is energized about the goal but flat about what it ultimately means, the goal may be functioning as a distraction from a deeper need that is not being addressed.

After the cascade is complete, ask: 'Is the reason you started pursuing this goal the same as the reason you're still pursuing it?' If the answer is no, the conversation moves to what changed — and whether the goal still fits. Then: 'If you achieved this goal tomorrow, would the thing in your final field — [the client's answer] — actually follow?' Sometimes the answer is no: the stated goal does not actually produce the outcome the client has been assuming it will. That discovery changes the plan.

Client has arrived with a goal they articulate confidently. When asked where the goal came from, the answer is a performance review, a manager's suggestion, a comparison to a peer, or a generic professional development expectation. The goal is real enough — it is worth pursuing — but the client has not asked whether they want it or whether it is the right goal for this moment. The cascade is the fastest way to find out, because it moves from what to why, and the why often reveals that the goal is borrowed rather than chosen.

Frame this as the first thing — not a challenge to the goal but a foundation for it. 'Before we build a plan around this goal, let's spend a few minutes understanding what it's in service of. The four boxes ask the same question four times: what will this give you? The answer at the bottom is the one that makes a plan worth building.' Some clients in first sessions are not yet comfortable admitting uncertainty about their goals. Name it: 'There's no wrong answer here. The goal might land exactly where you expect, or somewhere different. Either is useful to know.'

Watch for the cascade arriving at a value or outcome that is not the one the client expressed as their goal. The stated goal is 'get promoted' but the cascade ends at 'feel like my work matters.' Those are not the same goal. Also watch for the final field answer being something the client is already achieving — in which case the goal may be a proxy for recognition rather than a genuine unmet need. The distinction between 'I want this outcome' and 'I want to be seen pursuing this kind of goal' is one the cascade can surface.

After the cascade is complete, read back the original goal and the final field answer: '[Goal] — so that [final answer].' Then: 'Does the goal you came in with actually lead to [final answer], or does it approximate it?' If the client identifies a gap, the next question is: 'What would a goal that led more directly there look like?' The debrief should produce either a confirmed goal or a refined one — not an abandoned one, unless the client chooses that. The cascade is diagnostic, not prescriptive.