3 ms·
I've never worked for Google, but in every company I've worked for, when productivity was considered low or something, developers and designers weren't to blame
by zac23or 4y ago
I've never worked for Google, but in every company I've worked for, when productivity was considered low or something, developers and designers weren't to blame for the low productivity.
1. We had 26 teams and 16 meeting rooms, and we often didn't have rooms for meetings. How was this fixed? They created a new meeting room.
2. After the discovery of "low productivity", a new meeting was created, obliging all teams to participate in meetings on "the reasons for low productivity"
3. The most productive week is the week when all scrum managers have been in training for one week.
But the accusations always came to the development team...It was hell on earth.
Probably something similar is happening at Google.
- not2b 4y agoYes, if they aren't getting the results they want from all those smart people, it's because they aren't managing right. Most people want to do good work, but sometimes process and teams fighting each other gets in the way.
- adolph 4y agoMaybe similar to a startup incubator/fund the idea is that most effort does fail and as long as some small percentage is wildly successful the whole enterprise continues. The “low productivity” is a feature indicating low priority effort is appropriately prioritized. A key challenge is when something without a strategic purpose/value is released and becomes a beloved product that eventually must be depreciated, like Google Reader. It is much better to develop and never release than to release something without strategic benefit that causes problems in long run.