# AI Centre of Excellence launch plan

Template id: `coe-launch-plan`

Responsible skill: `ai-centre-of-excellence:coe-launch-roadmap`. The readiness section is completed with
`ai-centre-of-excellence:coe-readiness`. Phase dates are copied into the launch roadmap section of the `coe-charter`
template.

How to use this template: complete every section in your own words. Replace each `[To confirm: ...]` marker only with a
fact your organisation has agreed. Use roles, never personal names. Plan the first ninety days in detail and later
months in outline, and replan at every phase boundary. Durations shown are typical starting points; exit criteria, not
dates, decide when a phase ends. For a Starter working group, use sections 1, 2, 4, 6 and 11 on one page with two
phases (set up, then deliver).

## 1. Document control

| Field | Value |
|---|---|
| Organisation | [To confirm: organisation name or alias] |
| CoE form | [To confirm: AI working group / business-owned CoE / hub / spoke of a named hub] |
| Executive sponsor (role) | [To confirm] |
| Plan owner (role) | [To confirm: CoE lead role] |
| Linked charter version | [To confirm] |
| Version and date | [To confirm] |
| Next replan | [To confirm: at the next phase boundary] |

## 2. Readiness and open conditions

Completed with `ai-centre-of-excellence:coe-readiness`.

| Field | Value |
|---|---|
| Readiness verdict | [To confirm: launch / launch with conditions / not yet] |
| Date of assessment | [To confirm] |

| Open condition | Gate (before launch / Foundation) | Owner (role) | Due | Status |
|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

Nothing is announced while a "before launch" condition is open.

## 3. Launch objectives

| Objective | Measure | Baseline | Target and date | Owner (role) |
|---|---|---|---|---|
| [To confirm: for example first measured value from a quick win] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| [To confirm: for example ideas reaching a decision within the service level] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 4. Phases and exit criteria

| Phase | Typical duration | Planned start and end | Exit criteria | Go or hold decided by |
|---|---|---|---|---|
| Establish | About a month | [To confirm] | Sponsor commitment agreed; lead and core team in place with agreed time; forums scheduled; collaboration space live; front door ready but not announced | [To confirm: steering] |
| Foundation | About a month | [To confirm] | Backlog live with first ideas framed; knowledge register started; approved-use guidance and tiers in use; quick wins chosen with owners and baselines; launch communications ready | [To confirm] |
| Deliver | Two to three months | [To confirm] | Quick wins live with owners; first value measured against baseline; first value review held | [To confirm] |
| Scale | Ongoing | [To confirm] | Patterns reused by other teams; pipeline within service levels; first maturity assessment scheduled | [To confirm] |

## 5. Workstreams and milestones

Write milestones as outcomes, each with one owner role.

| Workstream | Establish | Foundation | Deliver | Scale | Owner (role) |
|---|---|---|---|---|---|
| Sponsorship and governance | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Team and ways of working | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Opportunity pipeline | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Knowledge | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Delivery | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Adoption and Champions | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Value | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 6. First ninety days

| Period | Actions and outcomes | Owner (role) | Done |
|---|---|---|---|
| Weeks 1-2 | [To confirm: for example sponsor commitment agreed; team time confirmed with managers] | [To confirm] | [To confirm] |
| Weeks 3-4 | [To confirm: for example forums scheduled; collaboration space set up; inventory of existing agents and automations started] | [To confirm] | [To confirm] |
| Weeks 5-6 | [To confirm] | [To confirm] | [To confirm] |
| Weeks 7-8 | [To confirm] | [To confirm] | [To confirm] |
| Weeks 9-10 | [To confirm] | [To confirm] | [To confirm] |
| Weeks 11-13 | [To confirm] | [To confirm] | [To confirm] |

## 7. Quick wins

Choose two or three during Foundation. A quick win is tier 0 or 1 (or tier 2 with reviews available), has a keen
business owner, ready knowledge, a measurable outcome and fits the Deliver phase.

| Quick win | Business owner (role) | Risk tier | Knowledge ready | Baseline captured | Effort fits Deliver | Selected |
|---|---|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 8. Dependencies

| Dependency | Owner outside the CoE (role) | Needed by | Status | Impact if late |
|---|---|---|---|---|
| [To confirm: for example approved-use guidance] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| [To confirm: for example maker environments ready] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| [To confirm: for example security review capacity for tier 2] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 9. Launch risks

| Risk | Likelihood | Impact | Mitigation | Owner (role) |
|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 10. Communications moments

| Moment | Audience | Message | Voice (role) | Planned date |
|---|---|---|---|---|
| CoE launch announcement (end of Foundation) | [To confirm] | [To confirm: how to bring an idea and what happens next] | [To confirm: executive sponsor] | [To confirm] |
| First quick win live | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| First value review result | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 11. Phase decision log

| Phase boundary | Date | Decision (go / hold) | Conditions | Deciding role | New review date if hold |
|---|---|---|---|---|---|
| Establish to Foundation | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Foundation to Deliver | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Deliver to Scale | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |

## 12. Sign-off

| Role | Decision | Date |
|---|---|---|
| [To confirm: executive sponsor role] | Agreed / Agreed with conditions | [To confirm] |
| [To confirm: CoE lead role] | Agreed | [To confirm] |

> Credit: Template from CopilotForge by Simon Foote (https://github.com/SimonFoote-greensparx/CopilotForge), licensed under CC BY 4.0. Keep this credit when you share or adapt the template; in your own completed document you may keep it as a footer or remove it.