Kads Aziz
Writing About

Still Accountable · 7 parts

All writing
01 MAY 26
Part 01

The Demo Is Not the System

An impressive AI demo and a system you can ship under audit are different projects. The gap between them is the work. First in a series for regulated teams.

08 MAY 26
Part 02

When the Model Is Wrong, You're Still Accountable

When an AI system gets it wrong, your team still answers for it. How regulated teams design for accountability that can't be delegated to the model.

15 MAY 26
Part 03

The Data You Can't Paste Into a Prompt

AI and data governance for Australian regulated teams: residency, data sovereignty, and the Privacy Act duties that decide where your data can go.

22 MAY 26
Part 04

Your AI Is a Brilliant Junior

AI produces senior-looking code and content with junior reliability, and never learns from mentoring. The review burden is the cost regulated teams underprice.

29 MAY 26
Part 05

You Can't Audit a Guess

AI explainability for regulated teams: a model that can't explain why it produced an answer is a liability the moment a regulator asks you to justify the call.

05 JUN 26
Part 06

Speed Was Never Your Bottleneck

AI in regulated engineering makes code faster, but speed was never the constraint. Correctness, trust, and sign-off were. Don't optimise what wasn't slow.

12 JUN 26
Part 07

Where AI Earns Its Place

A decision lens for adopting AI on regulated teams: sort tasks by what being wrong costs, then act differently in each zone. The finale of Still Accountable.

Advisory and fractional work with Australian software teams.

[email protected]

New writing by email, when a piece is worth your time.

© 2026 Kads Aziz
Writing About RSS LinkedIn