If your team conflates outputs with deliverables, you're not even ready for the "outputs vs outcomes" conversation.
A designer is not "done" once there's a working prototype in the team's Figma directory, because the function of the designer's job is not "make prototype."
They are "done" when the customer-facing system behaves as designed (and can then have the conversation whether what was done was good).
People grasp that for coding, your definition of done is when the behavior of the code satisfies the Jira ticket and goes into production.
What they don't get is that the definition of done for *writing the ticket* or *drawing the wireframe* is exactly the same - code in prod.
@PavelASamsonov AFAIK teams need a single, common Definition of Done; if you are comparing different disciplines’ DoD’s you’re already going astray
@sakhavi 💯 shared goals and methods is the definition of a team!