TemplateDepartment 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
- Pull the department's problem statements, workflow maps and scored opportunities from the portal.
- Pick the opportunities for this cycle. Two or three is typical for six weeks; more usually means none finish well.
- For each, propose a Clone role and a build path: Marketplace template first, configuration second, custom skill only where needed.
- Set the starting autonomy level per workflow, using the risk score.
- List the baseline metrics to capture this week and next.
- Name the champion and pilot users.
- Review with the business owner and champion. Get approval before Design starts.
#The template
#1. Department at a glance
| Field | Entry |
|---|
| Department | |
| Rollout cycle | Cycle # · Weeks to of the engagement |
| Business owner | |
| Champion | |
| Pilot users (3–5) | |
| Team size | |
| Key systems | |
#2. Problems in scope
| Problem ID | Problem statement (short) | Executive owner | Priority score |
|---|
| | | |
| PS-004 | AP invoice-to-PO matching takes ~18 min per invoice for ~2,400 invoices/month | VP Finance | 73 |
Out of scope this cycle (and why): e.g. vendor onboarding, which depends on a supplier portal change.
#3. Opportunities and proposed Clones
| Opportunity | Proposed Clone (role) | Build path | Starting autonomy | Target autonomy this year | Key systems | Custom skill needed? |
|---|
| | Marketplace template / Configure / Custom | | | | |
| OP-09 Invoice matching | AP Matching Clone (AP specialist role) | Configure + 1 custom skill | Recommend | Execute within limits | ERP, shared AP inbox | Yes: ERP three-way match lookup |
| OP-11 Vendor inquiry replies | AP Matching Clone | Configure | Assist | Execute with approval | Shared AP inbox, ERP | No |
#4. How the work will change
| Today | With Clones | Stays with people |
|---|
| | |
| Specialist opens each email, finds PO, keys invoice | Clone reads invoice, finds PO and receipt, proposes match with evidence | Specialist confirms; supervisor approves variances over tolerance |
#5. Metrics and baseline
| Metric | Baseline (or capture plan) | Target after launch | Source |
|---|
| | | |
| Handling time per invoice | Time sample this week, 3 specialists | < 7 min | Time sample, then platform data |
#6. Knowledge and data readiness
| Knowledge or data | Location | Owner | Ready? | Action before Build |
|---|
| | | Yes / Partial / No | |
| Tolerance policy | File share | Controller | Partial | Controller approves one version by Week 2 |
#7. Dependencies and risks
| Item | Type (Connection / Data / People / Other) | Owner | Needed by |
|---|
| | | |
| ERP service account with read + match-status write | Connection | ERP admin | Week 3 |
#8. Plan for this cycle
| Week | Stage | Key activity | Exit criterion |
|---|
| 1 | Discover | Problems, workflow maps, baseline started, champion named | This brief approved |
| 2 | Design | Clone Design Spec, connections approved by InfoSec | Design Spec + InfoSec approval |
| 3–4 | Build | Deploy, load knowledge, connect, configure skills, test | All test scenarios pass |
| 4–5 | Pilot | Champion + pilot users, daily feedback | Pilot thresholds met |
| 5–6 | Launch | Department training and communications | Live; 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
| Role | Name | Date | Decision |
|---|
| Business owner | | | Approved / Approved with changes |
| Champion | | | Committed |
| Solutions Partner | | | Aligned with roadmap |