[ghaff]

And there should be some degree of flexibility. If a new unplanned but important project comes up, you don't want to say "Nope, can't help it's not on the list" even if everyone else agree this should be your priority. (Or you're told to do it and then are dinged because you didn't meet your goals.)

In general, having a set of agreed-upon goals/priorities works for me so long as they're not being rigidly followed past the point where they make sense.

[mason55]

Yeah this is why we end up setting goals for our teams that are generic, like “respond to production issues within one business day”.

Not the dev’s fault if the big Q3 feature they were supposed to work on gets deprioritized in Q2 or some important customer cancels for an unrelated reason and their goal was to get the customer live.

Yes, you can redefine goals as things change, but at a certain point it adds a lot of overhead and the goals just turn in to “your job”.

[ghaff]

There’s probably some happy medium between super-generic and super-specific in many cases.