As a terrible programmer my trick is to read statements backwards. Maybe programming should be taught that way too not just reading of it but the history of it all the way back to Charles Babbage, Ada Lovelace and even weaving looms.
As a product manager, I have often found it beneficial to write requirements backwards. Start first with the desired result of a feature or flow and work backwards to the necessary steps, options, preconditions, actors, setup/enrollment steps etc. that would have been required required to get there.
I ran across an interesting essay on Medium recently on this topic, advocating a new approach to roadmaps focused on the problems: the problem roadmap. Instead of saying what new features the team will be working on in the future, map out what problems they’ll be working on.