The last few months, I have spent plenty of time using AI to build applications, automate tasks and generally see what is possible… not leading edge, just helping out.
The experience has been enlightening and humbling.
What would previously have taken weeks can now be created in days… sometimes in an afternoon. It is like having a development team inside your laptop.
… and the faster and easier it is build… the more exciting it is… but, the less time you get to focus on what is really going on underneath.
Obviously this results in risk (and a whitepaper, more considered that my blog is a here), but here are some that really stood out
What did I just approve exactly?
AI is no longer just providing answers. It now runs code, installs software, opens files, calls APIs and can make changes on your computer.
That little approval box appears, ‘do you approve’. We click yes. Everything carries on.
But did we check the code, do we really understand what is it doing?
Probably not… honestly… of course not.
I mean do you want to spend 3 months coding, or bash an output out this afternoon to test the idea!
It is a risk, one that human psychology is making it hard to defend against.
Who else is in the room?
Most AI processes are not powered by just one system, they are models, an ecosystem of APIs, installed packages and skills.
It all feels seamless, but underneath what is happening to the data, which firms are touching the data, where, how? … and we are increasingly reliant on these models… what happens if we lose access, or in my case, the price goes up?
We are quickly stumbling further down the rabbit hole of extended (data) supply chains. Whilst this probably doesn’t matter much when we are building small, JavaScript, stand alone websites… okay I put the wrong bins out on Wednesday…. but, beyond this, into enterprise processes it is something we need to understand for sure, and fast.
A numbing effect?
I hear… ‘we managed the AI risk, by putting a human into the process’. Human oversight, human decision.
As a human, this is all very reassuring… but six months later you can foresee the problem.
After six months of approving nearly every decision, humans get bored… checks become cursory, a rubber stamp… and then the mistakes so to filter through (small in number but maybe consequential).
… how do we think about “the computer said yes… but the human says no” to customers. Something to consider.
The new legacy process?
This AI rollout is increasingly reminding me of the early days of spreadsheets.
Anyone could build something useful… nobody documented it.. then the person who built it and actually understood left. The spreadsheet continued running… for the next 15 years, and no one dared to go near it.
This pattern could easily repeat… but as it is AI… faster.
We have redesign and rebuild processes in an afternoon. But who owns it afterwards? Who supports it? Does the next person understand why it was built that way? Can we may changes?
Today’s automation may very quickly become tomorrows legacy system. A spaghetti diagram of legacy systems, connected by AI pipes, that no-one understands… locking us into vendors and providers long term. Something to avoid.
Downskilling?
You can already feel it. AI is changing skill-sets. Tasks, often mundane, I once completed manually are now delegated.. to my AI assistant. Yes, it has saved time… but also means I practice less often.
The same thing has already happened with my handwriting… I only really now type and my handwritten notes are, as a result, only remotely legible.
Of course new skills are coming in too, but staying up to date, and picking where to continue to practice existing skills (such as writing) is going to be important.
Lastly… sameness
It is me, or with the explosion in the use of AI, is everything is starting to look the same?
The same style. The same language. The same graphical format.
I know this is something I am guilty of too… everything looks really polished… but the question I always have is… does it stand out, especially when AI content is becoming increasingly easy to spot.
Being different matters, and if we are all creating content from the same handful of models and tools, it can relatively easily all look the same… no matter how good the content, it will not stand out.
Being human, we know what being human actually feels like… what is funny, on trend, irrational and those slightly odd ideas that do connect.
And, this is something we need to remember, in this blur of AI development, back in the office. For connecting with real customers… our humanness is in some ways our advantage.
READ THE WHITEPAPER HERE

