I’m David Knott. I’ve been working in enterprise technology for over forty years and I’m still learning. This blog is based on mistakes, failures, lessons and some things I find interesting:
<x> is too important to delegate to your Chief <x> Officer
I started my career in the late 1980s, when the term ‘Chief Technology Officer’ was just starting to be used in companies. (It wasn’t used in the government department where I was working: that still referred to IT as ‘Automated Data Processing’. This was a place where we still had to write out our documentation by hand and send it to the typing pool to be processed,)
Since that time, I have seen the creation of many Chief <x> Officer job titles in the field of enterprise computing: alongside the Chief Information Officer and Chief Technology Officer, we have had the Chief Digital Officer, the Chief Information Security Officer, the Chief Architect and the Chief Data Officer. The latter has undergone mutation in recent years, showing up as the Chief Data and Analytics Officer (CDAO) or, now, the Chief Data and Artificial Intelligence Officer (CDAIO - a title which I can’t help singing to the tune of Old MacDonald Had a Farm - C-D-A-I-O).
The hand shapes the tool; the tool shapes the hand
Humans make tools: it is one of our defining characteristics. But our tools shape us, just as we shape our tools. If, like me, you don’t usually do a physically demanding job, try using a hammer for a few hours, and experience the blisters that it raises. Try using it for a few more days, and feel your calluses and other changes in your body.
Researchers now believe that our hands have been shaped by our history of tool use. Early human species (always remember that Homo sapiens is not the only, or the first, species of human) had weak wrists and clumsy digits compared to modern humans. The development of stone tools, and their impact on prospects of survival, meant that, from approximately 1.7 million years ago, the structure and strength of our hands evolved to get better at using tools. Our tools wrote themselves back into our DNA.
Look on the bright side: the power of applied optimism
Somewhere in the 20th century, at the beginning of my career, I worked with a project manager on several projects. After a while, they told me why they liked to have me on their team.
I waited for them to tell me that it was due to my technical brilliance, my architectural insight, or my all-round charm and charisma. Instead, they told me that it was because I was an optimist, and that I was quite vocal about my optimism.
That gave me an immediate lesson in self-awareness: that the attributes that people value you for are not always those that you value in yourself. I would much rather have been known as the technical wizard than as the person who says, ‘Don’t worry, everything will probably be alright’. Especially as, on most IT projects, such optimism is often seen as a sign of naivety and inexperience.
Reasoning and reflex
I didn’t learn to drive a car until I was in my mid-twenties, and I found it difficult. It took me three attempts to pass my test, and a lot longer before I was a confident driver. But, as well as teaching me how to drive, the experience taught me the difference between reasoning and reflex: the difference between knowing what you should do, and doing it automatically due to muscle memory.
Later, I learnt the management lesson that, when we acquire new skills, especially those with a physical component, we pass through phases of unconscious incompetence (we don’t know what to do), conscious incompetence (we know what to do but we can’t do it), conscious competence (we know what to do, and we can do it when we think about it), and unconscious competence (we know what to do, and we do it automatically).
It’s okay to be overwhelmed by new technology (especially if you’re a technologist)
I’ve been overwhelmed by new technology many times in my life.
When I got my first microcomputer as a teenager, there was very little to help me make sense of it, other than the manual that it came with, some computer magazines, and the efforts of my friends, who were trying to understand their own computers. This new language seemed like a wall of gibberish, with no way to gain purchase.
When I first moved from a corporate environment to a startup environment in the dot com era, I realised that there was a whole new web based technology stack that had sprung up while I wasn’t paying attention, and that I needed to learn in order to lead my team effectively. The skills I had learnt over years of professional work suddenly felt obsolete.
We still don't understand one another
In 1864, Charles Babbage wrote, ‘On two occasions I have been asked, — "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" . . . I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.’
It is worth looking at that quotation twice. The first time we see the stupidity of people asking a blatantly ludicrous question. How could anyone imagine that the machine knows what the right numbers are supposed to be? The second time we see the complacency of the technical expert assuming an unrealistic level of understanding in his audience. How could anyone imagine that the audience knows what a brand new machine is capable of?
Sometimes I just want a blank sheet of paper (and sometimes I don't)
I call it the pushback moment.
It’s that moment when I am writing something - it might be a work document, or a presentation, or one of these articles - when it’s just not working. The sentences are tangled, the meaning is muddy, and I am not getting my point across.
That’s when I push back all of the papers and references and notebooks from my desk and reach for a fresh, blank sheet of paper (or, digitally, open another browser tab and create an empty document). And I ask myself a question: ‘What am I trying to say?’
Adventures in ignorance
Nobody knows anything.
That’s the number one rule in Adventures in the Screen Trade, the book by the late screenwriter and author William Goldman (Butch Cassidy and the Sundance Kid, Marathon Man, All the President’s Men and The Princess Bride, amongst many others). Goldman’s insight was that, even though the film industry was getting on for a century old when he was writing in 1996, no-one had been able to figure out what would be a hit and what would be a flop. Nearly thirty years later, it appears that it’s still true that nobody knows anything: despite algorithmic targeting, despite new ways of reaching audiences and measuring their reactions, it is still possible for juggernaut franchises to stutter and stumble, while unknown newcomers charm and delight.
There's always a bigger goat: don't let big problems stop you solving smaller problems
In the story of the three billy goats gruff, the goats want to cross a bridge guarded by a troll. They manage this by each telling the troll that there is a bigger goat just behind them until (spoiler alert!) the biggest goat comes along and butts the troll into the sky.
Sometimes, when we are trying to make the case for enterprise technology capabilities, it feels like we are the trolls, and that we are so scared of the biggest billy goat that we won’t tackle the smaller goats. When we look across our technology landscapes, we see mess, waste and mayhem, and wish that we had some of the foundational capabilities that would help clean things up. Yet we hesitate, because we know that every time we build something we will uncover another problem, and another problem, and another problem, until we get to problems that are so big that we cannot imagine how to solve them.
Which are more dangerous: slides, or sticky notes?
In the story of the three billy goats gruff, the goats want to cross a bridge guarded by a troll. They manage this by each telling the troll that there is a bigger goat just behind them until (spoiler alert!) the biggest goat comes along and butts the troll into the sky.
Sometimes, when we are trying to make the case for enterprise technology capabilities, it feels like we are the trolls, and that we are so scared of the biggest billy goat that we won’t tackle the smaller goats. When we look across our technology landscapes, we see mess, waste and mayhem, and wish that we had some of the foundational capabilities that would help clean things up. Yet we hesitate, because we know that every time we build something we will uncover another problem, and another problem, and another problem, until we get to problems that are so big that we cannot imagine how to solve them.
Thinking differently about . . . machine learning
Have you ever been introduced to someone then, five minutes into the conversation, realised that you can’t remember their name? If you have never had this experience, then you have a better memory than mine. Whenever that happens, it feels as if you have a window of acceptable ignorance - a period during which it’s embarrassing but not disastrous to admit your lapse of memory. But, as time goes on, you can feel that window expiring: it becomes more and more awkward to ask the person’s name.
It can feel like this in enterprise technology too: we hear about new technologies, trends and terms every day, and there’s a period during which it seems fine to admit that you don’t understand, and to ask people to explain. But then the new concepts are everywhere, and everybody seems to using them with confidence. How did you get left out? Is it okay to say ‘I don’t understand’ now, or is it too late?
I have to admit that I felt like this for a while with the concept of machine learning.
Relearning the habit of focus
Just last week, I wrote that the upcoming Christmas holiday in the UK, with many remaining restrictions on what we could do and where we could go, was an opportunity to reinforce or acquire habits of work/life balance, after many months of working from home.
What I didn’t expect was that, with new variants of the virus circulating, restrictions would become even greater.. The Christmas holiday, which already often contains long stretches of unstructured time - particularly that fuzzy period between Christmas Day and New Year - would be even more unscheduled and unstructured, as even our limited plans would have to be cancelled.
Is there any silver lining to be found in the next phase of our evolving situation? If there is, I think it is in the opportunity to relearn the habit of focus: to spend dedicated time on one thing, to the extent that we lose ourselves in it.