3 ms·

That's well put. I did some contracting work for a very large organization last year. It was my first experience trying to navigate the rules inside such a lar

That's well put. I did some contracting work for a very large organization last year. It was my first experience trying to navigate the rules inside such a large organization. The interaction that I found most amusing is that I would ask for something that would require crossing an organization boundary and the immediate response would be, "No.", followed shortly by, "Wait, why do you need that?" This happened several times and was just part of the dance required to find the right person to sign off on my plan.

ethbro 6y ago
That's a constant. As an external consultant, do remember you have the power to play the expert. "Well that's how other Top50 companies I've worked with have done it" isn't the worst card to play. Usually though, it requires hitching your wagon to whatever VP brought you in, and trying not to burn them with blowback. Although honestly, most of the time I think it was "No" on the basis of inertia / resistance to change, more than actual disagreement. So technical arguments can win the day there (with other engineers).