Clone Solutions
Template

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

  1. Start from the Year-1 Impact Report: targets met, gaps and the self-sufficiency assessment.
  2. 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.
  3. Set Year-2 targets (section 3).
  4. Decide what your team owns and where you still want help (section 4).
  5. Compare the three partnership options against your priorities and capacity (section 5). Scope and commercial terms are agreed separately and scoped to your organization.
  6. Lay out the quarterly plan (section 6) and the decisions needed (section 7).

The template

1. Starting point

FieldEntry
Departments live7
Workflows at Execute with approval or higher58%
Workflows at Execute within limits or Orchestrate21%
CoE maturity (from self-sufficiency assessment)Runs intake, governance and most builds; complex integrations still paired
Biggest Year-1 gapsHR provisioning below target; customer-facing Clones not yet live

2. Year-2 opportunities

#OpportunityTypeDepartment(s)ScoreQuarterWho leads
1Customer intake by phone and SMSCustomer-facing CloneSupport, Sales4.5Q1Clone team with CoE
2Procure-to-pay orchestrationOrchestration (Commander)Procurement, Finance4.2Q2CoE with Clone team
3Legal contract intakeNew departmentLegal3.8Q2CoE
4Consolidate enterprise chat assistants under the AI Use PolicyBroader AI & ITIT3.5Q3IT + Clone team

Types: new department · deeper autonomy · orchestration · customer-facing Clone · custom skills and integration · broader AI and IT · optimization.

3. Year-2 targets

TargetYear-1 resultYear-2 goal
Departments live710
Workflows at Execute with approval or higher58%75%
Workflows at Execute within limits or Orchestrate21%40%
Governance incidents above agreed severity00
Skills built by client builders6Most new skills
Hours given back per week (run rate)410
Department-specific outcomes

4. Ownership split

CapabilityYour teamClone Solutions
Intake and prioritizationOwnAdvise 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 levelAccelerateStep down to managed operations
Best whenThe Year-2 plan is similar in pace to Year 1 and you want continued embedded deliveryYou want more departments, orchestration or customer-facing Clones faster than Year 1Your CoE runs intake, builds and governance, and you mainly want the platform kept healthy and improving
Parallel department rollouts2, as in Year 13–4Led by your CoE
Clone teamSame embedded team mixAdditional implementer capacityLighter team focused on CloneOps
What continuesSteering, rollouts, custom skills, GRC, change management, CloneOpsEverything in renew, plus deeper integration and orchestration capacityClone Health monitoring, Power Rating and usage reviews, optimization, skill upgrades, quarterly advisory
Your team's roleCo-delivers; CoE growsCo-delivers at higher volumeLeads delivery
Readiness signalsSelf-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

QuarterPrioritiesMilestonesOwner
Q1
Q2
Q3
Q4

7. Decisions

#DecisionOptionsRecommendationDecisionDate
1Partnership model for Year 2Renew / Accelerate / Managed operations
2Year-2 priority list
3Year-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

RoleNameDateDecision
Executive sponsorRoadmap approved; model chosen: ______
CoE leadAccepted
InfoSec leadGovernance plan agreed
Solutions PartnerIssued