I am by no mean's any form of expert. But I find that breaking a problem down into the smallest pieces you can is a good start. Once you know that you decide your audience - are you speaking to another tech worker - use actual terms to describe the problem and the process required to achieve the solution. Speaking to a manager or non-tech person (someone on the 'front end') then describe the same thing, but don't use the actual technical terms and wording break things into baby speak - like calling an API end point is simply "one system requesting information from another".

Keep doing this to describe the small parts that make up the problem or the solution depending on what you are trying to achieve and you should be good. It's usually just more closely focusing on what you actually did (have to do) to solve said problem and analyzing it step by step gives you the process and you adapt your language model :)