Post-Launch Feedback Loop¶
Last verified: 2026-06-11
1. Alur Support → Dokumentasi¶
flowchart LR
Ticket[Support Ticket] --> Triage[Triage L1]
Triage --> Known{Ada di FAQ?}
Known -->|Ya| FAQ[Update FAQ jika perlu]
Known -->|Tidak| Runbook[Cek troubleshooting index]
Runbook --> Gap{Gap produk?}
Gap -->|Ya| MASTER[MASTER-GAP-REGISTER]
Gap -->|Tidak| Close[Tutup ticket]
MASTER --> Dev[Backlog dev]
FAQ --> Portal[Sync portal end user]2. Ritme Operasional¶
| Aktivitas | Frekuensi | Owner |
|---|---|---|
| Review ticket support | Harian | Business support |
| Update FAQ | Mingguan | Technical writer |
| Sync portal dari repo | Mingguan | Implementor |
| Changelog deployment | Per release | Dev + implementor |
| Re-audit domain | Per major release / upgrade tier | Tech lead |
3. Kriteria Eskalasi ke Dev¶
- Data integrity / security
- Workflow inti tidak bisa diselesaikan
- Error 500 berulang pada API domain
- Ketidaksesuaian FE-BE permission
Template eskalasi: sertakan domain audit ID dari MASTER-GAP-REGISTER
4. Upgrade Tier (P2 Audit)¶
Saat klien menambah paket:
| Add-on | Domain audit |
|---|---|
| SC-FIN | keuangan (akuntansi penuh) |
| SC-OPS | inventaris |
| SC-PEOPLE | hr |
| SC-STUDENT | kesiswaan / BK |
| SC-DAP | integrasi-regulasi |
| SC-FOUND | governance |
Jalankan audit template untuk domain baru sebelum aktivasi produksi.