Category Archives: learning

Leaning into absent-mindedness

From time to time, I notice a spike in the number of small mistakes I make due to inattention. It’s a good sign to slow things down, rejig systems and habits, and figure out how to make things better. For example, noticing that I often lost track of small things I was carrying around, I switched to a belt bag in summer and a vest in winter.

There are still quite a few slips I haven’t figured out how to work around, like the occasional times I put the oven mitts on the opposite side of the stove from where they usually are (I must have absentmindedly thought “Aha! An empty hook!”), or the time I tucked the sesame oil into the fridge. (“I’m holding a bottle; many bottles go into the shelves on the fridge door; this probably goes into the shelves on the fridge door.”)

2015-05-28b Absent-mindedness -- index card #research #fuzzy

2015-05-28b Absent-mindedness – index card #research #fuzzy

It turns out that there are lots of forms of absent-mindedness. Cheyne, Carierre, and Smilek (2005) defined a scale for attention-related cognitive errors (ARCES) that goes like this:

  1. I have absent-mindedly placed things in unintended locations (e.g., putting milk in the pantry or sugar in the fridge).
  2. When reading I find that I have read several paragraphs without being able to recall what I read.
  3. I have misplaced frequently used objects, such as keys, pens, glasses, etc.
  4. I have found myself wearing mismatched socks or other apparel.
  5. I have gone into a room to get something, got distracted, and left without what I went there for.
  6. I fail to see what I am looking for even though I am looking right at it.
  7. I begin one task and get distracted into doing something else.
  8. I have absent-mindedly mixed up targets of my action (e.g. pouring or putting something into the wrong container).
  9. I make mistakes because I am doing one thing and thinking about another.
  10. I have gone to the fridge to get one thing (e.g., milk) and taken something else (e.g., juice).
  11. I have to go back to check whether I have done something or not (e.g., turning out lights, locking doors).
  12. I go into a room to do one thing (e.g., brush my teeth) and end up doing something else (e.g., brush my hair).

I find that I tend to be okay at broad strokes (intentions), but sometimes I miss finer details. I’ve walked out of the house in inside-out or back-to-front clothing before (technical shirts feel the same either way!), although usually W- helps me catch those situations.

It’s not that bad, though. Although I sometimes don’t remember what I walked into a room for (especially if I get distracted by a conversation part way), I can almost always recall what I intended to do, and what was before that (if I hadn’t finished that yet). It also helps to have the habit of writing down quick notes and consulting my agenda for tasks to work on, but mental rehearsal is usually enough for me to “pop the stack”.

Fortunately, all this appears to be normal human experience. I might be a smidge more absent-minded than some folks, but it doesn’t get in the way of life, and even W- forgets a mug of hot water in the microwave occasionally. Besides, I enjoy working around the limitations of my brain by taking notes and tweaking the way I live.

This is probably why I enjoy reading research into the brain. It turns out that there are many possible explanations for absent-mindedness. There are different ways to measure it, and even a few ways to play around with it.

2015-05-28c Different models of absent-mindedness -- index card #fuzzy #research

2015-05-28c Different models of absent-mindedness – index card #fuzzy #research

When I read through the research, I feel oddly optimistic. Even though I know I’m likely to get more absent-minded as I grow older, I also know that experience, mindfulness, more deliberate responses, and good habits using external-memory systems can help a lot.

2015-05-24d Accept or hack fuzziness -- index card #fuzzy

2015-05-24d Accept or hack fuzziness – index card #fuzzy

I notice that I respond to the fuzziness in my brain with curiosity instead of frustration. I like this attitude, and I hope to keep it as I go through life. Instead of getting frustrated with myself, I get a good laugh out of the little mishaps (oh hey, I’ve put the plates where the saucers usually go; I can see how that happened!), and I explore it to learn more. So a bit of both, I guess: accept the fuzziness and hack around it.

Besides, the incidents aren’t that frequent. They’re just more prominent in my memory because I pay attention to them. =)

