Hvordan handler du, når kravene er uklare?

Question

Accepted Answer

Tvetydighed er normen i rigtigt arbejde. De ønsker at se dig **aktivt reducere usikkerhed** i stedet for at fryse eller gætte stiltiende og bygge det forkerte.

## Sådan griber du det an

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

## Arbejdet eksempel

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

## Godt vs svagt

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

## Hvorfor det betyder noget

Klare specifikationer er sjældne; de ingeniører, der trives, er dem, der kan bevæge sig gennem tågen.

At finde det underliggende mål forhindrer dig i at bygge nøjagtigt hvad der blev bedt om, men ikke hvad der var behov for.

At demonstrere en tynd slice tidligt gør dyre gæt til billige, hurtige rettelser.