A reading workflow based on Leveen's "Little Guide"

The best of a book is not the thought which it contains, but the thought which it suggests. -- Oliver Wendell Holmes

Many of my subscribers are active readers and book lovers. My post How to read a lot of books in a short time is my most popular, and I've even had the pleasure of receiving surprise copies in the mail! Along those lines, Steve Leveen's book The Little Guide to Your Well-Read Life is a great meta book, and one of those "I have to give copies to friends" works that leaves a lasting impact.

There's a lot to the diminutive tome, but here I'd like to share his suggested workfow, an example of a specialized system [1] (unlike Getting Things Done, which is a general one).

Overall Flow

Here's the staging Leveen recommends (a "shelf flow," if you will [2]). The basic idea is repeated reviews over time (including during reading and after) help strengthen recall. (Note: "*" indicates my additions.)

1. Pre-candidates list* (desired books, i.e., your wish list)
   
2. Candidates library (acquired books - a Someday/Maybe list)
   
3. Currently reading stack
   • Castaways*
4. Après reading 1 shelf
   
5. Après reading 2 shelf
   
6. Après reading 3 shelf
   
7. Living library

Briefly, you have three concurrent phases happening: Collecting (managing your pre-candidates list, and buying from it - steps 1 & 2 above), Reading ("activating" one or more of your candidates - step 3), and Reviewing (steps 4-6). Finally, you continue to return to your living library over time, re-reading favorites, or using it for reference or inspiration (step 7). Of course if the book doesn't pass the 50 page test (see ), it gets rejected as a castaway [3].

In addition to these phases, Leveen suggests keeping a reader's journal or annotated bookography [4], which I've generalized to include tracking your candidates (including who recommended each one (and why), the books you've read (just the ones you're really glad you read), and your notes from them. (He recommends writing in the book itself, but I prefer a voice-dictation-to-electronic-storage model. I use a simple text file, but a wiki or something like stikkit would work as well.)


I think most stages are straightforward, but let's look a bit more carefully at reading (step 3) and the Après reading shelves.

Reading

Leveen has us approach reading with two things in mind. First, read actively: Ask questions of yourself and the author. Engage in a dialog by asking:

• Why am I going to read now?
  
• What do I want to get out of it?

(For more see the SQ3R method - Survey, Question, Read, Recite, Review. I like the Mind Tools summary.)

Second, he has us read the book at a high level (skimming), and gradually come in closer, i.e., starting with superficial reading then zooming into analytical reading.

The stages:

1. First tour: In this cursory inventory you preview the book by asking questions about the author, her background, the index, table of contents, and bibliography. Spend a few minutes looking at the overall book and thinking about what that means - what you know about the subject, what you expect to learn. This stage should only take a few minutes.
   
2. Second tour: Read the front and back matter, think about intended audience, scan the major index headings, and look at reprint/revise info.
   
3. Third tour: Read a few introductory and concluding paragraphs from each chapter, where Leveen says most writers sum up their major points. This allows you to create a customized outline in your head, and to better target where the book's meaning lies for you (often the real meat of the book is somewhere in the center).
   
4. Finally: Fully read the book. This may be the entire work, or just the parts that looked useful to you from previous scans. Importantly, don't be afraid to give up on the book. Leveen reminds us there are so many other great books awaiting, so why spend time on ones that don't speak to us?

Note: You should pause between each stage to reflect on what you learned, and to sharpen your focus/questions. Note-taking is highly recommended.

Après Reading Shelves

I'd not seen the term après before (my education's been very technical up to this point), but basically it means stages of review after you've read a book. Leveen says this is important - it's where we cement our understanding and make the ideas relevant (and applied) to our lives. He recommends three shelves:

1. This shelf holds books that you've just finished reading and awaiting your first review. Note: They should only sit there a few days before you review them.
   
2. The second shelf is for second-round reviews (they should sit maybe a week or so).
   
3. The third shelf is for six-month or later reviews.

After these stages, your books go into your living library.

My Status and Comments

Right now I have:

