Changes for content/handbook/eta/ai/strategy/hub-and-spoke/operating-rhythm/_index.md: 8 added lines, 2 removed lines.
Original line number
Diff line number
Diff line
@@ -20,7 +20,7 @@ Enterprise AI is the platform Hub: it builds, governs and supports the AI capabi
The cadence is deliberately stepped: lighter while we are small, heavier as we scale. Async-first throughout, with formal forums kept slim.
### Daily
@@ -28,14 +28,17 @@ Async-first in `#ent-ai-ato`. No mandatory standups across the cohort.
### Weekly
-**ATO Council.** All ATOs plus Enterprise AI representation. 60 minutes. Mandatory. Show-and-tell, platform updates, shared problems, cross-spoke learnings. This is the de-siloing forum, and it naturally grows in scope and value as more ATOs join.
-**AI Engineer to ATO sync.** Minimum once weekly between each ATO and their assigned AI Engineer. More during the launch of a new spoke or an active build (typically two to three times a week), daily during a production push. Async in Slack between syncs. Assignments are reviewed quarterly.
-**ATO to function leadership team.** The ATO joins their function's leadership meeting where appropriate, with a standing agenda slot, so AI work surfaces to the wider function exec team alongside the exec sponsor.
### Every two weeks
-**ATO to exec sponsor.** Updates and reactive prioritisation as priorities evolve.
-**ATO Council.** All ATOs plus Enterprise AI representation. 60 minutes. Mandatory. Show-and-tell, platform updates, shared problems, cross-spoke learnings. This is the de-siloing forum, and it naturally grows in scope and value as more ATOs join.
-**Champion to ATO sync.** 30 minutes. In-function intake and coaching. Daily async happens in `#ent-ai-champions` between syncs.
-**Function AI office hours.** 45 minutes. Mandatory: every ATO runs them. Open to everyone in the function, not just Champions. Hosted by the ATO with the AI Engineer present, so technical questions get answered in the room rather than becoming a ticket. Drop-in and unstructured: no agenda, no attendance expectation, no preparation asked of anyone who turns up. Scheduled on the alternate week to the Champion to ATO sync, so there is something open in the function's diary every week.
This is the front door for the majority of the function who are not Champions. It is also the ATO's cheapest source of signal: the questions people bring are unqualified use cases, and the ones that recur are the ones worth taking to the roadmap.
### Monthly
@@ -68,10 +71,13 @@ Async-first in `#ent-ai-ato`. No mandatory standups across the cohort.
**Cadence.** See the [Cadence](#cadence) section above for the full schedule. In short: ATO to Champion sync every two weeks with daily async in `#ent-ai-champions`, a monthly Champion demo across the function, and a quarterly cross-spoke Champion show-and-tell run by Enterprise AI.
**Champions are not the only route in.** The Champion network extends the ATO's reach, but a function member should never have to find their Champion before they can ask a question. Fortnightly office hours are open to the whole function for exactly that reason. Champions are welcome there too, but it is not their forum.
**Routing rules.**
- Use-case requests, ideas and project work: **Champion to ATO**. Never direct to Hub.
- Bugs, security issues and platform feedback: **Champion to Hub** directly (via `#ent-ai-champions` or Serval).
- Anyone else in the function: **office hours, `#enterprise-ai-collab`, or their Champion**. All three land with the ATO for use-case work. The routing rule is about where work is triaged, not about who is allowed to raise it.