2015-05-28e Sneak previews of life -- index card #fuzzy

2015-05-28e Sneak previews of life – index card #fuzzy

Actually, it works out really nicely that I’m thinking about this at this time. I know people around me also experience absent-mindedness, so I don’t have to have a hypochrondiac’s worry about early-onset diseases. (Although if we get to the point where this does actually get in the way of an awesome life, I’ll be sure to ask for help.) Instead, since I keep my life relatively smooth (low stress, plenty of sleep), I have a baseline of feeling good. That lets me notice changes more clearly, instead of the changes getting obscured in the noise of perpetual sleep deprivation or constant background stress. It also means that I can think of fuzzy-brain moments as temporary, local, and impersonal, and I can use my non-fuzzy times to figure out how to make the fuzzy times even better.

What are some things that could make absent-minded moments better?

2015-05-28d Imagining adaptations for absent-mindedness -- index card #fuzzy

2015-05-28d Imagining adaptations for absent-mindedness – index card #fuzzy

I might need to wait for better technology for some of these ideas, but most of the ideas are ready to go. Putting things in the wrong places is a minor inconvenience, and safety hasn’t been a big issue for me yet. I’ll probably focus on fuzzy memory and observation, looking for ways to take notes on or automate the things I do. For example, I’ve added notes on how to find and deploy code to the TODO lists for my personal projects, since I might go a few months without thinking about them. Notes also help with checking and monitoring. As I gain more experience and develop those systems and habits, that will help with brain fog as well. I trust my lists to help me with task disruption, and I keep lots of buffers in my life to soften the impact of forgetting. It’s a fascinating balance between taking things slowly and keeping things interesting enough so that my brain doesn’t go into too much of an automatic mode.

It’s odd how taking this kind of perspective changes how I experience forgetfulness. Instead of thinking to myself, “Where did I put those keys? I suck!”, I find myself thinking, “Oh look! I wonder what I’ll learn from this one…” We’ll see!

Mapping knowledge

I chatted with someone about maps and personal knowledge management, so I thought I’d write an extended reflection.

2015-05-13e Mapping knowledge for yourself and others -- index card #mapping #pkm #sharing

2015-05-13e Mapping knowledge for yourself and others – index card #mapping #pkm #sharing

Mapping is useful for myself and for others. For managing my own learning:

  • Scope: What’s included, and what’s not? How does this relate to other things I’ve learned or I’m learning?
  • Landmarks and destinations: Role models, motivation, tracking progress…
  • Main path, detours: How do you get from A to B? Are there interesting places in the neighbourhood?
  • Here there be dragons, places under construction: Managing appropriate difficulty; tracking areas to explore or revisit

When helping other people learn, mapping lets me:

  • Define scope: Define a manageable chunk, and link to related maps: zooming in, zooming out, going to other places
  • Provide landmarks
  • Main path, detours: Organize a reasonable path (particularly based on someone’s interests) and nice detours
  • Here there be dragons / construction: Warn newbies, encourage intermediate/advanced exploration

So here’s my current workflow:

2015-05-13f Mapping what I know -- index card #workflow #blogging #index-cards #mapping #pkm

2015-05-13f Mapping what I know – index card #workflow #blogging #index-cards #mapping #pkm

2015-05-08c Managing my structured information -- index card #pkm #knowledge #sharing

2015-05-08c Managing my structured information – index card #pkm #knowledge #sharing

Using index cards, outlines, and chunks seems to be working well for me in terms of current thinking, although I haven’t been turning my attention to organizing, fleshing out knowledge, and filling in gaps.

Here are some notes from 2013 on mapping forwards (plans) and backwards (guides for other people). I’ve figured out ways around some of the challenges I encountered before:

  • Rough categorization of blog posts: I’ve written some Emacs Lisp code to help me update my blog post index monthly.
  • Hundreds of sketches with few links: Now I have more than a thousand sketches! But that’s okay, I have metadata in the filename, integration in my outline, and eventual chunking into blog posts.
  • Duplicate metadata entry, no synchronization: Tags in the filename and a NodeJS script that sets the same tags on Flickr upload, yay
  • No clear picture of follow-up questions, ideas, or actions: Outline still needs work; maybe also a quick way to review open sketches?
  • No clear role models: Found historical and contemporary ones, yay!

