Contoh Percakapan Bahasa Inggris: Rapat evaluasi proyek (post-mortem)
B2Project post-mortem meeting
Situasi: Rapat post-mortem di kantor sebuah perusahaan e-commerce di Jakarta setelah promo besar 12.12. Website sempat down dua jam dan notifikasi promo terkirim satu jam lebih awal. Aiko, engineering manager asal Jepang, memfasilitasi rapat.
Peranmu: Reza, project manager promo 12.12 · Lawan bicara: Aiko (Engineering manager)
Target: Membahas apa yang salah dalam proyek dengan should have, could have, dan might have tanpa menyalahkan siapa pun, lalu menyepakati action item yang jelas.
Frasa penting
- Traffic was five times higher than we expected.Trafiknya lima kali lebih tinggi dari perkiraan kami.
- We should have run a proper load test.Seharusnya kita melakukan load test yang benar.
- We could have used last year's data.Sebenarnya kita bisa memakai data tahun lalu.
- The time zone might have been set incorrectly.Zona waktunya mungkin salah diatur.
- If we had tested earlier, we might have found the problem.Kalau kita menguji lebih awal, mungkin kita sudah menemukan masalahnya.
- Let's focus on the process, not on people.Mari fokus pada proses, bukan pada orang.
- What could we put in place to prevent this?Apa yang bisa kita terapkan untuk mencegah hal ini?
- I'll own the checklist and share it by Friday.Saya pegang checklist-nya dan bagikan paling lambat Jumat.
Contoh percakapan lengkap
- Aiko: Thanks for joining, everyone. Remember, this is a blameless post-mortem. Reza, could you start by summarizing what happened during the twelve twelve sale?Terima kasih sudah hadir, semuanya. Ingat, ini post-mortem tanpa saling menyalahkan. Reza, bisa mulai dengan merangkum apa yang terjadi saat promo 12.12?
- Kamu: Sure. The site went down for about two hours on the first night, when traffic was five times higher than we expected.
- Aiko: Thanks. Looking back, what do you think we could have done differently before the sale?Terima kasih. Kalau dilihat lagi, menurutmu apa yang sebenarnya bisa kita lakukan secara berbeda sebelum promo?
- Kamu: We should have run a proper load test. If we had, we might have found the problem earlier.
- Aiko: Agreed. There was also the push notification, which went out an hour earlier than planned. What happened there?Setuju. Ada juga push notification yang terkirim satu jam lebih awal dari rencana. Apa yang terjadi di situ?
- Kamu: The tool might have been set to Singapore time, which is one hour ahead. We should have double-checked it.
- Aiko: That makes sense. What else should we change before the next big sale?Masuk akal. Apa lagi yang perlu kita ubah sebelum promo besar berikutnya?
- Kamu: I'd suggest a load test two weeks before, a second person to check scheduled messages, and an on-call engineer during the sale.
- Aiko: Great. Who would like to own these action items, and by when?Bagus. Siapa yang mau bertanggung jawab atas action item ini, dan kapan tenggatnya?
- Kamu: I'll own the checklist and share a draft by next Friday. Could the infrastructure team take the load test?
- Aiko: Perfect. Let's make next Friday the deadline for the checklist. Thanks, everyone, this was a really useful discussion.Sempurna. Kita tetapkan Jumat depan sebagai tenggat checklist. Terima kasih semuanya, diskusi ini sangat bermanfaat.
Kamu membahas kegagalan proyek tanpa menyalahkan siapa pun, memakai should have, could have, dan might have dengan tepat, lalu menutup rapat dengan action item yang jelas.
Jawaban mana yang paling pas, dan kenapa
Aiko: Thanks for joining, everyone. Remember, this is a blameless post-mortem. Reza, could you start by summarizing what happened during the twelve twelve sale?
✓ Sure. The site went down for about two hours on the first night, when traffic was five times higher than we expected.
Ringkasan faktual: apa yang terjadi, berapa lama, dan kenapa. Tidak ada nama yang disalahkan, sesuai semangat blameless.
✗ The website was down two hours because too many traffic. (Bisa dipahami, tapi kurang pas)
Traffic tidak bisa dihitung, jadi pakai too much traffic. Lebih lengkap: The site was down for two hours because traffic was much higher than expected.
✗ Basically, the IT team made a big mistake. They didn't prepare the servers, so the website crashed in the middle of the sale. (Kurang tepat)
Langsung menyalahkan satu tim melanggar prinsip blameless. Fokus pada fakta: The site went down for two hours when traffic spiked.
Aiko: Thanks. Looking back, what do you think we could have done differently before the sale?
✓ We should have run a proper load test. If we had, we might have found the problem earlier.
Should have, third conditional (If we had...), dan might have dipakai tepat dalam dua kalimat. Pelajarannya jelas, dan tidak ada nama yang disalahkan.
✗ We should do load test before the sale. (Bisa dipahami, tapi kurang pas)
Untuk penyesalan di masa lalu pakai should have + V3: We should have done a load test before the sale.
✗ Honestly, nothing. It was just bad luck. Nobody can predict traffic, especially during a big sale with so many promos at the same time. (Kurang tepat)
Menyebut bad luck membuat tim tidak belajar apa pun. Coba: We should have run a load test before the sale.
Aiko: Agreed. There was also the push notification, which went out an hour earlier than planned. What happened there?
✓ The tool might have been set to Singapore time, which is one hour ahead. We should have double-checked it.
Might have been pas untuk dugaan tentang masa lalu, lalu should have untuk pelajarannya. Fokusnya ke pengaturan alat, bukan ke orang.
✗ Maybe the setting of the time zone is wrong. I'm not sure yet. (Bisa dipahami, tapi kurang pas)
Untuk dugaan tentang masa lalu pakai might have been: The time zone might have been set incorrectly.
✗ Ask the marketing team. Dinda sent it, not me. (Kurang tepat)
Menyebut nama dan melempar ke orang lain bertentangan dengan semangat blameless. Fokus ke proses: The time zone might have been set incorrectly.
Aiko: That makes sense. What else should we change before the next big sale?
✓ I'd suggest a load test two weeks before, a second person to check scheduled messages, and an on-call engineer during the sale.
Tiga usulan konkret dalam satu kalimat, dan masing-masing bisa langsung dijadikan action item.
✗ Next time we must to make the load test two weeks before, and also check the notification double before we send it to customers. (Bisa dipahami, tapi kurang pas)
Must tidak diikuti to, dan check double terjemahan harfiah: Next time we must do a load test and double-check the notifications.
✗ Next time just make sure nobody makes mistakes. (Kurang tepat)
Tidak realistis dan tidak bisa ditindaklanjuti. Usulkan langkah konkret: a load test, a second reviewer, and an on-call engineer.
Latihan langsung, gratis
Di aplikasi, kamu yang menjawab: pilih balasan, ucapkan dengan suaramu, dan lihat bagaimana percakapan berubah. Gratis dan bisa offline.
Buka latihan di aplikasi