Fortæl mig om et hold- eller projektsvigt, du tog ejerskab over.

Question

Accepted Answer

Dette tester **ansvarlighed ud over dine egne opgaver** — at eje et delt resultat i stedet for at pege på andre. Brug "jeg" for dine handlinger og "vi" for holdet, men undvik ikke at påtage dig skyld.

## Sådan tilgår du det

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

## Praktisk eksempel

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

## Godt vs svagt

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

## Hvorfor det betyder noget

Ejerskab af delte fiaskoer — ikke bare personlige — er et kendetegn ved senioriumadfærd.

At reparere systemet i stedet for at bebrejde en person er det, der faktisk forhindrer næste svigt.

Ledere leder efter mennesker, der løber *mod* problemer og ansvarlighed, ikke væk fra dem.