Mostly I’ve been focusing on little explorations rather than map-making. It’s like collecting nature specimens so that I can start to classify them, since you don’t see that order until later. Sometimes I look back and retrace my path. That’s when I can try to figure out where things are and how people might go a little faster or in a better order. Other times, when I’m looking forward, I’m trying to see what’s close by and how to get there. I remind myself of the landmarks in the distance, too, and what progress might look like. But I can only walk the routes until I reach a height that lets me review the paths ahead, so sometimes it’s just the accumulation of steps…

2015-05-12d What do I want to get from my blog archive, looking back twenty years from now -- index card #blogging #pkm #archive

2015-05-12d What do I want to get from my blog archive, looking back twenty years from now – index card #blogging #pkm #archive

2015-05-12e What do I want from my archive of index cards -- index card #pkm #archive #drawing #index-cards

2015-05-12e What do I want from my archive of index cards – index card #pkm #archive #drawing #index-cards

The balance between doing and improving – evaluating yak-shaving

A reader wrote:

… I came to realize that many Emacs users seem to spend a great deal of time learning about Emacs, tweaking it, and writing new extensions, rather than getting non-Emacs-related work done. Sometimes it feels as though heavy Emacs users actually get less done overall, if you consider only non-Emacs-related tasks. My question is, is it possible to get work done in Emacs, without most of that work being Emacs-related?

It got me thinking about skills or tools that can be used to improve themselves, and the balance between using and improving tools.

2015-03-15c Skills or tools that can be used to improve themselves -- index card #learning #bootstrapping

2015-03-15c Skills or tools that can be used to improve themselves – index card #learning #bootstrapping

Not all skills or tools can be used to improve themselves. I’m learning how to sew, but that doesn’t lead to making my sewing machine better (aside from fiddling with the dials).

Here are some skills that can be used reflexively:

  • Philosophy asks questions about good questions to ask
  • Learning about learning helps you learn more effectively
  • Woodworkers and machinists have a tradition of making their own tools
  • 3D printers can print parts for their own models
  • You can program tools to help you program better: testing, version control, project management, etc.

Although making your own tools takes time, here are some advantages of doing so instead of buying them off the shelf:

  • You understand the internals better, and you can appreciate the subtleties
  • You can customize it to fit the way you work
  • You can create different variants for greater flexibility. Mass customization can’t anticipate or cost-effectively provide all the different types of things people may want.
  • As your skills and needs increase, you can create better and better tools for yourself.

Many programmers spend time deliberately improving their toolkits; if they don’t, they stagnate. At the basic level, people try programs or frameworks that other people have created. The next level might be scripting things to work together. A third level might be writing customizations or extensions, and a fourth level might be creating entirely new tools or frameworks. Beginner programmers might start at the first level of reusing other people’s code, but wizardly performance often involves a mix of the other levels.

So the question is: How can we balance doing things and improving things?

No one can answer this for you.

Me, I tend to avoid hard deadlines and I do things faster than people expect them to be done, so I have plenty of leeway to improve my tools – which helps me be even more effective, so it’s a virtuous cycle.

You’ll need to find your own balance. You might get urgent stuff out of the way first, and then figure out how to balance smaller requests with investing in capabilities.

Here’s something I put together to help you figure out where you might be in terms of balance. Alternatively, if you’re thinking about whether to pick up a skill or tool that can be used to improve itself, you can use this to evaluate what you read from people sharing their experiences with the tool. Can they find a good balance for themselves, or are they frustrated by the challenges of getting something to work?

2015-03-16a The balance between using and improving tools -- index card #learning #bootstrapping

