Organisation and ownership

Centralise the road. Keep ownership distributed.

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

Intent enters. Evidence comes out.

An AI can suggest, plan and act. It should not be the only party deciding that its own work is correct.

1

Human intent

State the work and expected outcome in language the domain team owns.

2

Bounded task

Define what the agent may do, where the step ends and what is forbidden.

3

Agent and tools

Give the model enough context and the smallest useful set of actions.

4

Evidence

Check system state, captured values, tool history or human acceptance.

5

Close or recover

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

A core AI team, with shared ownership.

The central team builds a reusable road. Domain teams drive on it and still own where the work needs to go.

01

Domain teams

Own the meaning

  • Workflow and exceptions
  • Domain tools and knowledge
  • Acceptance criteria
  • Final outcome sign-off
02

AI platform & enablement

Build the shared road

  • Agent foundation and tool standards
  • Evaluation and observability
  • Common controls and cost visibility
  • Coaching, patterns and adoption
03

SRE and Security

Remain independent gates

  • Reliability requirements
  • Security and data policy
  • Production readiness
  • Incident and audit standards

What I measure

Usage is a signal. Outcome is the result.

The management view is quality-adjusted productivity: useful delivery after including review, rework, defects, safety and cost.

Completion

Task success

Did the requested outcome actually happen?

Human cost

Review and rework

How much correction made the output usable?

Quality

Defect escape

Did speed move defects into a later stage?

Control

Safe execution

Were permissions and approval boundaries respected?

Flow

End-to-end time

Did the complete workflow become faster?

Economics

Cost per success

What did each accepted outcome actually cost?

The practical foundation

One road. Clear interfaces. Named owners.