I'm not sure if this will be useful since I'm not very good at "formal" education systems. But through the course of my career I often need to rapidly learn new concepts, keep on top of new concepts, and be able to effectively utilize what I learned quickly.
I've found that having a specific project/goal helps immensely. Then I break it down into its base components. The base components aren't ever perfect, but I just do the best I can with what I have at starting. Next I figure out what looks like a logical order of operations and start at the base and work my way up.
Conceptually, I think of it like Captain John Boyd's OODA loop framework.
The Tao of Boyd: How to Master the OODA Loop
I take concepts I know, try to apply them to the specific challenge, then fill in the gaps and update the models accordingly.
Longer term learning I like to use Obsidian's note taking system. (I've lost so many notes due to closed file formats it's ridiculous, Evernote did me dirty). I have just a few folders in Obsidian. Daily notes, Literature notes, Long notes, Distilled Notes, and Assets. Basically literature notes are when I'm taking notes on blogs, books, videos, etc. Long form notes are basically all of the literature notes and daily notes organized by topic. Distilled notes are the summary form of the long notes, and Daily notes are whatever I'm learning that day. Asssets is just where I dump all the images, PDFs, audio files, etc. that are linked up in the other notes.
An example: Recently I had to learn to hand code HTML emails. Previously I only had experience with bash and PoSH scripting. (I work more on the automation side, but due to a management decision I went from having arguably one of the worlds best drag and drop email builders to one that was outdated two decades ago, making it functionally unusable for what we wanted to do.)
The first step I broke the problem down into the components I knew of. I read some blogs and articles about hand coding emails and made a literature note about every specific blog that I had. Those literature notes were put into a long note (Obsidian links notes together, so no copy pasting. If I update a lit note, it updates the Long note.)
The next step I identified which of my assumptions were wrong. Updated the long note accordingly and formulated a plan to address the newly refined problem. I needed to learn basic HTML and CSS to build a decent email. So I found a good website that covered HTML and CSS basics in a format that I understood. (Project Odin, one of the great things on the internet). I went through the program and took literature notes and long notes about each topic (in this case it was HTML and CSS).
Now that I had the basic blocks down I needed to apply them. I went through several blogs and took notes on how to tweak HTML to work with email clients and identified what needs to happen to make them work universally across clients. At this point I could tweak existing templates to be what I needed them to be. It wasn't as fast as the drag and drop builder, but it worked.
During this phase I found some tools that relied on basic HTML and CSS knowledge to automate a lot of the background stuff. (MJML, if anyone has to build an email from scratch, this is the best tool I've found so far.) So I took what I just learned about basic web development and utilized that to rebuild our templates in MJML, which allows me to iterate new and completely custom emails in 30 minutes.
So at the end of this process I was able to do in 30 minutes the same task that took the agency's email expert 4 hours to do. All within the span of a couple weeks. And with less errors and malformed emails in certain clients.
To use the great analogy from the AoM article above, I learned to build snowmobiles faster and better.
I've used this method to learn basic business accounting, python and pandas basics, media buying, business development, strength training, and to tackle just about any problem that comes up. If in any of those areas I find I need to dive deeper, I just repeat the process with the newly identified problem that needs to be solved.
Some key concepts that I like to keep in mind when working this type of system. "Strong beliefs, loosely held"- Peter Attia "If something is correct 80% of the time, just assume it is correct"- Ray Dalio and "Its OK to assume, but know when you are assuming and be honest when your assumptions are wrong" -Dunno probably something I synthesized in a distilled note.
I'm in my late 30s, have two jobs, and have hobbies that are time intensive along with trouble focusing for long periods of time. This method seems to fit my personal set of challenges pretty well. Plus it is enjoyable too.
Hopefully that helps and doesn't just send you down a productivity procrastination loop. At the end of the day you do have to actually read the material and you do actually have to learn it enough to utilize it.