Jeff Bezos says the "smartest thing" they did at Amazon was to ban low effort presentations and embrace writing long-form briefs for each meeting. That made sure the problem was thoroughly thought out by the meeting owner and is read by the group in detail for the first 30 minutes of the meeting.
In open source, many projects adopt a RFC(request for comments) process in which a problem is written about exclusively with solutions and asking for public feedback. This works effectively in ecosystems like Rust, Python, JavaScript, and C#.
If you think about knowledge work in general, 80% of the job is problem solving, creative thinking, etc. 20% of the job is implementing / coding. Jumping straight to code was something I did when I was early in career, but now it's the last thing I do until I understand the problem in detail.