Skip to main content

Beginning Sketchnoting


In September 2017 I attended Ian Johnson's visual note-taking workshop at DDD East Anglia. For the rest of the day I made sketchnotes, including during Karo Stoltzenburg's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis.

Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said.

Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves.

I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evolved for different situations: how are they similar? why aren't they more similar? what could I change to give me more benefit from them?

In mid-2017, I'd analysed some of my notes from talks I'd attended and pulled out common characteristics like these: whole sentences or at least phrases; quotation marks around actual quotes; questions annotated; stars, boxes, circles for emphasis; arrows to link thoughts; structure diagrams; occasional mind maps; plenty of doodles.


Predominantly though, I knew that I was writing a lot and I wondered whether I might be missing interesting content because I was spending time writing, and whether I might be taking down material I didn't need to. I was aware of sketchnotes but I didn't really know much about how they were created. I did know that the examples I'd seen tended to be pretty, perhaps discouragingly so.

Tanmay Vora
Yikes! I doubted that I could get to that standard even with lots of concentration, patience, and spare paper let alone live in real time while listening to a talk. But did I have to? I mean, what are sketchnotes anyway?

Sketchnote Army says this:
  • Sketchnotes are purposeful doodling while listening to something interesting. 
  • Sketchnotes are as much a method of note taking as they are a form of creative expression.

I find that interesting, but I think I started with a very different slant on them:
  • Sketchnotes are a way of forcing me to listen and note-take differently.

The basics that I got at DDD East Anglia helped with that. Ian Johnson has blogged in detail about them so I'll just summarise what I took from him:
  • Use a consistent layout.
  • Practice neat writing.
  • Learn to draw a handful of common icons, e.g. book, tick, cross, etc.
  • People add emotional impact ... and stick people are easier to draw than you think.
  • Fill in decoration during the "boring bits".

I'd add a few more things, based on my own experience over the last few months:
  • Landscape not portrait: I find this so much more natural.
  • Any paper and pen will do: don't fetishise the materials, just draw!
  • Date, title, person at the top: usually top-right; consistency helps with later reviewing.
  • Start drawing in the middle of the page ...with the key concept.
  • Work around the page from top right, clockwise: perhaps even mentally divide the page into quadrants and use a quarter of the talk time per quadrant
  • Do it in one pass, in the moment: important for me; these pictures are my notes. I'm not going back to make them pretty afterwards.

Here's a few examples, in rough time order:












I think there's an evolution in style here, mostly in terms of trying to get less down on the page in less busy ways. Some other reflections:
  • I wait longer before writing something down.
  • I look for groups of points.
  • If I don’t get the structure right my notes go wrong.
  • If the talk is short I am more likely to end up with rubbish.
  • I can’t use sketchnotes for meetings, 1-1, etc.
  • I am more motivated/find it easier to review a sketchnote than notes.
  • I don't yet know whether I generally preserve enough information in sketchnotes.

If you're thinking of starting I'd offer these pieces of advice, again based on my own experience and needs:
  • Don’t worry if you can’t draw much very well.
  • Get over the feeling of self-consciousness ... by doing it more!
  • Don’t worry if you end up with words not pictures.
  • Practice. For me, if you want to do something, do it as much as you can so that you
  • ... learn how to do it
  • ... learn when it applies
  • ... learn when it doesn’t apply
  • I use internal events like our user conferences, Team Eating, and even staff meetings as practice opportunities.
  • Don’t worry when your notes turn out bad: THEY WILL TURN OUT BAD.

I've been trying this out for just under a year and I still regard myself as an absolute beginner. Will you join me?
Title image: Ebay

Comments

  1. Thanks, again, James, for this post. I am going to give it a try. I also shared them with my two boys (age 14 and soon to be 11). They are both sketchers so I am hoping that they will take a liking to this and help stay focus during these long, long hours on the computer for school.

    ReplyDelete
  2. A challenge for me is to start at the right place. Starting in the middle of the page is often not the right thing to do when a talk is more of a journey than a top down discussion. Some talks are bits of techniques that go in the tool box. Enjoying trying this.

    ReplyDelete
    Replies
    1. Yep. I practiced through January this year with a bunch of different talks and found I wanted to start in the middle less often than I used to: Top Draw.

      Delete

Post a Comment

Popular posts from this blog

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested in your working context and the way

Meet Me Halfway?

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answer would be almost meaningless and certa

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito

Testing (AI) is Testing

Last November I gave a talk, Random Exploration of a Chatbot API , at the BCS Testing, Diversity, AI Conference .  It was a nice surprise afterwards to be offered a book from their catalogue and I chose Artificial Intelligence and Software Testing by Rex Black, James Davenport, Joanna Olszewska, Jeremias RĆ¶ĆŸler, Adam Leon Smith, and Jonathon Wright.  This week, on a couple of train journeys around East Anglia, I read it and made sketchnotes. As someone not deeply into this field, but who has been experimenting with AI as a testing tool at work, I found the landscape view provided by the book interesting, particularly the lists: of challenges in testing AI, of approaches to testing AI, and of quality aspects to consider when evaluating AI.  Despite the hype around the area right now there's much that any competent tester will be familiar with, and skills that translate directly. Where there's likely to be novelty is in the technology, and the technical domain, and the effect of

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro

Testers are Gate-Crashers

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w

Build Quality

  The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

The Association for Software Testing is crowd-sourcing a book,  Navigating the World as a Context-Driven Tester , which aims to provide  responses to common questions and statements about testing from a  context-driven perspective . It's being edited by  Lee Hawkins  who is  posing questions on  Twitter ,   LinkedIn , Mastodon , Slack , and the AST  mailing list  and then collating the replies, focusing on practice over theory. I've decided to  contribute  by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me?   --00-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll