I'd like to refine the sentiment a little bit. In technical circles, trustworthiness is sufficient to get you some traction, but you'll have a glass ceiling unless the bosses like you. If you don't plan to climb very high in the org, this might seem like a reasonable deal to you, but remember that there are other times besides getting promoted when you need to spend social capital with the management team.

> The role growth part is also relevant, as people with context don't want to come to you unless they have to, you slowly lose context on what's going on until you are in a basement with a stapler.

This is my first to promotions to lead in a nutshell.

People who had been there longer lost context because I categorize some/many fuck-ups as reasonable, and I was good at bailing people out if my advice was wrong. If you broke something, or just thought something was broken (ie, QA) I was least likely to bite your head off. If something I asked you to do exploded, I'd help you fix it.

Technically and emotionally trustworthy people hear about more 'dirt', and many serious architectural problems are hidden in that dirt. If you are technical you can parlay that information into bug fixes (including production outages) and technical initiatives. If you're getting stuff done and people generally seem to trust you (even if they don't like you), then that means they listen when you talk. Your boss would be stupid not to promote you.