[Gupie]

"agreed upon deliverables" is one definition of output. I think he is talking more generally, e.g. lines of code, over-long email, unnecessarily verbose documentation, ..., I could go on indefinitely.

But you are really arguing in general against such lists like this, that don't "examine the nuance". But perhaps they are useful discussion point or memory joggers. And shouldn't the senior members of a team or managers explain to novices the importance of meeting such milestones that you mentioned?

[Verdex]

> And shouldn't the senior members of a team or managers explain to novices the importance of meeting such milestones that you mentioned?

I basically read the whole list as: "How do be successful? Step 1: Be successful. Step 2: Be successful at purple. etc"

Some of it sort of makes sense. Some of it might as well be gibberish. None of it is useful without a bunch of senior members of a team who have been successful before. And if that's the case, then we can just delete the list and stick with the senior members of the team.

[Gupie]

The prefer "outcomes to output" is not a "How do be successful? Step 1: Be successful. Step 2: Be successful at purple". I can see the use of such a list for example on a team wiki as a reminder that you don't get credit for writing a 3 page email when a 6 liner would be as useful.

I can see the use of such a list for example on a team wiki as a reminder of what the team considers good practice.