La ambigüedad es la norma en el trabajo real. Quieren ver que reduces la incertidumbre activamente en lugar de quedarte paralizado o adivinar en silencio y construir la cosa equivocada.
Por qué es importante
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
Ejemplo práctico
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.