当需求不清楚时，你如何继续进行？

Question

当需求不清楚时，你如何继续进行？

Accepted Answer

模糊是真实工作中的常态。他们想看到你**主动降低不确定性**，而不是冻结或默默猜测，然后构建错误的东西。

## 如何处理

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

## 实际例子

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

## 好的与薄弱

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

## 为什么这很重要

清晰的规格很少见；蓬勃发展的工程师是那些能够在雾中穿行的人。

找到潜在目标可以防止你构建确切要求的东西，但不是真正需要的东西。

早期演示薄片可以将昂贵的猜测变成廉价、快速的更正。