Insights · The Growth Coach HK
How to Use Goals as a Learning System, Not Just a Scorecard
2 October 2025
Introduction
Most goal-setting produces a scorecard. At the end of the period, you either hit the goal or you did not, and that outcome is recorded somewhere and influences some subsequent decision.
This is useful. Knowing whether you achieved what you set out to achieve is important information. But it is a fraction of what goals can produce if they are used well.
The leaders and teams I have seen develop fastest consistently use goals differently, not as a scorecard for judging performance but as a structure for learning. They treat the goal-setting process as a way of making explicit what they believe will produce results. They treat the work period as a test of those beliefs. And they treat the review as a learning conversation: what did we find out? What did we get right? What were we wrong about? What would we do differently?
This reframe, from goals as evaluation to goals as learning, changes almost everything about how goals function in a team or individual’s development.
Main Insight
Goals used purely as scorecards tend to produce a specific set of dysfunctions.
They focus attention on the metric rather than on what the metric is supposed to represent. Teams optimize for the number in ways that do not always serve the underlying purpose: hitting a call volume target with lower-quality calls, closing easy deals to make the revenue number while neglecting harder opportunities that would build more strategic value.
They create an adversarial relationship with difficulty. When goals are primarily evaluative, missing them is a failure that needs to be explained and managed. This makes it psychologically costly to take on ambitious goals. The downside of a miss is high, so the rational response is to set goals you are confident you can hit rather than goals that would push development.
And they provide very little information about how to improve. “We hit 87% of target” tells you the outcome. It does not tell you what drove the gap, which assumptions were wrong, which activities produced the most return, which investments of time and attention made the least difference.
A goal should not only tell you whether you won. It should help you understand what you learned.
Common Mistakes
The reframe that produces the most useful shift is treating goals as hypotheses rather than predictions.
A prediction is a statement about what will happen. A hypothesis is a statement about what you believe will happen if certain conditions are met, combined with an openness to finding out whether you were right.
When a goal is framed as a hypothesis, “we believe that if we do X, Y, and Z, we will achieve outcome Q,” it contains the structure for learning. After the period, the questions are not just “did we hit Q?” but “did we do X, Y, and Z? If yes, and we still did not hit Q, what does that tell us about our assumptions? If no, what got in the way of the activities we planned?”
This kind of reflection produces genuinely useful information about how to improve. Not just whether you achieved the outcome, but what you learned about the relationship between your activities and your outcomes, which is the information that actually drives improvement over time.
Framework: Building Learning Into the Rhythm
The hypothesis-based approach to goals requires a different kind of review rhythm than the scorecard approach.
Scorecard reviews are periodic and backward-looking: what happened? Learning-based reviews are both backward and forward-looking: what happened, what did we learn from it, and how does that change what we do next?
In practice, this means building reflection into the operating rhythm rather than just reporting into it. Not long, elaborate reviews, often fifteen to twenty minutes at the right frequency is more valuable than a quarterly deep-dive, but regular, honest conversations about what you are learning from the work rather than just what results the work is producing.
The specific questions that make these conversations useful:
- What did we get right?
- What were we wrong about?
- What is working better than we expected?
- What is working worse?
- What would we do differently if we were starting this period again?
- What should we change about our approach going forward?
These questions feel obvious but they are underused because the instinct in performance conversations is to focus on what happened rather than on what it means for what you do next.
Practical Lessons
One concern about reframing goals as learning systems is whether it lets people off the hook, whether the focus on learning becomes a way of rationalizing underperformance rather than addressing it.
This is a legitimate concern and the answer is to hold both. The question “what did we learn?” is not a substitute for “did we deliver what we committed to?” It is an addition to it. Accountability to outcomes remains important. The learning lens adds a second layer of inquiry that improves the quality of what comes next.
The distinction that matters is between using learning as an explanation for underperformance and using it as a tool for improvement. “We did not hit the target because we learned that our qualification process is not working” is useful if it is followed by concrete changes to the qualification process. It is not useful if it is followed by the same qualification process producing the same miss next quarter.
Learning that does not change behavior is not learning. It is narrative. The test of whether a goal review has produced genuine learning is whether anything actually changes as a result.
Conclusion
Goals are useful as scorecards. But they are more powerful when they also become learning systems.
A scorecard tells you whether you hit the number. A learning system tells you what your work revealed about your assumptions, your process, your priorities, and your next move.
The goal is not to make accountability softer.
It is to make improvement sharper.
This is part of the Growth Mindset series. The pillar article, Why Leadership Growth Is Harder Than It Looks, covers the full framework. The series also covers leadership difficulty, the feedback gap, rest and performance, and self-leadership after leaving corporate.
To talk through how to build this kind of learning rhythm into your leadership, start with a conversation.
FAQs
What does it mean to use goals as a learning system?
It means treating goals as a way to test assumptions, not just record outcomes. Instead of only asking whether the goal was hit, leaders ask what the work revealed, what assumptions were right or wrong, and what should change as a result.
Why are scorecard goals limited?
Scorecard goals show whether performance met the target, but they often do not explain why. They can also encourage people to optimize for the metric rather than the underlying purpose. Without reflection, a missed target becomes an outcome to explain rather than a source of useful learning.
How can leaders make goal reviews more useful?
Leaders can make goal reviews more useful by asking what was learned, what worked better or worse than expected, and what should change next. The review should preserve accountability while also turning performance data into better decisions and better behavior.
This site requires JavaScript for the full experience. Email us or enable JavaScript to continue.