MVP Boundary
MVP 邊界
One user group, one trigger, two or three data sources, one reviewable output.
一個使用者群、一個觸發情境、兩到三個資料來源、一種可檢查輸出。
Unit 6 | 14:50-15:35
Group Design Workshop II: MVP, Risk, and ROI
小組設計工作坊 II：MVP、風險與 ROI
The second workshop block makes the idea smaller, safer, and measurable. A useful MVP creates evidence for the next decision.
第二段工作坊要把構想縮小、變安全、變得可衡量。好的 MVP 會為下一個決策產生依據。
MVP Discipline
The first version should be small enough to test honestly.
第一版要小到可以誠實測試。
A large AI platform proposal often hides weak assumptions. A small MVP reveals whether the data exists, whether users trust the output, and whether review costs are acceptable.
大型 AI 平台提案常常把脆弱假設藏起來。小型 MVP 才能看出資料是否存在、使用者是否信任輸出，以及審核成本是否可接受。
Risk Control
風險控管
State privacy limits, source checks, approval points, and what the agent cannot do.
寫出隱私限制、來源查核、核准點，以及 Agent 不能做的事。
ROI Signal
ROI 訊號
Measure time saved, error reduction, faster follow-up, or better decision readiness.
衡量節省時間、降低錯誤、加快追蹤，或提升決策準備度。
4-6 Week Roadmap
4-6 週導入路線
- Week 1: collect sample data and define review rules.
- Week 2: build a manual or semi-automated draft workflow.
- Week 3: run with a small user group.
- Week 4: compare baseline time, quality, and risk.
- Weeks 5-6: decide whether to expand, revise, or stop.
- 第 1 週：收集樣本資料並定義審核規則。
- 第 2 週：建立人工或半自動草稿流程。
- 第 3 週：讓小範圍使用者試跑。
- 第 4 週：比較原流程與新流程的時間、品質與風險。
- 第 5-6 週：決定擴大、修正或停止。
Presentation Standard
發表標準
The group has three minutes. Spend less time naming tools and more time explaining the process, review point, and business metric.
小組只有三分鐘。少講工具名稱，多講流程、審核點與商業指標。