I’m not sure if the competence is really in the last place. I’d say it’s on the equal level. Great communication and ownership of the problems means little if you can’t really solve the problems.
People have those things in spectrums, not all or nothing. You have to have at least some of all of them, but I’d argue that mediocre competency with really good communication and accountability is a better combination that really good competency with one of the others being mediocre.
I still kinda disagree. We’re talking here about engineering role after all. I have a colleague who is a code wizard, but has kinda problem with (under)communicating. He’s still widely respected as a very good engineer, people know his communication style and adapt to it.
But if you’re a mediocre problem solver, you can’t really make up for it with communication skills. That kinda moves you into non-engineering role like PO, SM or perhaps support engineer.
But I would say this - once you reach a certain high level of competence, then the communication skills, leadership, ownership can become the real differentiating factors. But you can’t really get there without the high level of competence first.
I’m halfway through scrolling this long thread, and this is the first comment I’ve seen that isn’t overly cynical. It’s also correct.
I’ve been working for 38 years, and I’ve been someone who makes promotion decisions for 15 of them. The third one is helpful, not essential, but the others are super important. The people who rise to leadership positions aren’t necessarily the top technical people, they’re the ones who do those things with a good attitude.
The other thing I’d add is that they’re people who are able to see the big picture and how the details relate to it, which is part of strategic thinking.
The most important traits for doing well at work (in this order):
I’m not sure if the competence is really in the last place. I’d say it’s on the equal level. Great communication and ownership of the problems means little if you can’t really solve the problems.
People have those things in spectrums, not all or nothing. You have to have at least some of all of them, but I’d argue that mediocre competency with really good communication and accountability is a better combination that really good competency with one of the others being mediocre.
I still kinda disagree. We’re talking here about engineering role after all. I have a colleague who is a code wizard, but has kinda problem with (under)communicating. He’s still widely respected as a very good engineer, people know his communication style and adapt to it.
But if you’re a mediocre problem solver, you can’t really make up for it with communication skills. That kinda moves you into non-engineering role like PO, SM or perhaps support engineer.
But I would say this - once you reach a certain high level of competence, then the communication skills, leadership, ownership can become the real differentiating factors. But you can’t really get there without the high level of competence first.
I’m halfway through scrolling this long thread, and this is the first comment I’ve seen that isn’t overly cynical. It’s also correct.
I’ve been working for 38 years, and I’ve been someone who makes promotion decisions for 15 of them. The third one is helpful, not essential, but the others are super important. The people who rise to leadership positions aren’t necessarily the top technical people, they’re the ones who do those things with a good attitude.
The other thing I’d add is that they’re people who are able to see the big picture and how the details relate to it, which is part of strategic thinking.