Year-2 Roadmap
Sets Year-2 priorities and the partnership model that fits them, whether renew at the same level, accelerate or step down to managed operations.
What this is for
Year 1 builds the foundation: departments live, governance proven, your own CoE in place. Year 2 decides what that foundation is for. This roadmap sets the priorities for the next twelve months (more departments, deeper autonomy, more orchestration, customer-facing Clones, broader AI and IT work) and chooses the partnership model that fits them. Your team decides; the evidence from the Year-1 Impact Report informs the decision.
When to use it
Draft it in Month 11 with the CoE lead, using the Year-1 Impact Report and the CoE's intake backlog. Decide it at the Month 12 quarterly business review. Revisit it at each Year-2 quarterly review.
Who's involved
- Executive sponsor decides.
- CoE lead co-authors and will own most of the execution.
- Steering committee and business owners set department priorities.
- InfoSec lead confirms the governance implications of deeper autonomy.
- Solutions Partner facilitates and recommends a model.
How to fill it in
- Start from the Year-1 Impact Report: targets met, gaps and the self-sufficiency assessment.
- Build the Year-2 opportunity list from the CoE intake backlog, departments not yet live and workflows ready to promote (section 2). Score them with the opportunity rubric.
- Set Year-2 targets (section 3).
- Decide what your team owns and where you still want help (section 4).
- Compare the three partnership options against your priorities and capacity (section 5). Scope and commercial terms are agreed separately and scoped to your organization.
- Lay out the quarterly plan (section 6) and the decisions needed (section 7).
The template
1. Starting point
| Field | Entry |
|---|---|
| Departments live | 7 |
| Workflows at Execute with approval or higher | 58% |
| Workflows at Execute within limits or Orchestrate | 21% |
| CoE maturity (from self-sufficiency assessment) | Runs intake, governance and most builds; complex integrations still paired |
| Biggest Year-1 gaps | HR provisioning below target; customer-facing Clones not yet live |
2. Year-2 opportunities
| # | Opportunity | Type | Department(s) | Score | Quarter | Who leads |
|---|---|---|---|---|---|---|
| 1 | Customer intake by phone and SMS | Customer-facing Clone | Support, Sales | 4.5 | Q1 | Clone team with CoE |
| 2 | Procure-to-pay orchestration | Orchestration (Commander) | Procurement, Finance | 4.2 | Q2 | CoE with Clone team |
| 3 | Legal contract intake | New department | Legal | 3.8 | Q2 | CoE |
| 4 | Consolidate enterprise chat assistants under the AI Use Policy | Broader AI & IT | IT | 3.5 | Q3 | IT + Clone team |
Types: new department · deeper autonomy · orchestration · customer-facing Clone · custom skills and integration · broader AI and IT · optimization.
3. Year-2 targets
| Target | Year-1 result | Year-2 goal |
|---|---|---|
| Departments live | 7 | 10 |
| Workflows at Execute with approval or higher | 58% | 75% |
| Workflows at Execute within limits or Orchestrate | 21% | 40% |
| Governance incidents above agreed severity | 0 | 0 |
| Skills built by client builders | 6 | Most new skills |
| Hours given back per week (run rate) | 410 | |
| Department-specific outcomes |
4. Ownership split
| Capability | Your team | Clone Solutions |
|---|---|---|
| Intake and prioritization | Own | Advise at quarterly review |
| New department rollouts | ||
| Complex custom skills and integrations | ||
| Orchestration design | ||
| Governance and audit evidence | ||
| Training and Champions | ||
| Monitoring and optimization (CloneOps) | ||
| Executive advisory and roadmap |
5. Partnership options
Choose the model that fits the plan above. Scope and terms are scoped to your organization and agreed separately.
| Renew at the same level | Accelerate | Step down to managed operations | |
|---|---|---|---|
| Best when | The Year-2 plan is similar in pace to Year 1 and you want continued embedded delivery | You want more departments, orchestration or customer-facing Clones faster than Year 1 | Your CoE runs intake, builds and governance, and you mainly want the platform kept healthy and improving |
| Parallel department rollouts | 2, as in Year 1 | 3–4 | Led by your CoE |
| Clone team | Same embedded team mix | Additional implementer capacity | Lighter team focused on CloneOps |
| What continues | Steering, rollouts, custom skills, GRC, change management, CloneOps | Everything in renew, plus deeper integration and orchestration capacity | Clone Health monitoring, Power Rating and usage reviews, optimization, skill upgrades, quarterly advisory |
| Your team's role | Co-delivers; CoE grows | Co-delivers at higher volume | Leads delivery |
| Readiness signals | Self-sufficiency assessment mostly "yes"; runbooks verified; builders shipping | ||
| Fit for our plan (1–5) |
Recommendation and rationale:
Example: Step down to managed operations from Q2, after a Q1 at the same level to launch customer-facing intake. Our CoE already runs intake and most builds, and the remaining complex work fits a lighter model.
6. Quarterly plan
| Quarter | Priorities | Milestones | Owner |
|---|---|---|---|
| Q1 | |||
| Q2 | |||
| Q3 | |||
| Q4 |
7. Decisions
| # | Decision | Options | Recommendation | Decision | Date |
|---|---|---|---|---|---|
| 1 | Partnership model for Year 2 | Renew / Accelerate / Managed operations | |||
| 2 | Year-2 priority list | ||||
| 3 | Year-2 targets |
Good looks like
- Priorities come from evidence: Year-1 results, the CoE backlog and workflows ready for promotion.
- The ownership split is honest about what your team can carry, which drives the partnership choice.
- Stepping down is treated as a success when the CoE is ready. That was the point of Year 1.
- Deeper autonomy goals come with the governance plan to support them.
- Targets carry forward the Year-1 definitions so progress stays comparable.
- Common mistake: choosing the model first and fitting the plan to it. Plan first, then choose.
How Clone helps
The Solutions Architect Clone drafts the opportunity list from the CoE intake backlog, autonomy history and Systems & Workflow Map, and scores it with the opportunity rubric. The Project Clone builds the quarterly plan and carries the agreed roadmap into the portal as the Year-2 plan. The GRC Clone flags governance work needed for the autonomy targets.
Sign-off
| Role | Name | Date | Decision |
|---|---|---|---|
| Executive sponsor | Roadmap approved; model chosen: ______ | ||
| CoE lead | Accepted | ||
| InfoSec lead | Governance plan agreed | ||
| Solutions Partner | Issued |