When I started the PerformaGo Diary last summer, it was all about the AI. The vision was to create an AI-first performance support tool for learning and development.
Consequently, many of the posts I wrote during the second half of last year were tech (and more specifically) AI-focused.
If you look back and go through them, many of the posts are like a laymen’s guide to AI.
I was writing about what I was learning and trying to communicate this in relatively straightforward terms.
This was a very helpful part of the learning process for me; I hope it may have de-mystified a few things about AI for you, too.
Everything I learnt then about AI (and since) has been invaluable. It will all definitely get put to good use. But it’s not going to end up being quite as front and centre as I had imagined.
This is just one part of a fairly significant shift that has happened since the start of this year. The realisation that although PerformaGo is a piece of tech that is still going to make use of AI; it just won’t be all about the AI in the way I had originally envisaged.
So, perhaps PerformaGo might now be better described as an AI-enhanced piece of software, rather than an AI-first application.
And, it’s quite likely that the AI-enhancements won’t even be in the first iteration of what I’m building.
When that realisation first started to dawn, no-one was more surprised than me. I had been thoroughly convinced that AI-first was the way to go.
However, once I started to really dig into what would sit behind the tech things changed. I started to get a much deeper understanding of the real purpose and value of the initial concept. At that point, it became crystal clear that I would be building something a little bit different from the initial idea.
Most important, I think the revised version of the concept is much better. It will come closer to achieving the original goal of PerformaGo: to support people post-training, once they return to their workplace and start applying what they just learnt.
So, what caused that shift in perspective?
That’s what I would like to explore in the next post, where I can explain a bit more of the conceptual thinking that will be underpinning PerformaGo.
Until then…
