Elicitation and Collaboration: Asking the Right Questions to Build the Right Solution

Elicitation and Collaboration: Asking the Right Questions to Build the Right Solution Most failed projects don’t fail because of bad code. They fail because the team built the wrong thing. Somewhere along the way, a need was misunderstood, a stakeholder was never consulted or an assumption went unchallenged. That’s why elicitation and collaboration are among the most important skills any analyst, product person or project lead can develop. What Is Elicitation? Elicitation means drawing out information about needs, expectations and constraints from the people involved in or affected by a change. The word is deliberate. You don’t simply “collect” requirements, because they rarely arrive ready to use. Stakeholders often describe symptoms rather than causes, ask for solutions instead of explaining problems, or leave out details they think are obvious. Good elicitation brings the real need to the surface. The BABOK View The IIBA’s Business Analysis Body of Knowledge (BABOK) treats Elicitation and Collaboration as a full knowledge area made up of five tasks: Prepare for Elicitation: clarify the purpose, choose stakeholders and techniques, and gather supporting materials. Conduct Elicitation: run the actual sessions and record what you learn. Confirm Elicitation Results: check the information for accuracy, gaps and contradictions. Communicate Business Analysis Information: share findings in a format that suits each audience. Manage Stakeholder Collaboration: keep people engaged, informed and committed throughout the work. Elicitation isn’t a single phase at the start of a project. It runs continuously as understanding deepens. Common Techniques No single technique works everywhere. Skilled practitioners mix and match: Interviews: one-on-one conversations that give depth and let people speak freely. Workshops: structured group sessions that build consensus quickly. Observation (job shadowing): watching people work to see steps they’d never think to mention. Surveys and questionnaires: useful for reaching large or spread-out groups. Document analysis: reviewing policies, manuals and existing system specs. Prototyping: sketches, wireframes or clickable mockups that get concrete reactions. Focus groups: moderated discussions to test ideas with representative users. The best choice depends on who you’re talking to, what you need to learn and how much time you have. Tips for Effective Elicitation Prepare thoroughly. Know the goal of each session, read up on the topic beforehand and bring open-ended questions. Preparation shows respect for stakeholders’ time. Listen actively. Talk less and listen more. Asking “why?” a few times helps you get past a requested feature to the underlying business need. Watch for what isn’t said. Hesitation, vague answers and quick topic changes often point to hidden concerns, politics or risks. Confirm early and often. Summarise what you heard in writing, or sketch a quick process diagram, and ask stakeholders to validate it. A misunderstanding fixed in week one costs far less than one found during testing. Common Challenges to Watch For Even experienced practitioners run into obstacles: Busy stakeholders may skip sessions or send a junior colleague who lacks the full picture. Subject-matter experts sometimes find it hard to explain tasks they do on autopilot. Some people hold back concerns because they fear blame or think the change will hurt their job. Requirements can shift halfway through a project as priorities change. The answer is patience and flexibility. Book short, focused sessions, and use observation when explanations fall short. Create a safe space for honest feedback, and keep a change log so everyone can see what moved and why. Collaboration: The Other Half Elicitation gets information, and collaboration keeps it flowing. Strong collaboration means: Building trust: stakeholders share more honestly with someone who has listened to them before. Handling conflict constructively: when departments want opposing things, bring data, facilitate open discussion and escalate to the right decision-maker when needed. Keeping communication visible: shared backlogs, regular demos and short status updates stop people feeling left out. Closing the loop: let stakeholders know how their input shaped the outcome, so they stay engaged next time. Final Thoughts Elicitation and collaboration aren’t soft extras. They are the foundation of every successful solution. Teams that invest in asking better questions, listening carefully and working as genuine partners with their stakeholders build products people actually want to use. They also spend far less time on rework. Start with your next meeting: prepare well, listen closely and confirm what you hear.