POSTS ON 

Learning

(0)
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.

David Allen’s Ideas about Getting Things Done

Reading about personal knowledge management (PKM) and reading books by Tiago Forte, I became interested in how PKM and productivity can help get more done. I decided to read up on productivity frameworks. Years ago, I read Getting Things Done: The Art of Stress-Free Productivity by David Allen. I remember it only vaguely and decided to revisit it. Learning that an updated version had been released, I bought it.

I haven’t finished it yet, but a few of the concepts he writes about have caught my attention. Here are two:

Clarifying

Allen evaluates incoming information based on its actionability, who should execute a task, and how long it will take to accomplish. If something isn’t actionable, trash it, “incubate” it until it becomes actionable, or store it for reference. He has a 2-minute rule for actionable items: anything actionable that you can do in less than 2 minutes should be handled on the spot. Anything that can’t be handled in 2 minutes should be delegated to the appropriate person or deferred to a time when you’ll do it. He has a nice flowchart in the book that simplifies his clarification process.

I’ve used this approach to handling email for some time, aiming to be inbox zero every day. I’m a big fan of my email app’s “remind me” feature. I queue up tasks and email responses that will take more than 2 minutes and handle them at times I’ve dedicated to this predetermined work. This approach has helped keep my inbox tame, ensure that nothing falls through the cracks, and allowed me to be more proactive by doing this kind of work as I deem appropriate.

Identifying Next Actions

For projects with multiple steps and a clearly defined goal, Allen advocates constantly asking, Is there something someone could be doing on this right now? Asking this question continuously surfaces the next actions, keeping a project moving forward.

People sometimes have project plans defining actions to take and when to take them. However, the problem with those plans is twofold. First, they’re hypothetical. Those plans are often crafted before execution begins. They don’t consider current real-world reality. Second, if a team is involved, they’re likely to be top-down. The people executing the work have little or no input into how they achieve the goal for which they’re responsible.

Allen’s approach is more of an iterative bottom-up approach. It reminds me of Coinbase CEO Brian Armstrong’s analogy of climbing a mountain shrouded in fog. The goal is defined, but the path to get there is flexible. The next action always reflects the current realities and incorporates learnings from previous actions. For teams, this approach empowers members closest to ground level to pinpoint and take the best action at any given time.

The iteration that results from Allen’s approach of asking this question constantly is more powerful than most people realize. This approach is how the impossible becomes possible. It’s how people successfully navigate uncertainty. It’s progress toward a stated goal with constant recalibration.

I hope to share other good concepts from the book in another post. I’m looking forward to finishing the book.

+ COMMENT

Why I’m Testing Checklists

After reading Tiago Forte’s book Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential, I digested the PARA and CODE concepts. Part of my process was to see whether other credible people mentioned any of the same ideas Forte did. When multiple unrelated credible people reach the same conclusion through trial and error, their wisdom is often worth paying attention to.

One of Forte’s ideas—that using checklists in your process is valuable—met that criterion. Forte mentioned using checklists to ensure that you’re starting and finishing projects consistently. In a post last week, I shared that Josh Kauffman, in his book, recommended checklists to prevent omissions when learning about and acquiring a new skill rapidly. I also remember Charlie Munger’s “Investing Principles Checklist” from Poor Charlie’s Almanac: The Essential Wit and Wisdom of Charles T. Munger.

I know checklists work—they were key components of the processes at my e‑commerce company. The teams followed them to ensure that we executed processes consistently. We became known for our reliability and built a solid reputation because of it. Sadly, I never applied checklists to my work style. I keep in my head an idea of how I need to execute things I do more than once, but I haven’t always executed consistently on some of them, even though I consider them important.

Today, I decided I’m going to test using checklists for things of high importance that aren’t one-offs. I’ll spend some time thinking about what deserves a checklist (I don’t want to go crazy with this) and then thoughtfully create the checklists. I’ll test using them and adjust as necessary. I’ll also make sure using checklists is lightweight and doesn’t bog down my workflow.

I’m excited about this experiment and can’t wait to see the results. My gut tells me it’ll have a positive impact given that smart, credible people use checklists.

+ COMMENT

Tiago Forte’s Framework for Actionable Knowledge

I finished reading Tiago Forte’s book Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential. Yesterday I shared Forte’s PARA method for managing information you consume. I’m still learning about this method and comparing it to others. I may end up modifying my current approach and borrowing some aspects of PARA.

