6.3 Elicitation Techniques: Interviews, Surveys, Prototyping & Document Analysis

6.3 Elicitation Techniques: Interviews, Surveys, Prototyping & Document Analysis

Quick Answer: Elicitation is the proactive discovery of underlying business needs, not passive requirements gathering. The four primary techniques are: (1) 1-on-1 Interviews (best for deep dive into complex domain logic, executive alignment, and sensitive workflows), (2) Surveys / Questionnaires (best for collecting quantitative data from large, distributed user populations), (3) Interactive Prototyping (best for visual learners to validate UI and screen flows rapidly in sandbox mockups), and (4) Document Analysis (best for establishing baseline business rules and data structures from existing SOPs and legacy spreadsheets). BAs must actively prevent cognitive traps like confirmation bias and leading questions.

In business analysis, the word "elicitation" is used deliberately instead of "gathering." Gathering implies that requirements are fully formed, neatly packaged artifacts sitting on a shelf waiting to be picked up. In reality, business requirements are often latent, poorly understood, contradictory, or buried beneath layers of corporate habit and legacy workarounds. A Salesforce Certified Business Analyst acts as an investigator—employing structured elicitation techniques to draw out tacit knowledge, challenge assumptions, and unearth the true operational needs of the organization.

---

The Four Core Elicitation Techniques in Salesforce Engagements

No single elicitation technique is sufficient for an enterprise Salesforce implementation. Successful BAs select and combine techniques based on stakeholder seniority, organizational culture, geographic distribution, and the complexity of the domain.

                                ┌──────────────────────────────────────┐
                                │  Document Analysis                   │
                                │  (Review SOPs, Spreadsheets & Manuals)│
                                └──────────────────┬───────────────────┘
                                                   │  Builds Domain Baseline
                                                   ▼
                                ┌──────────────────────────────────────┐
                                │  Broad Quantitative Surveys          │
                                │  (Engage 500+ Distributed Users)     │
                                └──────────────────┬───────────────────┘
                                                   │  Identifies Macro Trends
                                                   ▼
                                ┌──────────────────────────────────────┐
                                │  Targeted 1-on-1 Interviews          │
                                │  (Executives, SMEs & Process Leads)  │
                                └──────────────────┬───────────────────┘
                                                   │  Uncovers Root Causes
                                                   ▼
                                ┌──────────────────────────────────────┐
                                │  Interactive Sandbox Prototyping     │
                                │  (Lightning App Builder Mockups)     │
                                └──────────────────────────────────────┘
                                   Validates & Confirms Requirements

1. One-on-One Interviews

One-on-one interviews represent the most common and versatile qualitative elicitation technique. They involve direct, focused dialogue between the BA and a single stakeholder or Subject Matter Expert (SME).

• When to Use:
  • Executive discovery and strategic goal alignment.
  • Exploring politically sensitive topics, organizational friction, or departmental conflicts that stakeholders will not discuss in group workshops.
  • Eliciting highly complex, specialized business rules from senior technical or domain specialists (e.g., enterprise pricing formulas, compliance algorithms).
• Interview Modalities:
  • Structured Interviews: The BA follows a rigid, pre-determined script of questions. Useful for standardized benchmarking across multiple regional managers.
  • Semi-Structured Interviews: The BA utilizes a question guide covering core themes but allows the conversation to diverge naturally to explore unexpected insights. This is the gold standard for Salesforce discovery.
  • Unstructured Interviews: Informal, open-ended discussions used in early exploratory discovery.
• Strengths: Builds personal rapport and trust; allows immediate probing into nuances; creates psychological safety for candid feedback.
• Limitations: Time-consuming to schedule and conduct; requires extensive note-taking and synthesis; represents the perspective of only one individual.

2. Surveys and Questionnaires

Surveys utilize structured sets of written questions distributed electronically to collect feedback from a broad audience.

• When to Use:
  • Gathering quantitative data from large, geographically distributed user bases (e.g., 2,500 retail sales associates across 50 countries).
  • Measuring baseline user sentiment, frequency of operational pain points, or ranking feature priorities.
  • Benchmarking current system satisfaction prior to a Salesforce rollout to calculate post-implementation adoption gains.
• Design Best Practices:
  • Utilize closed-ended questions (Likert scales: Strongly Agree to Strongly Disagree, multiple-choice, numerical rankings) for quantifiable statistical analysis.
  • Include limited, optional open-ended text fields for qualitative commentary.
  • Keep completion time under 10 minutes to maximize completion rates.
  • Pilot test the survey with 3 to 5 representative users before distributing globally to eliminate confusing phrasing.
• Strengths: Highly cost-effective; rapid data collection across global time zones; generates statistically defensible metrics.
• Limitations: Lacks context; cannot ask clarifying follow-up questions when a user submits an unexpected response; prone to low response rates and self-selection bias.

3. Interactive Prototyping & Wireframing

Prototyping involves creating visual, interactive mockups of future-state Salesforce user interfaces and workflows to help stakeholders conceptualize how the solution will function.

• When to Use:
  • Working with visual and kinesthetic stakeholders who struggle to comprehend abstract written requirement specifications ("I don't know what I want until I see it").
  • Validating complex, multi-step screen flows, guided intake wizards, or Lightning Service Console layouts.
  • Reconciling conflicting opinions between departments regarding page design, component placement, and field sequencing.
