Lookahead
Back to blog home

Leigh Gibson: Making AI Governance Practical for SMEs

5 min Lookahead friends

Lookahead ·

Leigh Gibson

Founder of Tech Exec Australia, helping SMEs adopt AI safely, and co-founder of Technology Executive Women. Find her on LinkedIn. We chatted with Leigh for our Ducks in a Row newsletter.

Introduce yourself

Hi Everyone, my name is Leigh (pronounced Lee), I don’t have any nicknames, and I love to read. This got me into trouble as a kid because I would lose myself in fictional worlds and sometimes get in trouble for reading books under my desk at school when I was bored! 😅

What do you do for work?

I’m establishing a new tech consultancy, Tech Exec Australia, to help SME businesses without a full-time CIO/CTO make strategic technology decisions and set them up to use AI safely (practical and adaptable AI governance).

I started out as an engineer. My experience—both as a bootstrapped founder for 3+ years and leading large tech platforms in regulated industries (internet banking for a big 4 bank + global employee tech for Australia’s largest telco)—means I know how to own and manage technology in a way that is appropriate to customer needs.

What do you do outside work?

My family enjoy sailing Couta boats through summer in Victoria’s Port Phillip Bay. They are vintage-era wooden fishing boats designed for speed at a time when the first boat back to shore would get the best price for their catch. No automated components allowed and the fastest boats are often the ones with a calm skipper, team of people with clearly explained/understood roles, high trust and great communication. Just like tech delivery! 😉

I also enjoy sewing and inventing new houses/toys for my family’s pet guinea pigs from recycled materials. It’s a win-win because my kids enjoy the creative building process and the guinea pigs find the new inventions entertaining and mentally stimulating.

You led the largest Microsoft Copilot rollout in Asia Pacific for Telstra. What’s the biggest misconception you see business owners have about rolling out AI tools like Copilot internally?

The biggest misconception that I see is the assumption that employees understand how to maximise benefit from using the tools without needing any training. Or that AI can support work being transferred to new team members without prior planning. The majority of teams who use tools like Copilot well and enjoy significant benefit have spent time establishing appropriate structural foundations to ensure success. Most beneficial supports to teams have included train the trainer type activities to localise support, weekly prompt ideas shared on the company intranet, and intentionally communicating the ‘boring stuff’ (information security, data protection, data quality and provenance, and specific legal implications).

Currently, the people I see who gain the most benefit from creating new AI agents are people who deeply understand the underlying business drivers for their work and can anticipate how to navigate any undocumented rules or processes. Anyone can create a new agent, but those who recognise specific pain points and know how to address them with an agent generate the most benefit.

You’ve done AI governance for both scale-up and enterprises. What does each end of that spectrum get right that the other could learn from?

When starting to use any new type of technology, it’s useful to run structured experiments with new AI tools initially to quickly validate value and effectiveness. Scale-ups are great at experimenting but could benefit from appropriately structured quality checks and establishing controls before launching. The transition from startup to scaleup can be tricky if the team culture does not evolve to accept a baseline level of important checks prior to launching something new. This is critical when a scale-up operates in a regulated industry - shortcuts acceptable in the early years are likely to be frowned upon by their regulator now, especially as potential cyber risks grow quickly.

Enterprises are also experimenting with AI tools and most have extremely rigorous processes to follow due to the catastrophic potential risk triggered by the wrong decision, so the evaluation and deployment speed can feel painfully slow. Senior stakeholders sometimes need bravery and deep breaths to provide final approval when the timeframe is shorter than usual - even after all of the processes have been followed!

You’re co-founder of Technology Executive Women (TEW) - what prompted starting it in 2022, and what’s changed for

women in tech leadership since?

In 2020, I had completed the modernisation of ANZ’s internet banking platform and was asked to move to a new part of the bank (outside Digital) to establish a new tech team. There were 6 women leaders in Digital whom I had sponsored into their roles, and they wanted to stay in touch. I established a fortnightly meeting since my new role was quite busy, and invited some other female tech leaders I met at ANZ who expressed interest. Within 6 months, more than 50 women working in tech leadership roles across the bank were actively participating! We realised that the group was useful for connecting people with similar skills and experience so they could support each other.

I accepted a redundancy from ANZ in 2022 and decided to co-found Technology Executive Women with Sam Davies that year so we could keep the group going outside ANZ. Forming an independent body allowed us the freedom to focus specifically on supporting, connecting and empowering our members. We don’t meet often, but the energy in the room is magical when we do! :) While progress is being made on technology leadership diversity, there are peaks and troughs to navigate as the work continues.

Any podcast you are currently listening to, or a book you are reading?

Here are two books I’ve enjoyed in the past year, both written by members of Tech Exec Women :)

“The Quality Coach’s Handbook” by Anne-Marie Charrett - super useful guide for technology leaders wanting to ensure their engineering teams maintain a focus on quality and a fantastic resource for anyone seeking to continuously improve how they build software.

‘Win the Night to Win the Day’ by Penelope Barr - a thoughtful personal productivity strategy book based on her experience as a senior technology leader.

What is your favourite tool or resource, and why?

Claude is my favourite at the moment because it helps in various contexts. Tools and resources are constantly evolving, so I don’t typically get too attached.

The best way to tackle a really HUGE change is by ensuring every small daily decision supports it. This effect expands exponentially when teams focus this way because many more minds are involved in achieving the shared goal.


Subscribe to our monthly newsletter to get our latest content in your inbox.

Worth reading. Promise.

We write when we have something worth saying. Drop your email and we'll send it when we do.