Skip to main content

Drawing Conclusions

You can learn a lot from your kids, and not just how much you hate High School Musical 1, 2 and friggin' 3. I play a game with my daughters (Hazel aged 5, Emma aged 3) that we call Follow the Leader, dreamed up one rainy afternoon. It's like the traditional game except that you play it on paper: one person draws something and the others have to copy along.

When the pictures are finished we line them up and see how they compare. Here's three of our efforts from one recent game. In order below, Emma was the leader, Hazel sat next to her and I was on the other side of the table (click to enlarge the images):



Emma likes to work bottom-up, incrementally building the big picture and often jumping from detail to detail without giving much, if any, indication of how they interconnect and which are the most significant. This is fine for her - she's a late-binding kind of leader - but it makes it harder for the followers to be sure they're building up the right kind of groundwork.

Initial distance between different areas of the image makes them harder to align correctly, and late correction of gross differences is generally not possible in this game. When Hazel leads she tends to prefer to work top-down and relatively symmetrically, making it much more likely that the followers will produce a reasonably accurate version of her template.

As the game goes on early differences, perhaps quite small when the page is relatively empty, lead to larger and larger differences. As and when the leader changes their mind on how the, shall we say, specification should look, any alterations they make to it are by definition correct and straightforward for them to apply. Mimicking the change in the followers' pictures can be much much harder because, despite the change being conceptually identical, the physical constraints are often different.

In the game these pictures are from, Hazel lost interest in Emma's sketching after a while and started to go her own way. She looked like she was playing but what she produced, although attractive and creative in its own right, is not a good recreation of the desired design.

Emma will often correct small omissions on other people's sheets and occasionally notice a big mistake too, but for no obvious reason she put much more effort into monitoring my drawing in this game than Hazel's and so made no attempt to stop her sister's, I don't know, implementation from diverging radically.

While she's leading, Emma will frequently say she's doing one thing and then do something else. Mostly this seems to be due to her inability to execute the stated idea rather than any kind of intent to mislead. It leaves the followers unsure whether to take the verbal instruction or that from the hard copy. The same is true in reverse and sometimes she'll be upset that, although some element of a follower's picture resembles hers reasonably well, it doesn't fit with the idea of what her picture should look like that's in her head.

The different skill levels of the participants in different areas makes a big difference too. I like to think I'm better at drawing than my daughters are - for now at least - so I'm probably best at reproducing what they've put down. But they're unconstrained by convention and so have much greater proclivity for doing something I'd probably never do, like cover a whole page in scribble.

I'm more likely to create a picture that's quite representational as a kind of gently pedagogical exercise. This exposes skill level differences too. Where the original is recognisable as a thing, it's much more obvious to all concerned that the reproductions are further away from the thing than if followers are working from something abstract.

When sitting on the other side of the table from the leader, the followers have a physically opposed view what's going on. There's an additional load on them in trying to put themselves in the place of the leader, to try to understand how they're seeing it. But that takes more effort and frequently the follower will draw what they think looks best from their own standpoint instead. Typically the leader doesn't think to hold their version up the right way for everyone to see from time to time.

Common outcomes of this game include:
  • Shapes are right but size is wrong. 
  • Overall size is right but proportions are wrong. 
  • Shapes and sizes are correct but relative positions are wrong. 
  • Big picture is correct but detail is wrong.
  • Aspects are correct but don't hang together well.
  • The "spirit" is right but there are some significant divergences.
  • Arguments about which shade of  blue should be used
  • Associated arguments about how to share the two dark blue felts between three people.
And some observations on the degree to which reproductions are faithful to the original design:
  • Relatively small initial differences magnify up into a large final differences if not checked.
  • If all players look at all other players' pictures, consistency tends to be better.
  • The closer the hard copy and any other instruction are to one another, the better the results.
  • The earlier it's clear what the big picture is, the more likely the small elements will fit into it.
  • The more shared context, the more likely that the followers can self-correct.
Yes, you can learn a lot from your kids - about drawing, obviously.
Image: http://flic.kr/p/9aKzSG

Comments

Popular posts from this blog

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 answ...

The Best Programmer Dan Knows

  I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

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 ...

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 evol...

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

How do I Test AI?

  Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components .  I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete.  Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report.  Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia.  ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Software Sisyphus

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-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

Not a Happy Place

  A few months ago I stopped having therapy because I felt I had stabilised myself enough to navigate life without it. For the time being, anyway.  I'm sure the counselling helped me but I couldn't tell you how and I've chosen not to look deeply into it. For someone who is usually pretty analytical this is perhaps an interesting decision but I knew that I didn't want to be second-guessing my counsellor, Sue, or mentally cross-referencing stuff that I'd researched while we were talking. And talk was what we mostly did, with Sue suggesting hardly any specific tools for me to try. One that she did recommend was finding a happy place to visualise, somewhere that I could be out of the moment for a moment to calm disruptive thoughts. (Something like this .) Surprisingly, I found that I couldn't conjure anywhere up inside my head. That's when I realised that I've always had difficulty seeing with my mind's eye but never called it out. If I try to imagine ev...

Why Question?

Questions are a powerful testing tool and, like any tool, can be used in different ways in different scenarios with different motivations and different results. A significant part of my role is generating questions and I will generally have a lot of them. I will rarely ask them all, though, and I've put a lot of time and effort into learning to be comfortable with that. A couple of examples: I was in a meeting this week where the technical conversation was too deep for me to give a perspective from a position of knowledge. I could have disengaged, but I didn't. Instead, I asked occasional questions, not wanting to derail the discussion or disrupt the flow. Some were detail questions, to help grow my understanding. Some were scoping questions, to help understand motivations. The one that really landed, however, was about the focus of the meeting. Although I couldn't contribute at a low level, I understood enough to suspect that we were not discussing the key problem tha...