7 ms·

Ah, thanks for the detail regarding the origin of this. For some reason I just assumed it came out of some scrum cult type thing as the rise of that was also fo

Ah, thanks for the detail regarding the origin of this. For some reason I just assumed it came out of some scrum cult type thing as the rise of that was also for around the time OKR became part of the lexicon. I completely agree. Are we just stuck with this then for the foreseeable future I wonder? It seems to be that there are enough people that share this sentiment that this whole overbearing process ritual has become largely performative and toxic.

BlargMcLarg 4y ago
Well, management types are probably not going to collectively vote against something that could jeopardize their jobs, even if it would be beneficial for the corp. So we're waiting for higher management (C-level) and startups to take the risk and show it can be done differently and more efficiently. Meanwhile, most developers are not uncomfortable enough they are willing to unionize and stir the pot over this. There's a disturbing lack of empirical evidence over all this, some even pointing towards how destructive these trends are. Yet, if the people themselves are unwilling to combine their collective weight and push back, nothing's going to happen. I think the best way to put it is "most people don't care or flat-out dislike it, but it is too much effort to push back given the perceived success rate". Some adjacent comments already hint to it: stirring the pot is a great way to get yourself on the no-no list and have to start looking for a new job.
- bogomipz 4y ago
  Agreed. What a sad state of affairs though. All these companies that aspire to disrupt but that spirit somehow doesn't apply to their own management. The irony is quite spectacular. I think your right that any meaningful change will likely come from some successful startups(s.) What a great way differentiator that will be for any startup who actually thinks differently and markets themselves as such as a means to attract talent.

BlargMcLarg 4y ago

Well, management types are probably not going to collectively vote against something that could jeopardize their jobs, even if it would be beneficial for the corp. So we're waiting for higher management (C-level) and startups to take the risk and show it can be done differently and more efficiently. Meanwhile, most developers are not uncomfortable enough they are willing to unionize and stir the pot over this. There's a disturbing lack of empirical evidence over all this, some even pointing towards how destructive these trends are. Yet, if the people themselves are unwilling to combine their collective weight and push back, nothing's going to happen. I think the best way to put it is "most people don't care or flat-out dislike it, but it is too much effort to push back given the perceived success rate". Some adjacent comments already hint to it: stirring the pot is a great way to get yourself on the no-no list and have to start looking for a new job.

bogomipz 4y ago
Agreed. What a sad state of affairs though. All these companies that aspire to disrupt but that spirit somehow doesn't apply to their own management. The irony is quite spectacular. I think your right that any meaningful change will likely come from some successful startups(s.) What a great way differentiator that will be for any startup who actually thinks differently and markets themselves as such as a means to attract talent.