Approach
Three principles shape every cohort. They are simple to read and difficult to install as habits, which is why the programme is built around practice.
Principle 1
What goes into the model decides what comes out.
The role you assign, the rules you set, the reference material you attach, and the prior turns of the conversation determine whether you get useful work or polished noise. We teach context design because it survives vendor changes.
Principle 2
Build. Audit. Coach. Challenge.
Most teams use build for everything. The largest productivity gain often comes from reorganising the same work across the four moves: produce something, check something, think through something, or deliberately push back.
Principle 3
The interesting use is reflection, not just speed.
Upload a document you wrote. Ask the AI to surface unstated assumptions and read it like a sceptical outside reviewer. The result is not merely faster work; it is better thinking before a decision hardens.
Why a cohort
A one-day intensive can explain the moves. It does not embed them. The cohort format gives participants time to use the moves on their own work, meet the predictable friction, and return with questions that deserve a real answer.