Field Notes on Team AI
From My AI to Our AI: What Changes When Your Whole Team Uses It
Using AI on your own is a personal habit. Getting a team to use it well is a different job entirely. Moving from private shortcuts to shared capability requires structure, consistency, and clear boundaries.
The core challenge
Personal shortcuts build habits. Shared workflows build team assets.
Across New Zealand and Australia, professionals have developed clever ways to speed up their own workday using generative AI. But when these workflows remain trapped in individual chats, organisations face a major risk: if that person leaves, the productivity gain disappears with them.
Over the past two years, I have spoken with dozens of managers and team leaders who are quietly thrilled with how much time AI saves them personally. They draft client emails faster, summarise lengthy PDFs in minutes, and polish internal memos during their morning coffee.
Yet when I ask how their team handles those same tasks, the conversation turns hesitant. One analyst uses Claude with elaborate custom instructions. A project lead uses ChatGPT with zero context formatting. A senior manager relies on Microsoft Copilot, while the junior staff write everything manually. The result is a fragmented patchwork of personal habits rather than a coherent team capability.
Moving from my AI to our AI is the single most important step an organisation can take to capture real, lasting value from these tools. It transforms random individual efficiency into reliable, documented processes that anyone on your team can run.
Two real workplace examples from New Zealand and Australia
To understand how this shift works in practice, consider two real operational scenarios from professional service environments in Sydney and Auckland.
Example 1: The Auckland engineering consultancy. A senior environmental planner developed an outstanding prompt system for summarizing local council planning submissions. She could process fifty public submissions in an afternoon, extracting key compliance risks into a clear spreadsheet. However, because the entire workflow lived inside her private account history, her team remained completely dependent on her. When she went on parental leave, the consultancy reverted to manual summary methods, instantly losing four weeks of accumulated efficiency.
Example 2: The Melbourne advisory firm. A commercial advisory team established a central, shared prompt repository for client onboarding briefs. Instead of each consultant prompting in isolation, they created a standardized template with defined source requirements, formatting rules, and mandatory human review checkpoints. When a new analyst joined the team, she was able to produce client briefing papers to the firm’s standard on her second day.
The difference between these two firms is not technical skill or budget. It is operational design. The Melbourne firm built an asset that belongs to the business; the Auckland firm relied on an individual habit that walked out the door.
The true measure of team AI is not how fast one expert moves, but how easily a colleague can achieve the same quality result.
Steve Wilson · Zero to AI Field Note
Four steps to build shared team capability
Transitioning from personal tool use to a shared team practice does not require complex software development. It requires clear communication, agreed standards, and simple documentation. Follow this four-step transition sequence:
Audit existing private habits
Run a brief working session with your team. Ask everyone to share one task where they currently use AI to save time, including the prompts and files they rely on.
Select one high-frequency process
Do not attempt to standardise every task at once. Choose one recurring text-heavy task, such as drafting weekly status updates or reviewing vendor proposals, and establish one agreed standard.
Establish human review boundaries
Define explicit review checkpoints. Ensure your team understands what the AI generates, what human checks must be completed, and how to verify information against authoritative sources under New Zealand responsible AI guidance.
Document in a shared workspace
Store approved prompt structures, reference materials, and output rules in a location accessible to the whole team, such as a Microsoft Teams channel or Claude Project workspace.
Practical takeaway: start your team transition this week
To begin moving from private habits to shared capability, complete these four actions with your immediate team:
- Identify the top recurring drafting task across your team this month.
- Gather the two best examples of completed work to serve as reference standards.
- Create a single shared prompt template using our Season 3 Episode 1 guide.
- Test the shared template with two team members who did not write the original prompt.
By documenting your methods and building shared practice, you create an operational environment where capability scales, quality remains consistent, and team productivity outlasts any single employee.
Build shared capability
Turn individual AI habits into a recognised team asset.
Zero to AI helps experienced professionals in New Zealand and Australia transition from solo prompting to structured team workflows, sensible governance, and scalable capability.