This week: Finland were robbed; the MSc churned out new ideas; I wrote some code (that unwrote some code I’d previously written); and I serendipitously did not miss a train.
Continue readingAuthor Archives: Jonathan
S11E14A: The map is not the territory
I attended a show and tell by the team thinking about the branding of digital in government – the same content as the one Jukesie attended. His write-up is very good, but I had some different thoughts.
The proposal on the table, as I understand it, is to try to find a unifying brand for people working on ‘digital’ – whatever that means – in the Civil Service. I don’t understand this idea. From an engineering perspective, the abstraction feels all wrong.
When we abstract something, we essentially make a model. We lose fidelity, but we gain the ability to manipulate the thing itself through the model. So it’s important that the model actually maps to the reality, or at least, to enough of the reality.
For example: your mental model of how a lock works may just be “key goes in lock. If it turns, good. If it doesn’t turn, it’s the wrong key.” And that’s fine enough for most cases, but probably not if you’re a locksmith, or an archaeologist specialising in secure entry systems.
Where we start to make mistakes with models is where the model tries to include too much, and consequently becomes useless because it then doesn’t work for anyone. And I’m not talking about clashing mental models, although these are common and difficult: one element of interpersonal relationships is that everyone is carrying around mental models of other people, and these are necessarily simpler than reality. I’m talking about a model that tries to encompass totally different things, and which consequently doesn’t work for anything.
And this is where I come to “digital in government”. I will put aside for a moment that nobody in our weight class is doing this (Tesco, the NHS), and that I think that brands who already have a name for their people (Monzonauts is the first that springs to mind) should treasure and evolve that. I think the abstraction is wrong, because:
- ‘digital’ is already an abstraction, and a poorly defined one
- ‘government’ is already an abstraction, and a slightly-less-poorly defined one
Generally speaking, people these days seem to be joining organisations based on mission. They want to build the bank of the future; or they want to protect the nation; or they’re absolutely passionate about tasting the bottom of Elon Musk’s shoe. Whatever.
My point is that organisations in government have a very broad set of missions, and a very broad set of technologies. Generally speaking, my suspicion is that people join government organisations for their particular mission. Folks are joining MoD because of that mission. Other people are joining DWP, and their mission is markedly different. If we’re going to have brands, my view is that they already exist in departments and should be developed from that point.
‘digital’ is a nightmare of an abstraction. Are user researchers digital? Are business analysts? Engineers are, but are engineering managers? And I know I’m falling foul of my own critique, as I inch towards “all labour is Labour”, as the world divides itself neatly into people who live on rental income and people who labour…
But perhaps that’s why it’s a poor abstraction. ‘digital’ people might as well be ‘civil servants’.
At the end of the day, my experience of the hiring pipeline is something like:
brand awareness -> brand understanding -> job search -> application
And I feel, quite strongly, that there is no brand for digital in government. Instead, the brand is the work. The brand is the mission. And we could do more to lean into that.
S11E14: The bit after the painful bit of growth (is still painful)
This week I figured out how Roles and Users and things are supposed to work in AWS. From that, I’ve done some fun work to clean up bits of our infrastructure that needed a spring clean. I’ve also on-boarded permanent staff and contractors.
Despite not getting that promotion last week, I seem to have got that promotion. You know what I mean?
Continue readingS11E13: The painful bit of growth
This week I didn’t get a job I went for, and I’m trying to figure out what to do next. I’ve also got someone new on the team, and I’ve been catapulted into figuring out things that are interesting and should already have been figured out.
Continue readingS11E12: Feeling the strain
Gosh, this week has been busy. It’s been short, which I suspect is a reason why it feels so busy. But I’m also feeling the pressure of being the only technical person across many different places.
Continue readingS11E11: How responsible am I?
Some time off, some progress on things, and a bug. A big, annoying, Bug.
Continue readingS11E10: even-over
This week: two exams, one easy, one difficult. Work has become difficult, and I want to know what to think about that.
Continue readingS11E09: On study leave
Wrote answers for mock exam. Thought seriously about code. Took on new student. Watched a play.
Lemons. Lemons, lemons, lemons, lemons.
Continue readingS11E08: You only have to answer to one guy, newbie
This week I’ve been being serious and doing some reflective work on where I want to take my career, as well as asking for help. Asking for help is difficult, but rewarding. If you’re struggling with something, this is your sign to ask for help.
Continue readingS11E07: mixed feelings
This week: I found out I didn’t get the senior role I applied for, I found out I probably passed my first two MSc modules, and I probably found out a third thing that I’ve forgotten. The universe should obey the rule of threes, otherwise it’s just a chaotic mess, and we can’t have that. No. I remain optimistic.
Continue reading