I read two recommendations highlighted here.
First, there's a long time between when work is ready to go to production deployment and when deployment happens.
Second, PRs sit around waiting for review for hours or days.
For the first point, my experience is that the author's purely development/technical marker for "production-ready" fails to take into account a great many other forces that lead to software ostensibly production-ready sitting around waiting to be released.
The second point is something I see as an artifact of reliance on PR- and review-driven development. This is a choice, not a hard fact of workflows. If the team is using this kind of workflow and it's a bottleneck, maybe the problem is the process itself and not the execution.
