See It! Days 6-9

This post is part of a series showing my working through the 2025 Advent of System Seeing exercises set by Ruth Malan. For background see the introduction.

In this set of exercises, the idea of feedback is introduced. Feedback is at the heart of systems thinking because we humans seem to be primed to view the world as a simple linear cause-leads-to-effect machine in which only the causes and effects that matter are those that (a) we desire or (b) are glaringly obvious.

Day 6

Task: Watch a video on causal loops and take sketchnotes.

I know and like this kind of diagram (Be a Quality Detector) but I have struggled to build them for any system that I've looked at. In particular, I find the formal labelling of positive and negative loops to be more of a dark art than a science. The good news is that informality has proved sufficient for me up to now but perhaps I'll learn to be more formal on day 7.

Day 7

Task: Practice using causal loop diagrams to understand interacting effects in a system, for example the effect of adding lanes to a highway.

My diagram captures a scenario where I have assumed that a road is already at or near capacity so that throughput (say, number of cars passing a specific point per hour) is lower than desired. I have several problems with it

1. The wording in the nodes is very important. Take (A) where I instinctively said adding a lane to our road would result in a "reduction in traffic elsewhere." This seems reasonable but makes it harder to decide whether we have a positive or negative relationship. Probably I should have labelled this node "amount of traffic elsewhere" and it'd be more obviously negative.

2. The idea of positive and negative relationships is problematic because they have both a mathematical and a value judgement interpretation. I suspect that what we're really annotating is direct and inverse relationships.

3. Temporality is hard to express. Both (A) and (B) are potential impacts of the action in this scenario, but likely at different times. How can I reflect that?

4. Some of the impacts are secondary, for example (C). How far should I go when thinking about them? In this artificial exercise I don't have a remit so I noted a few and stopped.

5. I have drawn a dashed line (D) to indicate the temptation to loop through the whole cycle again, once congestion returns to the system. I would like to somehow indicate that other choices are available at this point.

6. I don't know how to represent magnitude on these kinds of pictures. How should outcomes be balanced against on another?

Day 8

Task: Create another page for the zine from earlier. Focus on context: why do we consider (system) context? What are associated concepts? Is there an explanatory diagram that helps convey why context is important to consider?

I spent waaaaaay more time than I intended to on this one. I had in mind that there's an interesting parallel between the "start with the why" call of Simon Sinek's elegantly simple Golden Circle model and the idea that systems are "surrounded by the why": the context in which a system sits is the reason it does what it does.

I started with the basic idea of this parallel

Why: the context. The system is the shape it is because of it.
How: the actions performed by the system.
What: the outputs from the system.

and iterated through four or five sketches to get the one above. It's the first time in this series that the image you're seeing is not the first image I drew. Here's some of the along-the-way versions:

I'm not sure what I've done here satisfies the brief, to be honest. I don't think that by itself my diagram really motivates the primacy of context. It's probably less interesting to someone who hasn't come across Sinek's work too, but I think it is at least memorable and graphic.

Other things that I would have liked to included: showing that something designed in a linear way on the left can be part of a system on the right, or that context from analysing a system on the right can feed into the why on the left, but I didn't want to try to superimpose that additional layer onto the sketch because of the risk of obscuring the core detail that's already there.

On top of all of that, enamoured as I am with the idea I've drawn, I'm still not certain whether it holds up.

Day 9

Task: (1) Watch a short video about trees. Jot down notes (and sketches) as you watch it. (2) Draft a zine page on relationships.

I'd come across the so-called Wood Wide Web before, so the basic information in the video was not new to me. What to pull out into my sketchnotes and then into a more general zine page on relationships was tough to decide, and in the end I'm not sure whether I'm happy with what I did. Unlike on day 8, I am comfortable that what my page says is true, but I question whether it's helpful.

Next: Days 10-16
Image: Inspired by Explore It! by Elisabeth Hendrickson. Pragmatic Press

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

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

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

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy, followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

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

Why Test, Test What, Then How?

There was a time when testing was all about the mnemonics . Well, we had no AI back then so thinking about our human craft and how to share what we had learned using our human intelligence with other engaged humans for later recall in their human heads seemed important. But this post isn't about dumping on AI. It isn't about mnemonics either even if WTTWTH does look like something that'd fit well into that ancient world. No, this post is just a snappier version of what I said to my team this week when I was walking through some testing I'd done the day before. It was concerned with a change to a particular turn in the dialog system we're building where multiple variables are in play, some populated by an external call to an LLM service. I wanted to make the point that the bulk of the testing work was done in the research I did and the spreadsheet I made, not in the interaction with our product. That spreadsheet was the result of me looking in our service's cod...

Exploratory Testing Reimagined

Maaret Pyhäjärvi gave a talk, Exploratory Testing Reimagined , last week. There's a blog post to go with it, so I won't say much on top of what's in my sketchnotes above, just pull out a few reflections. I don't have the data or wide range of experience reports that Maaret does, but my own anecdotal results from using AI tools for testing align closely with what she says in the talk. I have created skills to assist me, and my colleagues, in our testing work. For example, I used the contents of this blog and five years of test notes in my current role to distil a conversational workflow, facilitated by Claude, which runs through risk identification, test idea generation, and test mission creation. All four skills (the facilitation is its own skill) are backed by a fifth, on general testing theory and practice, and a sixth about how I like to interact with the AI: which notably includes that I want it to be concise, evidence-backed, well-structured, and critical. I st...

LLEWT 2024

This weekend I was at LLEWT 2024, a peer conference on Anglesey , north Wales, discussing communication. Given the day jobs of the participants, it was no surprise that the experience reports and the conversations that followed them mostly focussed on software development contexts. Notes from my presentation are in Express, Listen, and Field . I made sketchnotes (below) for each presentation and a mindmap (above) to try to summarise the whole. Without much reflection yet, I guess I would pull these common high-level threads from the day: There are multiple reasons that communication fails ... like, duh! ... but having multiple strategies for framing a message can help ... and having multiple tactics for delivering a message can help too. Understanding what you want from an interaction is key ... so setting the context to make that more likely is wise ... which might mean meta-conversation, being transparent, or changing your approach...

Hiccupps

Search This Blog