Today I want to zoom out a bit and share the central concept of Forte’s book: his method for capturing and storing information in a “second brain” and then using it as needed. The second brain is “an external, centralized, digital repository for the things you learn and the resources from which they come.” Forte’s approach is called CODE. Here are its pillars:

  • Capture – Capture information and ideas that could be useful later—but only what resonates with you. Forte thinks of it as creating a knowledge bank from all the various sources we encounter on a regular basis (email, podcasts, etc.). Instead of trying to remember all this information, store it digitally.
  • Organize – Organize the information you’ve captured in such a way that it’s actionable. The PARA method is a significant component of this step.
  • Distill – Find the essence of the information you’ve gathered. What’s the core concept or wisdom? Forte uses the progressive summarization technique to find the core and enhance its discoverability for future reference.
  • Express – Express what you’ve learned in smaller chunks, even if everything hasn’t been completed. Forte calls these chunks Intermediate Packets. One thing they’re good for is sharing with others to solicit feedback quickly. He views them as building blocks that are intellectual assets and can be reused in the future.

Forte’s approach doesn’t include anything we haven’t seen or heard before, but it combines components in a simple way that encourages you to think about how to use a second brain to turn information into actionable knowledge.

If you’re interested in learning more, Forte shared a detailed blog post on CODE.

+ COMMENT

Tiago Forte’s Framework for Organizing Digital Information

An entrepreneur friend shared with me that he uses the methods of Tiago Forte to organize all the information he consumes. He suggested Forte’s book Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential. It sounded interesting, so I ordered it.

I haven’t finished the book yet, but one method it mentions has already caught my attention. Forte calls it the PARA method, and it’s his flexible approach to managing digital information on various platforms. The idea is to create four top-level folders to manage all incoming information you consume. Here are the main parts of the method:

  • Projects  – Things you’re currently working on in the short-term. Ideally, you have a goal in mind for each project. Think implementing a payroll system or hiring a contractor.
  • Areas – Responsibilities you must manage. They’re ongoing and essential to you. Think managing your finances or direct reports.
  • Resources – Topics you’re interested in but not actively working on. Think cooking, fashion, or customer discovery.
  • Archives – Inactive items from the above three categories.

An important part of this method is that information is grouped based on how actionable it is, which makes sense to me. Another thing I like about this system is that nothing is lost; everything can be retrieved in the future if it’s needed. The archive folder serves as a repository.

I’ll continue learning about the PARA system, but so far it seems very flexible, and it isn’t complex, which is attractive to me.

If you’re interested in learning more, you can read Forte’s blog post about PARA.

+ COMMENT

Framework Books and Tactical Learning

I’ve been enjoying reading more. Usually, I read biographies and recounts of historical financial events, but this weekend, I spent time with what I would consider a framework book. The author gives readers his framework for managing and using all the digital information they consume.

I initially considered framework books as self-help, which I tend to shy away from because I don’t get much value from them. But after this weekend, I revisited my thinking on that. I realized that framework books aren’t self-help, and I do get value from them—in specific situations, not generally. These framework books are tools for tactical learning, while biographies and historical books are for general learning. Framework books are useful if I have a problem I’m actively trying to solve. They don’t solve my problem for me, but they give me an approach or method that, if followed, empowers me to solve my problem more efficiently.

I still enjoy reading biographies more than any other genre. However, I recognize the value of framework books when I’m trying to solve a specific problem. I won’t read them when I’m interested in general learning, but they’re part of my tactical learning toolbox going forward.

+ COMMENT

First Impressions of Personal Knowledge Management

I have a problem storing all the important things I learn from the books, videos, articles, and other content I consume. A founder friend shared with me how he does it: he uses a variety of tools cobbled together. Doing some digging on the tools he uses and their competitors, I stumbled upon a world focused on this problem: personal knowledge management (PKM).

This world is new to me, and I was curious. I spent time this weekend watching PKM experts explain the frameworks, systems, and processes they use in their daily lives. A few early thoughts after today’s learnings:

  • PKM is niche but seems to have gained momentum around 2020-ish.
  • PKM is different from productivity management, but both were incorporated into many PKM experts’ systems.
  • A ton of tools help with PKM, but they all do things differently. No one tool can do everything, so cobbling tools together is the norm.
  • People consume information from so many different sources that it’s hard for one tool to be great at capturing all of it.
  • The need to cobble together tools increases complexity. There are just too many systems and moving pieces for the average person to manage. This decreases the likelihood that someone will adopt PKM.
  • Embracing the PKM approach that “experts” demonstrated requires a high degree of consistency in process execution. There isn’t a lot of room for error.
  • I expected AI to be mentioned and utilized significantly. It wasn’t.

I’m still learning about this, but I get the sense that PKM can get rigid and complex very quickly. In my experience, rigidity and complexity often lead to spending more time managing the system than getting value from the system. I don’t want to use anything rigid and complex.

