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.


Popular posts from this blog

Enjoy Testing

  The testers at work had a lean coffee session this week. One of the questions was  "I like testing best because ..." I said that I find the combination of technical, intellectual, and social challenges endlessly enjoyable, fascinating, and stimulating. That's easy to say, and it sounds good too, but today I wondered whether my work actually reflects it. So I made a list of some of the things I did in the last working week: investigating a production problem and pairing to file an incident report finding problems in the incident reporting process feeding back in various ways to various people about the reporting process facilitating a cross-team retrospective on the Kubernetes issue that affected my team's service participating in several lengthy calibration workshops as my team merges with another trying to walk a line between presenting my perspective on things I find important and over-contributing providing feedback and advice on the process identifying a

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

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually

The Great Post Office Scandal

  The Great Post Office Scandal by Nick Wallis is a depressing, dispiriting, and disheartening read. For anyone that cares about fairness and ethics in the relationship that business and technology has with individuals and wider society, at least. As a software tester working in the healthcare sector who has signed up to the ACM code of ethics through my membership of the Association for Software Testing I put myself firmly in that camp. Wallis does extraordinarily well to weave a compelling and readable narrative out of a years-long story with a large and constantly-changing cast and depth across subjects ranging from the intensely personal to extremely technical, and through procedure, jurisprudence, politics, and corporate governance. I won't try to summarise that story here (although Wikipedia takes a couple of stabs at it ) but I'll pull out a handful of threads that I think testers might be interested in: The unbelievable naivety which lead to Horizon (the system at th

Agile Testing Questioned

Zenzi Ali has been running a book club on the Association for Software Testing Slack and over the last few weeks we've read Agile Testing Condensed by Janet Gregory and Lisa Crispin. Each chapter was taken as a jumping off point for one or two discussion points and I really enjoyed the opportunity to think about the questions Zenzi posed and sometimes pop a question or two back into the conversation as well. This post reproduces the questions and my answers, lightly edited for formatting. --00-- Ten principles of agile testing are given in the book. Do you think there is a foundational principle that the others must be built upon? In your experience, do you find that some of these principles are less or more important than others?  The text says they are for a team wanting to deliver the highest-quality product they can. If we can regard a motivation as a foundational principle, perhaps that could be it: each of the ten pr

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

Leaps and Boundary Objects

Brian Marick  recently launched a new podcast, Oddly Influenced . I said this about it on Twitter: Boundary Objects, the first episode of @marick's podcast, is thought-provoking and densely-packed with some lovely turns of phrase. I played it twice in a row. Very roughly, boundary objects are things or concepts that help different interest groups to collaborate by being ambiguous enough to be meaningful and motivational to all parties. Wikipedia  elaborates, somewhat formally:  [boundary objects are] both plastic enough to adapt to local needs and constraints of the several parties employing them, yet robust enough to maintain a common identity across sites ... The creation and management of boundary objects is key in developing and maintaining coherence across intersecting social worlds. The podcast talks about boundary objects in general and then applies the idea to software development specifically, casting acceptance test

Where No-one Else Looks

In yesterday's post, Optimising start of your exploratory testing , Maaret Pyhäjärvi lists anti-patterns she's observed in testers that can lead to shallow outcomes of testing. She ends with this call: Go find (some of) what the others have missed! That strikes a chord. In Toujours Testing I recalled how my young daughter, in her self-appointed role as a Thing Searcher, had asked me how she could find things that no-one else finds. I replied Look where no-one else looks. Which made her happy, but also made me happy because that instinctive response externalised something that had previously been internal.  The phrase has stuck, too, and I recall it when I'm working. It doesn't mean targeting the obscure, although it can mean that.  It also doesn't mean not looking at areas that have previously been covered, although again it can mean that. More, for me, it is about seeking levels of granularity, or perspectives, or methods of engagement, or personas, or data, or im

Am I Wrong?

I happened across Exploratory Testing: Why Is It Not Ideal for Agile Projects? by Vitaly Prus this week and I was triggered. But why? I took a few minutes to think that through. Partly, I guess, I feel directly challenged. I work on an agile project (by the definition in the article) and I would say that I use exclusively exploratory testing. Naturally, I like to think I'm doing a good job. Am I wrong? After calming down, and re-reading the article a couple of times, I don't think so. 😸 From the start, even the title makes me tense. The ideal solution is a perfect solution, the best solution. My context-driven instincts are reluctant to accept the premise, and I wonder what the author thinks is an ideal solution for an agile project, or any project. I notice also that I slid so easily from "an approach is not ideal" into "I am not doing a good job" and, in retrospect, that makes me smile. It doesn't do any harm to be reminded that your cognitive bias

External Brains

A month or two ago, after seeing how I was taking notes and sharing information, a colleague pointed me at Tiego Forte's blog on Building a Second Brain : [BASB is] a methodology for saving and systematically reminding us of the ideas, inspirations, insights, and connections we’ve gained through our experience. It expands our memory and our intellect... That definitely sounded like my kind of thing so I ordered the upcoming book, waited for it to arrive, and then read it in a couple of sittings. Very crudely, I'd summarise it something like this: notes are atomic items, each one a single idea, and are not just textual notes should capture what your gut tells you could be valuable notes should capture what you think you need right now notes should preserve important context for restarting work notes on a topic are bundled in a folder for a Project, Area, or Resource and moved into Archive when they're done. ( PARA )