
Team AI Fluency
A design-partner pilot starts with a question about the work your team does. Together we agree which tasks can reveal how the group frames a problem, explores options, checks evidence and uses the result.
The Lab works with each pilot partner to choose a capability question and agree what evidence would help answer it.
Teams become AI-fluent when the people inside them can collaborate with AI deliberately, critically, and responsibly.
A team may generate good options quickly and still need practice checking which ones stand up.
Choose where to focus coaching so people keep exercising the judgement their work requires.
The AI Fluency Engine describes four ways people govern work with AI. A pilot uses these four Cs to show where the team is strong and where a habit needs practice.
Give AI clear intent, context, constraints, and the information needed to work toward the right goal.
Use AI as an active collaborator to explore, iterate, and extend thinking rather than as a one-shot answer engine.
Question outputs, assumptions, risks, and weak reasoning before relying on AI-supported work.
Turn useful AI-assisted work into durable knowledge, reusable workflows, and stronger team capability.
Usage figures tell you how often people open a tool. A team assessment can show, for example, whether people check the evidence behind an AI recommendation before acting on it. Our Lab Journal examines what counts as evidence of capability and what it takes to detect a failure.
Policies and technical guardrails matter. So does the human capability to frame goals, challenge AI, handle risks, preserve accountability, and turn AI-assisted work into durable value.
A learning team can use anonymised findings to choose what to practise. Repeating comparable challenges over time can show whether the targeted behaviour changes.
Before the pilot begins, we agree the question, the cohort, the challenges, the duration, the delivery channel and the findings the sponsor will receive.
Agree what the organization needs to understand or develop, which population is relevant, and what responsible use looks like in that context.
With the learning team, design comparable challenges around decisions people actually make in each role. Use the same four Cs to interpret the interactions.
Where the agreed pilot includes individual reports, participants receive and control their own reports.
The organisation receives anonymised, aggregated findings about the group’s strengths and development priorities.
Review what the evidence can and cannot support, where workflow or capability interventions may help, and what should be tested next.
Decide whether to refine challenge design, extend development activity, repeat a bounded measurement moment, or stop without implying maturity the evidence does not show.
Who sees the results? In this developmental pilot, each participant controls their individual report. The organisation receives anonymised cohort findings about strengths and development priorities. For a separately sponsored individual assessment, the invitation specifies who will receive which results before the participant begins. Privacy policy.
01
People first understand and grow how they collaborate with AI.
02
Strength grows across Communicate, Co-Create, Challenge, and Curate rather than concentrating in one mode of AI use.
03
Teams develop stronger, more resilient AI-augmented ways of working without giving up human judgment or accountability.
We are speaking with leaders interested in the human-capability side of AI adoption: balanced augmentation, dependency risk, Responsible AI execution, and stronger AI-enabled teams. Pilot scope and deliverables are confirmed before an engagement begins.
It means building strength across Communicate, Co-Create, Challenge, and Curate rather than over-optimizing one part of AI collaboration. The aim is to expand capability while preserving human judgment, knowledge, accountability, and the ability to govern the work.
No. Adoption shows activity. AI Fluency asks whether people are collaborating well, producing strong results against their goals, and handling risks responsibly.
The capability question, participant group, challenge approach, supported AFA experience, duration, individual and organizational deliverables, data handling, and interpretation boundaries are agreed during discovery.
In this developmental pilot, each participant controls their individual report. The organisation receives anonymised cohort findings about strengths and development priorities.
No. The organisation receives an anonymised view of the group. The pilot is designed to direct development and excludes named employee rankings.