What progress would you need to see from me in one year to move from, let's say, a mid-level role to a senior role? What do you need from me? Now, if you've got a good manager, they will be like, great, let me show you this graph I have. Let me show you this table of career progression. In my workplace, I was part of building what is called the technical expert track. It's a career matrix. If you're in a bigger company, you probably have a career matrix you can refer to. That helps a lot. If you're in a small or medium company, it may or may not exist for you where there are actual criteria you can follow as to like, okay, you've got to be at this kind of level with a programming language, you need to have this kind of mentoring experience, et cetera. If you don't have something like that, then you have to build that with your manager. If you have a good manager, as I said, they will already kind of know how to do this. The problem I've also seen is that there are some managers who don't treat management as a craft. They're more like, oh, I'm just going to go support my people. Peace out, yeah, and they don't actually take the time to go like, how do I do that effectively? So if you have someone who doesn't know how to do this, it's fine. Then you need to learn this. Any management or team lead person will have heard of this before, maybe you've also heard of it before. This is a guideline for building goals. When you build goals, it shouldn't be like, okay, you might have a well-meaning manager who says, yeah, I guess if you wanted to be a senior, I guess like mentor someone, maybe like give a talk somewhere. Work on a cool feature, you know, and you're like, okay, thanks. What do you do with that information, right, in a year's time. I worked on a cool feature and I mentored someone, okay, yeah, but it's still not quite what I meant, you know, and then you end up in this awful loop where you're kind of not really meeting each other's expectations. If you create goals in this way, you will find that it's a lot easier to meet them. The first is specific, right? If they want you to give a talk, how many talks do they want you to give? What kind of talks? Does it have to be a technical talk? Or can it be about teamwork, agile work, about software architecture? What does it have to be? What kind of thing are you looking for here? Measurable, right? Is it one talk, two, three? Give me a number, right? Don't be like, it would be nice if I get a bit more public speaking experience. It's like, okay, but how, what, yeah? Achievable, obviously. If you're a manager, don't set a goal for 20 talks in a year. Maybe keep it a bit realistic to the person. Relevant, okay? I think that goes without saying. You don't want to be like, oh, yeah, to get promoted to senior, I want you to bake me a cake. Like, no, thanks. And time-bound. By that, I mean, yes, you should have these one-year goals, but also you should be making goals in between. How many goals, if you set ten goals for the end of the year, how many of those do you think will be done after a month? Zero! For most people, right? For most people, you say, yes, ages away.
Comments