2015-03-16a The balance between using and improving tools – index card #learning #bootstrapping

  • “I have what I need in order to work.” This is the basic scenario. People focus on doing things instead of improving things.
  • I can keep pushing, but performance is dropping, so I should invest time in maintenance.” It’s like the way a knife or a saw dulls over time. When you notice diminishing returns, it might be good to invest some time in maintenance. It’s not an urgent need, but it can pay off.
  • I’d better take care of this now before it becomes a problem.” This is like maintaining a car or taking care of your health. A little time now can avoid big problems later.
  • Grr, it’s broken. I have to fix it before I can work.” If you let things go for too long, or if you’re working with something finicky, you’ll be forced into maintenance mode. For example, some 3D printers require a lot of fiddling. Watch out for this scenario.
  • It’s fine the way it is, but I know I can make it better.” The way you’re currently doing things is okay, but you know (from your experience or from what you’ve read of other people) that you can invest a little time to work more effectively. You might even know the return on investment. It’s easy to decide whether you should just go ahead with the status quo or invest the time in improving.
  • It’s fine the way it is, but I think I can make it better.” The way you’re currently doing things is okay, but you have some ideas that might make it even better. If you think those ideas might be worth it, it might be good to give yourself a time limit for exploring those ideas so that you don’t get distracted. Alternatively, you can save it for a slower time.
  • I’m waiting or stuck, so I might as well work on tools.” Maybe you’re waiting for feedback from someone else. Maybe you’re waiting for programs to compile or tests to pass. Why not spend a little time exploring how to make your tools a little better?
  • I’m doing this for fun/learning.” Tool improvement can become more enjoyable than some of the other ways you used to like spending time. For example, you might find yourself wanting to watch a screencast or try out a tweak instead of watching TV or browsing random sites on the Internet. You don’t have to completely replace other activities, you just have to shift a little time from things that have less value to you.
  • I can’t write about my actual work, but I can write about this.” If you’re wondering about yak-shaving propensity based on the blog posts you’re reading, consider: do people write about their improvements instead of the work that they’re doing because their work is confidential or hard to explain? Maybe they think blog posts about improvements are more interesting. Maybe they’re writing about improvements in the process of figuring things out (which in an excellent process, by the way). All these things can skew your perception of how much time people spend doing things versus improving things, and how much they accomplish within that time.

In terms of Emacs, these things mostly apply to me:

  • “I’m doing this for fun/learning” – Emacs tickles my brain, and the community is wonderful.
  • “I can’t write about my actual work, but I can write about this” – I suppose I could write more about the other stuff I’m interested in (sewing? cooking?), so there’s that. However, the consulting stuff is covered by agreements, and that’s a small fraction of my life anyway.

I assume other geeks are rational, especially if they have a lot of experience with it and other tools. Therefore, if people spend time tweaking (while avoiding the consequences of low performance), I assume it’s because they see the value of doing so (whether the pay-off is certain or not). On the surface, an effective person’s behaviour might resemble an ineffective person’s behaviour – six hours sharpening the saw for two hours of work, or six hours procrastinating and two hours of cramming? But if you look at:

  • if they get stuff done
  • whether other people are happy with their performance, or if they generally appear successful in their endeavours
  • how happy they are about the process

then you can get a better idea of whether it’s working for them.

As you think about your own balance or read other people’s blogs, can you identify what scenarios you and other people might resonate with? Am I missing any that I should add to the list? Please comment below!

The imperfect fungibility of time: thinking about how to use money to accelerate learning

2015-01-30 Leaving money on the table -- index card #consulting #experiment #balance

2015-01-30 Leaving money on the table – index card #consulting #experiment #balance

Any time I want to, I could spend more time consulting. This would make my clients happy. It would help me create much more value, and they would get more value from me than from other ways they could spend their budget. I would improve my skills along the way, especially with people’s requests and feedback. And to top it all off, I would earn more money that I could add to my savings, exchange for other people’s time or talents, or use to improve our quality of life.

