The culture of feedback has the infected your brain. The "strong objections" framing is just collaboration cosplaying as decisiveness. You're still waiting for permission, just with extra steps and passive-aggressive phrasing designed to shame people into silence. It's corporate theater. You've invented a mechanism that still makes one person wait on others, fragments their attention, and creates the expectation that decisions are collaborative by default.
Why not just: ship it, get feedback from actual usage, iterate.
First of all, just because you (or the author) call collaboration a bad thing doesn't make it so. Secondly, you seem to have misunderstood the process. The steps are: I will be shipping shortly, here is the direction I decided on because XYZ, if you want to react there is some limited amount of time to do so but those objections better be nontrivial. There is no waiting for permission, the path is set - yes, barring strong objections. Apparently you think it's best to leave those for after the fact, well, good luck with that.
Why not just: ship it, get feedback from actual usage, iterate.