Kako se lotite, ko so zahteve nejasne?

Question

Accepted Answer

Negotovost je norma pri resničnem delu. Želijo si videti, da **aktivno zmanjšujete negotovost**, namesto da bi se ustavili ali tiho ugibali in zgradili napačno stvar.

## Kako se lotiti

```text
1. Ask the questions that change what you'd build
2. Find the goal behind the request (the "why")
3. State your assumptions in writing and confirm them
4. Build a thin slice, demo early, adjust fast
```

## Delujoči primer

```text
S: A ticket said "add a dashboard" with no detail on metrics or users.
T: Building blind risked weeks of wasted work.
A: I asked who'd use it and what decision it drove, wrote down three assumptions,
   and built a clickable prototype of the top two metrics first.
R: The demo surfaced that they actually needed exports, not charts. We pivoted
   after two days instead of two weeks.
```

## Dobro proti šibkemu

```text
✓ Clarifies the "why," states assumptions, demos early
✗ Building the full thing on a guess
✗ Refusing to start until everything is spec'd
```

## Zakaj je to pomembno

Jasne specifikacije so redke; inženirji, ki uspevajo, so tisti, ki znajo delati skozi meglo.

Najdba osnovnega cilja vas preprečuje pred tem, da bi zgradili natanko tisto, kar je bilo zahtevano, toda ne tisto, kar je bilo potrebno.

Prikaz tanke plasti zgodaj spremeni drage ugibe v poceni, hitre popravke.