How hard is it to resist the temptation to work on other people’s things? It’s like trying to focus on cooking lentils when there’s a pan of fudge brownies right there, just waiting to for a bite. It’s like wandering through the woods in hope of coming across something interesting when you know you can go back to the road and the road will take you to an enormous library. It’s like trying to build something out of sand when there’s a nifty LEGO Technic kit you can build instead. It’s probably like Odysseus sailing past Sirens, if the Sirens sang, “We need you! You can help us! Plus you can totally kit out your ship and your crew with the treasures we’ll give you and the experience you’ll gain!”

Maybe I can use this temptation’s strength against it.

2015-02-02 What if I use the lure of work to help me grow -- index card #consulting #experiment

2015-02-02 What if I use the lure of work to help me grow – index card #consulting #experiment

Maybe I can treat client work (with its attendant rewards and recognition) as a carrot that I can have if I make good progress on my personal projects. If I hit the ground running in the morning, then I can work on client stuff in the afternoon. A two-hour span is probably a good-sized chunk of time for programming or reporting. It’s not as efficient as a four-hour chunk, but it’ll force me to keep good notes, and I know I can get a fair bit done in that time anyway.

The other part of this is making sure that I don’t give myself too-low targets so that I can get to client work. It’ll be tempting to pick a small task, do it, and say, “There, I’m done. Moving on!” But I have to sit with uncertainty and figure things out. I expect that learning to work on my own things will mean encountering and dealing with inner Resistance. I expect that my anxious side will whisper its self-doubt. So I lash myself to the mast and sail past the Sirens, heading towards (if I’m lucky!) years of wandering.

Part of this is the realization that even after my experiments with delegation, I’m still not good at converting money back into time, learning, ability, or enjoyment. Time is not really fungible, or at least I haven’t figured out how to convert it efficiently. I can convert time to money through work, but I find it difficult to convert money back to time (through delegation) or use it to accelerate learning.

2015-01-07 What am I happy to pay for in money or time -- index card

2015-01-07 What am I happy to pay for in money or time – index card

Extra money tends to go into projects, tools or cooking experiments. Gardening is one of my luxuries: a few bags of dirt, some seeds and starters, and an excuse to be outside regularly. Paying someone to do the first draft of a transcript gets around my impatience with listening to my own voice. Aside from these regular decisions, I tend to think carefully about what I spend on. Often a low-cost way of doing something also helps me learn a lot – sometimes much more than throwing money at the problem would.

2015-01-27 Financial goals -- index card #finance

2015-01-27 Financial goals – index card #finance

But there are things that money can buy, and it’s good for me to learn how to make better decisions about that. For example, a big savings goal might be “buying” more of W-‘s time, saving up in case he wants to experiment with a more self-directed life as well. House maintenance projects need tools, materials, and sometimes skilled help. Cooking benefits from experimentation, better ingredients, and maybe even instruction.

2015-02-01 Accelerating my learning -- index card #learning #accelerating

2015-02-01 Accelerating my learning – index card #learning #accelerating

What about accelerating my learning so that I can share even more useful stuff? Working with other people can help me:

  • take advantage of external perspectives (great for editing)
  • organize my learning path into a more effective sequence
  • learn about adjacent possibilities and low-hanging fruit
  • bridge gaps
  • improve through feedback
  • create scaffolds/structures and feed motivation
  • set up and observe deliberate practice
  • direct my awareness to what’s important

In order to make the most of this, I need to get better at:

  • identifying what I want to learn
  • identifying who I can learn from
  • approaching them and setting up a relationship
  • experimenting
  • following up

How have I invested money into learning, and what have the results been like?

Tools? Yup, totally worth it, even for the tools I didn’t end up using much of (ex: ArtRage). Do more of this. How can I get better at:

  • keeping an eye out for potentially useful tools:
    • Emacs packages
    • AutoHotkey scripts/ideas
    • Windows/Linux tools related to writing, drawing, coding
  • evaluating whether a tool can fit my workflow
  • supporting people who make good tools
    • expressing appreciation
    • contributing code
    • writing about tools
    • sending money

