The artefacts that turn an AI mandate into a defensible programme.
Your CEO wants AI in every product surface by year-end. Your CTO wants tooling boundaries. Your GC wants audit trails. Your CHRO wants a rollout that doesn’t lose the IC bench. Your Board wants one honest read. We’ll teach you to write all of it — graded by your role coach against the criteria a real C-suite reviewer applies.
Policy templates aren’t the bottleneck.
Practice writing them is.
Every AI consultancy can sell you a template. None of them grade your draft against what a CHRO and GC actually push back on. We pair you with a role coach that pushes back the way your sceptical IC, your Compliance lead, your Board observer would. You ship a draft that survives the room.
Six artefact types. Seventeen industry-grounded scenarios.
The one-page (or three-page) charter your CTO + CHRO + GC actually sign. Intent, scope, sanctioned tools, training expectations, no-go zones, governance, public-reporting commitments.
- •Product AI Enablement Charter — FY26
- •Engineering AI Enablement Charter — FY26
- •K-12 EdTech AI Enablement Charter
- •Federal Agency AI Enablement Charter (OMB M-24-10)
The honest one-pager your VP needs to give the Board. Ready / conditional / not-ready, capability gaps, risk inventory, investment band, the decision the Board is being asked to make.
- •Q4 Board readiness memo (cross-industry)
- •Value-based-care AI readiness (health-insurance payer)
- •Vision-AI QC readiness (14 manufacturing lines)
Which AI dev tools your engineers can use, for which workflows, with which data. Audit hooks (PR tagging, prompt logs), IP + licence posture, exception process, quarterly review cadence.
- •AI Tooling Policy — 40-engineer org
- •SaMD Eng AI Tooling Policy (FDA-regulated)
A brief that ends in a recommendation, not a comparison table. Capability test cases, hallucination guardrails, data-residency, vendor risk (financial, model lineage, training-data), TCO, exit clause.
- •Customer-Support Copilot — 3-vendor evaluation
- •Fraud-detection vendor evaluation (regional bank)
- •Citizen-Services chatbot evaluation (municipal)
Roll out an AI tool to a sceptical engineering org without losing the IC bench. Pilot cohort, training, success metrics, opt-out path, kill criteria — and not used in perf reviews.
- •Copilot rollout to a sceptical 40-eng org
- •200-engineer bank rollout (with regulator-letter plan)
New CAB gates for AI features. Model lineage, hallucination test pass-rate, kill-switch verified, audit-log retention, rollback SLA — without doubling your release cycle.
- •Generic CAB addendum (48-hour budget)
- •Credit-decisioning CAB addendum (ECOA / FCRA-ready)
- •Clinical-decision-support CAB addendum (SaMD / HIPAA)
If you’ve been handed the AI mandate, this is for you.
You write the Tooling Policy and the Change Plan. You decide which AI tools survive contact with your IC bench.
You write the Charter and the Readiness Memo. You translate the CEO's mandate into a scope your team can deliver.
You write the Vendor Evaluation Brief. You're the one who has to recommend a vendor your CISO will sign for.
You write the CAB Addendum. You're the gate between an AI feature and a regulator letter.
You're rolling AI capability to thousands of seats. You need an evidence library, not slides.
Your client says 'help us build the AI programme'. You need a workbench your associates can use credibly.