Concerned about Productivity Drop due to New Policy of Requiring Two Sign Offs per Pull Request on Four Person Dev Team

I work on a 4 man development team, and up until recently, we had the standard policy of requiring one other developer to sign off on each pull request. But in the coming month, that will switch to requiring 2 people to sign off. I am concerned for a number of reasons.

Most of our work does not lend itself well to PRs in the first place. 90% of the PRs are extremely simple, such that they don't warrant a PR at all (adding new reference data to an existing table, adding a new column to an existing table, etc) 10% are so complex that they can't be effectively reviewed in less time than the original developer took to do the work (creating a 1000+ line stored procedure to populate new tables A, B and C, rewriting existing process X to run in 50% less time using set based processing, etc) As a result, essentially nothing of substance changes as a result of a PR, but they take up a large amount of time, because the volume of work is so high.

So we'll be effectively doubling that time. Every task will now involve 75% of the team (one to write it, another two to review it) and if two team members are out at the same time, no PRs can be completed during that time period.

We are the team that simultaneously has the highest throughput, longest PR turnaround (complex PRs often sit for weeks before being reviewed by a single person), and every other team depends on our work. This seems like a very obvious recipe for disaster, and management decided to make this blanket change in policy without consulting any developers.

Has anyone out there faced a similar situation? Is so, how did it end up?