Design Pattern: Is there a common method/approach to abstract from a real world example towards a pattern?

Note: I do not want to know a real world example of pattern xyz.

I often read about design pattern in the way, that the pattern are explained first and then a real world example is provided (or not) which actually fits this pattern. It always seems that the authors 'think' from the solution (pattern) to the problem (example) and not vice versa.

Then, mostly the conclusion is given: You have to know most of the pattern and you have to be experienced and smart enough to know when to apply a pattern for your concrete example. And it is an art and you have to be creative.

This seems somewhat non-intuitive to me, since I learned to design software by abstracting from real world problems into code systematically. So to me there should be a systematic way to abstract from a problem to a pattern, too.

Has someone ever invented an approach of abstracting from a concrete problem effectively into a common design pattern?