Povedaj mi o času, ko si prepričal svojo ekipo, da sprejme tvoj pristop.

Question

Accepted Answer

To preverja **tehnično prepričljivost**: ali lahko predstaviš primer z dokazi in prepričaš ljudi, medtem ko ostaneš odprt za možnost, da se motiš? Prepričevanje ni zmaga v argumentu.

## Kako se lotiti

```text
1. State the problem and the criteria for a good solution first
2. Present options fairly, including the team's preferred one
3. Back your choice with data, a spike, or a small benchmark
4. Invite critique — adjust if they find a real flaw
```

## Praktičen primer

```text
S: The team planned to build a custom job queue; I thought we should use an
   existing tool.
T: I had to make the case without dismissing their work.
A: I listed our actual requirements, built a one-day spike with the off-the-shelf
   tool, and showed it met every need with far less code to maintain.
R: The team agreed, and we shipped two weeks earlier. I noted the one case where
   their concern was valid and we documented the workaround.
```

## Dobro proti šibkemu

```text
✓ Evidence + fair comparison + open to critique
✗ "I argued until they gave up"
✗ Pushing your idea with no proof
```

## Zakaj je to pomembno

Dobre odločitve potrebujejo podporo; odličnih idej, ki jih nihče ne sprejme, se nič ne spremeni.

Vodenje s kriteriji in dokazi ohranja fokus na najboljši rezultat, ne na to, čigava je bila ideja.

Genuina odprtost za možnost, da se motiš, je tisto, kar naredi, da ljudje naslednjič zaupajo tvojim zaključkom.