Opovijedi mi o neuspjehu tima ili projekta u kojem si preuzeo/a odgovornost.

Question

Accepted Answer

Ovo testira **odgovornost izvan vlastitih zadataka** — preuzimanje dijeljene odgovornosti umjesto okrivljavanja drugih. Koristi "ja" za svoje akcije i "mi" za tim, ali nemoj umanjiti vlastitu odgovornost.

## Kako pristupiti problemu

```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
```

## Praktični primjer

```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.
```

## Dobro nasuprot slabom

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

## Zašto je to važno

Odgovornost za dijeljene neuspjehe — ne samo osobne — je oznaka iskusnog ponašanja.

Ispravljanje sustava umjesto krivljenja osobe je ono što zapravo sprječava sljedeći neuspjeh.

Vođe traže ljude koji trče *prema* problemima i odgovornosti, a ne od njih.