PKM isn’t the same as productivity management, yet many people combined the two in the approaches I watched today. My gut feeling is that this isn’t the right approach for me. My task management will likely be more effective if it’s managed separately in a simple and loose system than as part of a PKM system.

I haven’t reached a verdict on PKM yet, but I think a better use of my time going forward is to learn about the frameworks and methods used in PKM. If I find a framework I like and want to use, it may be better for me to create a simple, flexible system that suits me instead of copying a complex, rigid system developed by someone else.

PKM is still new to me. What I learned today was useful and gave me a good idea of what PDK is and how people are using it. There’s a lot I don’t know about PDK, and I’m not sure if it’s something I’ll adopt. But I’m curious to learn more so I can determine whether it’s for me.

+ COMMENT

Principles for Rapid Skill Acquisition and Learning

I want to share more takeaways from The First 20 Hours: How to Learn Anything . . . Fast!. The major premise of the book, which I posted about yesterday, is that learning and skill acquisition are different. By combining the two, you accelerate your acquisition of a new skill. I found author Josh Kauffman’s thinking around the specifics of each area and how they work together interesting.

Skill acquisition

Kauffman defines rapid skill acquisition as the process of breaking down a skill into its smallest parts, pinpointing the important ones, and practicing those key subskills first. He believes “temporary obsession” aids skill acquisition and that “rapid skill acquisition principles” are a way to cultivate temporary obsession. Here’s a checklist of his acquisition principles:

  • Choose a lovable project – Pick a skill you’re excited about. Your excitement will fuel you when you’re frustrated.
  • Focus your energy on one skill at a time – Acquiring new skills requires concentrated time and focused attention. If you spread yourself too thin, your skill acquisition will likely be extremely slow.
  • Determine your performance level – Rapid skill acquisition is about sufficiency, not perfection. Define what sufficiency means to you.
  • Deconstruct skills into subskills – Identify what subskills make up this skill.
  • Obtain critical tools – Get the tools necessary for you to practice the skill.
  • Eliminate barriers to practice – Remove the soft barriers that will make it more difficult to practice the skill.
  • Make dedicated time for practice – Schedule time to practice consistently. Commit to practicing regularly until you’ve completed at least twenty hours of practice.
  • Create fast feedback loops – Figure out ways to learn how you’re performing when you’re practicing. The faster the feedback, the faster you can make the right adjustments. The faster you adjust, the faster you acquire the skill.
  • Practice by the clock in short bursts – Set a timer for twenty or thirty minutes for your practice session.
  • Emphasize quantity over speed – Do as many reps as you can without worrying about perfection. The more reps, the better your rep quality will become.

Learning

Learning about a skill is the acquisition of knowledge related to that skill. Kauffman doesn’t believe jumping straight into practicing a new skill is the most efficient approach. Doing some advance research and planning can reduce the amount of time and energy you’ll have to expend and the frustration you feel. He believes “learning principles” help you get the most out of your practice sessions. Here’s a checklist of his learning principles:

  • Research the skill and related topics – Look for patterns—the same ideas and tools being mentioned repeatedly as you research. These will likely reduce your trial and error.
  • Jump in over your head – You want to learn at an uncomfortable pace. Confusion is part of being uncomfortable and can pinpoint areas you should focus on more.
  • Identify mental models and mental hooks – Look for ways to help you make sense of what you’re seeing. These mental models will help you understand the present and what the future could hold if you take specific actions. These will come in handy during practice.
  • Imagine the opposite of what you want – Determining your goal’s natural opposite can highlight what to avoid. This is called inversion and is a technique Charlie Munger embraced heavily.
  • Talk to practitioners to set expectations – Unrealistic expectations can be discouraging. Talking to others with more experience can illuminate blind spots so you’ll know what to expect.
  • Eliminate distractions – Distractions can ruin focused practice, slowing or stopping skill acquisition. Figure out what could distract you during practice and eliminate it beforehand.
  • Use spaced repetition and reinforcement for memorization – Review important information regularly. New or difficult information should be reviewed more often; familiar or simple information less.
  • Create scaffolds and checklists – Create checklists to systematize your practice process and make it more consistent. Create a pre-practice sequence (i.e., a scaffold) to ensure that you approach the skill the same way each time you start practicing. A basketball player’s pre–free throw routine is a good example of a scaffold.
  • Make and test predictions – Come up with your predictions based on your research and test them as you practice. Adjust accordingly.
  • Honor your biology – If your mind and body aren’t good, your practice won’t be good. Put yourself in the best physical and mental state to get the most out of your practice.

