Efficiency in influencing within the Staff+ engineer’s routine
Your influence strategy is probably just expensive noise
Let me tell you something that took me embarrassingly long to figure out. For years, Staff engineers approached influence this way: They’d identify a problem, build a compelling argument, present it to anyone who would listen, and then wonder why nothing changed. They were the human equivalent of a broadcast UDP packet. Lots of energy, zero delivery gua…
Keep reading with a 7-day free trial
Subscribe to Alex Rios Substack to keep reading this post and get 7 days of free access to the full post archives.

