So this is, and isn’t, my ukgovcamp post. I wanted to reflect on the day, and write up my session notes, but ended up focusing on my thoughts coming out of the session that I ran. So there’s not much here on the day itself. But I had an amazing day, as always. And massive, massive props to all the organisers, who hopefully I’ve thanked already in other places. You still never quite get used to the enthusiasm and passion on the day. I urge anyone interested in where democracy and government is going to try to get along next year. There are loads of amazing round-ups to read through to get you in the spirit (or help you reminisce).
Admin note: This was first published on my own weeknotes blog, if you’re not a Medium fan. Read it wherever you like.
On the train, the night before. I have a few minutes in the carriage, among tourists’ oversized baggage and creaking fold-down tables, to work out a session for ukgovcamp 2019. A week-long Twitter poll indicated that people were interested in how to stop and think, which is something I’ve been not-stopping about recently, but have been doing a lot of thinking about. I wrote down in my notebook.
“If our survival depends on passing information between us rapidly, and making good decisions, then why are we so busy doing stuff, instead of listening and sensing?“
As OCSI‘s only head of technology, I am in charge of not just “THE TECHNOLOGY”, but the whole tech team. Actually, it’s hard to be “in charge of” technology as a thing — at a certain scale (ie once you start using it), technology has a life of its own — software updates, hardware failures, security risks, new services, old legacy code and technical debt. All these things will do as they will. I’ve come round to seeing that it is the Tech Team that I am in really in charge of, and that this team is responsible for tending to the technology, in the same way that a gardening team tends to the plants. So team first, tech as a by-product.
As a tech team, working with the forces that make up technology, we often have to react to incidents, either external ones, or ones we’ve made through our own past selves. This will never completely go away, there will always be a reactive aspect to ‘Technology’. But we can be a bit smarter about it.
But being smart is hard when there are lots of things to react to. And this is a problem which seems to affect a lot of people — there is so much to do, and then so much on top of that as well, that being smarter about it just doesn’t get any love.
So at the start of the day, I got up and pitched a pitch, based on the fact that we make bad decisions just because everyone is in a rush. How, indeed, do we — as individuals, and as organisations — deliberately make more time to stop and think, so that we can listen better, reflect better, and make more awesome decisions?
Lots of arms up, indicating I’d hit a nerve, so a good start.
I had one of the first sessions on the almighty matrix of time and thought.
The room was full, but no-one was standing — about 17 or 18 of us, which felt about right and the conversation seemed to flow well. I have a fear of talking too much and taking over. And a fear of the conversation drying up. And a fear of everything being too chaotic to get any sense from.
We did introductions and I gave a bit of background spiel about how I’m very busy, etc etc. I mentioned my weeknotes practice and how that had encouraged me to reflect more. After that, the session mostly ran itself, which was good.
I was particularly interested in what stopped people from stopping, and whether that was a practical thing (actually too much to do), a cultural thing (got to be seen to be doing stuff) or what. From the conversation, I confirmed that it’s definitely not an uncommon thing to always be on the go, and that while it’s a shared experience, everyone has slightly different obstacles and opportunities. Some people had more flexible and remote working possibilities (which can help take more time, or hinder it). Others had particular spaces or times allocated to thinking (although not always necessarily used for this). I wrote down terms in quotes such as “different hats”, “treadmill”, and “safe space”.
The notion of Permission came up a few times, which I noted down with a bubbly squiggle round it. “Giving permission to yourself” came up a bit — and this forged on into what it means to be part of a team with expectations about how we work. We are, fundamentally, social creatures. It can often feel self-indulgent, almost arrogant, to give yourself some space and time. Like you’re taking a break, like you’re slacking. Apparently, in the 21st knowledge-worker economy, you’re only productive if you’re typing, or in a room with somebody else.
This idea of “permission to think” reminds me a bit, and slightly randomly, of the notion of Parrhesia set out by Foucault, or the notion of being able to speak freely, for different reasons, but often to explore a situation and gain truth from the scenario. This could be in a democracy, in a court, or even in a diary approach (cf. weeknotes again) to explore one’s own, private situation or behaviour. But there is, in all cases, a sense of ‘formality’ and practice, even ritual to it. It is not ‘casual’ speech, but speech with gravitas, and the value of this speech is that it has a real impact on something — often this is the reflection involved, and the realisation that emerges from that.
Parrhesia refers to speech and writing. And yet, it is firmly tied to the idea of permission — and the act of considering what to say is fundamentally an act of thought, not of speech itself.
So perhaps, practically speaking, there is an interesting avenue I can explore further here on the links between interrogation, evidence, progress, truth and structures of time/space.
This idea of “permission” seemed to tie directly in with the values that an organisation has. In any organisation, how people communicate, and what people expect from each other, will emerge from a variety of factors, from the building itself to the organisation’s brand, and also — obviously — from how the people in the group choose to interact with each other, or think they should. If the organisation lead, whoever that is and how they got there, seems to value “busy-ness”, then it is a struggle to go against that.
At one point, I asked everyone in the room if they felt they had the power to change things, and everybody seemed to put their hand up. Maybe that’s the ukgovcamp crowd, or maybe I asked the wrong question in a mumbled way. It’s hard to tell. But I like to think that none of us is so disempowered that we can’t have an impact on the people around us, no matter how small. We’re all potential agents for cultural shift.
So expectations are a big part of this. Expectations to deliver, to produce, to create, in a visible way. (My wife mentioned the term ‘invisible labour’ a while ago, and I keep coming back to this, and will again do below.) We feel like we need to be part of that group, and work in the same way. We have traditional, accepted forms of taking a break — namely lunch, TOIL, and annual leave (including bank holidays). Other, less regular forms remain an enforced group session, such as away days and other team building exercises. And everyone loves those, right?
In the session, this led on to some really interesting tips for how to change a team’s Values and Culture. Louise brought up the User Manuals for yourself that Cassie Robinson put together, and mentioned how doing this across a team offers a way to be open with each other, rather than let habits fester that nobody really likes. Other people (sorry — comment if it was you!) mentioned the idea of ‘share backs’ — holding (alcohol-free) ‘speakers corners’ events on a Friday, ‘team tea-time’ sessions, and other ‘all the things’ timeouts which take us away from direct deliverable work. And this aspect of building groups informally, and feeling comfortable around each other, seems really important, making it easier to take the permission about doing things differently.
There were also some handy tips to do if you can. Someone — possibly Katy I think — came up to me afterwards and mentioned an experiment to have 2 minutes of quiet mindfulness at the start of each meeting. Not enough to eat into the meeting, but enough to stop, feel uncomfortable, push on, and get some grounding back. Little things make such a difference, sometimes.
Returning to this idea of visibility, I was (and am) very interested to explore how we could value thinking time more. As one session attendee noted, if you’re by yourself, but at least drawing on bits of paper, it makes it look like you’re doing something.
As mentioned, the wife mentioned “invisible labour” to me a while ago, which is a term often associated with working mothers to highlight the work they do without getting paid, and also with jobs that society doesn’t want to acknowledge. I’ve come to think about it more as I try to get across to people the value of what I do as a “technologist” (someone what understands technology a bit), and increasingly as a “strategic” thinker. Your brain is going a mile a minute, but your body is staying still. And that’s GOOD. But thinking is a kind of invisible labour at times*.
So there are different ways of being more visible with our thinking time. Being active in the space is one. Sharing it with others, in whatever way is another, whether that’s lunch time sessions, or meaty documents, or even just internal blog posts — this small dissemination/communication activity is often overlooked, but is a valuable tool for both shaping our thinking, and for letting others in on it. It’s why (I believe) weeknotes, and open working generally, can be so powerful.
We didn’t discuss much about being more open about asking permission, and ways to improve that. I can imagine a more structured approach might involve being clear about what question or problem you’re trying to tackle. A good way could be to book in a calendar item, clearly with yourself as thought time, and to set this question as the agenda. “THIS IS WHAT I AM THINKING ABOUT. Leave me alone.”
*That said, I do prefer thinking ‘out loud’ on a massive whiteboard, or with a thousand post-it notes.
Well, first up, massive thanks to all the attendees and note-takers who came along and made it a great session. Someone came up to me in the pub after and said it was their best session of the day, which made me smile A LOT.
There are lots of places I could go with this. I want to try more things out, on a personal level, at work — especially around being more open with my thought time, and making more space for that “As A Thing”. I’m in a good position to not be toooo crazy, and to set my own agenda and be something of a role model. Got to count your blessings.
I’m hoping that draws more attention to the need to set aside proper thought time. I’m also hoping that it brings more attention to the kind of problems I’m thinking about, and why they’re actually important.
Sadly I don’t think I’ll be able to do the User Manuals across the whole team yet. But I’d like to do one for myself, to help others understand the MYSTERY that is me. And it would be a useful tool in about 4 or 5 months, I think.
Otherwise, I’d be very happy and keen to keep the conversation going, and stay in touch with anyone else interested in discussing it, or getting support on it. If that’s you, then drop me a comment, or say hi at @6loss on Twitter, or you can even email me.
Here’s a list of potentially useful resources, some from the session, some from after, and some from my memory:
- Cassie Robinson’s User Manual for Me as mentioned above
- Book: Will it Make the Boat Go Faster? by Harriet Beveridge
- Book: It Doesn’t have to be Crazy at Work by Jason Fried and the Basecamp/Rework ethos
- Book: Fearless Speech by Foucault, on Parrhesia as above, but OMG THAT’S EXPENSIVE. Maybe your library has a copy?
- Article: To reach your goals, have meetings with yourself
- Book: Make Time by Jake Knapp and John Zeratsky
Originally published at 6work.exmosis.net on January 30, 2019.