Scenario: Your boss calls you into the office and says that you are taking over this huge project that’s in an area that you are not familiar with and this is happening in a week. You, being the smart-genius type tell your boss that’s great, you’ll be ready in a week to take over the project.
Problem: You take on the new project because having more responsibility tends to lead towards even bigger things down the road. But now, what do you do? You have close to ZERO knowledge in this area? But it’s important to realize that when you feel uncomfortable you have the greatest chance to learn.
What I did: I was called in to take over an ASP/MSSQL project with 50K active users back when I knew almost nothing about these technologies. I felt like I had no choice but to take on the project because I wanted the responsibility and because of the new challenge (and because I was pretty much expected to).
So I went down the local Borders and bought four books. Two “For Dummies” books on ASP and MSSQL and two of these 600 page advanced guide to ASP and MSSQL and then I read through all four of the books in the next three days.
The rest of the time I used to get familiar with the code and with the entire system. When the time came for me to take over this project I was ready.
I have used this method to learn countless other technologies and to pass many tests in college. Without further ado, here is how to learn anything quickly online (or offline).
Here’s how and why this works:
If you are pushed for time either externally or by a self-imposed due dates, this method works great.
Step 1: Get the big picture, that’s where the “For Dummies” or “Idiots Guide” type of book comes in. Other “intro” type of books work also. It covers the matter, but does so broadly and covers all of the areas of a particular subject, so you get the big picture of what is possible, what is covered and where the limitations lie.
Step 2: Get the details. This is where the “advanced” version of the books comes in. This is where you’ll actually read the details, the nuts and bolts of the subject, the actual code and so forth. You don’t want to apply this knowledge while reading the details, that’s next step. Make sure to read the entire book or all of the details that are available.
The reason for reading all of the details is to get them into your head so that when it comes to actually applying it, you won’t remember how to do it, but you’ll remember that you read about it and you’ll be able to look back and find the code or the specific knowledge that you know already exists because you read it in the details. The goal here is not to hold everything in your mind, but to get it through your conscious into your subconscious. The goal is to oversaturate the mind and let the subconscious handle the sorting.
Step 3: Apply the knowledge. In my example, I inventoried the system, learned the different parts of it. When something needed to be changed I then proceeded with the understanding that I already know what is possible and a general idea of how to solve it. After that I would just look up the code snippets and get it done. Knowledge is only potential power, only if organized into definite plans of action and directed to a definite end.
Applying the knowledge makes the subject more real and forces the mind to sort all of the information and associate it with previous information that’s already in your mind.
Conclusion: I still use this method, because works for me. And I think it pretty much covers everything that is needed to learn something and learn it quickly with the broad approach.
How do you learn? Check out my “Dumies” post about learning SEO.