[Chris2048]

> Nobody on my teams would say I micromanage them

Perhaps that's b/c you are apparently in a position to get rid of people who "go AWOL" despite maintaining "a large degree of autonomy".

If autonomy is prefixed on "within a framework of shared goals and shared values" then why do you think individuals can't do work based on their own conception of those shared goals/values, rather than requiring signoff first? Autonomy is being able to make (and execute) decisions on your own (possibly based on shared information/value/etc) - requiring signoff is not autonomy, it's merely the ability to participate in decision making.

[sirsinsalot]

There really shouldn't be an issue getting work approved and visible to the whole team (if anything for team input, collaboration, opportunities for others to object).

If you're working for the benefit of the product/team I don't see why you would need to, or have an issue with this.

Strange.

[Chris2048]

> team input, collaboration, opportunities for others to object

You don't always need a ticket for this, if it applies at all. I'm not unaware of these benefits, but the burden lies with you to demonstrate devs cannot be trusted to be autonomous, or choose the appropriate mode of collaboration.

> getting work approved

Why is this always needed?

> If you're working for the benefit

This is a strawman, you can do this without the overhead.

Who do the approvers seek approval from, for the same reason(s), and who do they seek approval from?

> visible to the whole team

This is what standup / status updates are for. It takes all of a few seconds, no approvals needed.