Every principle won’t apply to every situation, but going through each checklist can prevent omissions that could hamper you from achieving your goal.

Acquiring a skill is the result of practicing it. How you practice impacts how fast you acquire the skill. Learning makes your practice more efficient and accelerates acquisition, but it doesn’t replace it. There is no replacement for practice. You must do the work. But how you go about it matters.

The insight and principles in Kauffman’s book aren’t earth-shattering, but his combination and articulation of them could provide clarity and an action plan to people who struggle to acquire new skills.

+ COMMENT

To Acquire a New Skill Faster, Learn About It

During one of my learning survey conversations, a founder friend mentioned he’d read The First 20 Hours: How to Learn Anything . . . Fast! by Josh Kauffman. He described the book as an approach to learning any skill quickly. It sounded interesting, so I ordered it. I just finished reading it.

The book highlighted that skill acquisition and learning are different. Acquiring a skill requires practicing the skill until you become proficient at it. Learning, though, is about understanding the skill. Learning about a skill doesn’t mean you’ll acquire the skill—it means you’ll know more about it. The book uses the example of learning about a foreign language. You can understand all the nuances and history of the language without being able to speak the language. Speaking it results from practicing by speaking it with others.

Kauffman goes on to say that to acquire a skill, learning about it isn’t necessary, but it is helpful because it’s important to acquire the skill rapidly. Learning about the skill helps you focus on the most important subskills, understand the key concepts related to the skill, avoid practice pitfalls, etc., all of which make your practice more efficient. And you’ll acquire the skill sooner if you improve more rapidly.

Kauffman’s distinction is helpful. I now think about learning as the prework I do that will make practicing a new skill more efficient.

+ COMMENT

My Reading Mojo: Gone (Temporarily)

I’ve been on a good roll reading books. I’ve got a solid habit down, and I’m getting more from my reading than ever. This weekend I started another book. After a few days, I noticed that I couldn’t stay focused as I read and my pace was much slower. I tried to power through it, but today I had a realization.

The book I’m reading is killing my momentum. It was recommended in another book I read. But now that I’m into this book, I’m finding that it isn’t a good fit for me.

The book feels like a textbook. It goes into tons of detail about everything and contains many references to others’ works. And its main concept isn’t clearly articulated. This is all very different from the biographies and historical recounts I enjoy reading.

I tested my thesis: I started reading another book. Within thirty minutes, I was laser focused and reading twice as fast. I was back!

My takeaway is that all books aren’t for me. If a book is zapping my energy, best to put it aside for now and read something else.

+ COMMENT

The $2B Davis Dynasty and the Weekly Bulletin

I finished reading The Davis Dynasty: Fifty Years of Successful Investing on Wall Street this week. The book chronicles three generations of the Davis family and how an initial $50,000 investment in stocks by the patriarch has turned into more than $2 billion for the family and an investment firm that manages over $25 billion in total assets.

This book caught my eye because I enjoy learning about “investor entrepreneurs” —investors by profession who don’t want to work for someone else, so they choose to become entrepreneurs by starting companies that invest capital

In the 1940s, the Davis family patriarch had a unique insight about insurance companies. He realized that (1) the companies had hidden investment portfolios that would compound for long periods until claims were paid out, but they were disguised as unprofitable companies because of accounting rules, and (2) the market for life insurance was exploding because of World War II. He quit his job in 1947 and became a full-time investor specializing in the stocks of insurance companies. His timing proved ideal: his portfolio ballooned from $50,000 to roughly $10 million by 1959.

One key takeaway from this book is the patriarch’s insistence on writing and distributing a weekly bulletin about the insurance industry. In the early 1990s, his grandson began helping him write this newsletter. He asked why they should bother when the lack of feedback suggested that no one was reading it. The patriarch’s response? “It’s not for the readers. It’s for us. We write it for ourselves. Putting ideas on paper forces you to think things through.”

The patriarch used the weekly bulletin as a tool for reflection and learning. Distributing it to others added accountability to the process.

When I read this, I thought about a few successful founder friends with a similar habit—which I remembered because it’s rare. They’ve built companies worth hundreds of millions of dollars or more. Each sends a weekly email update to their investors and/or team. They’ve kept up with this habit for years, since their earliest days. I asked one of them why he keeps doing it. He does it for himself, he said, not the recipients. It forces him to reflect on the past seven days and plan for the next seven.

I’m a proponent of founders sending update emails. It’s a habit with superpower potential. Everyone can do it, and because few people do, it gives those who take the time for it an edge.

+ COMMENT

Subscribe to receive new posts via email.

Submitted successfully!
Oops! Something went wrong while submitting the form. Try again?