Books? Some books have been very useful. On the other hand, the library has tons of books, so I have an infinite backlog of free resources. Buying and sketchnoting new books (or going to author events) is good for connecting with authors and readers about the book du jour, but on the other hand, I also get a lot of value from focusing on classics that I want to remember.

Conferences? Mostly interesting for meeting people and bumping into them online through the years. Best if I go as a speaker (makes conversations much easier and reduces costs) and/or as a sketchnoter (long-term value creation). It would be even awesomer if I could combine this with in-person intensive learning, like a hackathon or a good workshop…

Courses? Meh. Not really impressed by the online courses I’ve taken so far, but then again, I don’t think I’m approaching them with the right mindset either.

Things I will carve out opportunity-fund space for so that I can try more of them:

Pairing/coaching/tutoring? Tempting, especially in terms of Emacs, Node/Javascript, Rails, or Japanese. For example, some goals might be:

  • Learn how to improve Emacs Lisp performance and reliability: profiling, code patterns, tests, etc.
  • Define and adopt better Emacs habits
    • Writing
    • Organization
    • Planning
    • Programming
  • Write more elegant and testable Javascript
  • Set up best-practices Javascript/CSS/HTML/Rails environment in Emacs
  • Learn how to take advantage of new features in WordPress
  • Write more other-directed posts
  • Get better at defining what I want to learn and reaching out to people

Actually, in general, how does one accelerate learning?

  • General learning techniques: spaced repetition, skill breakdowns, deliberate practice…
  • Structure and motivation: personal trainers, courses
  • Instruction and perspective: expert, peer, or external
  • Higher-quality resources: original research, well-written/organized resources, richer media, good level of detail, experience/authority
  • Better tools: things are often much easier and more fun
  • Experimentation: learning from experience, possibly coming up with new observations
  • Feedback, analysis: experience, thoroughness
  • Immersion: languages, retreats
  • Outsourcing: research, summaries, scale, skills, effort
  • Relationships: serendipity, connection, conversation, mentoring, sponsorship
  • Community: premium courses or membership sites often offer this as a benefit
  • Freedom: safety net that permits experimentation, time to focus on it instead of worrying about bills, etc.

Hmm. I have some experience in investing in better tools, higher-quality resources, experimentation, feedback/analysis, delegation, and freedom. I’d like to get better at that and at investing in relationships and outsourcing. Come to think of it, that might be more useful than focusing on learning from coaching/instruction, at least for now.

Let me imagine what using money to accelerate learning would be like:

  • Relationships
    • Get to know individuals faster and deeper
      • Free: Build org-contacts profiles of people who are part of my tribe (people who comment/link/interact); think about them on a regular basis
      • Free: Proactively reach out and explore shared interests/curiosities
      • $: Figure out digital equivalent of treating people to lunch or coffee: conversation + maybe investing time into creating a good resource for them and other people + sending cash, donating to charity, or (best) cultivating reciprocal learning
      • $: Sign up for a CRM that understands Gmail, Twitter, and maybe even Disqus
    • Identify things to learn about and reach out to people who are good role models for those skills
      • Free: Be specific about things I want to learn
      • Free: Find people who know how to do those things (maybe delegate research)
      • $: Possibly buy their resources, apply their advice
      • $: Reach out with results and questions, maybe an offer to donate to their favourite charity
    • Help the community (like Emacs evil plans; rising tide lifts all boats)
      • $: Invest time and money into creating good resources
      • Be approachable
      • $: Bring the community together. Invest in platforms/organization. For example, I can use whatever I would have spent on airfare to create a decent virtual conference experience, or figure out the etiquette of having an assistant set up and manage Emacs Hangouts/Chats.
  • Outsourcing
    • Identify things that I want to do, regardless of skills
    • $: Experiment with outsourcing parts that I don’t know how to do yet (or even the ones I can do but want external perspectives on)
    • Use the results to determine what I actually want and what to learn more about; iterate as needed

