OKRs from a development team’s perspective

Re:OKRs from a development team’s perspective by hobs on Friday May 24, 2019 @03:51PM (#20004751)

And then you have to do the hard thing, which is listen to the engineers (which is why most business folks are fine with keeping the siloing as is.)

[ Parent | on HN ]

Re:OKRs from a development team’s perspective by BurningFrog on Saturday May 25, 2019 @12:16AM (#20007053)

A lot of engineers talk about how business people should listen to engineers.

A lot fewer engineers talk about how they like to listen to business people.

[ Parent | on HN ]

Re:OKRs from a development team’s perspective by hobs on Saturday May 25, 2019 @12:26AM (#20007079)

Well, if they dont they get fired :) and I dont like to talk about the business doing things, just working this weekend because they didnt listen for the last six months.

[ Parent | on HN ]

Re:OKRs from a development team’s perspective by edmundsauto on Monday May 27, 2019 @02:33PM (#20024266)

Engineers think (sometimes incorrectly) they could do the job of the business people, in a pinch. Business people know they can't do what an engineer does. This dynamic contributes to why business people respect engineering on engineering decisions, and why engineers don't respect business people on business decisions.

[ Parent | on HN ]

Re:OKRs from a development team’s perspective by MrDunham on Friday May 24, 2019 @09:54PM (#20006648)

I love listening to my engineers. They usually know how to solve something faster and more elegantly then I do.

But I'm someone who will learn enough Node/React/python to understand what can, and can't, be done.

[ Parent | on HN ]