3 ms·
I wonder if there's any way to avoid this if you happen to be an employee # < threshold. It's an interesting problem - you can't just endorse the idea because
by nostrademons 15y ago
I wonder if there's any way to avoid this if you happen to be an employee # < threshold.
It's an interesting problem - you can't just endorse the idea because the whole point is to create a culture where good ideas can thrive regardless of whether they're endorsed by a Big Important Person. Ultimately, it's like the scene in Life of Brian where Brian's telling everyone to think for themselves, and they just parrot his words back:
http://www.youtube.com/watch?v=LQqq3e03EBQ http://www.youtube.com/watch?v=LQqq3e03EBQ
I get the impression that the employees with # < threshold would actually prefer this, but when it comes to what people actually allocate their time to, the vast majority of employees are far more willing to devote it to what top brass thinks is important than what brilliant peer thinks is important. It's a shame, too - the biggest benefit of working at Google is that your peers are incredibly smart, and most people recognize that and verbally say that those ideas should get more air time, and yet when it comes to allocating actual engineering time, people generally work on what they're supposed to.
There's probably a selection bias at work as well - people who don't like taking orders from the top generally don't work as an employee of large companies, which means that the majority of employees do like taking orders from the top.
- ChuckMcM 15y ago"I wonder if there's any way to avoid this if you happen to be an employee # < threshold." That is, and continues to be, an excellent question. At Google some of the low employee number folks were actively trying to break this bias. (for them its a question of being able to scale their time, if nothing gets done until they engage in it, they become a limit to scaling. And while there will always be people who bask in the 'I'm so important the company stops when I do' limelight, I felt that in general those folks were in the minority.) It was the overall bias in the otherwise weak senior management (remember Google is very engineering driven) against ideas from people who weren't already 'well known.' Prior to Google I was with a company called Network Appliance and they had an excellent program where every 6 months or so the senior engineers got together and talked about various ideas (some evolutionary, some revolutionary, and some very off beat ones). It was later that I recognized that for a certain size and larger, you needed some sort of event like that so that folks could talk face to face, without the 'distractions' of the day to day fire drills, which created the constituencies which could champion ideas from any source. It also gave the folks who had to allocate resources (the managers) some notion that the idea had been surfaced in a place where, had it been untenable for some reason, those reasons would have come out and been discussed and weighed. I knew it worked at NetApp when I participated, and I missed it when I was at Google, but more importantly I came to understand how important it was to have a company have a healthy way of having technical conversations internally when you were bigger than a single office in terms of your engineering staff. Without it, the ability for a manager to filter 'good' ideas from 'bad' ideas is limited to their own experience and I can completely understand how they might unconsciously (or consciously) use tenure of an employee as a crutch. At Sun we called it 'checkin approval by uid' (which was to say that some folks just wrote good code and so the gate keeper for a release would be much more likely to take their change than the same change from an unknown contributor.)