Hands-on: Requirements interviews

The most common mistake: the BA shows up with closed questions, ticks them off, and leaves with „requirements” that fall apart at implementation. Truth is, the stakeholder never told them — because they didn't feel safe saying what they didn't know.

Setup: the first 3 minutes decide everything

• Relatedness first. Genuine small talk, not mechanical „how was your weekend?”. Something specific from their context.
• Status protected. Openly say: „I don't expect you to have all answers. I want to understand together with you”.
• Autonomy. „How much time do you have? We can finish early if we cover what's needed.”
• Certainty. „Plan: 1) how you work today, 2) what frustrates you, 3) what „perfect” looks like. ~30 min.”

Questions that open (vs. those that close)

Închise (provocă defensivă):
  ✗ „De ce procesul e atât de complicat?”
  ✗ „Nu se poate face mai simplu?”
  ✗ „Cum nu ați automatizat asta până acum?”

Deschise (toward state):
  ✓ „Spune-mi cum arată o zi tipică pentru tine.”
  ✓ „Care sunt primele 3 lucruri care îți fură timpul?”
  ✓ „Dacă ai avea un buton magic care rezolvă o singură
     problemă, ce ar fi?”
  ✓ „Ce am uitat să te întreb și ar trebui să știu?”

Signs the interview has closed

• Short answers, „yes/no/depends”.
• Looks at laptop / phone / past you.
• Cross-checks with a colleague, „right Ana?”.
• Ends the meeting early.