Clone Solutions
Template

Department Opportunity Brief

A two-page brief that closes the Discover week of a department rollout: the problems, workflows, Clones, metrics and champion, approved to proceed.

What this is for

Every department rollout starts with a short, firm agreement on what this department will get and how success will be judged. The brief pulls together the department's problem statements, the workflows mapped in Discover, the opportunities chosen for this cycle, the proposed Clones, the baseline metrics and the named champion. Its approval is the exit criterion for Discover. Nothing is designed until the business owner has signed it.

When to use it

At the end of Week 1 (Discover) of each department rollout cycle. One brief per department, per cycle. If a department comes back for a second cycle, write a new brief.

Who's involved

  • Business owner: approves scope and owns the outcome.
  • Champion: confirms the plan is workable for the team and commits time.
  • Implementation Engineer: drafts the build approach.
  • Solutions Partner: checks fit with the roadmap and steering priorities.
  • InfoSec lead: sees the brief early so connections can be reviewed in Design week.

How to fill it in

  1. Pull the department's problem statements, workflow maps and scored opportunities from the portal.
  2. Pick the opportunities for this cycle. Two or three is typical for six weeks; more usually means none finish well.
  3. For each, propose a Clone role and a build path: Marketplace template first, configuration second, custom skill only where needed.
  4. Set the starting autonomy level per workflow, using the risk score.
  5. List the baseline metrics to capture this week and next.
  6. Name the champion and pilot users.
  7. Review with the business owner and champion. Get approval before Design starts.

The template

1. Department at a glance

FieldEntry
Department
Rollout cycleCycle # · Weeks to of the engagement
Business owner
Champion
Pilot users (3–5)
Team size
Key systems

2. Problems in scope

Problem IDProblem statement (short)Executive ownerPriority score
PS-004AP invoice-to-PO matching takes ~18 min per invoice for ~2,400 invoices/monthVP Finance73

Out of scope this cycle (and why): e.g. vendor onboarding, which depends on a supplier portal change.

3. Opportunities and proposed Clones

OpportunityProposed Clone (role)Build pathStarting autonomyTarget autonomy this yearKey systemsCustom skill needed?
Marketplace template / Configure / Custom
OP-09 Invoice matchingAP Matching Clone (AP specialist role)Configure + 1 custom skillRecommendExecute within limitsERP, shared AP inboxYes: ERP three-way match lookup
OP-11 Vendor inquiry repliesAP Matching CloneConfigureAssistExecute with approvalShared AP inbox, ERPNo

4. How the work will change

TodayWith ClonesStays with people
Specialist opens each email, finds PO, keys invoiceClone reads invoice, finds PO and receipt, proposes match with evidenceSpecialist confirms; supervisor approves variances over tolerance

5. Metrics and baseline

MetricBaseline (or capture plan)Target after launchSource
Handling time per invoiceTime sample this week, 3 specialists< 7 minTime sample, then platform data

6. Knowledge and data readiness

Knowledge or dataLocationOwnerReady?Action before Build
Yes / Partial / No
Tolerance policyFile shareControllerPartialController approves one version by Week 2

7. Dependencies and risks

ItemType (Connection / Data / People / Other)OwnerNeeded by
ERP service account with read + match-status writeConnectionERP adminWeek 3

8. Plan for this cycle

WeekStageKey activityExit criterion
1DiscoverProblems, workflow maps, baseline started, champion namedThis brief approved
2DesignClone Design Spec, connections approved by InfoSecDesign Spec + InfoSec approval
3–4BuildDeploy, load knowledge, connect, configure skills, testAll test scenarios pass
4–5PilotChampion + pilot users, daily feedbackPilot thresholds met
5–6LaunchDepartment training and communicationsLive; baseline vs. actual tracked

9. Approval checklist

  • Problems in scope have confirmed problem statements
  • Champion named and has agreed time (suggest 2–4 hours a week during the cycle)
  • Pilot users named
  • Baseline capture is under way
  • Connections needed are listed for InfoSec review in Design week
  • Out-of-scope items recorded

Good looks like

  • Two or three opportunities, finished, rather than six started.
  • Marketplace first. Custom skills are justified, not assumed.
  • "Stays with people" is filled in. It answers the team's first question and shapes the governance record.
  • The champion has time, agreed with their manager, not just a title.
  • Common mistake: skipping the baseline because "we already know it's slow." Capture it now or the results report will have no before.

How Clone helps

The Solutions Architect Clone drafts the brief from the department's problem statements, workflow maps and opportunity scores, and proposes Marketplace templates that match each opportunity. The Project Clone turns the cycle plan into tasks and tracks the exit criterion. In the portal, the brief is the Department Opportunity Brief deliverable for that department's rollout; approval unlocks the Design stage.

Sign-off

RoleNameDateDecision
Business ownerApproved / Approved with changes
ChampionCommitted
Solutions PartnerAligned with roadmap