An immediate goal is often a means to several different outcomes. “Get promoted” may stand for more income, recognition, responsibility, learning, or future freedom. If those outcomes are fused into one target, it becomes hard to see what a promotion would and would not deliver. Surface Higher-Level Goals makes the hierarchy visible without pretending that every person has one hidden motive.
A useful method asks, “What would achieving this make possible?” and then stops after the first few answers that could change a decision. The links are hypotheses about the person’s aims and circumstances, not interpretations the assistant should impose. Multiple branches matter because one route can satisfy one branch while neglecting another.
Immediate goal: Get promoted
├─ Earn more → build financial security
├─ Gain responsibility → work on more consequential problems
└─ Receive recognition → feel that the work is valued
If income is central, salary negotiation or a new employer may be relevant. If responsibility is central, a project lead role might help even without a new title. If recognition matters, the person may need feedback, visibility, or a different environment. These are not interchangeable substitutes; the tree clarifies what should be compared.
Immediate goal: “Finish a novel this year.”
Possible higher goals: Tell a story that matters, develop craft, share work with readers, or make writing a stable part of life.
Reframe: “Which outcome would count as meaningful progress if the full manuscript is not finished by December?”
Immediate goal: “Increase sign-ups for our app.”
Possible higher goals: Reach more people who benefit, sustain the service financially, or learn whether the product solves a real task.
Reframe: “Which of these outcomes would more sign-ups actually improve?”
The third example shows why a goal tree also reveals assumptions. More sign-ups might not improve retention or sustainability if the wrong people are joining. That question belongs to Challenge Goal Logic.
Use this pattern when a person is attached to a milestone but unsure why it matters, or when collaborators agree on a target for different reasons. Its failure mode is repetitive “why?” questioning that climbs until every branch becomes a broad value such as “happiness.” Stop when the higher goal is specific enough to change options. Another misuse is assuming the assistant knows the user’s motives better than the user does. Offer branches as possibilities and invite correction. Find Alternative Paths then holds a chosen higher outcome steady while comparing different routes.
Related patterns
Challenge Goal Logic · Find Alternative Paths
Source
Inspired by Thomas Wedell-Wedellsborg's What's Your Problem? This is an original Patternverse procedure, not reproduced book text or an official implementation.