Many groups suffer from having too many levels of sign off: designers seek sign off on UI changes from the head of their department and, potentially, the studio manager. This is after UX have sought sign off from their functional head. After that, we need stakeholder sign off, product owner sign off, marketing, brand and communications sign off (to ensure the message is correct) and who knows who else will need to have a say?
“With all this signing off going on, how will we ever get the damn thing launched!?” said the frustrated team members.
Perhaps you’re conflating “sign off” with “feedback”. Ultimately, there is usually only one or two people who are accountable for the success or failure of the thing you’re working on. Pragmatically speaking, this would be the product owner. For the sake of argument, we can also extend this to key stakeholders too. It’s these people that give “sign off” on whether something is ready or not.
Everyone else is just giving feedback, which can be taken on board, or ignored, as the product owner and key stakeholders see fit. If it’s a decision between pixel perfect designs and getting it in front of customers, let the PO decide. If you’re one of these functional heads and you’ve employed people whose work you need to “sign off” before it sees the light of day, perhaps you’ve employed the wrong people?
As Roy Castle sang, “Delegations what you need.” (He didn’t, he sang “Dedication…” but, whatever). If you’re building websites, your mistake won’t be live long. The more time you spend in the cycle of sign off, the less time you spend with your product creating value for your users.