How to Make Your Annual Review Actually Useful
Do not treat it only as a backward-looking performance discussion. Use it to shape your role, compensation, and next career step
For most of my career, annual reviews were simple and quick. My manager would usually confirm that things were going well, tell me to keep up the good work, and sometimes give me a small raise. While I appreciated it, those conversations were not so useful from a career development perspective.
Often, I did not even have concrete goals to review. Or the targets were so vague that you could not really tell what success was supposed to look like. That ambiguity was quite convenient, as it gave the review board the freedom to decide for themselves whether the goals had been met or not.
My goals are more practical these days. Still, I have come to realize that most professional growth does not happen in the annual review meeting. Instead, it comes from hands-on work in client projects, taking on new responsibilities, helping with proposals, doing some business development, and sometimes, just plain luck. The annual review might point you in the right direction, but you build your career in the everyday work.
Still, taking a moment once a year to look back at what you have achieved is valuable. The problem is that these chats tend to look backward too much, focusing on what happened and how the year went before everyone runs back to their actual work.
Because of this, I have made a real effort over the last five years or so to push these conversations toward the future.
I am preparing for my own review once again, which means doing the usual self-assessment. It is always a tricky balance of being honest, ambitious, positive, realistic, modest, and impressive all at the same time.
The process means looking at the goals from a year ago, trying to remember what we actually meant by them, and digging up the notes you hopefully kept along the way. From there, you put together a good story about your achievements and write down a new set of goals that might or might not be relevant in January.
Despite its flaws, the annual review can be an useful tool. It is one of those rare, formal moments when you can discuss your performance, skills, responsibilities, next projects, career path, and pay all in one setting. But there are certain good practices to consider to make the most of the meeting.
Start With What Changed Because of You
Your manager may be smart, observant, and generally pleasant. However, they still do not fully know what you do, what you have achieved, or what you want next. That is particularly true if you work in consulting, where your work can be spread across various clients, projects, teams, proposals, and internal activities.
Expert work also creates value in ways that are difficult to measure. You may clarify a confusing situation, prevent a poor architectural decision, reduce project risk, help a colleague complete difficult work, rescue a proposal, or gain the confidence of an important client. These contributions matter, but they do not always appear neatly in neat metrics such as financial figures.
Even highly visible outcomes can hide your individual contribution. The final presentation features the company logo rather than your name. The manager may receive the credit, as often happens. A decision looks obvious only after someone has done the work to make it look obvious. A serious problem that was successfully prevented is particularly difficult to present as an achievement.
That is why preparation should start with value rather than busywork. Simply being busy is a weak career argument, although many organizations still treat busyness as a minor religion.
Instead, identify the important problems you solved, the decisions you improved, the risks you reduced, the responsibilities you accepted, the people or clients you helped, and the revenue you brought in. Include feedback and concrete outcomes wherever possible.
For example, whenever I take part in a proposal, I briefly describe my role and the outcome of the case. When I receive positive feedback, I forward it to my manager and include it in my annual summary. Otherwise, nobody may remember it six months later, including myself.
Numbers help when they mean something. For many consultants, billable hours are a critical metric. I have also found it useful to compare my annual billing with my salary. It is a simple calculation, but it provides a clear indication of how well your salary reflects the value you bring to the company.
For sales professionals, the crucial metric is sales, for obvious reasons. I also count the proposals to which I have contributed and estimate their total value. These metrics do not explain everything, but they are far more useful than general impressions.
Ultimately, the goal is to help your manager understand and appreciate the work they did not directly observe.
A useful question to ask yourself is this:
What changed because I was involved?
Check Whether Your Role Has Already Changed
Annual reviews often assess performance inside the current role. Did you meet expectations? Did you achieve your goals? Did you demonstrate the company values listed somewhere on the intranet?
These are all reasonable questions. But they miss an important one:
Is this still the same role I had a year ago?
Expert roles tend to expand quietly. You begin supporting sales, mentoring colleagues, working with more senior client representatives, leading parts of assignments, handling difficult situations, developing internal practices, or taking ownership of something that never had an official owner.
One additional responsibility looks small. Ten of them can create a different job.
This is one reason compensation can fall behind the actual work. Responsibilities change continuously, while titles and salaries move through formal processes. One system updates every week. The other may have a committee meeting once a year.
Compare your current work with the role you originally accepted or the expectations discussed in the previous review. Look at complexity, autonomy, influence, judgment, and consequences.
Doing more of the same work does not automatically make the role more senior. Handling broader problems independently, influencing larger decisions, and carrying responsibility for other people’s success are stronger signals.
Your manager may see parts of this development. They probably do not see the full accumulation unless you explain it.
Separate Expertise, Responsibility, and Results
Expertise, responsibility, and results are connected, but they are not the same thing.
Expertise is what you can do. Perhaps you now understand enterprise architecture more deeply, facilitate difficult discussions better, know the client’s business, use AI effectively, or handle complex stakeholders with less drama.
Responsibility is what others trust you to handle. You may own a larger workstream, advise senior people, mentor colleagues, represent the company, or make decisions with wider consequences.
Results are what the work produced: better decisions, successful deliveries, reduced risks, stronger client relationships, improved practices, sales, or new capabilities.
The strongest career argument is that all three have developed together:
I can do more, I am trusted with more, and my work produces more value.
That is more convincing than saying you worked hard and deserve recognition. The useful question is what the work amounted to.
Give the Next Year Some Direction
An annual review should produce more direction than “keep up the good work.”
That feedback is friendly, but it leaves the direction undefined. You continue responding to whatever projects, client needs, proposal cases, and internal gaps appear, doing what seems necessary at the time.
The organization keeps receiving your contribution, while your role expands through accumulation rather than intention. A year later, you may be doing a rather different job without anyone having decided that this was the plan.
In my case, some of my recent goals have been development goals in a fairly practical form. One has been to build practical AI skills. Another has been to gain experience from new industries and clients. They are concrete enough to guide the year, although you cannot control everything yourself. You can study a new industry, but you still need a suitable client assignment. You can develop your AI skills, but the exact opportunities depend partly on what happens around you.
Practically, the AI goal has included using AI responsibly in my work, acting as an AI champion in my unit, learning more about AI-assisted development, guiding and training others, and supporting the direction of AI use more broadly. I have gradually moved from being someone who mainly uses AI in his own work to someone who also helps others use it and takes part in planning where it should be used and how.
That is the kind of change a development goal should make visible. It should describe more than a topic you plan to study. It should say something about how your work and responsibility are expected to change.
So, discuss what should happen next. What responsibility will you take? What expertise will you deepen? What kind of assignments should you seek? What evidence would support the next role or compensation level? When will progress be reviewed? Also decide what the new focus replaces. Otherwise, role development becomes just workload development.
Keep the plan small. Choose one or two concrete changes that can become visible in actual work. A 90-day cycle may be more useful than a grand annual plan: select one area, define a concrete responsibility or behavior, and review what happened after three months.
Discuss Compensation Directly
A compensation discussion should sound like a compensation discussion. Do not hide it inside comments about motivation and future opportunities. Your manager may leave thinking you had a productive career discussion, while you leave wondering why the subject you cared about never appeared.
You can bring it out directly. For example, you can say:
“Over the past year, my role has expanded in these specific ways. I would also like to discuss whether my compensation still reflects the responsibility and value of the work.”
Connect compensation to expertise, responsibility, and results rather than to effort or personal need. Show where the work has become broader, more demanding, or more senior. Where useful, compare it with the next career level or similar roles in the organization.
Your manager may not be able to make the decision in the meeting. There are salary budgets, approval processes, and review cycles, especially in large companies.
You should still leave knowing who makes the decision, what evidence is needed, what the timeline is, and when the matter will be discussed again. “Let’s return to this later” is not a timeline.
Prepare One Page
Even a 10-slide presentation is usually excessive for an annual review. One page is usually enough.
Use the categories required by your organization’s HR system, but make sure you cover the following five things:
What value did you create?
How did your role change?
What can you now do better?
What should happen next?
What decision is needed about your responsibilities, role, title, development, or compensation?
Review the goals from the previous cycle as well. Some were achieved. Others may have become irrelevant or been replaced by more important work. Real work does not always respect the categories created twelve months earlier. Explain what happened instead of quietly ignoring the goals.
Send the summary to your manager before the meeting. This gives them time to prepare and reduces the risk that half the discussion is spent reconstructing your year from calendar entries.
After the meeting, document the decisions, expected evidence, and next check-in. Annual reviews produce surprisingly little unless someone writes down what was agreed.
Make It Useful
Many people treat the annual review as a workplace ritual that simply needs to be completed. Fill in the form, have the discussion, click the correct button, and continue with the real work.
That is understandable. An annual review does not advance your career by itself. It is only a meeting, and often a rather predictable one.
Still, you can get something useful out of it. You can make your contribution visible, examine how your role has changed, agree on what should happen next, and discuss compensation directly.
For senior experts, career progress rarely comes from one spectacular achievement. It is usually the accumulated result of expertise, responsibility, trust, visibility, and useful outcomes. The annual review is one place to make that accumulation visible and decide where it should lead.
It may remain a ritual. But at least it can be a useful one.
📘Explore the Topic Further
The annual review is just one of part of a larger question: how do expert careers actually move forward?
I explore this question in more detail in my Senior Expert Playbook series.
The Senior Expert Career Playbook looks at how expert careers develop in practice: how you build a position and help others understand the value of your work.
The Senior Expert Pay Playbook focuses on compensation. It explains how pay is shaped by perceived impact, trust, role, and organizational dynamics—not only by performance or one successful salary discussion.
The basic idea behind both books is simple: doing good work matters, but so does making that work understandable.
📚 Related Reads from the IT Consulting Career Hub
If you found this topic interesting, you might also enjoy the following articles:
👨💻About the Author
Eetu Niemi is an enterprise architect, consultant, and author.
Follow him elsewhere: Homepage | LinkedIn | Substack (enterprise architecture ) | Medium (writing) | Homepage (FI)
Books: Enterprise Architecture | The Senior Expert Career Playbook | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)