Huh, that’s interesting. When I start thinking about investing in learning, I tend to fixate on finding a coach because I feel a big gap around directly asking people for help. But I can invest in other ways that might be easier or more effective to start with. Hmm… Thoughts?

How can I make better use of my index card drawing process?

I really like this practice of working with index cards, especially now that I’ve sorted out a sweet digital workflow for them.

2015-02-10 Evolution of my index card workflow -- index card #drawing #workflow

2015-02-10 Evolution of my index card workflow – index card #drawing #workflow

I started with a straightforward workflow:

  1. Think of a question.
  2. Draw it on a paper index card.
  3. After I complete 5+ index cards, scan the cards.
  4. Convert and process the cards (colouring, etc.).
  5. Rename the cards.
  6. Upload the cards.
  7. Add them to my Flickr set (and to blog posts and so on).

I replaced my Flickr uploading process with a script. Then I replaced the paper index cards with digital index cards. I wrote another script to make renaming files easier. Then I built an outline of questions and used that to create index card templates. So now my workflow looks like this:

  1. I use Org Mode in Emacs to collect and organize questions. I use TODO states to track ones that need further research, ones that are ready to be drawn, and ones that are ready to be blogged.
  2. When I switch to tablet mode, I can select questions to draw using a custom pen-friendly Emacs interface that sets up the template for me.
  3. I upload the images using another script and add the links to my outline.

After I draft the blog post, I use another bit of code to move the relevant images out of my “To blog” directory and into another directory so that I can easily upload them (since I still haven’t tweaked the all-Emacs way of doing things the way I want them).

An index card is a good size for a chunk. It’s smaller than a blog post, so I can accelerate my learn-do-share-review cycle. If I invest more time into creating, organizing, and sharing them, I think they’ll pay off well. Other people report that their Zettelkasten (index card organization systems) become almost like conversational partners and collaborators. I already feel that way about my blog archive, and it will probably be even more

Hmm… Should I add a unique identifier to sketches so that I can refer to them more concisely than giving the full link? This mostly matters for referring to sketches in the drawing itself, since I can use links in text or metadata. For example, I can assign codes to each chunk, possibly differentiating between sketches (letters?) and blog posts (numbers?). So, maybe “2015-01-01a” for the first sketch on January 1, and “2015-01-01-1” for the first blog post? I could omit the dashes, but then searching requires that mental translation, so we’ll keep the dashes in there. The downside is that there’ll be a little additional clutter, but it might be interesting to experiment with – adding a reference line, and maybe even adding the info to the filename. It gives some linking capability that can survive the disparate systems I publish sketches to (my blog, Evernote, Flickr), even for sketches that don’t get turned into blog posts.

What about my 5-cards-a-day target?

2015-02-08 Reflection on 5 index cards a day target -- index card #drawing #reflection

2015-02-08 Reflection on 5 index cards a day target – index card #drawing #reflection

Sometimes making five cards feels like a stretch, since I have to Think Interesting Thoughts. Using templates can help – I could make four cards and a journal entry, for example. I expect the awkwardness will subside as I build up my question store and do more research/experimentation.

Colour slows me down if I think about it too much or worry about becoming too repetitive. It might be fine to just quickly highlight things most of the time and save the development of colour sense for sessions of deliberate practice.

2015-02-09 How can I make better use of my index card drawing process -- index card #drawing #index-cards #zettelkasten

2015-02-09 How can I make better use of my index card drawing process – index card #drawing #index-cards #zettelkasten

In terms of thinking, spending the extra few minutes to think about and capture the next questions or actions for a card can make a big difference in my focus. I can also relax my chunking guidelines so that a single sketch can be fleshed out into a quick blog post instead of waiting until I accumulate several sketches related to the topic – taking my own advice to schedule Minimum Viable Posts. If I phrase my outline in terms of questions instead of keywords, I’ll probably find that more motivating and easier to scope.

2015-02-09 How can I make better use of my laptop -- index card #tech

