This collection of personal learning and cognitive habits will help you learn more, faster. These suggestions are just that, feel free to start with these ideas and expand as you discover what works for you.
For more information in this area, see Pragmatic Thinking & Learning (Hunt, 2008).
❑ Critical ✓ Helpful ❑ Experimental
Steps to first adopt this practice:
Human brains are not built to multitask. Various studies have shown that it can take twenty to forty-five minutes to resume a task after an interruption (see TeamWideInteruption).
Email is a pernicious source of interruption; try sending less of it. The less email you send, the less you’ll get back. Personal contact is higher bandwidth and more effective. If you have to use email, you can set the tempo for the conversation. If you reply immediately, you’ve set the expectation for that conversation, which may or may not be appropriate.
Don’t context switch
Don’t context-switch. For any work queue (bugs in a database, emails, tasks on a Kanban board), work through that queue only. That is, don’t constantly switch tasks. For instance, you might find developing a new feature gets interrupted by a bug fix, which gets interrupted by new email, which gets interrupted by a text message, which gets… If you try to do many things at once, you may find none of them get done.
Mental lists are cognitively expensive. Don’t try to keep lists in your head, write them down instead.
You’re never “done” learning and you’ll never know “enough.” Learning is a lifelong activity, and so is “un-learning”—tearing down old mental models that are no longer accurate or useful. Learning is a messy, complex process, and does not include a straight line to success. You don’t know what you don’t know, and use discovery, exploration, and invention to learn and progress.
You have to deconstruct old mental models
New knowledge will invariably invalidate older, ingrained ideas, and it can be a real challenge to throw out “old” ways of thinking. For example, when object oriented programming first became popular, new OO programmers still wrote imperative code even in the new language. You can see the same thing with new functional programming attempts: trying to write in an OO or imperative style instead of embracing the very different functional idiom.
Instead of just reading technical books, blog posts, or watching videos, take a more deliberate approach, such as the SQ3R technique:
A training course, seminar, or book will only get you to a novice level at best. You only really learn by doing, with continual practice.
Learn by doing and reviewing
Make sure you have an opportunity to practice what you’re learning, whether it’s with at work, using open source software on a home system, or volunteering for a charitable organization.
Just “doing it” isn’t enough, of course, you need to constantly review your progress and get feedback from your practice so you can adjust and grow your capabilities. Do and review to grow.
Because of the structure of the brain and its networked processes, your best insights and creative ideas will likely hit you when you are not in front of a computer, or engaged in any “foreground” task. Instead, these insights arrive when the Default Mode Network (DMN) is activated, when there is little to no cognitive demand. You need to carry something with you at all times to capture every idea, question, insight, comment, curiosity, etc.
Henri Poincaré, the famous mathematician, was known to pose a problem to himself, then walk away from his study for a leisurely stroll around the grounds. In the middle of the walk, an insight would come to him and he’d quickly return to his office to capture it, solving that problem and proceeding to the next one.
Step away from the keyboard for the answer
You can use an expensive Moleskine-style notebook or a cheap spiral pad, index cards or even just a folded piece of paper with a mini pencil. But have something that always in your pocket, always ready for that idea.
Because if you don’t write it down, you will forget it.
Taking notes is just the start. Learning requires content creation: notes, summaries, mindmaps, highlights, cheat sheets, post-it flags, recipes, code fragments, How-To’s; whatever you need.
Mindmaps are a great tool for capturing and exploring ideas and insights.
Keep track of good ideas to get more of them
It’s best to create mindmaps by hand, not on a computer. Hand-drawn mindmaps engage large-motor functions and involve more of the brain—it’s a more fluid and dynamic exercise than filling in text fields on a device. On paper, there’s always room to squish in something extra. Assigning different colors and textures might illuminate new relationships and generate insights as well.
The hyper-prolific inventor Thomas Edison often took naps with a cup of ball bearings in his hand. Just as he’d drift off to sleep, he’d spill the cup and the clatter would wake him up, so he could write down and capture whatever thought he had at the moment.
Hypnogogia is the transitional state between wakefulness and sleep when the brain often reveals insights and thoughts arising from background processes. Edison knew this to be a rich source of creativity and problem solving.
Harvest your best pre-conscious thoughts
A more modern version—no ball bearings required—is the oft-taught technique called Morning Pages. First thing in the morning, before getting out of bed, reading email, or anything else:
It might take a while to reveal anything useful, but subjects have reported amazing and helpful insights, ideas, and approaches by using this technique.