The fastest way we've seen AI adoption spread inside an Australian business isn't a training session -- it's watching a colleague solve a real problem in five minutes and thinking 'I have that exact problem.' A recurring internal show-and-tell turns that moment from an accident into a routine.
Why a demo beats a manual
Written guides and training decks tell people what's possible in the abstract. A live 15-minute session where someone from accounts shows how they now draft supplier follow-ups, or someone in ops shows how they built a weekly report that used to take an afternoon, does something a manual can't: it proves the tool works on this business's actual, messy data, not a clean demo case.
It also surfaces uses nobody planned for. A Canberra professional services firm running monthly show-and-tells found that half the ideas people brought to share weren't things leadership had asked for -- they were workarounds staff had built themselves, some of which turned out to be worth rolling out team-wide.
Running one without it becoming a chore
Keep it to 20 to 30 minutes, monthly not weekly, so it doesn't compete with real work.
Ask for one thing that worked and one thing that didn't -- failures are often more useful to the room than polished wins.
Rotate who presents; if it's always the same person, it reads as a product pitch instead of peer learning.
Record a two-line summary of each session in a shared doc so people who missed it can still find the idea later.
What it costs and what it's worth
There's no license fee for this -- it's 30 minutes of time from three or four people a month, call it $150 to $300 in loaded staff cost for a small team. Against that, businesses running this consistently for six months report noticeably faster adoption of new workflows than ones relying purely on top-down rollout, because staff trust a peer's five-minute demo more than a slide deck from management.
The habit dies fastest when it's optional and unscheduled. Put it on the calendar with a standing time, protect it the same way you'd protect a team meeting, and it becomes self-sustaining once two or three genuinely useful demos have landed.
Getting past the awkward first session
The first show-and-tell is almost always the hardest to fill. Nobody wants to go first, and the instinct is to wait until someone has a polished, impressive result before volunteering. Fight that instinct directly -- ask the most AI-curious person on the team to present something rough and half-finished for the inaugural session, explicitly framed as 'here's what I tried and here's where it broke.' That lowers the bar for everyone who comes after, and a Sydney marketing agency running this format found their second and third sessions filled themselves once staff saw imperfect demos were genuinely welcome, not just tolerated.
It also matters who's in the room. Keep the first few sessions small -- one team, eight to twelve people -- rather than a company-wide event, so people feel comfortable admitting a demo didn't work as expected. Once the format is proven inside one team, it spreads naturally as other teams ask to sit in, which is a healthier growth path than mandating it top-down from week one.
What to do with the ideas afterwards
The session is only half the value if good ideas evaporate the moment the room empties. Assign one person to turn any genuinely useful demo into a two-paragraph how-to within a week, filed somewhere the whole team can find it later. Without that step, a great five-minute demo becomes a great memory nobody can reproduce three months on when the presenter is on leave or has moved teams.
Treat the first three sessions as a trial, not a permanent commitment. If attendance holds and at least one genuinely useful idea comes out of each session, keep going. If it's clearly not landing after three tries, that's useful information too -- it might mean the cadence, format or timing needs adjusting rather than the whole idea being wrong for your team.
One more practical detail: keep a running list of who's presented and when, so the same two enthusiastic people don't end up carrying every session. Spreading it around, even awkwardly at first, is what turns this into a team habit rather than one person's pet project.
It costs nothing to trial and almost never makes things worse, which is a rare combination in change management. Put a date on the calendar this week rather than waiting for a quieter month that never quite arrives.
If you want a template agenda and a starter list of prompts to seed the first session, we've built one for Australian SMB teams -- ask through /contact.
