While I doubt most people have sufficient "objective statistics" to truly remove ego from the equation, there's a middleground here.
Write up your detailed proposal as typical, but before you click send, put an "executive summary" at the top, with maybe two sentences. One to describe the problem and one to describe the solution. You can put all the detail you want in the rest of the document. But the onus remains on you the engineer to make a recommendation, not just list options. If you genuinely believe yourself to be a probabilities it should be easy!
Agree. Rounding most of the advice to providing an executive summary is about right.
If you’re not fully confident and think an experiment is worth while, lead with that, and provide assurances there are mitigations in place or a decision is easy to back out of. That’s still doing the work.
If you want an easy decision, you need to do the work. Not expect others to get into all the detail you did. There’s still room for those decisions - they’re just not as quick/easy.
Write up your detailed proposal as typical, but before you click send, put an "executive summary" at the top, with maybe two sentences. One to describe the problem and one to describe the solution. You can put all the detail you want in the rest of the document. But the onus remains on you the engineer to make a recommendation, not just list options. If you genuinely believe yourself to be a probabilities it should be easy!