• Salesforce Low-Code Prototyping Tools:
  • Lightning App Builder: Rapidly configuring Lightning Pages using Dynamic Forms, conditional component visibility rules, and standard tabs in a sandbox.
  • Screen Flows: Creating interactive click-through wizards with temporary input fields to simulate complex multi-step intake processes.
  • Experience Builder: Mocking up branded customer and partner portal pages.
• Strengths: Bridges the communication gap between business and IT; surfaces unarticulated requirements early; creates immediate stakeholder excitement.
• Limitations & Guardrails: Stakeholders may mistake a polished sandbox prototype for fully functional production software, underestimating the remaining back-end integration, data architecture, and testing effort. The BA must explicitly set expectations: "This is a visual prototype to validate workflow sequence, not working software."

4. Document Analysis

Document analysis involves researching and reviewing existing organizational assets, system specifications, standard operating procedures (SOPs), and regulatory guidelines to elicit requirements.

• When to Use:
  • Project initiation phase before scheduling discovery workshops or interviews.
  • Highly regulated environments (Financial Services, Life Sciences, Healthcare) governed by statutory compliance rules.
  • Understanding legacy systems scheduled for decommissioning when original system creators are no longer with the organization.
• Artifacts to Inspect:
  • Standard Operating Procedures (SOPs), employee onboarding manuals, and desk-level training guides.
  • Legacy Excel tracking sheets containing complex manual formulas, conditional formatting, and embedded VBA macros.
  • Existing software contract SLAs, data dictionaries, database schemas, and interface control documents.
  • Historical help desk ticket logs and customer complaint records to identify recurring process breakdowns.
• Strengths: Extremely cost-effective; respects stakeholder time by avoiding basic questions; uncovers formal business rules and compliance constraints.
• Limitations: Existing documentation is frequently obsolete, out of date, or describes an idealized theoretical process that users routinely bypass in daily practice.

---

Multi-Technique Comparison Matrix

---

Cognitive Traps and Elicitation Pitfalls

During requirements elicitation, even experienced analysts can fall victim to human cognitive biases. The Salesforce Certified Business Analyst exam tests your ability to recognize and counteract these psychological traps.

1. Confirmation Bias

• The Trap: The BA enters discovery with a preconceived architectural solution in mind (e.g., "We should definitely use Omni-Channel routing for this call center") and unconsciously asks questions or interprets responses exclusively to validate that hypothesis, ignoring conflicting evidence.
• Countermeasure: Practice active intellectual humility. Formulate deliberate "disconfirming questions" (e.g., "What are the scenarios where routing a case automatically would fail or disrupt customer relationships?").

2. Leading Questions

• The Trap: Framing questions in a manner that nudges or pressures the stakeholder toward a specific answer.
  • Leading Example: "Wouldn't it be much faster and easier if we replaced this 15-field page with a 3-step guided flow?"
• Countermeasure: Use neutral, open-ended inquiry starting with What, How, or Walk me through.
  • Neutral Example: "Walk me through how you currently complete this intake, and tell me where you experience friction or delays."

3. Passive Agreement and Groupthink

• The Trap: In group workshops, junior team members often remain silent or passively agree with dominant managers or outspoken colleagues, masking critical operational edge cases.
• Countermeasure: Utilize anonymous digital polling tools, post-workshop 1-on-1 validation interviews, or silent sticky-note ideation exercises before opening floor discussions.

4. Capturing Stated Wants vs. True Operational Needs

• The Trap: Taking stakeholder requests at face value. Stakeholders routinely ask for features they want (often duplicating what they had in legacy tools) rather than what they need to achieve their business goals.
• Countermeasure: Apply the 5 Whys and root-cause analysis. Ask: "If we provide this capability, what business decision will you make with that information? What is the operational consequence if this data is not captured?"

---

Realistic Scenario: Multi-Method Elicitation for a Global Call Center

The Challenge

Global Logistics Corp is modernizing its customer support operations across 1,800 agents in North America, Europe, and Asia. Support costs are escalating, and first-contact resolution has dropped to 61%.

The BA's Multi-Method Strategy

1. Phase 1: Document Analysis (Preparation): The BA reviews the past 6 months of customer escalation tickets, standard operating procedures, and the legacy agent training manual. The BA discovers that 42% of tickets involve simple shipment tracking lookups and that agents must reference three separate external systems to find a parcel's location.
2. Phase 2: Global User Survey (Quantitative Breadth): The BA designs a 10-minute Likert-scale survey distributed to all 1,800 agents. Over 1,200 agents respond. Results reveal that 78% of agents consider swivel-chairing between external databases their primary daily frustration, spending an average of 4.5 minutes per call simply copying tracking numbers.
3. Phase 3: 1-on-1 SME Interviews (Deep Qualitative Insight): Armed with survey data, the BA conducts 1-on-1 semi-structured interviews with 8 regional team leads and the VP of Customer Experience. The BA learns that European agents face strict statutory privacy rules regarding customer data visibility that North American teams do not share.
4. Phase 4: Interactive Sandbox Prototyping (Validation): The BA builds a Lightning Service Console prototype in a sandbox using Lightning App Builder. The prototype features a unified 360-degree customer view, a Screen Flow for one-click tracking lookups, and dynamic component visibility to hide sensitive fields for European profiles. The BA conducts interactive walkthrough sessions with agent focus groups, refining the layout based on direct user feedback before final sign-off.