The board is about to ask about AI. Have the one-page answer ready.
The memo and slide set that answer the four questions your board is about to ask about AI in engineering — before they ask them. Fill the blanks, drop in your numbers, walk in with a position instead of an opinion.
Your board is going to ask. Have the one-page answer ready.
Boards in 2026 have stopped asking "are we using AI?" They are asking "how is it governed, and can you prove it?" You get one meeting to answer that with structure, not anecdotes. This is the page that lets you walk in with a defensible position instead of a story.
of organisations using AI have enterprise-level governance
more production incidents per PR in AI-heavy teams
of AI-generated code fails security tests
Not a guide. The artifact you present.
The two-page board memo
The pre-read for the board pack — your position on page one, the risk and the plan in board language on page two. Fill the blanks, keep the sources.
The four board questions, answered
The four blunt questions boards are asking CTOs in 2026 — each with a fill-in-the-blank answer written from evidence, not assertion.
The 8-slide deck skeleton
Drop-in slides: the gap, the five most damning numbers, the cost of one incident, the two clocks, the method, your archetype, the path, the ask.
Speaker notes for every slide
What you say, not what you show — the sentence that lands each slide when the room goes quiet.
The hostile-question FAQ
Five push-backs a board member actually makes — "isn't Copilot governance?", "isn't it too early?", "what's the ROI?" — and the one-paragraph answer that holds.
The ask
A staged, board-shaped request — assessment, then workshop, then transformation — so risk is staged and the budget line is defensible.
See it before you gate it.
How many AI assets operate in our environment, what does each do, what data do they touch, and how are they governed?
Where do we intend to lead with AI, and where is it acceptable to be a fast follower?
Can we trust our AI output? (Not a technical query — a strategic, ethical and financial one.)
Could our CHRO, CFO and a BU lead explain what we're doing with AI — without you in the room?
Everyone is already using AI. Nobody agreed how.
The five most damning numbers.
What one ungoverned incident costs.
Two clocks are already running.
The answer is a method, not another tool.
Where [org] is today.
The path: chaos to capability in 18 months.
The ask.
Every bracketed field is yours to complete; every statistic and date is fixed and sourced. Do not change the numbers — each carries its source inline so a board member can check it. That is the point: you are trading anecdotes for evidence.
Don't walk in with a story about AI. Walk in with a one-page position the board can check, refreshed every quarter by the same diagnostic. Governance is a number engineering will say out loud — not a feeling.
Use this if you're a CTO who…
…needs board buy-in and a budget line for AI governance, not just another tool.
…has a board meeting coming and needs a position on one page, not a panic.
…can't yet answer "how much of our code did AI write, and who reviewed it?" — and knows the board will ask.
…needs to prove the EU AI Act deadline and insurance shift are board-level items, on the balance sheet.
Written for the earliest maturity bands — The Individual Champions (21–40) or The Emerging Framework (41–60) — where a few engineers have figured AI out but nothing is governed across teams. This is the pack that justifies the move to The Structured Org.
CRAFT Method wasn't designed in a boardroom. It was forged in production.
It was forged by building production software with AI, every day, for months. FIKR Space — eleven integrated products, built solo plus AI — is the live proof point.
EU AI Act high-risk obligations enforceable
Article 12 logging is architectural, not retrofittable. If it isn't built in, it isn't there when the audit arrives.
Insurance exclusions for generative-AI claims live
The financial backstop for AI-introduced defects is narrowing. The liability is moving onto the balance sheet.
The decision is yours. The clock is not.
Before you ask.
Is this really free?
Yes — the board briefing pack is a free download in exchange for your email. You'll get the memo, the 8-slide deck skeleton, the speaker notes, and the hostile-question FAQ instantly, plus the occasional field note. Unsubscribe anytime, and we never share your email.
Is it really fill-in-the-blank?
Yes. Every [bracketed field] — [org], [your DORA numbers], [AI tool spend], [our archetype], [budget line] — is yours to complete. Everything else — every statistic, every date — is fixed and carries its source inline, so a board member can check it. You supply the specifics; the evidence is done.
Do I need to know CRAFT Method to use it?
No. The pack stands on its own — the four board questions, the numbers, the two clocks, and the ask are all present and sourced. CRAFT Method is simply the method the ask proposes: a tool-agnostic, five-practice way to make AI-native development governable, measurable, and board-reportable.
What's the Enterprise Diagnostic the ask points to?
It's the Full Assessment — a 125-question diagnostic across all five practices, plus a 30-minute live debrief with Luis Gonçalves, free during the 2026 launch period. It produces a board-ready governance PDF: your true archetype, per-practice gaps, and first moves — the same number refreshed every quarter.