For example, hitting senior people with 3-4 questions via Chat or, godforbid, sending them a Word Document with questions would not get you taken very seriously here.
Subtlety is key. Less is more.
I'd like to mention that there's a converse. Say you're in a meeting and some idea comes up which you don't like the look of. There are different ways to sabotage it which probably also apply across multiple companies.
The most vicious I know of is to emphasise both the value and the risks of the idea if it goes slightly wrong to justify looping in a substantial number of senior people, ideally a pre-existing committee structure. Provided you can get a couple of people with no free time to engage with the idea and schedule a recurring meeting about it, you've successfully stalled the project for a number of years. That's usually enough for the proposer to run out of patience.
Also, I'm curious whether this style of engineering is what tends to kill established companies. A sort of stagnation until the competition overtakes it.
kridsdale1•19h ago
I also had my early career years at Apple. Knowing this stuff is the only way to survive. And we didn’t have Slack or Google Docs at the time, only email.
harryvederci•19h ago
Sounds like you had an unfair advantage!