Human intent
State the work and expected outcome in language the domain team owns.
Organisation and ownership
A core AI team should create reusable foundations and help teams adopt them. It should not inherit every domain decision or become responsible for every failure.
How work should flow
An AI can suggest, plan and act. It should not be the only party deciding that its own work is correct.
State the work and expected outcome in language the domain team owns.
Define what the agent may do, where the step ends and what is forbidden.
Give the model enough context and the smallest useful set of actions.
Check system state, captured values, tool history or human acceptance.
Pass, retry, stop or escalate with a reason another person can follow.
The prompt guides. Code still owns permissions and hard stops.
The agent acts. Evidence—not confidence—supports completion.
The team owns. AI does not erase accountability.
How I would scale
The central team builds a reusable road. Domain teams drive on it and still own where the work needs to go.
Domain teams
AI platform & enablement
SRE and Security
What I measure
The management view is quality-adjusted productivity: useful delivery after including review, rework, defects, safety and cost.
Did the requested outcome actually happen?
How much correction made the output usable?
Did speed move defects into a later stage?
Were permissions and approval boundaries respected?
Did the complete workflow become faster?
What did each accepted outcome actually cost?
The practical foundation