Well Spoken

Nervous about speaking in public? Yeah, me too, but nowhere near as much as I used to be.

Some years ago I wrote a blog post, Speaking Easier, about how I'd challenged myself to present at a testing conference to help myself with the extreme, and irrational, nervousness I was feeling about public speaking.

An absolutely crucial insight for me, as I struggled to find a way into the problem, was that my main goal was to be myself on that stage. I found that I could be comfortable with success or failure just as long as I felt that, in the moment, I'd been my natural self rather than some nervous wreck pulling speaking levers behind a calm and confident, but ultimately fake, facade.

My first conference presentation was Eurostar 2015 and although I got mixed reviews I was very pleased with what I achieved there. I've made an effort to speak at public events regularly since (including MEWT in 2016, UKSTAR in 2018, SoftTest also in 2018, and DEWT earlier this year) because I don't want to lose the progress that I made.

Last week I presented at OnlineTestConf 2020. It was my first webinar-style presentation, it was almost certainly the largest audience I've ever had, and my Zoom client crashed one minute before I was due to start and wouldn't reopen, so I found myself frantically rebooting my machine with fingers tightly crossed as I messaged the organisers on Slack and the host waffled to give me time.

Nerves?

Hardly any, and I couldn't quite believe it.

So what helped?

It's hard to give an answer that I'm confident in, but I did all of these and felt happy about it:

Practice. I find that practising as-live works best; so for the online conference I practised sitting down with my headphones on in front of the computer with my slides in presenter mode. For more traditional conferences I will practice standing up.
Hooks. Consciously applying approaches that I learned at Toastmasters. These include asking a question early on to try to engage the audience, using lists of three items to help keep things straightforward to absorb, and finding places to add pauses and vocal variety to maintain interest.
Research. I looked into differences between online and traditional conference speaking. Alan Richardson's advice, Tips for Presenting Online, felt instinctively reasonable and so I tried to follow it. (This may have been in part because Alan's description of how he practices for non-webinar talks feels familiar to me.) I also asked the conference organisers for a dry-run of the presenter view of Zoom so that I was comfortable with what I needed to do, and so that my practice was aligned with it.
Material. I know my stuff. I know that I know my stuff to a deeper level than I'm presenting it at. In fact, I make a point of choosing topics to speak about that I want to explore for my own benefit so I'm motivated to understand it well.
Testing. Trying the presentation on people whose judgement I trust and taking their feedback is invaluable. I make a point of saying that I will accept feedback on any aspect of the presentation and, whatever the feedback is, I thank the person for giving it. I may not take the feedback on board, but that's my choice, and contributes to the feeling of being myself when I give the talk for real.

After all that, I was really pleased with how my talk went. I'm even more pleased with the feedback I've got on it from strangers. Naturally, it's a biased sample — people who happened to be there to watch the talk, and who felt motivated to take the time to contact me about it — but it still feels good that anyone took anything from it.

I'm particularly happy about comments like these that talk about the delivery and style and inspiration, rather than the content:

Your performance stood out from the crowd. And that's not only because some presenters had difficulties. It felt (at times) as if you had a dialog with me. And that's valuable experience.

This session was the main session I wanted to see. 100% it did not disappoint. It was FANTASTIC. I feel as though my philosophy on testing is closely related to what you presented, but you worded it more eloquently.

Awesome topic James.. How to test anything, now I will test anything

The talk was recorded. I've watched it back and I'm pleased to report that I recognise the chap who's visible in the top-right corner as me, just me, the me you'd experience if we were talking about testing together in person. (Although in real life I'm unlikely to monologue for 40 minutes.)

Comments

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

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

Test Now

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 is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there

Hiccupps

Search This Blog