---
but wtf is "staff"? and how does that differentiate from "senior"/mid-level?
a lot of people get stuck when they continue to view their only output as a design artifact
"i just wanna design, not deal w politics!"
"why cant we jsut do this awesome thing i designed? it's being butchered!"
"im going to go work in the corner and come back 2 weeks later with a magical solution to fix everything"
these types of outputs "scale" in that lots of other decisions will be made based on it, thereby increasing your "impact"
staff: i shaped this new framework that defines how to prioritize new component work and how they should be built
and lmk any questions :)
it's not a surprise (to me) that one of the "fathers of computing" douglas englebart's last initiatives was an institute dedicated to improving organizational efficiency and collaboration
dougengelbart.org/content/view/2…