# IL 302 — Enterprise AI Transformation Roadmap 提交檢查表 / Submission Checklist

## 中文

在提交 Enterprise AI Transformation Roadmap 前，請逐項確認：

- [ ] 投資組合分析涵蓋組織目前所有相關 AI 專案，且每個專案都有保留／停止／重新設計的建議與理由。
- [ ] 價值帳本清楚區分「容量釋放」與「實際現金效益」，沒有把估計工時直接乘上時薪就宣稱已實現效益。
- [ ] 系統與資料所有權都指定到具體角色或職位，不是只寫部門名稱，且附有交接程序。
- [ ] RACI 表中每一項活動的 Accountable 欄位都只有一個角色，沒有同一活動列出兩個以上的 Accountable。
- [ ] 已針對「換部門或擴散」的情境，逐項比較資料品質、流程、權限、採用意願、技能與成本六個面向的差異。
- [ ] 每項 90 天行動都填有負責人、到期日、依賴、資源、成功指標、證據來源與檢視日期七個欄位。
- [ ] 找不到負責人或資源的行動已明確標示為「未承諾」，沒有被寫得像是已經排定的計畫。
- [ ] 12 個月方向已明確區分「已規劃並有資源」與「仍待評估」的部分，並訂出檢視節奏與主持角色。
- [ ] 至少檢查過一次，是否把原部門的既有授權、流程或假設，未經檢驗就沿用到了新的部門或範圍（見 Module 3 範例）。
- [ ] 若為合成練習，已標明「合成練習，不等同正式專案」；若涉及真實企業策略與投資資訊，已依組織資料政策取得授權並視為敏感資料。
- [ ] Transformation Roadmap 內容視為敏感資料，僅存放於受管理位置並只分享給經授權人員。

## English

Before submitting an Enterprise AI Transformation Roadmap, confirm each of the following:

- [ ] The investment-portfolio analysis covers every relevant AI project the organization currently runs, and each project has a keep/stop/redesign recommendation with a rationale.
- [ ] The value ledger clearly separates capacity released from actual cash benefit, and does not claim a realized benefit by simply multiplying estimated hours by an hourly rate.
- [ ] System and data ownership are assigned to specific roles or positions, not just department names, with a stated handover procedure.
- [ ] Every activity in the RACI table has exactly one role in the Accountable column; no activity lists more than one Accountable.
- [ ] For any "move to a new department or scale out" scenario, data quality, process, access/permissions, adoption willingness, skill, and cost have all been compared between departments.
- [ ] Every 90-day action has an owner, due date, dependency, resource, success metric, evidence source, and review date: all seven fields.
- [ ] Any action with no findable owner or resource is explicitly marked "uncommitted," not written as if it were already scheduled.
- [ ] The 12-month direction clearly separates what is planned and resourced from what is still under evaluation, and states a review cadence and who runs it.
- [ ] You checked at least once whether the original department's existing authorization, process, or assumptions were carried over to a new department or scope without re-verification (see the Module 3 example).
- [ ] If this is a synthetic exercise, it states "synthetic exercise, not equivalent to a formal project"; if real company strategy or investment information is involved, it has been authorized per the organization's data policy and treated as sensitive.
- [ ] The Transformation Roadmap is treated as sensitive: stored only in managed locations and shared only with authorized people.