Povej mi o neuspešnem projektu ali timskem neuspešku, za katerega si prevzel odgovornost.

Question

Accepted Answer

To preizkuša **odgovornost onkraj svojih nalog** — prevzem skupnega rezultata namesto da kažeš na druge. Uporabi »jaz« za svoja dejanja in »mi« za tim, vendar ne prehajaj blame.

## Kako se lotiti

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

## Delujoči primer

```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 vs šibko

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

## Zakaj je to pomembno

Odgovornost za skupne neuspehe — ne le osebne — je značilnost starejšega vedenja.

Popravitev sistema namesto okrivljanja osebe je tisto, kar dejansko preprečuje naslednji neuspeh.

Vodilni ljudje iščejo ljudi, ki tečejo *k* problemom in odgovornosti, ne stran od njih.