2015-02-09 How can I make better use of my laptop – index card #tech

That will probably also help me with some of the bottlenecks I identified while contemplating how I can make better use of my laptop. I’m doing okay at generating questions and drawing index cards, but I can do better at translating those ideas into research, experiments, and blog posts. So, I can clear out more of my backlog of index cards that I want to share (probably ending up with two months of scheduled blog posts, or maybe even more!). Then I can research and try out more ideas, so I’m not just drawing questions that I can answer with what’s currently in my head. =)

Onward!

Sketched Book – The Checklist Manifesto: How to Get Things Right – Atul Gawande

Atul Gawande’s The Checklist Manifesto: How to Get Things Right (2009) emphasizes the power of checklists for improving reliability. Errors creep in when we forget things entirely or skip over things we should have done. In medicine, these errors can be fatal.

Gawande draws on his experience as a surgeon, the research he conducted with the World Health Organization, and insights from construction, finance, and other industries that take advantage of checklists to improve processes.

The book discusses ways to address the cultural resistance you might encounter when introducing a checklist. It recommends making sure that checklists are precise, efficient, short, easy to use, and practical. You need to develop a culture of teamwork where people feel that they can speak up as part of a team. You may even need to modify supporting systems to make the checklist doable.

I’ve sketched the key points of the book below to make it easier to remember and share. Click on the image for a larger version that you can print if you want.

2014-12-31 Sketched Book - The Checklist Manifesto - How to Get Things Right - Atul Gawande

I like the reminders that you should design your checklists around logical “pause points,” keep checklists focused on the essentials, and treat people as smart instead of making the checklist too rigid.

The book distinguishes between “Do-Confirm” checklists, which allow experienced people to work quickly and flexibly with a confirmation step that catches errors, and “Read-Do” checklists, which walk people step-by-step through what they need to do. I’m looking forward to applying the book’s tips towards systematizing my sharing. For example, I’m working on a YASnippets in Emacs that will not only display a “Read-Do” checklist for doing these sketched notes, but will also assemble the links and code to do the steps easily. Sure, no one will die if I miss a step, but I think discipline and thoroughness might yield dividends. I also want to develop a good “Do-Confirm” process for writing and committing code; that could probably save me from quite a few embarrassing mistakes.

I’m interested in the diffusion of ideas, so I was fascinated by the book’s coverage of the eight-hospital checklist experiment the WHO conducted. The book discussed the challenges of getting other people to adopt checklists, and adapting the checklists to local conditions. Here’s an excerpt:

… By the end, 80 percent reported that the checklist was easy to use, did not take a long time to complete, and had improved the safety of care. And 78 percent actually observed the checklist to have prevented an error in the operating room.

Nonetheless, some skepticism persisted. After all, 20 percent did not find it easy to use, thought it took too long, and felt it had not improved the safety of care.

Then we asked the staff one more qusetion. “If you were having an operation,” we asked, “would you want the checklist to be used?”

A full 93 percent said yes.

There’s a comparison to be made between the reluctance of doctors to accept checklists and the committed use of checklists by pilots and builders. I came across a quote from Lewis Schiff’s Business Brilliant in this comment by Rich Wellman:

The following quote sums up the essential difference between a checklist for a doctor and a checklist for a pilot.

“How can I put this delicately? Pilots are seated in the same planes as their passengers. Surgeons are not under the same knives as their patients. To paraphrase an old joke, surgeons may be interested in safety, but pilots are committed.”

So checklists are a good idea when you’re dealing with people’s lives, but what about the rest of us? Checklists are good for catching errors and building skills. They’re also great for reducing stress and distraction, because you know that the checklist is there to help you think. That’s why packing lists are useful when you travel.

Already a fan of checklists? Tell me what you have checklists for

Want the book? You can buy it from Amazon (affiliate link).

Like this sketch? Check out sketchedbooks.com for more. Feel free to share – it’s under the Creative Commons Attribution License, like the rest of my blog. Enjoy!

Somewhat related: