Ceritakne babagan kegagalan tim utawa proyek sing sampeyan tanggung jawab.

Question

Accepted Answer

Iki ngetesake **akuntabilitas lumaur saka tugas dhewe** — tanggung jawab kanggo hasil sing disinaoni tinimbang nuding satus liya. Gunakake "aku" kanggo aksi dhewe lan "kita" kanggo tim, nanging aja ngalihake salah.

## Carane ngadhepi

```text
1. Describe the failure honestly and your part in it
2. Resist blaming individuals — own the system or the call
3. Explain what you did to recover and to prevent it
4. Show the lasting change
```

## Tuladha sing bener

```text
S: A feature we shipped tanked a key metric and had to be rolled back.
T: As the senior IC on it, I felt responsible for the outcome.
A: Instead of pointing at the unclear spec, I owned that I hadn't pushed for an
   A/B test. I ran a blameless retro, we added experiment gates for risky
   changes, and I re-launched a tested version.
R: The re-launch moved the metric the right way. Experiment gates are now
   standard for the team.
```

## Apik versus lemah

```text
✓ Owns the shared outcome, fixes the system
✗ "The PM gave us bad requirements"
✗ Owning so much it sounds like you alone failed
```

## Kenapa penting

Tanggung jawab kanggo kegagalan disinaoni — dudu mung sing pribadi — minangka tandha saka perilaku senior.

Mbeneri sistem tinimbang nyalahake wong iki sing bener-bener nyegah kegagalan sabanjure.

Para pamimpin nggoleki wong sing lari *menyang* masalah lan akuntabilitas, dudu adoh saka bab kasebut.