Collective Campus
AI Workshops for Leadership Teams in Australia
Quick answer
An AI workshop for a leadership team is a working session where the executives who set direction use AI on their own work, agree which use cases the organisation will back, decide how those uses will be governed, and commit to the behaviours their managers will copy. The best ones in Australia end with three written outputs: a ranked use-case portfolio, a governance stance the board can recognise, and an adoption plan with named owners. Collective Campus runs these sessions as capability building for leadership teams, not as a tool demonstration and not as a strategy deck delivered to the room. Scope, format and depth are tailored after a scoping call, because a leadership team at a listed bank, a state agency and a professional services partnership need different rooms.
- Executive team
- Executive briefing
- Board briefing
Overview
What this page covers
This page explains what a strong leadership AI workshop covers, the formats available, the outcomes to expect, how governance fits, how the main types of provider in the Australian market compare, and a checklist for choosing one.
The sequence
Why leadership teams go first
Most Australian organisations already have AI tools switched on somewhere. Licences for Microsoft Copilot, ChatGPT Enterprise or Gemini are often live, pilots are running in a few teams, and a policy has been drafted. Yet the weekly leadership meeting frequently still runs on the old script. Papers arrive in the same shape, decisions take the same path, and nobody in the room has changed how they personally work.
Staff notice. They copy what leaders do, not what leaders announce. They watch which questions are asked in meetings, which documents are still expected, and whether the people at the top use the tools they are being told to use. If the leadership team has not changed its own habits, an all-staff training program has to push against that silent signal, and it usually loses.
That is why the sequence matters. When leaders go first, three things happen:
The ask becomes believable. A general manager who has rebuilt their own board paper with AI can ask their team to do the same and answer the follow-up questions.
Risk decisions get made by the people who own the risk. Data classification, client confidentiality, procurement and accountability are leadership calls. Leaving them to an IT team or a vendor produces either paralysis or exposure.
Investment follows evidence. Leaders who have seen where AI saves time on real work, and where it does not, fund the right pilots and stop the wrong ones earlier.
A leadership AI workshop is therefore less about AI literacy and more about leadership capability: the ability of a senior team to make good, fast, defensible decisions about a technology that is changing every quarter.
The workshop
What a leadership AI workshop should cover
There is no single correct agenda, but the strongest sessions cover six areas. Each is tailored to the organisation's sector, maturity and existing tools after the scoping call.
1. A shared, grounded picture of what AI can do now
Leaders do not need a history of machine learning. They need an accurate picture of what current generative AI and agent tools can and cannot do on the kinds of work their organisation actually performs. That means:
the difference between assistants, copilots embedded in existing software, and agents that take actions across systems
where the tools are reliable (drafting, summarising, analysing structured and unstructured information, first-pass research, synthesis of feedback) and where they fail (unverified facts, judgement calls, anything requiring accountability)
what has changed in the past year, so the team is not making decisions on outdated assumptions
what competitors and adjacent industries in Australia are visibly doing, drawn from public sources
The aim is calibration. Teams that overestimate AI chase moonshots and get burned. Teams that underestimate it treat it as a typing aid and miss the structural changes.
2. Hands-on work on the leaders' own material
This is the part most providers skip and the part that changes behaviour. Each leader brings a real artefact they own: a board paper, a quarterly business review, a strategy document, a customer complaint summary, a procurement brief. Using only the tools and data the organisation already permits, they work on it in the room.
The point is not to produce a finished document. It is for each executive to feel, first hand, where AI saved them time, where it introduced risk, and where their own judgement was essential. That experience is what makes later decisions credible. A leader who has caught an AI tool inventing a figure in their own paper writes a better verification rule than one who has only been told it happens.
3. Use-case discovery and prioritisation
Once leaders have a calibrated view, the room turns to the organisation. A structured exercise surfaces candidate use cases across functions, then filters them on criteria the team agrees, typically:
value to customers, staff or the bottom line
feasibility with current tools, data and skills
risk, including privacy, regulatory, reputational and safety exposure
reversibility, meaning how easily a pilot can be stopped
visibility, meaning whether success would change how the wider organisation sees AI
The output is a ranked portfolio, not a long list. A good portfolio has a few quick wins to build confidence, one or two bets that would matter if they worked, and an explicit list of things the organisation will not pursue yet, with reasons.
This is where Collective Campus draws on its background in design thinking and lean startup. Use cases are framed as testable assumptions with clear evidence thresholds, so pilots can be judged on what they show, not on how enthusiastic their sponsors are.
4. Governance and risk
Governance is not a separate topic bolted onto the end. It runs through the whole session, because every use case raises a governance question. The leadership team should leave with clear positions on:
Data: which classes of information may go into which tools, and who decides
Accountability: who signs off on AI-assisted outputs, and what a human must verify before anything reaches a customer, regulator or the board
Transparency: when staff and customers are told that AI was used
Procurement: how new tools are assessed, including where data is stored and how vendors use it
Monitoring: how the organisation will know if something goes wrong, and who is told
In Australia, these positions should be shaped by the federal government's Voluntary AI Safety Standard and its guardrails, the Privacy Act and the OAIC's guidance on using commercially available AI products, and any sector rules (APRA prudential standards for financial services, for example, or state government AI assurance frameworks for public sector agencies). The workshop does not replace legal advice. It gives leaders enough fluency to ask lawyers, risk teams and vendors the right questions and to recognise a weak answer.
For organisations that need a deeper governance build, the AI Governance Program extends this work into policy, risk registers, decision rights and board reporting.
5. Operating rhythm and leadership behaviours
Adoption is a habit problem. The session should end with specific changes to how the leadership team itself operates, for example:
which recurring meetings will change format, and how
what each leader will do differently on their own work in the coming weeks
which questions leaders will start asking in reviews ("What did you try with AI on this?", "How was this verified?")
how successes and failures will be shared without blame
These commitments are written down with names against them. Vague intentions such as "lead by example" do not survive the next busy month. Named, observable behaviours do.
6. Adoption plan and follow-through
Finally, the team agrees how the work continues after the room empties: who owns the use-case portfolio, how pilots will be resourced, how managers will be equipped to lead the change in their teams, what will be reported to the board, and when the leadership team will review progress together.
Collective Campus builds follow-up into the engagement by design. Returning to brief the executive team and the board on the commitments made in the room is part of how the capability sticks, and the cadence is agreed during scoping.
Formats
Formats
Leadership teams differ in size, geography and appetite. The format is chosen after the scoping call, but these are the common options.
Executive team immersion
A dedicated session for the CEO and direct reports. It works best when the team already meets regularly and can commit to decisions on the spot. The hands-on component is deepest here because the group is small and senior enough to work on real, sensitive material.
Extended leadership group
A session that brings in the next layer of leaders, often general managers and heads of function. The emphasis shifts from deciding to translating: how each leader will take the portfolio and governance stance into their own area. This format is often run after the executive team session so the senior group's decisions are already in place.
Board briefing
Directors need a different conversation. A board session focuses on oversight, not operation: what questions the board should ask management, how AI risk fits the existing risk appetite statement, what good reporting looks like, and where directors' duties intersect with AI decisions. The Australian Institute of Company Directors publishes useful material on director oversight of AI that can frame this discussion.
Offsite or strategy day module
Many leadership teams already have an annual offsite. An AI module can be built into that agenda, linked directly to the strategic priorities being set, not run as a separate event.
A series of working sessions
Some organisations prefer a series of shorter working sessions, not one larger block, with leaders applying what they learn between sessions. This suits teams that are geographically spread or that want to test pilots between meetings.
In person, online or hybrid
Collective Campus works with leadership teams in person in Sydney, Melbourne, Brisbane and other Australian cities, and online for teams spread across the country or across Australia and Asia. In-person is usually better for the decision-making work; online can work well for follow-up briefings and series formats.
Outcomes
Outcomes to expect
A leadership AI workshop is only worth running if it changes what happens afterwards. These are the outcomes a leadership team should expect to leave with, and should hold any provider to.
Written outputs
a ranked AI use-case portfolio with owners, evidence thresholds and a "not yet" list
a governance stance covering data, accountability, transparency, procurement and monitoring, in plain language the board can recognise
an adoption plan with named owners and review points
a list of leadership behaviour commitments, attributed to individuals
Capability outcomes
each leader has used AI on their own real work and can describe where it helped and where it did not
the team shares a common vocabulary for AI decisions, which shortens future debates
leaders can brief their own teams on the organisation's position without needing a specialist in the room
the team can evaluate vendor and consultant claims with more confidence
Organisational signals
staff see leaders using AI and asking AI-related questions in normal meetings
the first pilots are launched with clear criteria, not as vague experiments
risk and legal teams are engaged early, not as a late veto
What a leadership team should not expect is a finished AI strategy written by someone else. A strategy produced without the leadership team doing the thinking tends to sit on a shelf. The capability to keep making good AI decisions as the technology changes is the asset that lasts.
Governance
Governance in more depth: what Australian leaders need to decide
Because governance is the area where leadership teams most often feel underprepared, it is worth setting out the decisions in more detail. These are the questions a well-run session helps a leadership team answer for its own context.
Decision rights
Who can approve a new AI use case? Is it the business owner, a central AI committee, the risk function, or a mix depending on risk tier? Organisations that do not answer this end up with either a bottleneck, where everything waits for one committee, or a free-for-all, where shadow tools spread unseen.
A common pattern is risk tiering. Low-risk uses (drafting internal documents with approved tools, summarising public information) are pre-approved with simple guardrails. Medium-risk uses (anything touching customer data or external communications) need business owner and risk sign-off. High-risk uses (automated decisions affecting customers, staff or safety) need executive approval and ongoing monitoring.
Data boundaries
Which data may enter which tool? Leaders need to understand the difference between consumer tools, enterprise tools with contractual data protections, and tools hosted inside the organisation's own environment. The OAIC has made clear that privacy obligations apply to personal information entered into AI products, and that organisations should not enter personal information, particularly sensitive information, into publicly available generative AI tools without careful consideration.
Human accountability
Australian regulators and courts are unlikely to accept "the AI did it" as an answer. Leaders should agree where a human must review, verify and own an output before it is relied on, and how that review is recorded. This matters most for client advice, regulatory submissions, financial reporting and anything published under the organisation's name.
Transparency
When will the organisation disclose AI use to customers, staff, regulators or the public? Some organisations adopt a simple principle (disclose whenever AI materially shapes a customer-facing decision or communication). Others set rules by channel. Either way, leaders should decide deliberately, not by accident.
Vendor and procurement standards
Many AI risks arrive through existing software that quietly adds AI features. Leaders should agree what procurement and IT must check when a vendor introduces or changes AI functionality, including where data is processed and whether it is used to train vendor models.
Monitoring and incident response
What happens when an AI-assisted output is wrong and reaches a customer? Who is told, how fast, and how is the use case reviewed? Treating AI incidents within existing incident and complaints processes, not inventing a parallel system, is usually the most practical path.
Board reporting
What will the board see, and how often? Useful board reporting covers the use-case portfolio and its status, material incidents, changes to the risk profile, and progress on capability. The guide to AI governance training for executives and boards covers board-level questions in more depth.
Failure modes
Common failure modes, and how to avoid them
Leadership AI workshops fail in predictable ways. Knowing them helps when designing a session or evaluating a provider.
The vendor tour. A presenter shows polished demonstrations on generic examples. The room is impressed, nothing changes. Avoid it by insisting that leaders work on their own material.
The strategy deck. A consultant presents a pre-built AI strategy. Leaders nod, the deck is filed. Avoid it by making the leadership team produce the outputs themselves, with facilitation, not ghost writing.
The risk shutdown. The session spends so long on what could go wrong that the team leaves more cautious than when it arrived. Avoid it by pairing every risk discussion with a decision about how to proceed safely.
The hype spiral. The opposite failure: the team commits to ambitious transformation goals without the data, skills or governance to deliver them. Avoid it by using evidence thresholds and reversible pilots.
The missing middle. The executive team aligns, but general managers and team leaders are never equipped to carry the change. Avoid it by planning the extended leadership group and manager enablement as part of the adoption plan.
No follow-through. The workshop is treated as an event. Within weeks, the commitments fade. Avoid it by scheduling the review and briefing points before the session ends.
The supporting guide, how to run an AI workshop for your leadership team, goes further into agenda design, pre-work and how to shape each block of the day.
Sectors
How the focus shifts by sector
The core structure holds across industries, but the emphasis changes. These are the patterns Australian leadership teams most often raise during scoping.
Financial services and insurance
Leadership teams in banking, superannuation and insurance work under APRA prudential standards, including operational risk and information security obligations, plus ASIC expectations on conduct and disclosure. The governance block carries more weight: model risk, third-party and vendor risk, explainability of customer-affecting decisions, and how AI use is evidenced to regulators. Use cases often start internally, in areas such as policy summarisation, complaints analysis and document review, before moving closer to customers.
Government and public sector
Federal, state and local government leaders work within public sector AI policies and assurance frameworks, along with records management, freedom of information and procurement rules. Transparency and accountability for decisions affecting citizens dominate the discussion. Workshops often focus on reducing administrative load for frontline staff and improving service design, with clear lines on where automated decision-making is off limits.
Professional services and legal
Partners and practice leaders care most about client confidentiality, professional obligations and the quality of advice. The hands-on block is especially valuable here, because the gap between a fluent AI draft and a defensible piece of advice becomes obvious when leaders test it on their own matters. Commercial questions also come up: how AI changes pricing models, leverage and the development of junior staff.
Healthcare, education and not-for-profit
Leaders in these sectors balance stretched resources against heightened duty of care and sensitive personal information. Sessions tend to focus on freeing professional time from administration, with strict data boundaries and close attention to how staff, patients, students or clients would feel about AI use.
Property, energy, infrastructure and industrials
Asset-heavy organisations often have large volumes of reports, contracts, safety documentation and field data. Use cases cluster around document-heavy workflows, tendering, and knowledge capture from experienced staff. Safety-critical processes are usually placed firmly in the "not yet" list until stronger evidence and controls exist.
Retail, consumer and services
Customer experience leads the agenda: personalisation, service, marketing content and insight from customer feedback. Brand risk and transparency with customers are the main governance themes, along with the change impact on frontline teams.
In every sector, the scoping call is where these priorities are confirmed, so the session spends its time on the decisions that matter most to that leadership team.
Readiness
Signs a leadership team is ready
A leadership AI workshop delivers most when a few conditions are in place. Not all are required, but the more that apply, the faster the team will move:
the organisation has at least one approved AI tool available to leaders, or is about to decide on one
the CEO or a senior sponsor wants decisions, not just awareness
there is some appetite to change how the leadership team itself works
risk, legal or technology leaders are willing to be in the room as participants, not reviewers
the team can commit to a follow-up point to review progress
If several are missing, the scoping call can shape a preparatory step, such as a sponsor briefing or a short AI literacy session for the wider leadership group, before the main session.
Providers
Types of provider in Australia, compared
Leadership teams searching for AI workshops in Australia will find several distinct kinds of provider. Each suits a different need. The table below compares the types, not individual firms, so it stays accurate as the market changes.
Capability-building firms (such as Collective Campus). Strengths: Leadership behaviour, hands-on work on real material, use-case discovery with design thinking and lean startup methods, governance woven through, follow-up briefings to executives and board. Limits: Not an implementation or systems integration partner; organisations needing heavy technical build will pair with a technology partner. Suited to: Leadership teams that want to build lasting capability to make AI decisions themselves and lead adoption across the organisation.
Technology and IT consultancies with an AI practice. Strengths: Deep technical knowledge, data and platform expertise, can move from workshop to implementation. Limits: Sessions can lean towards technology selection and the consultancy's own delivery services; less focus on leadership behaviour. Suited to: Organisations that already know they will buy implementation services and want a technical starting point.
Project and change management training firms. Strengths: Structured delivery, strong change and project disciplines, established public course calendars. Limits: AI content may be one module among many; executive sessions can be standardised. Suited to: Teams that want AI framed within existing project and change methods.
AI specialist boutiques. Strengths: Current tool knowledge, fast-moving, strong on use-case identification. Limits: Narrower view of organisational change and capability; may focus on a particular tool or product. Suited to: Smaller businesses or teams wanting a quick, AI-specific strategy session.
Industry associations and peak bodies. Strengths: Credible, sector-aware, often aligned to member needs and regulation. Limits: Often public or semi-public courses; less tailored to a single leadership team's own work. Suited to: Individual executives wanting a grounding, or members wanting a sector view.
Universities and business schools. Strengths: Academic rigour, research base, executive education credentials. Limits: Generally open-enrolment programs; less hands-on with the organisation's own material and tools. Suited to: Individual leaders seeking a broad, credentialed program.
Vocational and online training providers. Strengths: Accessible, scalable, often accredited. Limits: Built for individual learners, not a leadership team making shared decisions. Suited to: Broad staff literacy, not leadership decision-making.
Leadership coaching and community programs. Strengths: Peer learning, reflection, support for individual leaders over time. Limits: May not produce organisational outputs such as a portfolio or governance stance. Suited to: Individual leaders wanting ongoing support and a peer network.
None of these types is wrong. The right choice depends on whether the leadership team needs technical implementation, individual education, a peer network, or a shared capability to lead AI adoption across the organisation. Many organisations use more than one: for example, a capability-building session for the leadership team, followed by a technology partner for implementation of the chosen use cases.
Why us
Why Collective Campus
Collective Campus has helped teams in large organisations since 2015 across Australia and Asia build the capability to adopt new ways of working, through design thinking, lean startup, agile, customer experience and, more recently, AI programs. That background shapes how leadership AI workshops are run.
Capability over content. The goal is a leadership team that can keep making good AI decisions after the facilitators leave, not a one-off briefing.
Real work in the room. Leaders work on their own documents with their own approved tools, so the experience transfers directly to Monday morning.
Methods that test assumptions. Use cases are framed and prioritised with design thinking and lean startup disciplines, so pilots produce evidence, not opinions.
Governance as a leadership skill. Governance is treated as a set of decisions leaders own, woven through the session, and extended where needed through the dedicated governance program.
Follow-through built in. Return briefings to the executive team and the board keep the commitments alive.
Tool-agnostic. Sessions use whatever the organisation already licenses, whether that is Microsoft Copilot, ChatGPT Enterprise, Gemini or another platform.
Collective Campus's published case studies include work such as an AI Design Sprint with M3 Property, an independent property advisory firm, where teams redesigned their own workflows, built working prototypes in Microsoft Copilot and pitched them to leadership. That same principle, working on real workflows, not generic examples, underpins the leadership sessions. More about the organisation is on the About page.
The engagement
How an engagement works
Each engagement follows the same five steps. Format, depth and timing are tailored after an initial conversation.
- 01
Scoping call
A conversation with the sponsor to understand the organisation's AI maturity, tools, risk context, leadership dynamics and what a successful outcome would look like. Format, depth and timing are tailored from this conversation.
- 02
Pre-work
Short interviews or a survey with leaders, a review of existing AI policy and pilots, and a request for each leader to nominate a real artefact to work on.
- 03
The session
Calibration, hands-on work, use-case discovery, governance decisions, behaviour commitments and the adoption plan.
- 04
Write-up
The outputs are captured in a concise form the leadership team owns and can share.
- 05
Follow-through
Return briefings to the executive team and, where relevant, the board, plus options to extend into manager enablement, AI champions or governance work.
Checklist
Decision checklist: choosing an AI workshop for your leadership team
Use these questions when briefing or comparing providers. A strong provider should be able to answer each clearly.
Purpose
Is the main goal leadership capability and shared decisions, or individual AI literacy?
Will the session produce outputs the leadership team owns, or a document the provider writes?
Content
Will leaders work hands-on with their own real material?
Will the session use only tools and data the organisation already permits?
Does the agenda include use-case prioritisation with explicit criteria and a "not yet" list?
Is governance woven through, with reference to Australian standards and privacy obligations?
Are leadership behaviour changes part of the output, with names attached?
Fit
Has the provider worked with leadership teams in comparable Australian organisations?
Is the provider tool-agnostic, or tied to a vendor or product?
Does the provider have a commercial interest in recommending its own implementation services?
Can the format be tailored for an executive team, extended leadership group or board?
Follow-through
Is follow-up built into the engagement, such as return briefings?
Is there a path to equip managers and the wider organisation after the leadership session?
Will the provider help define how progress is reported to the board?
Evidence
Can the provider show published case studies of similar work?
Will the provider talk through a scoping call before proposing an approach?
If a provider cannot answer most of these clearly, the session is likely to be a presentation, not a working room.
Before a session
Questions leaders often ask before a session
Do we need an AI strategy before the workshop? No. Many organisations use the workshop to form the core of their AI direction. If a strategy already exists, the session tests it against real work and turns it into commitments.
What if some leaders are sceptical? Scepticism is useful. Hands-on work on real material is the fastest way to replace opinions, positive or negative, with experience. Sceptical leaders often write the best governance rules.
What if our policy does not allow staff to use AI tools yet? The session can still run, using sanctioned tools in a controlled setting or synthetic versions of real documents, and one of the outputs can be the policy decision itself.
Should the board attend the same session? Usually not. Directors and executives have different roles. A separate board briefing, informed by the executive session, works better.
How do we keep the momentum? Agree the review points and owners before leaving the room, and build the follow-up briefings into the engagement.
Key terms
Key terms for leadership teams
Use-case portfolio: a ranked, owned set of AI uses the organisation will pursue, with evidence thresholds and an explicit list of uses deferred for now.
Governance stance: the leadership team's agreed positions on data, accountability, transparency, procurement and monitoring, written so managers and the board can apply them.
Risk tiering: sorting AI uses into low, medium and high risk so approval effort matches exposure.
Human in the loop: a defined point where a named person reviews and owns an AI-assisted output before it is relied on.
Agent: an AI system that can take actions across tools and systems, not just generate text, which raises new questions about permissions and oversight.
Evidence threshold: the result a pilot must show before it is scaled, agreed before the pilot starts so success is not judged on enthusiasm.
Further reading
Related programs and guides
How to run an AI workshop for your leadership team, the design note for the person briefing the room.
AI governance training for executives and boards, on the decisions directors and executives own.
AI training for executives, on choosing the right session for a senior group.
AI Governance Program for policy, risk registers, decision rights and board reporting.
AI training for teams once the leadership team has gone first and managers are ready to lead the change.
High-performance team workshops for the habits that let a leadership team decide and still be challenged.
Next step
Book a scoping call
Every leadership team starts from a different place. A short scoping call is the first step to shaping a session around the team's goals, tools and risk context. Book a call to start the conversation.
Sources
Sources
Voluntary AI Safety Standard, Department of Industry, Science and Resources
Guidance on privacy and the use of commercially available AI products, Office of the Australian Information Commissioner
Australian Institute of Company Directors, director resources on AI governance
Questions
Common questions
- What is an AI workshop for leadership teams?
- It is a working session in which a senior leadership team uses AI on its own work, agrees a ranked set of use cases, sets a governance stance and commits to the behaviours and plan needed to lead adoption across the organisation.
- How is a leadership AI workshop different from general AI training for staff?
- Staff training builds individual skills with tools. A leadership workshop builds the leadership team's shared capability to make decisions about AI: what to pursue, how to govern it and how to lead the change. It produces organisational outputs, not individual certificates.
- What should a leadership team leave with?
- A ranked use-case portfolio with owners, a governance stance on data, accountability, transparency, procurement and monitoring, an adoption plan with review points, and named leadership behaviour commitments.
- Does the workshop cover AI governance and risk in Australia?
- Yes. Governance runs through the session and is informed by the Voluntary AI Safety Standard, the Privacy Act and OAIC guidance, and relevant sector rules. It does not replace legal advice but equips leaders to make and defend governance decisions.
- Can the workshop be run for a board?
- Yes. Board briefings focus on oversight: the questions directors should ask, how AI fits the risk appetite, and what good reporting looks like.
- Which AI tools are used?
- Collective Campus is tool-agnostic and works with what the organisation already licenses, such as Microsoft Copilot, ChatGPT Enterprise or Gemini, within the organisation's existing data rules.
- Where are sessions run?
- In person in Sydney, Melbourne, Brisbane and other Australian cities, and online or hybrid for teams spread across Australia and Asia.
- How long is the workshop and how many people can attend?
- Format, length and group composition are tailored after a scoping call, based on the leadership team's goals, size and context.
- How much does a leadership AI workshop cost?
- Each engagement is scoped to the organisation, so the approach and investment are discussed on a scoping call, not listed.
- Is Collective Campus an AI consultancy?
- No. Collective Campus is a capability-building firm that helps teams in large organisations adopt new ways of working, including AI. It does not sell implementation or systems integration, so its recommendations are not tied to selling a build.
Tell us about the leadership team
The scoping call is the next step. You can also send a note. Name the tools already in the business and one document a leader is about to send.