Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

All these things are important, but this misses the important distinction - the higher up the leadership chain is about the scale you operate at, whether you affect one team of developers, a couple of teams, a director level organization, executive level organization, or the whole company.


Ah so influence :)


At Salesforce, one of the ways we measured influence was by the amount of internal social network activity an individual accumulated... posts, likes, replies, etc. In nearly all cases, the higher ups had the most influence.


everything you make an input of the recognition process become an output of the office politics hack. obviously it corelates. at my company, were its not part of recognition, higher ups have zero posts on the information sharing systems.


Hard to define, do you have ideas :)


The most succinct thing I've come up with is: "You're an influential engineer if an engineer magically becomes better just by sitting next to you."


In my experience influence is earned using much of what you outline. Lovely blog post.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: