BA tidak hanya analisis — tapi advocate untuk perubahan. Pelajari cara bangun business case yang convincing, ROI calculation, executive summary, dan struktur report yang dibaca manajemen.
Business case = dokumen yang menjelaskan kenapa sebuah inisiatif/proyek harus didanai. Memuat: problem, solusi, biaya, manfaat, risiko, timeline. Tanpa business case kuat, ide bagus tetap parkir di file Drive.
| Section | Konten |
|---|---|
| 1. Executive Summary | 1 halaman: problem + recommendation + impact + ask |
| 2. Background & Problem | Konteks, current state, masalah yang harus di-solve |
| 3. Proposed Solution | Apa yang ingin dilakukan, scope, deliverables |
| 4. Expected Benefits | Quantitative (revenue, cost saving) + qualitative (brand, team) |
| 5. Cost & Investment | Hard cost (tools, vendor) + soft cost (staff time, opportunity) |
| 6. Financial Analysis | ROI, NPV, IRR, payback period, sensitivity |
| 7. Risk Analysis | Potential risks + mitigation plans |
| 8. Timeline & Milestones | Phased rollout, key checkpoints |
| 9. Alternative Considered | Pilihan lain & kenapa tidak dipilih (showing rigor) |
| 10. Recommendation & Ask | Decision yang ingin diminta + budget allocation |
ROI = (Net Benefit / Cost) × 100%Net Benefit = Total Benefit - Total Cost
Payback = Initial Investment / Annual Cash FlowNPV = Σ (Cash Flow_t / (1+r)^t) − Initial Investmentr yang membuat NPV = 0Project layak kalau: NPV > 0, IRR > cost of capital, payback < threshold (biasanya 2-3 tahun untuk corporate). Pakai semua sebagai perspektif.
"What if asumsi salah?" — pertanyaan klasik dari CFO. Sensitivity analysis = ubah 1 variable, lihat dampak ke ROI.
Base case: Revenue +15%, ROI 320%.
Optimistic: Revenue +25%, ROI 580%.
Pessimistic: Revenue +5%, ROI 80%.
Worst case: Revenue +0%, ROI -30%.
Sajikan 3-4 skenario. Stakeholder appreciate intellectual honesty > over-promise.
CEO/CFO/COO baca executive summary dulu. Kalau tidak menarik, sisa 30 halaman tidak dibaca. Wajib mengandung: problem (1 sentence), recommendation (1 sentence), impact (1 number), cost (1 number), ask (1 decision). 1 minute pitch.
SITUATION: [konteks 1-2 kalimat]PROBLEM: [pain point + cost dampak]SOLUTION: [proposal singkat]BENEFIT: [Revenue / saving / efficiency]INVEST: [budget Rp X, payback Y months]RISK: [3 risiko utama + mitigasi]ASK: [decision yang dibutuhkan, deadline]
| Report | Frekuensi | Audience | Fokus |
|---|---|---|---|
| Daily Snapshot | Harian | Operations team | Real-time KPI, alerts |
| Weekly Update | Mingguan | Manager | Performance vs target, action items |
| Monthly Review | Bulanan | Director | Trend, deep-dive, learnings |
| Quarterly Business Review | 3-bulanan | VP / C-Suite | Strategic, OKR progress |
| Annual Plan | Tahunan | Board | Yearly roadmap, budget |
1. Over-engineering analysis. Jangan habiskan 3 minggu untuk analysis yang akan jadi 1 slide.
2. No clear ask. Stakeholder bingung apa yang harus dilakukan.
3. Cherry-picking data. Confirmation bias. Audit dengan team sebelum present.
4. Ignoring counter-argument. Address objection up-front.
5. Tidak ada follow-up. Track post-implementation, share hasilnya.
Sebuah BUMN besar Indonesia. Tim BA temukan inefisiensi di supply chain — barang stuck 3-5 hari di transit center. Mereka bangun business case investasi WMS (Warehouse Management System) Rp 25M dengan ROI 4× di tahun ke-2. Disetujui dalam 1 meeting karena exec summary clear: "WMS akan reduce transit time 60%, save Rp 100M/tahun, payback 3 bulan." Pelajaran: data + clear narrative = funded.