03/04/2026
Dear Junior BA,
You think requirements elicitation is about asking good questions. I know you do. I thought the same thing when I started. I walked into my first workshop with a polished template, color-coded agenda, and the quiet confidence of someone who believed clarity would naturally emerge if I just facilitated properly. It didn’t. What actually happened was confusion wrapped in confidence, agreement without understanding, and a room full of people who thought they were aligned but weren’t. So let me tell you what elicitation really is, before the profession teaches you the hard way.
Elicitation is not about questions. You will prepare twenty of them. Five will matter. And the one that truly changes the direction of the project won’t be on your list. It will be the question that forms in your mind when someone says, “We’ll figure that out later,” and you feel something tighten in your chest. That tightening is your instinct recognizing risk. Pay attention to it. The most important questions are rarely technical. They expose ownership, fear, politics, or uncertainty. When you ask, “Who makes the final decision?” and the room goes quiet, that silence is not awkwardness. It is information.
When someone tells you, “It’s simple,” do not relax. “Simple” usually means the edge cases haven’t been explored, the integrations haven’t been considered, and the consequences haven’t been mapped. Smile politely and ask, “What happens if this fails?” Watch how quickly the simplicity dissolves. Complexity isn’t your enemy; hidden complexity is. Your job is not to make the conversation comfortable. It is to make it clear.
You will learn that the room is never what it seems. The loudest voice is not always the most powerful one. The quiet stakeholder in the corner who barely speaks may be the one who can stop everything with a single comment after the meeting. Learn to notice who nods but doesn’t contribute. Learn to notice who avoids eye contact when ownership is mentioned. Elicitation is not just extracting information; it is reading dynamics. You are mapping influence whether you realize it or not.
There will be moments when everyone agrees too quickly. Heads nod. “Looks good.” “Makes sense.” “Let’s move on.” This is not victory. Real alignment creates friction. It invites clarification. If a complex topic passes with no resistance, slow it down. Say, “Before we move forward, does anyone see this differently?” The tension that follows is not failure. It is progress. Friction is clarity being born.
You will get tired. Not from the meetings themselves, but from the invisible weight of awareness. You will sense misalignment before others do. You will see risk forming in vague statements. Sometimes you will raise that risk and nothing will happen. Weeks later, when the issue explodes, you will remember the moment you tried to prevent it. This is the burden of awareness. Do not let it make you cynical. Let it make you sharper. Surface risks clearly, document them calmly, and understand that influence does not mean control.
Stop trying to be liked in workshops. You can be respectful. You can be calm. But you cannot be afraid of discomfort. The day you avoid the hard question because you don’t want to disrupt the mood is the day rework quietly enters the project. Requirements do not change because stakeholders are chaotic. They change because understanding evolves. People speak from partial perspectives. Your job is to expand the perspective. Sometimes that means asking the same question three different ways until the real answer surfaces.
Over time, you will talk less. You will prepare fewer questions. But the ones you ask will land harder. You will notice patterns. You will sense instability early. You will intervene with precision instead of volume. That is when you move from recorder to stabilizer. That is when elicitation stops feeling like interrogation and starts feeling like orchestration.
If you want to accelerate this learning instead of earning every scar the slow way, spend time studying how experienced analysts think, not just what they document. I share the political, psychological, and real-world side of requirements elicitation on the Mad BA YouTube channel. It’s not polished theory. It’s what actually happens in messy rooms with competing agendas and shifting scope. Watch a few episodes before your next workshop. Then walk in differently.
You are going to make mistakes. You are going to miss things. You are going to leave meetings replaying conversations in your head. That’s part of becoming good at this. Just remember that elicitation isn’t about filling documents. It’s about surfacing truth before it becomes expensive. Protect clarity. Respect tension. Ask the question that makes the room pause. That pause is where your value lives.
Stay sharp.
— A Slightly Battle-Hardened BA 😈
