Skip to main content

Their Art's in the Right Place


Mike Brearley was a professional cricketer for around 20 years and was England captain for 31 of the 39 test matches that he played.  His book, The Art of Captaincy, was recommended to managers by participants at both of the last couple of CEWTs, so it's been on my reading list for a while.

The book is, as you might expect, heavily biased towards the role of the cricket captain and some of the examples given in it require a bit of cricketing knowledge. Despite this, it has a lot to say to anyone with an interest in interpersonal relationships, particularly those in the workplace, particularly about manager-managee interactions. Here, I've collected and grouped a few of the passages that resonated with me.

Professionals should not rely only on practice during their day job

Compton was a genius and thus a law unto himself. But the general belief was then and continued to be that fitness for cricket was achieved simply by playing the game. (p. 54)
All cricketers can enhance their performance by better all-round fitness ... Injuries can be avoided, and an extra foot of speed, an extra inch of suppleness that avoid a narrow run-out or turns a half-chance into a chance can be achieved. (p.54-5)

Professionals, and those who advise, manage, train, lead, mentor, and encourage them, need to think carefully about the timing and context of learning

Most professional cricketers, myself included, have been unwilling to learn ... We distrust theory, and are apprehensive lest change bring catastrophe in its train. (p. 64)
If we define a good coach as "One who enables the potentialities of others to flower", Tiger Smith certainly qualifies: his advice helped me to my best season yet. It came from the right man ... at the right time ... The horse may not want to drink — or he may be unable to. (p. 68)
Excellent advice — but was this the moment for it? ... I felt that he should try to change at a less critical period in his career. The three of us talked this out throroughly. (p. 70)

Professionals recognise that there are different roles and responsibilities in their field, and that with them come different challenges

Gale's role in this process was typical of a good chairman of any committee. He had listened to the discussion, and was able to help the participants to see what it was that we were wanting. He did not, in this instance, need to be closely in touch with the facts on which our views were based in order to have this effect. (p. 84)
My own experience of vice-captaincy was in India, in 1976-7 ... I enjoyed the job, and was struck by how simple it is compared with being the man who has to act and "take the can". (p. 95)
In order to find all the evidence he needs a captain must watch the play. (p. 154)

The captain must be considerate, collaborative, and above all congruent

Some might argue that the captain should act like the junior officers in the First World War and never ask of another what he is not prepared to do himself ... However, such a policy may be simply silly. (p. 162)
The captain should expect the fielders to keep their positions, and not wander. He will demand that they are tidy in their work ... even when sloppiness does not cost runs. (p. 166)
I am often struck by the extent to which bowlers earn their attacking fields, and thus their wickets. Too often they deplore their bad luck when the edged shot misses the solitary slip; they forget that if they had bowled fewer half-volleys and long-hops they could have had a whole ring of slips. (p. 167)
... an important aspect of the captain's job: to remind, or even teach, bowlers that they have more resources than they give themselves credit for: they they have more strings to their bow. (p. 168)
... the captain should encourage all the team to think about the game from a tactical point of view; he must also insist that each member of his side plays a part in enouraging and motivating the others. (p. 170)
Bowlers expect their captain to give them a chance to perform at their best, be being aware of their capacities and preferences. They also have a right to a fair chance. The captain should avoid favouritism ... Yet true fairness is hard to assess. It is simply foolish not to give your best bowlers the first chance on a helpful pitch. (p. 172)
Certainly the captain can never please all his bowlers all the time. (p. 174)
... it was recognised that the captain is likely to get the best out of those he values highly. (p. 88)

The captain needs to maintain perspective

The captain's arc of attention will constantly oscillate between the short-term and other needs: between changes or schemes that concern the next ball or the next over, plans for the disposition of bowlers in the next hour ... or for the rest of the session, and indeed some outline of strategy for the whole day. (p. 182)
There was once a lionkeeper at the Dublin Zoo called Mr Flood, who was remarkable in that over the years he had bred many lion cubs but never lost one. When asked his secret he replied, "No two lions are alike." No doubt he had strategies and general lines of policy. But like a good cricket captain, he responded to each situation afresh. (p. 201)
Bob Paisley has said of managing Liverpool FC, "A manager has to cut his coat according to the cloth — he has to mould his team's style to the players available. The same applies to the individual player. None of them is perfect ... " The illusion of omnipotence is a particular trap for the captain with a well-developed sense of responsibility. (p. 273)
Image: Amazon

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

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

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

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

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

ChatGPTesters

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--  "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

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

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

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