Mjolnir is the most powerful weapon in Norse mythology, and Thor could not pick it up with his bare hands. He needed iron gloves to grip it and a belt of strength to carry what it could do. The hammer was never the whole answer. Most businesses are learning the same thing about AI right now.
There is a detail in the old Norse stories that almost everyone skips past. The dwarves who forged Mjolnir were sabotaged partway through the work, and the hammer came out of the forge with a handle that was too short. It was still devastating. It still levelled mountains and always returned to the hand that threw it. But it was awkward to hold, and it took equipment and practice to use properly.
Thor did not just own the hammer. He owned Járngreipr, the iron gloves he needed to grip it, and Megingjörð, the belt that doubled his strength so he could actually swing it. Three things, not one. Take away the gloves and the most powerful weapon in the nine realms is a very heavy object sitting on the floor.
That is a fair description of AI in a lot of Australian businesses this year.
The licence is the hammer
Buying AI is easy. A handful of accounts, a card on file, and the business can honestly say it has adopted AI. What that buys is the hammer. It does not buy the gloves.
We see the result. A business is paying for licences that a few people use for emails and summaries, one enthusiastic person has gone much further than everyone else, and within a few months the business has quietly decided AI is either overhyped or not for them. The tool did not fail. Nobody was ever shown how to hold it.
The flaw in the handle is real
The short handle is the honest part of the story, and it is worth sitting with. Mjolnir was not a clean, perfect tool. It came out of the forge with a defect, and everyone involved knew it.
AI is the same. These tools are extraordinary and they are also inconsistent, occasionally confidently wrong, and easy to misuse in ways that create real exposure. Staff who have not been trained still use AI. They use personal accounts, they paste client information into whatever tool a friend recommended, and they send output to a customer without checking it because it read well.
Pretending the handle is not short does not help anyone. Training that only shows the impressive demonstrations sets people up to be blindsided the first time the tool gets something badly wrong. The useful version teaches people where the flaw sits, how to work around it, and when to stop and check.
What the gloves actually are
The gloves are not a manual. They are the specific, practical knowledge of how these tools apply to the work your team already does.
That is why generic training does not stick. Plenty of it exists, and most of it walks a room through the same demonstrations: summarise this article, write this email, plan this holiday. People nod, find it mildly interesting, and by Thursday they are back to doing the job the way they always did. Nothing in the session connected to their actual work.
The tasks that change are rarely the ones people expect. They tend to be hiding in work so routine that nobody thinks to question it.
Each of these might save half an hour. Half an hour a day across a team of fifteen is not a productivity anecdote, it is close to a full-time role's worth of capacity you already employ and are not using.
Not everyone needs the same gloves
Thor's equipment was made for Thor. The other useful skills in a business are not the same across every team.
Leadership needs to understand strategy, cost, governance and what to ask a vendor before signing anything. They rarely need to be excellent at prompting. Developers need model selection, agentic workflows and cost control, and they get frustrated quickly in a session pitched at beginners. Operations and admin teams need everyday tools, practical prompting and safe habits. Sales and marketing need research, outreach and content with guardrails so the brand voice holds up.
Run one session for all of them and you will bore half the room and lose the other half. Run tracks that match what each group actually does and everyone leaves with something they can use on Monday.
The hammer always comes back
The part of the myth that matters most for business is the return. Mjolnir comes back to the hand that threw it, every time, which is what makes it worth learning to throw.
Training compounds the same way. A team that understands how to work with AI does not need retraining every time a new model ships. They already know how to test a tool against their own work, judge whether the output is good enough, and decide where it belongs in a process. When the next capability arrives, they pick it up in an afternoon rather than waiting eighteen months for someone to run another session.
That is the difference between buying a capability and building one. The licence expires. The skill does not.
How to tell if training is worth paying for
If you are assessing training, from us or anyone else, these are the questions worth asking.
That last one matters more than it sounds. Training backed by real build experience is different from training assembled out of other people's articles. We build AI calling agents and custom AI systems for businesses every week, which means what we teach has already been tested against real deadlines, real budgets and real things going wrong.
Final thought
Almost everyone has access to the same tools now. The hammer is not the advantage it was eighteen months ago, because your competitors can buy the identical one this afternoon.
What separates the businesses pulling ahead is that their people know how to hold it. That is not something you can buy, and it does not arrive on its own. It gets built deliberately, by teaching people how the work could be done differently.
If your team is paying for AI and only scratching the surface, that is the gap worth closing first. Tell us about your business in a couple of minutes and we will draft a program around it.