Its not just about going above and beyond. Its going above and beyond exactly where it will get you the best outcome and nowhere else.
It is a little bit like “it’s not what you know, is what you can prove”: I mean: “it’s not what you do, is what the boss of your boss sees”. And I emphasize “boss of your boss” because him is who you have to impress (or somebody 2 levels above, anyway).
Also in moderately big to big companies, is all about contacts and personal marketing, which could (and typically is) orthogonal to your actual work.
As you go up the levels that is exactly the job (for better or worse) so doing that is doing the work at the next level. You are organizational glue that connects people and ensures your team has proper visibility. If you didn't see it that way then that may explain your problems with promotions.
Between the most junior developer and the CTO, and all in between, is about taking good decisions, communicating clearly, and owning errors. If it is a healthy company with competent management, there is no need to make a powerpoint of every fart you shoot. Now the reality is, big companies are run typically by incompetent people with "cover your ass" mentality, with lots of internal and external corruption and nepotism. See Dilbert. It doesn't mean is the only model.
> If you didn't see it that way then that may explain your problems with promotions.
Big no. I totally knew and saw that, clear as day. But if when the position is open the nephew of the boss'es boss is looking for a job, you are just out of luck. Also if your boss is constantly talking bad of you anytime anyone internally asks for you.
I love managing initiatives - just not people. But anytime I have been bought into a company where I was responsible for major company wide strategy, I made sure I reported directly to someone with authority - a director or a CTO. It was mostly small companies.
Even now where as a staff level employee where I do report to a line level manager (who is at the same salary band as I am) who I like and respect very much, I am making sure I have visibility and the ear of my skip manager and my CTO about things I care about - without stepping on my managers toes.
Maybe this is a folksy anecdote about a junior developer working for John Email designing the protocol for trinary morse code over a token ring of twisted pair barbed wire. An RFC for that kind of project would be natural.
In the spirit of this, I propose we start calling things like flowcharts, SVG images of digraphs, UML diagrams etc "articles of war" just to spice things up.