As if you’re explaining the problem to a child (or better yet, an actual rubber duck), go through a situation step by step.
Useful in programming, and can be in real life situations as well.
When you’re overwhelmed by a decision and its impacts, take the time to divide the problem by rubber duck debugging. Then conquer by doing ‘commitment grounding’.
Even when faced with a complex problem, rubber duck debugging and following up with uncovering the essentials of the problem will often provide you with a very clear view of the solution. The question might still be: are you willing to accept it’s the most practical one?