• Pre-candidates: about 500 (they're here, FYI).
  
• Candidates: about 80.
  
• Après: haven't set it up yet!
  
• Living library: about 50.

Applying Leveen's workflow takes discipline, as does keeping up with reading. In my case, I read while exercising in the morning, which gives me a guaranteed 1/2 hour a day on either books or articles. However, my flow is slowed down when it comes time to notes processing. And I've not tried the review at all, except when (like here) I blog about a book, or include ideas from it in related posts.

I'll wrap up with this wonderful notion from Leveen: "Instead set out to always being able to answer yes to the following simple question: Are you reading something great right now?)"

So how do you manage your reading workflow? Do you use Leveen's ideas? Any tips or tricks you'd like to share?

References

• [1] Another typical one is financial flow - many clients already have a working system, which I do not mess with.
  
• [2] Adapted from the idea of a "folder flow," which I found in Practice your personal Kaizen over at http:Lifehacker.
  
• [3] The castaways term is from Orange Crate Art: Tools for serious readers?

Resources

• The Forum | Steve Leveen in Readerville | June 13-17, 2005
  
• In the same thread Leveen shares some permissions he gives out on a sheet to workshop participants, including permission to...:
  • ...make my own reading plan to the extent that feels right to me. (Just as you are free to have no plans, you are also free to develop lists of candidate books and better yet, a growing library of candidates.)
    
  • ...acquire books without the requirement of reading them.
    
  • ...define being well-read as a journey rather than a destination.
    
  • ...love, or not love, any book whatsoever.
    
  • ...read more than one book at a time.
    
  • ...give up on a book and abandon the "clean-your-plate" mentality.
    
  • ...debate, argue with, agree with, and write to an author.
    
  • ...write in my books.
    
  • ...listen to books, knowing that listening is just as good, and sometimes better, than silent reading with my eyes.
    
  • ...share my reading experiences with others.
    
  • ...read a classic, for the first time, much later in life.
    
  • ...improve at reading my whole life long.
    
  • ...linger in a library even if I prefer to buy books.
    
  • ...spend as much on books as I do on other great passions of my life.
    
  • ...make my own reading rules. (Seize your own well-read life as only you can and you will likely be an inspiration to others.)
• Leveen's detail on après reading is found here.
  
• Here's someone who has a short bookography on-line.
  

Report on a little experiment: Daily random entries from my personal log

I want to share the results of a little experiment I did over the last few months using my My Big-Arse Text File. I've been using this semi-structured text file to track my consulting activities for the past two years, and it contains a mixture of things like:

• consulting activities,
• networking connections [1],
• lessons learned (see Some thoughts from tracking "lessons learned" for a year),
• contact information,
• idea capture (see Pickle jars, text files, and creative idea capture),
• book notes (see How to read a lot of books in a short time),
• blog topics,
• GTD tips and holes,
• interesting news articles and reports,
• tips on blogging and writing,
• marketing and workshop ideas,
• tool tips and how-tos for clients,
• ...

Having all this information is very useful when I search for something specific, but I wondered whether it'd be helpful to get a random entry emailed to me daily. So I wrote short BASH script that sends me a random entry every night, kind of a mental "blast from the past" in my inbox. The results? After a few months of these, I have to say the results have been mixed, mostly negative.

What I liked about it: I'd occasionally get something cool I'd forgotten about, like the idea of embedding due date in names of time-sensitive projects (e.g., ending them with "DUE XX-YY"), or an equation from my self-help formuarly (e.g., Brian Tracy's success attitude formula: SA = D + D * PA + P [desire, direction, proper action, persistence]).

However, it's clear that selecting random entries isn't principled enough. What would be more useful is something that fits into a structure that's congruent with my goals/systems. Three important ones come to mind:

• book notes (so I can review the big idea, go deeper, and apply it to my life),
• lessons (so I can actually learn from them by changing behavior), and
• client/prospect contacts (so I can reconnect and be thinking of how I can help them).

(For the latter I strongly suspect I should be using a specialized tool - any recommendations?)

Final conclusion: Good idea, didn't work out, but gave me ideas for the next step.

I still pine for an integrated program that easily supports reminding like this, with structured fields (e.g., "this is a book review", "this was a client contact", etc.) yet has the flexibility to capture unstructured text, combined with the ability to link anything together, regardless of type (see Where's the IDE (Integrated Development Environment) for personal information?). I've looked at a number of them [2], but amazingly my text file plus simple macros remains a sweet spot for simplicity, portability, and power.

As always, your suggestions and comments are always welcome.


References

• [1] Two great books related to networking are Never Eat Alone and Love Is the Killer App. Additionally you might enjoy these posts on the topic:
  • A geek "gets" networking: The strange magic of connecting with others
  • A simple and useful networking gift that anyone can give for free
  • My Business Networking Advice article is up, FYI
  • Networking surprises - Some recent unexpected (but successful) outcomes
  • The most important networking question (although I'm changing my mind on that - the most important one might be "Who are you?" or "How can I help you?")
  • On the goal of meeting three new people a week - A ten week retrospective
• [2] E.g., Omea, Jot, and Dabble DB.

My Life Coaches Blog interview is up

I'm very pleased that Alvin Soon's email interview with me is up at Life Coaches Blog. The article is 10 Questions With The Productivity Expert: Matt Cornell, and I have to say Alvin asked some great questions.

Alvin and his fellow bloggers create a steady stream of very useful and deep articles on personal development, including NLP 101, Your Brain: A Guide to Fine-Tuned Performance, 9 Keys to Overcoming Difficult Times, and The Most Important Thing to Do: Stretch (he lists 13 of his favorites here).

Thanks very much, Alvin!

Five secret filing hacks from the masters

Stimulated by Frank's article Fileflag could be a good product over at What's the next action I'd like to share some simple filing tips I've picked up from clients and fellow practitioners. They're all low tech but high value hacks that many have found useful. Please share yours as well!

• The "File bookmark" hack
  
• The "Fold crease" hack
  
• The "Staple, don't clip" hack
  
• The "Unfold before you file" hack
  
• The "Magnetic bookend" hack

The "File bookmark" hack

While I'm all in favor of neat office gadgets like the File Flag, there's an even simpler solution for people who use plain (non-hanging) files. When you pull a file, simply lift up the file behind it a few inches and let the remaining files in front of that one lean back. You'll find they keep the bookmark file up above the rest until you're ready to return the pulled file. When it's time to return the pulled file to its original spot, simply drop it in front of the raised bookmark file, push the bookmark file back down, and close the drawer. Viola!

There are a few limitations, including:

• You can't shut the file drawer while the file is pulled, so this is only good for temporary uses.
  
• Sometimes the bookmark file drops down, esp. if there aren't many files in front of it, or if it's a heavy one.
  
• Sometimes you have to use the A-Z file guide itself if your file is the last in its group.

But for the most part this is an "aha" for clients.

The "Fold crease" hack

Have you ever noticed that set of horizontal creases at the bottom of most file folders? Guess what - they're amazingly useful! When you have a file that's grown to more than a dozen or so pages, it starts to bow outward, messing up your nice filing drawer. Terrible! To fix the problem, simply open the file flat on your desk, choose a crease that will give you enough extra room, fold the crease, and - bingo - neat, expanded file.

Of course if they get too big, you'll have to upgrade to expanding jackets, e.g., something like these.

The "Staple, don't clip" hack

To keep your files as thin as possible, replace paper clips with staples. For thick bundles that you don't want to staple, you might prefer the so-called "ideal clamps" (such as these) rather than paper clips.

The "Unfold before you file" hack

This one is real simple: To keep files thin and make easier future perusals, always unfold any papers before you file them. Also, take them out of the envelope if you feel the need to keep it (staple it to the pages if you like.)

The "Magnetic bookend" hack

If you're a follower of Getting Things Done (and let's face it, it's now the most-hyped productivity book on the planet), you know the reasons why I recommend against hanging files. However, converting a drawer to plain file folders often results in the dreaded "files falling down" problem for drawers that don't have a movable metal plate (AKA "follower block", "compression plate", "spring-loaded backstop", or "back plate"). Very bad. After extensive research (I kid you not), I've discovered the optimal solution (at least for metal drawers) is to use a magnetic 'L-shaped' bookend to hold them up, like this.

If this won't work for you (my last client had nice wooden drawers) you can get creative and find something to prop them up. My default is reams of paper, which can be stacked and oriented different ways to make up the space. You can also use empty boxes, etc.

My GTD Masters interview is up on Cranking Widgets

My GTD Masters interview is up on Cranking Widgets

Just a quick note that my interview with Brett Kelly over at The Cranking Widgets Blog is up. The article, GTD Masters: Interview with Matt from Matt’s Idea Blog, is part of Brett's GTD Master Series.

Thanks to Brett for the opportunity!