You can separate projects for learning technologies and projects for customer need. For example, when I wanted to learn Elixir, I made a simple to do list with concurrent users to test Elixir's scalability. A to do list is nothing new for customers but it still enabled me to learn more about the tech. Often, these two categories intersect over a large enough set of projects.
I still don't know how to get out of that mindset.