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:
- AI
- ambiguity
- architecture
- augmented reality
- books
- bureaucracy
- career
- change
- Christmas
- cloud
- collaboration
- communication
- corporate life
- data
- delivery
- devops
- end user tools
- ethics
- fear
- government
- halloween
- history
- hype
- innovation
- language
- leadership
- learning
- legacy
- measurement
- mental health
- networking
- New Year
- operations
- prediction
- process
- procurement
- programming
- risk
- science fiction
- security
- shadow IT
- space
- teaching
- teams
- technical debt
- technology advocacy
- testing
- thinking
- TV
- writing
When is it reasonable for technology architects to go to unreasonable lengths?
Teller, the silent half of the duo of magicians, Penn and Teller, is not always silent: he’s given interviews and written articles on the theory, practice and psychology of magic.
Any insight into how people perceive and believe can be helpful to technology architects, but I think that one principle shared in this article is of particular use: make the secret a lot more trouble than the trick is worth.
The idea is that every trick has a public side (what the audience sees) and a secret side (how the effect is achieved), and that most people will assume that an apparently simple effect (the magician identifies the right card) is achieved by a similarly simple cause, and, if they cannot figure out that cause, will be mystified and entertained.
Learn sense making and storytelling from the world around you
My wife and I paid a (socially distanced and suitably masked) visit to the Tower of London last week. It was a strange experience to be visiting this site of so many historical events whilst in the middle of our own historical event, and even stranger because it was so quiet: visitor numbers are currently strictly limited.
The quiet gave us an opportunity to spend a little time longer with the exhibits, and to appreciate them in more detail. The one that stayed in my memory was an exhibit in the Bloody Tower which told the story of the princes in the Tower. (If you’re not familiar with this story, then you can learn more on Wikipedia or, if you’re in London, plan a visit when conditions permit.)
This exhibit held my attention because it told the story in two very different ways.
Take a trip in your architect’s time machine
I have claimed in the past that technology architects have superpowers, particularly x-ray vision and, even more importantly, the ability to figure out how things work. But if you are lucky enough to work with a technology architect, you should make the most of another one of their special abilities: time travel.
You have probably already realised that architects can travel to the future. After all, they spend a lot of their time talking about the fantastic advantages that new technology will bring us, and how great our lives will be one we have built their vision. They also spend a lot of their time giving us dire predictions of how things will be if we make the wrong choices in the present. They may even talk about future state architectures (although this is not a phrase I am a fan of - I will explain more in an upcoming article but will just say for now that attempting to define a single fixed ‘state’ for anything which changes as rapidly as technology architecture feels like a mistake).
Make Feedback a Batch Process
How do technology architects know that we are doing a good job? We are often working as the only architect on the team, making decisions which others may not agree with, making sense of complex and ambiguous topics, and trying to set a direction which others can follow. How can we tell that this all adds up to something useful?
One way to find out is to ask for feedback. We do better when people tell us freely why they disagree with us, whether we are successful in making ourselves understood, and whether the paths we lay out lead to the right place.